How Lifty handles data.

Who this covers

This policy applies to people who set up a Lifty workspace (founders and their teams), to the members of Slack workspaces where the Lifty app is installed, and to the prospects Lifty researches and contacts on a customer's behalf. Where we act on a customer's instructions to reach their prospects, the customer decides who is contacted and we process that data to deliver the service.

What data we collect

Your account and workspace

• Name, email address and sign-in credentials for your Lifty account.
• Workspace configuration: your ideal customer profile, targeting filters, tone of voice, prompt instructions and the answers you give during onboarding.
• Review decisions: which leads you approve or reject, replies you send or edit, and the reasons you give, which we use to sharpen targeting.

Prospect data

• Business contact information about people and companies that match your profile: name, job title, company, work email, LinkedIn profile URL, company size, location and similar company details.
• Research notes Lifty produces about a company or person from public sources and from the data providers we use to find leads.
• Outreach activity: messages sent from your accounts, replies received, and meetings booked.

Connected services

• Slack. When you install the Lifty app we store the Slack workspace ID, the bot token Slack issues for that workspace, and the IDs of the channels you add. We store the interactions you make on Lifty messages (button clicks such as Approve, Not a fit, Send and Edit, and text you submit in Lifty's edit dialogs). We also receive Slack user IDs, channel metadata and the message context included with these interactions. When a conversation feature is enabled, we process the relevant messages and thread context available to the app to respond to your request. Access depends on the permissions granted and the channels the app has joined.
• HubSpot. If you connect HubSpot we store the OAuth grant and sync contacts, companies, notes and activities that Lifty creates, plus the existing records needed to avoid duplicates. Sync writes follow your workspace’s configured field mappings.
• Email and LinkedIn. Lifty connects sending mailboxes and LinkedIn accounts through Unipile. You sign in on a connection page hosted by Unipile, and Unipile keeps the password or tokens for that account. Lifty stores the Unipile account reference, the verified address or profile, the messages Lifty sends and the replies it receives from your prospects. See Unipile's privacy policy for its handling of connected accounts.

AI apps (MCP connectors)

You can use Lifty from an AI app, such as Claude, ChatGPT, or a coding agent, by adding Lifty as a custom MCP connector and signing in. The connector acts with your permissions to do what you ask in your workspace. Lifty receives the information included in those requests and sends the results back to the AI app. Depending on your request, this can include onboarding answers, saved workspace configuration, prospect details and research, draft messages, outreach activity, and connection or job status.

The company that provides your AI app (for example, Anthropic for Claude or OpenAI for ChatGPT) handles the information Lifty returns under its own terms and your account settings. Information you ask Lifty to save follows the retention rules below. Removing the connector from your AI app does not delete Lifty records or pause hosted outreach. Contact support to request account access revocation or deletion.

Google email connection

When you connect a Google mailbox for sending, Google asks you to allow Lifty to identify your Google account, read your email (gmail.readonly) and send email on your behalf (gmail.send). Unipile completes that sign-in with Lifty's Google app and keeps the resulting access. Lifty does not receive your Google password or tokens for this connection.

Lifty uses this access to:

• Confirm the address you connected and check that the connection is working.
• Send the outreach messages, follow-ups and replies your workspace is set up to send from that mailbox.
• Detect replies and bounces from prospects Lifty has emailed. Unipile notifies Lifty of new incoming mail. Lifty keeps only messages from those prospects and discards all other mail without storing it.

Stored prospect replies are shown to you for review, used to draft suggested responses, and logged to your CRM if you connect one. To draft a response, the reply text is sent to our AI provider. Lifty does not change, label, move or delete email in your mailbox.

If you connected your Google mailbox before we narrowed these permissions, it may still have the broader access you granted then. To limit it to the permissions above, revoke Lifty's access in your Google Account and connect again.

Microsoft email connection

When you connect a Microsoft 365 or Outlook mailbox, Microsoft asks you to let Lifty identify your account (User.Read), read and write mail (Mail.ReadWrite), send mail (Mail.Send), and retain access while you are away (offline_access). Unipile completes sign-in and keeps the resulting access. Lifty does not receive your Microsoft password or tokens.

Lifty uses this connection to verify your primary mailbox, send the outreach messages your workspace is set up to send, and detect prospect replies and bounces as described above. Microsoft sending through Unipile creates a draft before sending it, which requires mail write access. This connection does not authorize Mailivery warmup.

Google mailbox warmup

If you choose Google sign-in to warm up a mailbox, Lifty requests full Gmail access (https://mail.google.com/) for Mailivery's IMAP/SMTP connection. That permission allows reading, sending and deleting email across the mailbox, including messages unrelated to warmup. Lifty checks that Google returned the mailbox address you selected, then passes the Google access and refresh tokens once to Mailivery over HTTPS. Lifty does not store those tokens or download your mailbox contents during this setup. Mailivery keeps the connection and uses it to send, receive and reply to warmup messages. See Mailivery's privacy policy for its handling of mailbox access.

Lifty receives the mailbox address, connection and campaign status, and warmup metrics from Mailivery.

Microsoft mailbox warmup

To warm up a Microsoft 365 or Outlook mailbox, you authorize Mailivery separately from your Unipile outreach connection. Microsoft grants Mailivery access directly through Microsoft Graph. The permissions shown on Microsoft's consent screen let Mailivery read, write and send email and manage your mailbox for warmup. Lifty does not receive your Microsoft password, access token or refresh token for this connection.

Before starting warmup, Lifty verifies that the Mailivery campaign belongs to your workspace and uses the mailbox address you selected. The initial inbox placement test is part of this mailbox setup. Lifty receives connection and campaign status, warmup metrics and placement test results from Mailivery. It does not download your mailbox contents through this warmup connection.

Lifty retains a private, short-lived authorization link so you can resume the same setup attempt if sign-in is interrupted. See Mailivery's privacy policy for its handling of mailbox access.

Google user data

Lifty does not use Google user data for advertising, lead research or training general AI models, and does not sell it. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Usage and technical data

• Product analytics about how the dashboard and CLI are used, error reports, and server logs with IP address, browser and timestamps.

How we use it

• To find, research and qualify leads that match your profile.
• To draft and send outreach from your accounts, and to draft replies for you to approve.
• To detect prospect replies and bounces in a connected mailbox.
• To post reviews, replies and meeting updates to the Slack channels you add.
• To keep your CRM in sync.
• To warm up a connected mailbox before outreach begins.
• To operate, secure, debug and improve the service, and to answer support requests.

Lifty uses large language models to research leads and draft messages. Relevant prospect, workspace and message context may be sent to AI providers to generate those outputs. Feedback may be used to update your workspace configuration or instructions. We do not sell personal data.

Who we share it with

We share data only with the services needed to run Lifty: our hosting and database providers, the AI provider that generates research and drafts, the lead data providers we search, Unipile for email and LinkedIn connections, our other email and LinkedIn sending infrastructure, Mailivery for mailbox warmup, Slack and HubSpot (when connected), and our analytics and error-tracking tools. The providers receive the data needed for the connected feature and process it under their applicable service terms. Processing may occur outside your country. Contact us for information about the providers used for your workspace.

How long we keep it

• Workspace, prospect and outreach records remain stored while your workspace is active. After you cancel, you can ask us to export those records for 30 days. After that window we delete them, except the limited records described below. Contact us to request an earlier deletion; we verify the request and confirm its scope and completion.
• Removing Lifty from Slack revokes the app’s access in Slack. It does not by itself delete historical Lifty records. Disconnecting a service stops its use by Lifty; contact support to request removal of stored connection data and associated records.
• Lifty does not retain the Google access or refresh tokens passed to Mailivery for warmup. Mailivery states that it deletes email credentials when the mailbox is disconnected. Contact us to stop warmup and request deletion of the connection and Lifty's stored status and metrics.
• You can revoke Lifty's Google access in your Google Account at any time. Unipile and Mailivery use the same Lifty Google app, so revoking it ends both the email connection and warmup for that mailbox.
• Logs, error reports and backups follow the retention settings of the hosting and monitoring services. We do not currently apply a single automatic expiry across these systems. Ask us about the retention settings and deletion scope for your workspace.
• We may retain limited records needed to honor opt-outs, resolve disputes, maintain security or meet legal obligations. Data already sent to Slack, your CRM or message recipients is also subject to those services’ and recipients’ retention practices.

Your rights and how to make a request

You can ask us to access, correct, export or delete your data, or to stop contacting you, at any time. Prospects who received an outreach message can request deletion and ask us to stop further contact. To make a request, email support@liftygtm.com from the address you want us to act on, or reply to any message sent through Lifty. We aim to acknowledge requests within 2 business days and will explain any verification needed, the scope of the request and its expected completion time.

Security

We use HTTPS for data in transit, access controls that keep each workspace's data separate, and restricted storage for integration credentials. Access is limited to the people and systems needed to operate and support the service. If we learn of a breach of a workspace's data, we will tell that workspace's owner without undue delay.

Changes to this policy

We will post updates on this page and change the date at the top. Material changes will be identified in the updated policy.

Contact

Lifty Corp · support@liftygtm.com · see also our support page.