Privacy policy

WhatsApp Business

For WhatsApp Business messaging, an authorized administrator connects the business account through Meta’s official authorization flow. We process the WhatsApp Business Account (WABA) identifier, connected phone number identifiers and numbers, account information, granted permissions and access credentials. We use them to maintain the connection, manage the authorized messaging functions and receive webhook events. Reusable credentials are stored encrypted on the server.

For conversations, we process the contact’s phone number or identifier and name when provided, message identifiers and content, supported attachments, timestamps and delivery or read status returned by Meta. These data allow authorized workspace users to identify contacts, receive messages, send replies and use approved templates where applicable. If the customer enables an AI agent or workflow, the necessary conversation content and context may be sent to the configured AI provider to perform that function.

Disconnecting the account requests cancellation of its webhook subscription and deletes its reusable credentials from active systems. This does not automatically delete contacts, conversations or attachments already stored in Lippem. The retention, backup, verification and deletion periods described in this policy apply. Deleting copies in Lippem does not delete copies held by Meta or conversation participants. Data deletion instructions

Facebook Messenger

We use the Pages authorized through Facebook Login for Business to let you choose which ones to connect. The current Messenger connection does not query business portfolios or request business_management. The temporary user authorization used for selection is not stored as a reusable user credential. Portfolio metadata retained from an earlier connection follows the retention and deletion rules in this policy.

If you enable Messenger utility templates, we exchange template definitions, language, examples, review status and personalized parameter values with Meta to create templates, copy templates from Meta’s library and send transactional updates. Sent template content and identifiers are stored in conversation history. Templates are associated with the sending Page; Meta remains the authoritative source for their current approval status.

Connecting Messenger is optional and requires an authorized workspace administrator to sign in through Facebook Login for Business and select Facebook Pages they manage. We receive the authorized Page identifiers, names, category, available follower count and Page link, granted permissions and access credentials. We use these to list and connect Pages, display their connection status and subscribe to messaging webhooks. Reusable Page credentials are stored encrypted on the server and are not shown to contacts.

For people who message a connected Page, we process the Page-scoped identifier (PSID), first and last name and profile picture when Meta provides them, message identifiers and content, attachments, quick replies, postback selections, timestamps and delivery or read events. The PSID identifies a person within that Page; it is not a phone number. Messenger does not automatically provide a contact’s phone number or email. We save available names and picture links to identify contacts in the inbox, preserve manual edits and periodically refresh automatically obtained profile information.

We exchange the necessary identifiers, messages, media and credentials with Meta to receive messages and send authorized replies. Authorized workspace users can access conversations according to their roles. If the customer enables an AI agent or workflow for Messenger, the necessary conversation content and context may be sent to the configured AI provider, such as OpenAI, Anthropic or Google, to perform that function. Connecting a Page alone does not send all conversations to an AI model. We do not sell Messenger contact or conversation data.

Messenger data follows the retention, backup and verified-request periods in this policy. Disconnecting a Page deletes its reusable credentials from active systems and requests removal of the webhook subscription; it does not automatically erase stored contacts, profile information, conversations or files. You can also revoke Lippem’s authorization in Meta settings. A contact can request access, correction or deletion without having a Lippem account. Deletion in Lippem does not delete copies held by Meta or other participants.

How to request deletion of Messenger data

Google Calendar

Connecting Google Calendar is optional and authorized through Google OAuth. We access your account identifier and verified email; your calendar list and its permissions, names, and time zones; availability intervals; and event data returned by Google, such as identifiers, titles, descriptions, dates and times, locations, organizers, attendees and their responses, recurrence details, and video meeting links. We store encrypted OAuth access and refresh credentials, agenda settings, copies of synchronized events, and appointment records linked to WhatsApp contacts or conversations where applicable.

We use Google Calendar data to display calendars and events, check availability, and create, update, reschedule, or delete events following user actions or authorized automations. We may add attendees and request Google Meet links; Google may send invitations and updates according to the action and notification option selected. This connection does not grant access to Gmail, Drive, or Sheets. Authorized workspace users may access integration information according to their Lippem permissions.

We transfer the data needed to perform these actions to Google, including contact details that a user adds to an appointment. Infrastructure providers process data needed to host and operate the integration. If the customer enables an AI agent's scheduling tools, availability and appointment lookup or management results become part of the context sent to the AI provider used for that conversation. This supports replies and the requested booking; it does not automatically send all calendars to the model. Information shared with attendees or contacts depends on the invitations and replies authorized by the user or their automations.

Lippem's use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including its Limited Use requirements. We limit use to requested scheduling and assistance features. We do not sell this data or use it for advertising, credit assessment, or training general-purpose AI models. Transfers are limited to authorized features, security needs, legal compliance, or a corporate transaction with the prior consent required by Google. We do not allow our staff or providers to read this data except with the user's affirmative consent for specific data, for security, to comply with law, or for aggregated uses permitted by Google.

Disconnecting Google in Lippem disables the connection and deletes reusable credentials from our active systems. It does not automatically revoke permission in your Google Account: you can also remove access through your Google Account's third-party connections. Disconnecting or revoking permission does not automatically delete synchronized copies, settings, or appointment history stored in Lippem. We retain these for workspace features and history while needed or until a deletion request is fulfilled, subject to the exceptions and time limits in section 6.

To request deletion of Google data stored in Lippem, email support@lippem.com with the Google account, workspace, and data you want deleted. We verify your identity and authority; do not send passwords or tokens. See our Google data deletion instructions. Deleting copies in Lippem does not delete original Google Calendar events. Deleting an event in Google is a separate action that may affect attendees.