How we handle your data.

Data location

Where your data physically is.

Three vendors hold your data at rest, all in US data centers. Each is a named sub-processor under its own DPA.

Retention and deletion

How long we keep it, and how it goes.

Ask to delete the workspace and a 30-day grace period starts, during which you can change your mind. After it the purge is hard: every customer-data table and our file storage, the audit trail included. Copies that vendors keep on their own timers (AI request traces, error reports, email delivery logs, meeting recordings) expire under each vendor's retention terms, listed in the Data Retention Policy.

Before that, take everything: the export is machine-readable.

The shared cache of company email formats expires on its own timer and never holds an individual contact.

The full text is the Data Retention Policy. Data Retention Policy

Access controls

Connector scopes

Every operator-connectable system runs against a documented set of provider-side scopes. The list below renders from our internal scope manifest — what you see is what the OAuth client (or equivalent credential) actually requests.

• Amplitude Reads only; the grant would allow writes

  Reads, per customer, event counts, the date of last activity, and the most used events through Amplitude's Dashboard REST API, for the Renewal Manager's account-health signals, using your project's API key and secret key. Ataski issues read requests only — note that Amplitude offers no read-only project key: the same API key can send events into the project, so it is technically read and write.

• Anthropic (Bring Your Own Key) Can write

  Routes Claude calls through your own Anthropic API key. The key is stored encrypted and used only at the moment of a call; Anthropic bills you directly for that traffic, and Ataski's invoice leaves it out. Rotate or remove the key in Settings at any time.

• BambooHR Reads only; the grant would allow writes

  Reads your employees with job, pay rate, and pay period through a report run on demand (nothing is saved in BambooHR) so the Financial Analyst's headcount register can show staff and pay. Uses your company subdomain and an API key from a BambooHR user. Ataski issues read requests only — note that BambooHR offers no read-only API key: a key carries the permissions of the user who created it, so it is technically read and write wherever that user can write.

• Bitrix24 Reads only; the grant would allow writes

  Reads your deals (crm.deal.list — the only method called) so the Financial Analyst can plan revenue from the pipeline, through an inbound webhook you create in your own Bitrix24 portal with the CRM (crm) permission and can revoke in one click. Ataski issues read requests only — note that Bitrix24's crm permission has no read-only variant, so the webhook is technically read and write.

• Chargebee Read only

  Reads subscriptions and invoices so the Financial Analyst can build recurring revenue, with a read-only API key from your Chargebee site (Settings → Configure Chargebee → API Keys). Cannot create, change, or cancel a subscription or an invoice.

• Close Reads only; the grant would allow writes

  Reads opportunities for renewal dates, and searches leads so the Outbound Sales Assistant does not contact someone already in your CRM, with an API key you paste in. Ataski issues read requests only — note that Close offers no read-only API key: the key carries the full access of the user who created it, so the permission is technically read and write.

• Deel Read only

  Reads your people and each employment's pay rate and pay period so the Financial Analyst's headcount register can show staff and pay, with an API token you create in Deel (Developer → API keys). The token holds whatever access you give it in Deel; Ataski only reads the people list and never changes a contract or a payment.

• DocuSign Read only

  Reads completed envelopes and their signed documents for contract intake. DocuSign ships a single signature scope with no read-only variant — the token could send envelopes; our code never does. Cannot write: we never create, send, or void an envelope.

• Dropbox Read only

  Reads file listings and file content from the folder the customer connects for contract intake (files.metadata.read + files.content.read). Cannot write, move, or delete any Dropbox file.

• Microsoft Dynamics 365 Business Central Reads only; the grant would allow writes

  Lists your Business Central environments and companies so you can pick one, then reads only that company: its chart of accounts, general ledger entries with their dimensions, general ledger setup, company information, and aged receivables and payables, for the Financial Analyst; and its open sales invoices, credit memos, customers (name and email address), and unposted customer payment journal lines, for the AR Cash Collector. Ataski issues read requests only — note that Microsoft offers no read-only Business Central scope, so the permission you grant is technically read and write, limited to what your own Business Central user may do.

• Freshdesk Can write

  Posts the replies you approve onto the original Freshdesk ticket, and — only when you run the help-center import — reads your published Solutions articles. It uses an agent's API key from that agent's Freshdesk profile; Freshdesk keys carry the agent's full permissions, so the key can do more than Ataski uses. Ataski never edits, closes, or deletes a ticket or an article.

• Front Can write

  Posts the replies you approve onto the original Front conversation, using an API token you create in Front (Settings → Developers → API tokens) with the Shared resources scope. The token can do whatever its Front permissions allow; the only call Ataski makes with it is sending a reply to a conversation Ataski received. New messages reach Ataski through a Front webhook signed with a secret you paste.

• Gmail (operator mailbox) Can write

  Sends approved outreach and dunning email from the operator's own Gmail mailbox. The base connection requests only gmail.send — a send-only scope that cannot read the mailbox. Two optional feature grants ask for a separate re-consent: draft delivery (gmail.compose / gmail.modify, to place drafts in the operator's Drafts folder) and duplicate-contact checking (gmail.metadata / gmail.readonly, used for thread metadata lookups — message bodies are never read). Nothing sends without the operator's approval queue.

• Google Calendar Read only

  Reads free/busy availability windows only (calendar.freebusy) to propose meeting slots — never event titles, attendees, or descriptions. Cannot create or modify any calendar event.

• Google Drive Read only

  Reads the folder the customer connects for contract intake (drive.readonly). Cannot create, modify, or delete any Drive file.

• Gusto Read only

  Reads your company, its employees, and their compensation (companies:read, employees:read, compensations:read) so the Financial Analyst's headcount register can show staff and pay. Gusto assigns these scopes to the Ataski app when it reviews the app, so the consent screen lists none; every one is a read scope. Cannot create or change employees, and cannot run payroll.

• Help Scout Can write

  Posts the replies you approve back into the original Help Scout conversation. Help Scout has no OAuth scopes: the app acts with the Mailbox API access of the Help Scout user who connects it, so the permission is broader than what Ataski uses — the only call made with it is posting a reply to a conversation Ataski received. New conversations reach Ataski through a Help Scout webhook you create, signed with a secret you paste.

• HubSpot Read only

  Reads deals, contacts, and companies. Cannot create or modify any HubSpot record — CRM write-back runs on Salesforce only. A workspace that pasted a HubSpot private-app token instead of connecting is read through that token the same way: it carries the scopes ticked when the private app was created, and Ataski still only reads.

• Intercom Can write

  Reads contacts, companies, and conversations for account-health and renewal signals, reads your help-center articles when you run the import, and posts the replies you approve as an admin reply on the original conversation. It uses the access token of an app you create in the Intercom Developer Hub; what that token may do is set by the app's permissions in Intercom. Ataski never edits or deletes contacts, companies, or articles.

• Linear (legacy) Reads only; the grant would allow writes

  No longer accepted for new connections. A Linear connection made before 2026-09-07 is still read once a week for the operations digest: the list of teams, each team's active cycle, and that cycle's issues, through Linear's GraphQL API with the personal API key that was pasted in. Ataski issues read requests only — note that a Linear personal API key carries its creator's full access unless it was restricted when created, so the permission is technically read and write. Delete the key in Linear to end it.

• Mixpanel Read only

  Reads, per customer, the last event date, weekly active users, and event volumes through Mixpanel's Query API, for the Renewal Manager's account-health signals, using a service account (username and secret) you create in your project. Give it the Consumer role, which can only read; Ataski never sends events or changes the project.

• NetSuite Read only

  Reads GL transactions, AR aging, AP aging, accrual snapshots, and subsidiary roster over SuiteTalk REST. New connections sign in with OAuth 2.0 (authorization code + PKCE, scope rest_webservices) through an Integration record the customer creates in their own NetSuite account; existing connections may keep Token-Based Authentication (TBA) — an OAuth 1.0a-flavoured credential the customer generates inside their NetSuite UI (Setup → Users/Roles → Access Tokens). Either way the access is bounded by a read-only NetSuite role of the customer's choice, and Ataski only issues read queries. Cannot post journal entries, modify records, or close accounting periods.

• Notion Can write

  Uses an internal-integration token you create in Notion. A Notion integration sees only the pages and databases you share with it. Ataski reads the pages you share for the Support knowledge base, and adds one new page per delivered contract brief or financial digest to the database you choose. It never edits or deletes an existing page; what the token may do inside shared pages is set by the capabilities you tick on the integration in Notion.

• 1C:Enterprise Read only

  Reads the chart of accounts, accounting-register turnovers and balances, and receivables from your 1C:Enterprise base through its published OData interface, for the Financial Analyst and the AR Cash Collector. It signs in as a 1C user you create, so access is bounded by that user's rights in 1C — give it read-only rights. Ataski only issues read queries and never posts a document or changes the base.

• Microsoft Outlook / Microsoft 365 Can write

  One Microsoft consent covers document intake (Files.Read.All), calendar availability (Calendars.Read), reply detection (Mail.Read), and sending approved outreach and dunning email from the operator's own Outlook mailbox (Mail.Send — the write surface). A connection granted without Mail.Send is never treated as send-capable, and nothing sends without the operator's approval queue.

• Paddle Read only

  Reads subscriptions and transactions so the Financial Analyst can build recurring revenue, with an API key you create in Paddle. What the key may do is set in Paddle; Ataski issues read requests only and never changes a subscription or a transaction.

• Pipedrive Reads only; the grant would allow writes

  Reads deals and the organizations they belong to, for renewal dates and the Financial Analyst's pipeline, and searches people and organizations so the Outbound Sales Assistant does not contact someone already in your CRM. Uses your company domain and a personal API token you paste in. Ataski issues read requests only — note that Pipedrive offers no read-only API token: the token carries the full access of the user it belongs to, so the permission is technically read and write.

• PostHog Read only

  Reads, per customer, recent product events and the date of last activity for the Renewal Manager's account-health signals, with a personal API key and your region (US or EU). PostHog lets you limit a personal key's scopes, and read scopes are enough; Ataski never sends events or changes your project.

• Postmark (your own account) Reads only; the grant would allow writes

  Reads bounces, sent-message records, opens, and clicks from your own Postmark server so the Renewal Manager can spot customers whose mail stopped landing, with a Server API token you paste in (Postmark → Servers → your server → API Tokens). Ataski issues read requests only — note that Postmark offers no read-only server token: the token could also send mail from that server, so it is technically read and write. This is separate from Ataski's own Postmark account, listed as a sub-processor.

• QuickBooks Online Reads only; the grant would allow writes

  Reads chart of accounts, P&L, balance sheet, cash flow, invoices, customers, and vendors. Ataski issues read requests only — note that Intuit offers no read-only accounting scope, so the permission you grant is technically read and write.

• Recall.ai Can write

  Creates bots that join scheduled meetings and reads back their transcripts and engagement metadata. Write surface is limited to dispatching the bot; cannot mutate any calendar, video-conference, or meeting-host data.

• Recurly Read only

  Reads plans, subscriptions, and invoices so the Financial Analyst can build recurring revenue, with a private API key you create in Recurly. What the key may do is set in Recurly; Ataski issues read requests only and never changes a subscription or an invoice.

• Rippling Read only

  Reads workers, users, and compensation (workers.read, users.read, compensations.read) so the Financial Analyst's headcount register can show staff and pay, with an API token you create in Rippling (Tools → Developer → API Tokens). The token sees only what its creator can see, and every scope asked for is a read scope. Ataski never changes a Rippling record.

• Sage Intacct Read only

  Reads GL accounts, journal entries, AR/AP, and trial balance through Sage Intacct's Web Services, using Web Services credentials the customer provisions: a sender ID the customer obtains from Sage and authorises in their own company, and a read-only Web Services user the customer creates in their Sage Intacct admin. No OAuth sign-in is involved. Cannot post journal entries or modify any Sage Intacct data.

• Salesforce Can write

  Reads accounts, contacts, opportunities, and activity for renewal and outbound signals, and writes back CRM activity the customer switches on. Salesforce's api scope is the full REST API — Salesforce ships no narrower data scope, so we disclose it as write-capable rather than calling the connector read-only. refresh_token / offline_access only keep the grant alive.

• Segment Read only

  Reads, per customer, recent events from the Segment Profile API (part of Segment's paid profiles plan, on your own subscription) for the Renewal Manager's account-health signals, with a Profile API access token. The Profile API only reads profiles; Ataski never sends events.

• Shopify Read only

  Reads your store's orders (read_orders; add read_all_orders, or Shopify returns only the last 60 days) so the Financial Analyst can model order value, repeat purchases, and growth. Uses the Admin API token of a custom app you create in your store; the token can do only what the scopes you tick allow, and both scopes asked for are read scopes. Ataski never creates, changes, or refunds an order.

• Slack (Ataski app) Can write

  Installs the Ataski bot in your Slack workspace. It posts notices, digests, and answers (chat:write), opens a direct message with a teammate (im:write) after looking that one person up by email (users:read.email — Slack requires users:read alongside it; the directory is never listed), registers the /ataski command (commands), and reads only messages addressed to the bot: @mentions (app_mentions:read) and direct messages to it (im:history, im:read). It cannot read channels where it is not mentioned, and cannot change workspace settings or members.

• Slack incoming webhook Can write

  A Slack Incoming Webhook URL you create in Slack and paste in (only hooks.slack.com addresses are accepted). It can post messages into the one channel it was created for — contract briefs, obligation reminders, financial report notices and accounts-receivable alerts — and nothing else: it cannot read any message, list channels, or see who is in the workspace. Stored encrypted; delete the webhook in Slack to revoke it.

• SMTP mailbox Can write

  Sends the collection emails the AR Cash Collector prepares from your own mailbox (Yahoo, Apple iCloud, Fastmail, or your own server), signing in with the username and password you enter. Ataski connects only over SMTP, which can send mail but cannot read, move, or delete it. On your own server that password may be the real mailbox password — use an app-specific password wherever your provider offers one. Stored encrypted.

• Stripe Read only

  Reads subscriptions, invoices, customers, refunds, and payment intents via a customer-provided Restricted API key. Cannot create, modify, or refund charges.

• Microsoft Teams webhooks Can write

  Two Microsoft Teams links, both created by you inside Teams and both limited to one channel. An Incoming Webhook URL (a *.webhook.office.com or Workflows *.logic.azure.com / *.environment.api.powerplatform.com address) lets Ataski post obligation reminders and accounts-receivable alerts into that channel. An Outgoing Webhook lets the Financial Analyst answer when someone @mentions it there: Teams sends only that message, signed with a secret Ataski stores encrypted and checks, and the answer goes back as the reply. Neither can read other messages, list teams or members, or act anywhere else in Microsoft 365.

• Xero Read only

  Reads the P&L, the balance sheet, the chart of accounts, tracking categories, and organisation settings, plus the source documents behind them — invoices, bills, credit notes, bank transactions, and manual journals — which is how the posting-level detail is reconstructed, and the customer and supplier contact records those documents are addressed to, which is how a receivable finds a billing email. Each of those is a SEPARATE granular scope since 2026-09-08: the two broad names Xero deprecated (all transactions, all reports) are no longer requested. Xero's general-ledger feed itself (its Journals endpoint) is sold only from Xero's Advanced app tier and is NOT read, so entries Xero posts on its own — payroll runs, fixed-asset depreciation, tracked-inventory cost of sales, currency revaluation, the year-end close — do not appear in that detail. The three payroll read scopes are OPTIONAL and off by default: they are requested only when the operator asks the headcount register to read staff and per-person pay out of Xero Payroll, and a workspace that never asks holds a token without them. Cannot create or modify any Xero data, payroll included.

• Yandex Disk Read only

  Reads PDF, Word, and Excel files in the Yandex Disk folder you connect for contract intake (cloud_api:disk.read). Cannot create, modify, or delete any file on your Disk.

• Zendesk Can write

  Reads tickets and their history for account-health and renewal signals, reads published Help Center articles and macros when you run the import, and posts the replies you approve as a public comment on the original ticket. It uses an OAuth access token from an OAuth client you create in Zendesk Admin Center; the token's scope is set there, so Ataski records it as unknown rather than guessing. The help-center import instead signs in with your account email and a Zendesk API token, which carries that user's own permissions. Ataski never deletes tickets or changes users, groups, or settings.

• Zoho CRM + Zoho Books Read only

  Reads CRM contacts, accounts, and deal stages plus Zoho Books invoices, contacts, and organisation settings for the renewal book, and the Zoho Books chart of accounts, account transactions, and open bills (supplier, balance, due date, payment terms) for the Financial Analyst. Every requested scope is a .READ scope — cannot create or modify any Zoho record.

Contract

The documents your counsel will ask for.

All of them are public and versioned. The DPA is the GDPR Article 28 contract; under the CCPA we act as a Service Provider and do not operate as a data broker. The sub-processor list carries a fingerprint recorded on every signed DPA, so you can prove which version you agreed to.

• Data Processing Agreement
• Sub-processor list
• Privacy Policy
• Terms of Service
• Data Retention Policy
• AI Disclosure