Legal

Privacy Policy

This policy describes, in plain language, how Lievia handles information — including data accessed through Google accounts you connect.

Information we collect

Lievia handles three distinct categories of information: (1) information you give us directly as a customer, such as your name, business name, industry, contact email, chosen reply style, and billing details handled by our payment processor; (2) information submitted by your leads through the forms or systems you connect to Lievia; and (3) information accessed through Google accounts you choose to connect, described in detail in “Google User Data” below. We also collect basic usage information about how our website is used.

How we use information

Customer information is used to operate your Lievia account, configure your automated replies, notify you about leads, respond to inquiries, and improve the service. Lead information is used to qualify the lead, generate a reply on your behalf, notify you, and record the lead in your own Google spreadsheet. Google account data is used only for the specific integration functions you authorized.

Sharing

We do not sell personal information, and we do not sell Google user data. We share information only with service providers who help us operate Lievia — including our payment processor, our email delivery provider, our automation infrastructure, and the third-party AI provider described below — and only to the extent needed to deliver the functionality you requested.

Data retention

We retain information for as long as needed to provide the service and meet legal obligations, then delete or anonymize it. Lead records written into your Google spreadsheet stay in your own Google Drive and remain under your control.

Your choices

You can request access to, correction of, or deletion of your information, and you can disconnect any Google integration, at any time. Contact us at support@mylievia.com.

Google User Data

When you connect a Google account to Lievia, you authorize Lievia to act on your behalf for specific, limited tasks. Lievia currently requests only these Google permissions: openid and email (basic account identity), https://www.googleapis.com/auth/gmail.send (send-only Gmail access), and https://www.googleapis.com/auth/drive.file (per-file Drive access). No other Google scopes are requested. Below is exactly what Lievia accesses, why, how it is used, whether it is stored, and how to revoke access.

Google account identity (openid, email)

  • Lievia receives the connected Google account's email address and the basic Google account identifier returned by Google during sign-in.
  • This is used only to identify the connected account, show you which account is connected, and associate that Google connection with the correct Lievia customer account.
  • Lievia stores the account email address and Google account identifier. It does not access your Google profile beyond this basic identity information.

Gmail (gmail.send — send only)

  • Lievia requests https://www.googleapis.com/auth/gmail.send, which permits sending email through the connected Google account and nothing else.
  • This permission is used to send automated replies to leads submitted to Lievia and lead notification emails to you as the business owner, sent from your connected account with your configured sender name and signature.
  • Lievia does NOT read, search, download, modify, or delete your Gmail messages, and does NOT monitor your Gmail inbox. It has no permission to do any of those things, and Lievia has no incoming-email or inbox-ingestion functionality.
  • Lievia stores only an encrypted authorization token for the connected account plus that account's email address and Google account identifier. The contents of your mailbox are never retrieved or stored.

Google Drive (drive.file — per-file access)

  • Lievia requests https://www.googleapis.com/auth/drive.file, which grants access only to files created by Lievia or files you explicitly authorize Lievia to open. Lievia does not have unrestricted access to your Google Drive.
  • Lievia uses this access to create and maintain a single spreadsheet named “[Business Name] Leads” in your Google Drive: creating the “Leads” tab, writing and updating the header row, appending lead rows, and reading existing rows to detect duplicate email addresses.
  • Lievia does not access unrelated Drive files, folders, or spreadsheets, and does not request the broad Google Sheets permission.
  • Lievia stores the identifier of that one spreadsheet so it can keep using the same file.

Information written to your Lievia lead spreadsheet

  • Depending on what a lead submits and how your form is configured, a lead row may include the lead's name, email address, phone number or other contact details, company, requested service, budget, timeline, and the message or additional custom form fields they submitted.
  • A row also includes information Lievia produces while processing the lead: a lead qualification score, a priority level, a status, the date and time received, and a consolidated “Additional Details” summary of any custom form fields.
  • Lievia may also generate a short lead summary and a recommended next action, which are used in the qualification and notification steps sent to you.
  • When a lead does not provide a value for a field, Lievia records “Not provided” rather than inventing a value.
  • This information is processed solely to provide Lievia's lead management, qualification, automated response, owner notification, and recordkeeping functionality.

Revoking access

  • You can disconnect a Google integration at any time from the Lievia onboarding or setup screen, which revokes the authorization token with Google and removes Lievia's ability to use that account.
  • You can also revoke access directly from your Google Account permissions page at myaccount.google.com/permissions.
  • Gmail and Drive connections are separate, so revoking one does not affect the other.

Third-party AI processing (OpenAI)

Lievia uses the OpenAI API as its third-party AI provider to evaluate and qualify incoming leads, generate lead scores and priorities, produce short lead summaries and recommended next actions, and draft personalized replies to leads.

  • Information sent to OpenAI for this processing is limited to what is needed to produce the requested output: the lead information submitted to Lievia (including relevant custom form fields), the business information and configuration you provided during setup so the lead can be interpreted, and your selected reply style.
  • Lievia does not send your Google Workspace content to OpenAI beyond the lead and configuration information described above. Gmail message content is never retrieved by Lievia at all, and unrelated Google Drive files are never accessed, so they are never sent to OpenAI.
  • Lievia does NOT transfer raw or derived Google Workspace API user data to OpenAI or any other third-party AI service for the development or training of generalized AI or machine learning models.
  • Data submitted through the OpenAI API is not used to train OpenAI's generalized models by default, subject to the applicable OpenAI API and business data terms and the applicable account configuration.

AI training and secondary use

  • Lievia does not use Google Workspace API user data to train or improve generalized AI or machine learning models.
  • Lievia does not transfer Google Workspace API user data to any third party for generalized AI or machine learning model training.
  • Google Workspace API user data is used only to provide and improve the user-facing features you authorized — sending email through your connected Gmail account and maintaining your Lievia lead spreadsheet — consistent with Google's applicable policies.

Data protection

  • OAuth refresh tokens are encrypted at rest using AES-256-GCM before being stored.
  • Tokens and Google credentials are handled entirely server-side and are never exposed to the browser or to client-side code.
  • Access is limited to the functionality you authorized: sending email through Gmail, and reading and writing the Lievia-created leads spreadsheet.
  • Gmail and Google Drive connections are stored as separate records and may point to different Google accounts.
  • You can disconnect Google integrations at any time, which revokes the authorization with Google.
  • All data in transit is transmitted over HTTPS.
  • Access to server-side connection and token records is restricted to Lievia's server processes; these records are not readable from the public application.
  • Google user data is not sold.
  • Google user data is not used for advertising.
  • Google user data is not transferred to unrelated third parties, other than service providers required to operate Lievia, consistent with this privacy policy.

Google API Services User Data Policy — Limited Use

Lievia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions about this policy or about data Lievia holds can be sent to support@mylievia.com.

← Back home