← Ataski · Trust & security · DPA · Subprocessors

This is the canonical English version. Native translations for DE / ES / FR / PT / RU are pending counsel sign-off.

Approved 2026-10-08

Interoperability and Portability Policy

Owner: the founder. Approved: 2026-10-08. Review: annually, and on any significant change to the export, the connectors or the DPA's exit terms.

1. Principles

  1. The data is the customer's. Taking it out is self-service, available at any time, and does not need our permission or a support ticket.
  2. Open, documented formats — JSON, CSV, XLSX, PDF, UTF-8 text. No proprietary container that only Ataski can read.
  3. Standard interfaces — HTTPS everywhere; OAuth 2.0 to the customer's own systems; signed HTTPS webhooks; the Model Context Protocol for AI clients.
  4. The customer's systems stay the system of record where they exist: the workers read from and write back to the customer's CRM, helpdesk and accounting tools through the customer's own grants, which the customer can revoke at the vendor at any moment.

2. What exists today

Need How
Everything, at once /api/export (from the workspace settings): one JSON archive with a key per table holding that workspace's rows. It is generated from the data-classification registry, so a new customer table is in the export as soon as it exists; a test fails the build if the two disagree. It is streamed as one consistent snapshot, ends with an export_complete marker so a truncated download is detectable, and is recorded in the workspace's audit log. Excluded by design: stored credentials, and a short list of internal tables (cross-tenant caches, public-register copies, derived vectors), each with a written reason
One role's working data CSV or XLSX downloads inside each role — contact and company lists, collections and renewal worklists, forecasts and budgets, support conversations, the audit log
Generated documents PDF and spreadsheet files, downloadable where they are shown
Bring data in CSV and spreadsheet upload; OAuth connectors to the customer's CRM, accounting, helpdesk, mail and calendar systems
Push events out Signed HTTPS webhooks to a customer-chosen endpoint (contract obligation reminders)
Programmatic read An MCP endpoint for FP&A (read-only) and contract data, with tokens the customer mints and revokes; the Excel add-in and the Google Sheets add-on

3. Leaving

Per the served DPA (§2 and §6, return or deletion):

  1. After a workspace is cancelled there is a 30-day window in which the customer can still export everything above.
  2. On request within that window, we explain the export format, answer questions about it, and return files held in object storage that the customer cannot easily download one by one.
  3. After the window the workspace is purged — database rows and stored files — and vendor-side copies are deleted where the vendor offers a way, or expire on the vendor's timer (docs/legal/data-retention-policy.md). The purge is stamped as proof of erasure.
  4. Connected-account grants are the customer's to revoke at each vendor at any time; the purge deletes the tokens we stored for them.

Requests: security@ataski.com.

4. Our own portability

The stack has no proprietary platform underneath the system of record: standard Postgres (Neon), S3-compatible object storage (R2), Docker images and a Caddy reverse proxy. Moving any of them to another provider is a migration we could do, not a re-write.

5. Not in place today