Your data: what is read, stored and deleted
What OutboundManager reads from your tools, what it keeps, where it goes, and how to delete it.
For: Admins, legal and data protection contacts
This is a plain-language summary. The Privacy policy and the Data Processing Addendum are the documents that apply.
What is read from your tools
| Data | Details |
|---|---|
| Senders | Mailboxes, LinkedIn accounts, CRM owners and dialer seats, with their labels and email addresses |
| Campaigns | Names, channel, status and dates |
| Contacts | Name, email address, LinkedIn URL, company, company domain, job title and CRM ids. Phone numbers where a dialer or an enrichment run provides them |
| Activity | Sends, bounces, replies with a stored excerpt of the text, LinkedIn invites, accepts and messages, meetings and calls. Call recordings are not downloaded; only a link is kept where the dialer provides one |
| Deals | Name, pipeline, stage, amount, currency, owner, dates and company domain |
Opens and clicks are not read. Only the data needed for the reports is requested from each tool.
What is created inside OutboundManager
- Reps, targets, sender mappings, campaign owners and reply assignments.
- Replies your team sends from the reply queue.
- Enrichment lists your team uploads, and the emails and phone numbers found.
- Ask conversations (private to the person who asked) and stored coaching and diagnosis notes.
- Report settings: recipient emails and an optional Slack webhook.
Who is responsible for what
The data your workspace syncs and enriches belongs to you. We process it only to provide the service, on your instructions: you are the controller and we are the processor. We do not sell it, do not use it to contact your prospects, and do not use it to train AI models.
Where data goes
- It is stored in the United States, with the providers listed on Sub-processors.
- An enrichment run sends the names, companies, domains and LinkedIn URLs in that list to the providers your team selected, using your own keys.
- An AI request sends the fields listed in AI features to Anthropic.
- The weekly report goes to the email recipients and Slack channel you configured.
The tools you connect are not our sub-processors. You chose them and hold the account with them.
Deleting data
| Action | What is deleted |
|---|---|
| Remove a connection | Its key, and the senders, campaigns, activity, deals and sync history synced through it. Contacts and enrichment results stay. |
| Remove an enrichment provider key | The key. Past results are kept. |
| Delete an Ask conversation | That conversation. |
| Remove a member | Their access to the workspace. Their login still exists, because they may belong to other workspaces. |
| Delete the workspace | Everything in it, permanently: connections and keys, synced data, contacts, replies, enrichment runs and results, AI history and notes, members and invites. |
To delete a login entirely, or to have specific contact records removed, write to the address in the Privacy policy.
How long data is kept
- Workspace data is kept while the workspace exists.
- A read-only workspace (trial or subscription ended) keeps its data so you can come back. It is not deleted automatically today.
- Records of failed sign-ins are cleared after about a day.
Requests from your prospects
If a prospect asks you to delete or export their data, remove them in your sending tool and CRM as usual, then ask us to remove their contact record here. Their rights and how to exercise them are in the Privacy policy.
Agreements
A Data Processing Addendum is available, and Standard Contractual Clauses are available on request. See the DPA page.
Something unclear or out of date? Tell us and we will fix this page.