How we handle your data.

The short version

We collect what we need to run the product and nothing else. Your sales activity, account list, prospect notes, and AI conversations are yours. We store them so the app works across your devices, but we don't sell them, share them with advertisers, or use them to train models outside your account.

Who this covers

salesascode.com and the product sites, gtmcron.com, salescron.com, leadercron.com, secronjob.com, partnercron.com, bdrcron.com, crocronjob.com, cscron.com, supportcron.com, are operated by the same company. Whichever site you arrive from, your account and data live on salesascode.com and are handled exactly as described in this policy. The product sites are marketing front doors and don't hold separate copies of your data.

What we collect

• Account identity. Your email address, and the unique account ID Google returns when you sign in with Google. We store these in our user database so we can recognise you next time.
• Your work in the product. Accounts, prospects, opportunities, conversations, meeting notes, AI chat history. Everything you create or that flows in from a connected tool.
• Integration data. You connect your tools (Gmail, Calendar, CRM, prospecting, chat, etc.) in the product. We custody the access token for each connected tool, encrypted at rest with AES-256-GCM, and read on a schedule only within the scopes you authorise on the provider's own consent screen. We never request scopes beyond what a feature needs, and you can revoke any connection at any time, which stops further processing of that tool.
• Operational metadata. Session cookies (one HttpOnly cookie per signed-in browser), the user-agent and IP address of each session for security, and standard request logs (URL, status code, latency) to keep the service healthy.
• Billing. Stripe processes payments. We receive Stripe's metadata (customer ID, subscription status, plan, period dates). We never see your card number.

What we do with it

• Run the product, render the dashboard, answer brain questions, send the integrations engine after fresh activity.
• Keep your data in sync across the devices where you've signed in.
• Generate AI responses against the Claude API (Anthropic). The prompts include the relevant subset of your data needed to answer your question; Anthropic does not retain it for training.
• Bill you, via Stripe.
• Send a tiny number of transactional emails (subscription receipts, password-reset confirmations). No marketing without your opt-in.

How your products process your data

Your products run on our servers on a schedule. To do the work, each run reads the data you connect (CRM records, email, calendar) and the context you provide, and processes it to research an account and draft the work. This produces two kinds of stored data:

• Drafts and reports (content). The output a run generates for you, for example an account brief, a follow-up draft, or a forecast rollup. These contain content drawn from your data and live in your account until you dismiss them. You choose where each product delivers them: an in-app queue, your Google Drive, or your own mailbox as a draft. Nothing is sent for you.
• Run telemetry (metadata only). Which product and skill ran, when, how long it took, the counts it produced, and the outcome. This is metadata about the run, not its content.
• Brain state. The working memory a product builds up (signal weights, your ICP, a decision log, review summaries) so the app can show how your operation is evolving.

What we never do: we do not sell your data, share it with advertisers, or use it to train models outside your account. Everything is scoped to your authenticated account and never mixed with another account's data.

How that is enforced, not just promised. The Anthropic API, which serves the great majority of our model calls, is contractually zero-retention for training. Where a call is routed through OpenRouter we send its data_collection: deny policy, so any upstream provider that would store or train on the prompt is ineligible to serve the request; if no eligible provider exists for a given model, the request fails rather than being routed to one that would. Our subprocessor list on the Trust page names every model provider we use.

This data is yours. You can export it and delete it from the product, and deleting your account removes it on the schedule in "Your rights" below.

Subprocessors

We rely on the following third parties to operate. Each has its own privacy practices linked. Several are conditional. They only process your data when you connect or enable the feature that uses them. This list is rendered from the same registry as the one on Trust & security, so the two can never drift apart.

• Anthropic: AI inference (Claude). Scheduled runs call the Claude API to research and draft your work; prompts include the subset of your data needed and are not retained for training. (United States.)
• OpenRouter: AI inference routing, when a run is configured to use it instead of the Claude API directly. Sees the same prompt content: the subset of your data the run needs. (United States.)
• Amazon Web Services (Bedrock): AI inference, when a run is routed through Bedrock rather than the Claude API. Same prompt content as above. (United States.)
• Gong: Call recordings and transcripts, read from your Gong workspace when you connect it, so a run can prepare a meeting or coach a call. (United States.)
• Neon: Primary Postgres database, accounts, entitlements, telemetry, brain sync. (United States.)
• Vercel: Application hosting and edge delivery. (Global edge, U.S. compute.)
• Stripe: Payments, subscriptions, invoices. We never see full card numbers. (United States.)
• Resend: Transactional and digest email delivery. (United States.)
• Google: Google sign-in (OpenID) and, if a deployment enables the first-party connectors, Gmail / Calendar / Drive data within the scopes you grant. (United States.)
• Recall.ai: Meeting-bot recording and transcription when you enable call recording, audio, video, and transcripts of the meetings you point it at. (United States.)
• Dropbox Sign: Electronic signature for enterprise contracts, signer name, email, and the executed contract document. (United States.)
• Apollo: Contact and company enrichment when you connect the Apollo integration. The identifiers you look up and the firmographic results. (United States.)
• ZoomInfo: B2B contact and company data when you connect the ZoomInfo integration (partner-gated). The identifiers you look up and the results. (United States.)
• PostHog: Product analytics on marketing pages, page views and click events, only after you consent via the cookie banner. (United States.)
• Voyage AI: Text embeddings for in-product semantic matching. The text snippets being matched are sent for vectorization. (United States.)
• ElevenLabs: Text-to-speech for the audio weekly recap. The recap text you generate audio for. (United States.)
• Slack: Slack notifications and the Slack assistant when you connect a workspace. The messages and channels you route through it. (United States.)
• Snowflake: Warehouse reads when you connect the Snowflake integration, query results from the tables you point it at. (Customer-selected cloud region.)
• Cloudflare Turnstile: Bot protection on public forms. A browser challenge token and IP metadata, no tracking cookies. (Global (U.S. company).)

For our full security posture, compliance status, and data handling, see Trust & security.

Your rights

• Access. Everything we have on you is visible inside the product. Open any account, prospect, or brain entry to see it.
• Export. Settings → Data → Export to download your data as JSON.
• Delete. Settings → Data → Delete account. We hard-delete your user row, sessions, integrations, and all associated records within 7 days. Four narrow exceptions, and this list is what the code actually does:
  1. Stripe subscription history is retained per Stripe's standard policy for tax and accounting.
  2. Audit-log entries (the security trail of who changed what, including the deletion itself) are retained with the link to your account removed.
  3. If you signed an enterprise contract, we keep the anonymized commercial record (deal value, term, status) and remove your name, email, company and the contract document.
  4. Records you shared with a team stay with that team. Anything you recorded under your own scope is deleted; a record you contributed to a shared team workspace belongs to that workspace and survives, the same way it would if you left the company. Your personal scope, your connections and your activity all go.
• Disconnect integrations. Disconnect any connected tool from Settings → Connections. Future polling and processing of that tool stop immediately; data already processed into your drafts and rollups stays until you delete it or your account.

Cookies & analytics

• Strictly necessary. One HttpOnly session cookie (si_session) that keeps you signed in, and a short-lived state cookie during OAuth handshakes. These are required for the product to work and are set without asking.
• Analytics (opt-in only). Our marketing pages can use PostHog product analytics. PostHog loads (and its cookies are set) only after you click Accept on the cookie banner. Your choice (accept or decline) is stored in a sac_analytics_consent cookie for 180 days; if you decline, no analytics script loads at all. You can change your mind any time with the Analytics preferences control just below.
• Nothing else. No advertising cookies, no fingerprinting scripts, no cross-site trackers, and no Google Analytics.

Analytics preferences

Checking your current choice…

Reset my analytics choice

Resetting clears the sac_analytics_consent cookie and reloads this page; the consent banner will ask again, and no analytics loads unless you accept.

Where your data lives

Primary database: Neon (Postgres) in their default U.S. region. Application servers: Vercel, distributed globally. AI inference and embeddings: Anthropic, OpenRouter, Amazon Web Services (Bedrock), Voyage AI and ElevenLabs, U.S. regions. If you're outside the U.S., your data is processed in the U.S. The Trust page lists every subprocessor with what it processes and where.

Security

OAuth tokens are encrypted at rest with AES-256-GCM. Sessions are HttpOnly, SameSite=Lax, and Secure in production. The API key you provide for direct AI access (Settings → API) is stored only in your browser's localStorage. It never reaches our servers.

Enterprise controls. Teams can enable SAML single sign-on (Settings → Team) and route sign-in through their own identity provider at /login/sso. Every admin-relevant action is written to an append-only audit log. You can retrieve your own entries (the actions you took, and the actions taken on your account) as JSON from /api/me/audit. Entries are never edited in place; they are retained for 18 months and then pruned. A team-scoped view and CSV export for team admins is on the roadmap and is not available today. You can export all of your data at any time (Settings → Data) and request deletion, which we hard-delete within 7 days (Stripe billing records are retained per Stripe's policy for tax and accounting).

Changes

If we materially change this policy, we'll surface a notice inside the product the next time you sign in. The "Last updated" date at the top always reflects the current version.

Who operates this service

This service is operated from the State of Illinois, United States. The registered entity name and address are not yet published here; write to admin@salesascode.com for them.

Contact

Questions, requests, or concerns: admin@salesascode.com.