Privacy policy

What we store

Your account email. Your password and sign-in credentials are held by Clerk, the identity provider that runs our sign-in, and we do not receive them. The credentials for accounts you connect, whether an OAuth refresh token or a key you paste, encrypted at rest with a key bound to your organization. A log of every call made with your API keys that records the shape of each request, meaning which service, which endpoint, the status and the duration, and never its contents.

Connectable services today: Google, Slack, HubSpot, Stripe, Gong, Coda, Asana, Instantly and GitHub, and Meta Ads and LinkedIn Ads for organizations in their previews. Every one of them is connected by you, with your own account. All of them are read-only except two. In Slack, the assistant also replies with a message in the workspace that installed it, and can add itself to a public channel so you do not have to invite it. That is the whole of what it writes in Slack: it uploads no files, edits no canvases and changes nothing that was already there. It acts as itself, with the permissions that workspace granted, and Slack lists every one of them on the install screen before you agree. The person who connects Slack also grants a search permission on their own Slack identity, which lets their agent search messages as that person and see only what they can already see in Slack. We keep that token private to them: even when a connection is shared with your organization, search runs only for the person who connected it, and teammates are asked to connect their own Slack. In Instantly, if the key you paste allows it, your agent can also add leads to a campaign or lead list and create a campaign. We never activate, pause or delete an Instantly campaign. Campaigns we create stay drafts until you activate them in Instantly. If you ask the agent to add leads to a campaign that is already active, Instantly will email those leads on that campaign's schedule.

Some tools work without you connecting anything, because they run on our own accounts and are charged to your credit balance. Today those vendors are DataForSEO, OpenAI, Apollo, Perplexity, Exa, Apify, Hunter, TypeSafe and Vercel. Your agent chooses what it sends them. We never send data from a connected account to them automatically.

If your agent sends an image to a Jev tool, the image goes to TypeSafe so it can be read. It can contain personal data, such as faces, names or contact details in a screenshot. We pass the picture itself and nothing that names it, and we do not store it. If your agent sends a link to an image instead, our server fetches that link first and then sends TypeSafe the picture, never the link. TypeSafe handles the image under its own terms.

For models served through Vercel, prompts go on to the Upstream Vendor of the model the customer picks, with zero data retention requested on every call.

How we use your contact information

We may also use your information to contact you about goods and services that may be of interest to you. If you do not want us to use your information in this way, email us at the address below.

We may disclose your account and contact information to contractors, service providers, and other third parties we use to support our organization and who are bound by contractual obligations to keep personal data confidential and use it only for the purposes for which we disclose it to them. Examples include hosting, cloud storage, email communications, analytics, security and anti-fraud, payment processing, and customer relationship tools.

Our product analytics provider is Mixpanel. It knows each organization by its organization id. On that organization's profile it also receives one email address, the account owner's, so we can tell which customer an organization belongs to when we look at how it uses the product. The usage events themselves carry no email address and no name. We do not send Mixpanel an address for our own team's organizations. When the owner changes, the new owner's address replaces it. When an organization has no owner left, is deleted, or becomes one of our own team's, we remove the address from its profile.

What we never do

We never sell your data and we never share it with a third party for their own purposes. We never read your connected accounts except when your own API key asks a tool to. One organization's credentials and data are never reachable from another organization's requests: the database enforces this with row-level security, and each connected platform enforces it again, because the credential is yours and not ours.

We do not use your data, from any connected service, to develop, train, or improve any generalized artificial intelligence or machine learning model.

Google user data

This application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Google user data is used only to provide or improve the features you visibly requested; it is never transferred to others except as needed to provide those features, to comply with applicable law, or as part of a merger or acquisition; it is never used for advertising; and it is never used to develop, improve, or train generalized artificial intelligence or machine learning models. No human reads your Google data, except with your explicit permission for a support request you raised, where it is necessary for security, or where the law requires it.

What we ask Google for, and why. Each one is read-only:

• Analytics and Search Console: so an agent can report your own traffic and search performance.
• Sheets, Docs and Calendar: so an agent can read a document or schedule you point it at.
• YouTube: so an agent can report your own channel's performance.
• Your email address: so the connection can be labelled with the account it belongs to, which matters when you connect several.

We deliberately do not request access to Google Drive or Gmail.

Where your Google data goes, and where it does not. This service holds no artificial intelligence or machine learning model of its own, and no code path here takes data from a connected account and sends it to an AI provider. Reading your Google account and asking a model something are separate tools, and nothing joins them: the joining, if any, is done by your own agent on your own instruction. That agent and the model behind it are yours, running on your own account with whichever provider you chose.

One tool is an exception worth naming plainly, because we would rather say it than have you discover it. We offer an OpenAI-backed tool on our own credential, metered per call, for agents that want a model without holding a key. If your agent calls it, whatever your agent puts in the prompt goes to OpenAI's API. We never put your connected-account data there ourselves, and OpenAI's API terms state that data submitted through the API is not used to train their models. We never use your data, from Google or from any other connected service, to develop, improve, or train any model, our own or anyone else's.

You can revoke our access to your Google account at any time, either by disconnecting it here or at myaccount.google.com/permissions.

Meta Ads

Meta Ads is in a limited preview. When you connect it, you sign in with Facebook Login for Business and pick the ad accounts we may read in Meta's own selector. We ask Meta for one permission, ads_read, which is read-only, and our code has no path that writes to Meta at all. Meta issues a token scoped to the ad accounts you picked, and we store that token encrypted, like every other connection.

We read your ad data only when your own API key asks a tool to, and we pass it straight to your agent. We keep no ad data: nothing Meta returns is stored, and the call log records only the shape of each call: which tool ran, its status, how long it took and how many rows came back.

Deleting your Meta data. Disconnecting Meta Ads deletes the stored token immediately. Because we keep no ad data, that token is the only Meta data we hold, so there is nothing else to delete. You can also remove our app from your Meta business settings, which revokes the token on Meta's side, or email the address below and we delete it for you within one business day.

LinkedIn Ads

LinkedIn Ads is in a limited preview. When you connect it, you sign in to LinkedIn and approve three read-only permissions: r_ads to list your ad accounts and campaigns, r_ads_reporting to read their results, and r_organization_social to read the post behind an ad so your agent can see its copy. LinkedIn lets us read only the ad accounts where you hold a role, and our code has no path that writes to LinkedIn at all. We store the tokens LinkedIn issues encrypted, like every other connection.

We read your ad data only when your own API key asks a tool to, and we pass it straight to your agent. We keep no ad data: nothing LinkedIn returns is stored, and the call log records only the shape of each call.

Deleting your LinkedIn data. Disconnecting LinkedIn Ads deletes the stored tokens immediately, and they are the only LinkedIn data we hold. You can also remove SingleBrain Gateway under Permitted services in your LinkedIn data privacy settings, which revokes it on LinkedIn's side, or email the address below and we delete it for you within one business day.

Instantly

You connect Instantly by pasting an API key from your own workspace, and we store it encrypted like every other connection. We read or write your workspace only when your own API key asks a tool to, and only as that tool describes.

We act as your processor for Instantly data. The leads, replies, campaign results and other data your agent reads through us, and the leads it sends us to add, are your data about your prospects, and you are their controller. We process them only on your documented instructions, which are the tool calls your API keys make, solely for your own business-to-business sales and marketing. We never sell them, share them, add them to any list or dataset, use them for another customer, or use them to train any model.

We keep no Instantly data. Lead details, email bodies and replies pass straight through to your agent or to Instantly and are not stored. The call log records only the shape of each call: which tool ran, its status, how long it took and how many rows came back. It never records a lead's name, email address or message, and neither do our error reports.

Disconnecting Instantly deletes the stored key immediately. Because that key is the only Instantly data we hold, nothing else remains.

GitHub

You connect GitHub by pasting a fine-grained personal access token that you create in your own GitHub settings, and we store it encrypted like every other connection. We ask for Contents and Metadata, both read-only, on only the repositories you choose, and our code has no path that writes to GitHub at all. We read your repositories only when your own API key asks a tool to, and pass what we read straight to your agent.

We keep no GitHub data. File contents, search results and commit messages are not stored. The call log records only the shape of each call: which tool ran, its status, how long it took and how many rows came back. It never records a file path, a line of code or a commit message.

Disconnecting GitHub deletes the stored token immediately. Because that token is the only GitHub data we hold, nothing else remains. You can also delete the token in GitHub, which stops it working at once.

How long we keep it

Your account, your connected credentials and your call log are kept for as long as your organization exists, and are deleted when it is. Nothing here expires on a timer, so there is no window in which we hold something you thought was gone.

Your contact record in our customer relationship tool is the one exception: it stays until you ask us to remove it.

Getting a copy, or getting rid of it

Disconnecting a service deletes its stored credential immediately. Revoking an API key stops it immediately.

For anything else, email the address below and a person answers within one business day. Ask for a copy of what we hold about your organization and we send it as a file you can keep. Ask us to delete your account and everything it stored, including your record in our customer relationship tool, and it happens within 30 days.

Contact

support@singlebrain.com · policy last updated 2026-10-27