Security & Data
Last updated: October 28, 2026
The summary
Transept is a translation workspace built for secure translation. When you submit text, we send it to an AI provider to translate, store the result in our database, and let you edit it. This page explains everything around that — where the data lives, who can see it, and what we promise not to do with it. If you’re evaluating platforms for secure machine translation and translation project management, this is the plain-English version; the full legal text lives on the Privacy Policy.
- We do not use your content to train AI models — not ours, not our providers’.
- Your data lives in the EU — application and database hosted in Germany (Hetzner).
- Encrypted in transit — TLS 1.2+ on every connection.
- You own your content — we hold a narrow processing license, no ownership claim. Delete your account and your data goes with it.
- A published Data Processing Agreement — our DPA under GDPR Article 28 applies to every account, with no signature needed, and our security measures are public too.
What we do with your content
When you submit text for translation, three things happen:
- Your text is stored in our database as part of your document.
- For each translation request, the relevant block is sent to an AI provider over an encrypted connection. The provider returns the translation, which we store as a new block version.
- Your text stays in your document until you delete it (or delete your account). It is never used to train any AI model.
What we do not do:
- We do not sell your data.
- We do not use your content to train models — ours or anyone else’s.
- We do not share your content with advertisers or third-party marketing platforms.
- We do not scan your connected Google Drive or Notion workspace. We only see files you explicitly pick to import.
- We do not run our own foundation models or fine-tune on customer data.
- We do not write the text of your documents into our server logs — they record requests and errors, not content.
Where your data lives
Transept’s application servers and database run on Hetzner Online GmbH, a European hosting provider, in its Falkenstein data centre in Germany, which is certified to ISO/IEC 27001. Your account, your documents, your translations, your glossaries and styleguides — all of it sits on EU infrastructure.
When you translate, the relevant block of text is sent to an AI provider for the duration of that request. Most AI providers (Anthropic, OpenAI, Google) process requests in the US under contractual data-protection commitments and, where applicable, the EU–US Data Privacy Framework or Standard Contractual Clauses (SCCs). Anthropic, which translates today, deletes a request within 30 days; its safety systems can keep a flagged request for up to two years. The Data Processing Agreement lists what each provider receives.
Encryption
- In transit — TLS 1.2 or higher on every connection between your browser, our servers, and AI providers. HTTPS-only; HTTP is redirected.
- Backups — a copy of the database is made before each deployment and kept in Germany under the same access controls as production. We keep the ten most recent copies.
- Authentication — sign in with an email address and password, or with Google or Microsoft. Passwords are never stored in a readable form: we keep only a salted bcrypt hash. The one-time codes we email for password resets and email changes expire after ten minutes and are hashed the same way. Session tokens are stored in your browser’s local storage.
Who can access your data
Production access is restricted to a small number of named operators (currently the two co-founders), authenticated via SSH keys with audit logging. Customer content is not accessed in routine operations.
To investigate a translation issue or other support request, we ask permission and the specific document before opening it. Admin-panel access to user accounts is logged and auditable; sensitive actions (role changes, impersonation, credit adjustments) write permanent audit-log entries.
AI providers and training
Your text is sent to the following providers, depending on the task and the model in use. Transept runs on a mix of proprietary and open-source models:
- Anthropic — Claude family models, via Anthropic API. Anthropic’s commercial API does not train on customer inputs or outputs.
- OpenAI — GPT family models, via OpenAI API. OpenAI API data is not used to train models by default for API customers.
- Google — Gemini family models, via the paid Gemini API and Vertex AI. Customer data submitted through these paid tiers is not used to train Google’s foundation models.
- Groq — Llama-family and other models hosted on Groq for fast inference. Groq’s API does not train on customer data.
- OpenRouter — gateway to models run by other companies. We route requests through it only to providers that do not store or train on the data they receive.
None of these providers train on your content under the API tiers we use. Transept itself does not run foundation models, does not fine-tune on customer data, and does not retain prompts or outputs for any training purpose.
We do keep a technical record of each AI request — the model, timing, token counts, cost, and any error — on our own monitoring server in Germany (Langfuse, hosted by netcup), so we can find faults and keep costs in check. The text of your prompts and of the AI’s replies is masked before it is recorded, and the records are deleted when you delete your account.
Sub-processors
The full list of third parties that may process your data on our behalf — name, role, region, data, lawful basis, and DPA — lives at /subprocessors. Summary:
- AI translation — Anthropic (US; the model that translates today), and OpenAI (US), Groq (US) and OpenRouter (US) where one of their models is selected. Reading PDFs and scans, and translation-memory search — Google, Gemini API and Vertex AI (global endpoints, mainly US), and our own text-recognition engine on Google Cloud in the Netherlands (EU). Literess’s routing decisions — TypeSafe AI (US), which receives her recent conversation lines. See above.
- Hetzner Online GmbH (Germany, EU) — application and database hosting.
- netcup GmbH (Germany, EU) — hosts our own AI request monitoring (Langfuse); prompt and reply text is masked before it is recorded.
- Cloudflare, Inc. (global edge network) — DNS, content delivery, and the network proxy every request to transept.ai and app.transept.ai passes through.
- Google, Microsoft, Notion, Figma — only when you choose them: Google or Microsoft sign-in, and Google Drive, Notion, or Figma import and export.
- Stripe, Inc. (US / Ireland) — subscription billing and one-time purchases. We never see or store full card numbers; Stripe handles all card data under PCI DSS Level 1.
- PostHog (EU-hosted) — product analytics and error tracking. In your browser it loads only with your explicit analytics consent (opt-in for every visitor); our servers also record key in-app actions and server errors, never document text, under our legitimate interest.
- Customer.io (EU workspace) — transactional email (password-reset links and email-change codes, account notifications, billing receipts and payment reminders), the welcome and getting-started emails, and the product and marketing emails every account receives by default (legitimate interest; each carries an unsubscribe link).
- Google Tag Manager, Google Analytics and Google Ads (US) — web analytics and ad-conversion measurement, loaded only with your explicit consent and gated via Consent Mode v2.
- Meta Platforms (US) — Pixel + Conversions API for ad-conversion measurement, loaded only with your explicit marketing consent.
Material changes to this list (new sub-processor, change of region) will be flagged on this page and at /subprocessors before they take effect for new processing.
Compliance and certifications
Transept is a young company. We follow the substantive obligations of the frameworks below but do not yet hold third-party certifications. We are transparent about what we have and what we don’t.
- GDPR (EU) and UK GDPR — yes. We comply as a data controller for account and usage data, and as a data processor for content you submit. We offer the full set of data-subject rights, EU data residency for stored content, breach notification within 72 hours, and a published DPA.
- CCPA / CPRA (California) and other US state privacy laws — yes. We honor right-to-know, right-to-delete, right-to-correct, and right to opt out of sale or sharing for all US residents (we do not sell personal data).
- SOC 2 — not yet. We follow SOC 2-aligned practices for access control, encryption, change management, and incident response, but have not undergone a Type 1 or Type 2 audit.
- ISO 27001 — not certified.
- HIPAA — Transept is not a HIPAA-compliant platform. Do not submit Protected Health Information.
- PCI DSS — payment data is handled by Stripe (PCI DSS Level 1). We never see or store full card details.
Data Processing Agreement (DPA)
Our Data Processing Agreement covers our obligations as a processor under GDPR Article 28: sub-processors, security measures, data-subject requests, breach notification, deletion and audits. It applies to every account without a signature, and it ends with the entry for your records of processing, also as a PDF in English, German and Polish. The security measures it refers to are on Technical and organisational measures.
If your client or authority needs a signed copy, email support@transept.ai from your account address and we send it countersigned.
Incident response
If we become aware of a personal data breach likely to result in a risk to your rights and freedoms, we will:
- Notify affected users without undue delay, and within 72 hours where the severity warrants under GDPR Art. 33.
- Notify the relevant supervisory authority where required.
- Share what we know about the nature of the breach, the data affected, the likely consequences, and the steps we are taking to contain and remediate.
For service-affecting incidents that are not data breaches (outages, degraded performance), updates are posted via in-app banner and email to active users.
Responsible disclosure
If you find a vulnerability in Transept, please email support@transept.ai with details. We ask that you:
- Give us a reasonable window to investigate and fix before public disclosure.
- Avoid privacy violations, data destruction, or service disruption while testing.
- Only test against your own account or accounts you have permission to access.
We do not currently run a paid bug-bounty program, but we will acknowledge credible reports and — if you wish — credit the reporter publicly once a fix is shipped.
More information
For the full legal text, see our Privacy Policy and Terms of Service. For anything not covered here, email support@transept.ai.