Privacy Policy

Account information: name, work email, company, role, and the identifiers used to sign you in.

Billing information: plan, add-ons, subscription status, and invoice records. Card details are handled by our payment processor and are not stored by us.

Service usage: product interactions, device information, IP address, time stamps, diagnostics, and crash data.

Content you create: campaigns and sequences, message and invitation copy, templates, event details, schedules, and settings.

Contact data you provide: the records you import or create for the people you want to reach, such as name, email address, phone number, company, role, website, social identifiers, tags, and any custom fields you add.

Communication records: requests you send to support, feedback, and survey responses.

Cookies and similar technologies: to maintain sessions, remember preferences, and measure product performance.

Email and calendar: When you connect Google Workspace, you do so with your organization's own service account and the domain-wide delegation you authorize in your admin console. We never receive your Google password. That authorization lets us send email from the mailboxes you nominate, create and update calendar events and invitations, and read the mailbox activity needed to run your campaigns. We process the messages needed to match activity to your campaigns, and we do not retain unrelated mail.

Message content: We process the messages sent from your connected mailboxes and the responses they receive, including reply text, delivery and bounce notices, and message metadata such as sender, recipient, subject, and thread identifiers. This is what lets the product detect replies and bounces, stop a sequence when someone answers, honor unsubscribe requests, and show your conversations in the shared inbox.

Calendar and RSVP data: The events you create through the Services, their attendee lists, and the RSVP responses returned by the calendar provider.

Messaging and social accounts: If you connect a LinkedIn, WhatsApp, or Telegram account, we process the identifiers and profile details of that connected account, the messages, connection requests, and profile actions sent through it, the replies received, and the social identity of the recipient used to deliver a message, such as a profile identifier, username, or phone number.

Webinar platforms: If you connect a webinar platform such as Zoom or WebinarGeek, we process the webinar and session details, registrant records, and attendance information needed for reporting and for attributing attendance to a campaign. Registering a contact with a provider on their behalf happens only where you turn that option on, and the provider may then email that person directly.

Credentials for connected platforms: Service account keys, provider client secrets, and similar credentials you upload are encrypted before they are stored and are used only to operate the connection you created.

Outbound webhooks: If you configure a webhook, we send the events you select, and the associated recipient and campaign data, to the destination URL you provide. You choose that destination and you are responsible for how the receiving system handles the data.

API keys and assistant tools: Account-level API keys, and the tools that use them, including our MCP server for AI assistants, allow you or a tool you authorize to read and write the same data you can access in the product. Anyone holding a valid key can act as your account, so treat keys as credentials, share them carefully, and revoke a key you no longer use.

Tracking links and opt-outs: Where you enable link tracking or an unsubscribe link, we record that a recipient clicked or opted out so that reporting and suppression work. We do not use tracking pixels to record message opens.

Some optional features use AI models to draft or personalize message content and to classify the intent of a reply. You can supply your own provider API key, in which case the request is sent to the provider you selected under your own account. If you have not configured a provider, we send the request to our default provider on your behalf. The content sent can include the message or reply text and the campaign context needed to produce the result.

Where you turn on website personalization, the public web page of a recipient or their company domain is fetched through a third-party page-to-markdown conversion service, and the text it returns is used as context for the generated message. That means public page content leaves our systems to reach that service. Website personalization is off unless you enable it on a step or campaign.

We record the model used, token counts, and the request and response content of AI calls so that you can audit usage and cost. API keys you store for a provider are encrypted. AI providers process the content we send under their own terms, so review those terms before enabling these features. We do not use your Customer Content to train models.

We retain information for as long as your account is active and for as long as needed for the purposes described in this Policy, including reporting, security, resolving disputes, and meeting legal and accounting obligations.

You can delete contacts, campaigns, messages, and templates in the product, and you can disconnect any connected account at any time. Disconnecting revokes our ability to act on that account going forward. You can also revoke access directly with the provider, for example in your Google Workspace admin console.

When your account is closed, we delete or anonymize the personal data we hold for you within a reasonable period, except where we must keep records to comply with law, resolve a dispute, or enforce our agreements. Suppression and unsubscribe records are kept so that an opt-out continues to be honored.

You may request export or deletion as described in Section 12.

Email: [email protected]