Data processing
What we process on your behalf, where it lives, and who else touches it — the annexes of a DPA, published so you do not have to ask for them.
Roles
For documents your people write in Specio, you are the controller and we are the processor. We process them only to provide the service and on your instructions. We do not sell them, and we do not use them to train models.
What we process
- Account data — name, email address, and the workspaces and organisations someone belongs to.
- Content — documents, comments, uploaded files and images.
- Learning records — for Specio Learn: enrolments, progress, answers and submissions, grades and feedback, certificates.
- Usage records — counts of AI actions, storage totals, and the days a member was active. Counts, never what was written.
- Administrative log — who invited whom, who changed a role or a setting. Deliberately contains no reference to any document.
Sub-processors
These are the third parties that may process customer data. We give notice before adding one. The list is also on the privacy policy. The payment providers (Lemon Squeezy, Polar) are merchants of record and independent controllers of what a buyer enters at checkout; they receive data only when someone buys, and never your organisation’s documents.
- Supabase — Database, sign-in, file storage and live collaboration. Data: Account data, documents, comments, uploaded files, learning records.
- Vercel — Application hosting and edge delivery; cookieless Web Analytics and Speed Insights. Data: Every request passes through it (IP address, browser, page). Analytics are aggregate page views and performance timings.
- Resend — Transactional email (sign-in codes, invitations, notifications). Data: Email addresses and message contents.
- Inngest — Background jobs (long AI tasks, scheduled notifications, imports). Data: Job inputs, which can include document text and identifiers.
- Lemon Squeezy — Payments, as merchant of record for subscriptions and course purchases made through it. Lemon Squeezy has announced that it will shut down on 31 March 2027; until then it may still take payments. Data: Name, email, billing address and card or other payment details, which you enter on Lemon Squeezy's checkout. We send Lemon Squeezy your email, your name if we have it, your account id and the order reference, and receive back order, subscription, refund and dispute status. We never see your card number. When the checkout page names Lemon Squeezy, and for subscriptions bought through it. Legal entity: Lemon Squeezy, LLC; its website now names it “Sold through Link, LLC f/k/a Lemon Squeezy LLC” (United States). Role: Merchant of record: it sells the purchase to you, charges you, handles sales tax or VAT, issues your receipt or invoice, and handles refunds and chargebacks with your bank. For the details you enter at checkout it is an independent controller under its own privacy policy; for the order details we send it, it acts on our instructions. Where: United States, and other countries where it or its providers operate (per its privacy policy). Transfer basis: Vietnam: covered by our cross-border transfer impact assessment (PDPL Art. 20, Decree 356/2025) [Operator/counsel: dossier not yet filed]. EU/UK buyers give their checkout details directly to the provider; the provider sets out its own transfer safeguards in its privacy policy. Privacy policy: www.lemonsqueezy.com/privacy
- Polar — Payments, as merchant of record for subscriptions and course purchases made through it. Polar uses Stripe to process card payments and to pay our revenue out to us. Data: Name, email, billing address and card or other payment details, which you enter on Polar's checkout. We send Polar your email, your name if we have it, your account id and the order reference, and receive back order, subscription, refund and dispute status. We never see your card number. When the checkout page names Polar. Legal entity: Polar Software, Inc., 3500 South DuPont Highway, Dover, DE 19901, United States. Card payments are processed by Stripe, Inc. as Polar's payment processor (privacy policy: stripe.com/privacy). Role: Merchant of record: it sells the purchase to you, charges you, handles sales tax or VAT, issues your receipt or invoice, and handles refunds and chargebacks with your bank. For the details you enter at checkout it is an independent controller under its own privacy policy; for the order details we send it, it acts on our instructions. Where: United States, Canada or other countries (per Polar's privacy policy). Transfer basis: Vietnam: covered by our cross-border transfer impact assessment (PDPL Art. 20, Decree 356/2025) [Operator/counsel: dossier not yet filed]. EU/UK buyers give their checkout details directly to the provider; the provider sets out its own transfer safeguards in its privacy policy. Privacy policy: polar.sh/legal/privacy
- Railway — LaTeX compilation servers. Data: The LaTeX source and assets of the project being compiled.
- RunPod — GPU hosting for text recognition (OCR) and for models we run ourselves. Data: Images and PDF pages sent for text recognition; prompts sent to self-hosted models.
- AI model providers — OpenAI, Anthropic, Google (Gemini, Speech-to-Text), OpenRouter — Generating, reviewing and transcribing text when you use an AI feature. Which provider serves a request is configured by us per model. Data: The prompt, the parts of the document you include, and audio you dictate. Only when you use an AI feature. On Institution plans with your own provider credentials, prompts go to your provider under your contract instead.
- Langfuse — Tracing AI requests to debug failures and check quality. Data: AI prompts, outputs, timings and the account identifier. When enabled by the operator.
- Sentry — Error monitoring. Data: Error reports with the page, browser and error details. Since the 2026-11 review the app no longer sends IP addresses, cookies or request headers (sendDefaultPii off). [Operator: also enable Sentry's 'Prevent storing of IP addresses' project setting.]
- Axiom — Application logs. Data: Request logs (path, status, timing, IP address). When enabled by the operator.
- PostHog — Product analytics. Data: Pages viewed, features used, device and browser. Only after a visitor allows analytics in the cookie banner.
- Umami — Cookieless page-view counts. Data: Page, referrer, browser and country; no cookie and no cross-site identifier.
The list follows what the code calls; it is a draft until counsel and the operator confirm it against deployed contracts and add regions.
Deletion and return
Any account can export everything it holds at any time, without asking us. Closing an account is scheduled thirty days out and reversible throughout; after that the account and its content are deleted.
Security measures
Set out on the security page, including the structural separation that stops an organisation administrator reading a member’s documents, and our incident-notification commitment.
Getting a signed DPA
Write to legal@specio.space with your institution’s name and, if you have one, your own template — most universities do, and we would rather start from yours than argue about ours.
We deliberately do not offer a click-to-accept DPA. A data processing agreement is a contract between two named parties, and one signed against text nobody reviewed protects neither of us.