Skip to content
StartFree Trial
Privacy & Trust

How your data is handled.

The architecture is simple — keep as little as possible, keep it in Europe, and keep your documents on your machine.

Thalassa is built for conversations you can't afford to leak: client calls, advisory sessions, negotiations.

What we never keep

No permanent record of your meetings.

Raw audio

Never stored — audio is transcribed as it streams and is not written to disk on our side.

Full transcripts

Deleted after the meeting. Our database has no tables for meeting content — enforced by automated tests.

Screenshots

Screen analysis happens for your answer only; captures are not retained.

Your documents' contents

Your knowledge base lives on your device. We hold no copy — we couldn't read your files if we wanted to.

The additional MCP connector retrieves text resources from a compatible server you configure and approve yourself, and can call tools that provider offers — each call only after you have confirmed it, and depending on the provider such a tool may read or change information in that system. Retrieved text is indexed and searched on your device; selected excerpts for answers and briefings pass through Thalassa's backend and the configured model service using the existing request path. MCP connections and data flow.

Where it runs

Hosted in Europe.

Answer generation and account infrastructure run in the EU. We designed for European data-protection expectations from day one: data minimisation, no permanent meeting records, and your knowledge base kept out of our hands entirely.

Contracts

Data-processing agreement.

If you process personal data through Thalassa on behalf of your own clients, you need a data-processing agreement under Art. 28 GDPR. You can download it here and sign it yourself — version 1.3 of 24 September 2026, reviewed by our lawyer. It covers the processing, the technical and organisational measures, the approved sub-processors and the international transfer annexes. If you need a counter-signed copy, send us the completed document and we will sign and return it.

Download the data-processing agreement (PDF)

Also available as a Word document for your own records, or ask us for a counter-signed copy.

The same agreement in German: PDF · Word.

The overlay, honestly

Private to you — and off your shared screen.

Your answer overlay is private to you and stays off the screen you share — so you stay present and your shared screen stays clean. It floats above your call window, only on your own monitor; move it, resize it, forget it's there.

What that means per platform, precisely. On Windows the window is excluded from screen capture by the operating system itself. On macOS it is absent from any single-window share — it was never in the picker. Since macOS 15.4, however, Apple no longer lets an application opt out of a full-screen share: Apple's own developer support has confirmed there is no public interface for it. We would rather you read that here than discover it in a client call. The application says so at the point you switch cloaking on, and it ships a self-test that captures the screen and tells you whether the window is hidden right now — the state, not the intention.

Your responsibilities

Consent & AI transparency.

You are responsible for obtaining any consent required to transcribe a conversation (in Germany, all participants must consent) and for disclosing AI assistance where required. Thalassa gives you the controls; you decide how to use them.

Privacy

Built to be trusted with a client call.

Audio → transcribed live → a sourced answer, translated on demand → deleted. Your knowledge base stays on your machine. Answers are generated in the EU. Nothing about your meetings is kept as a permanent record.

  • Audio captured locally, during the call
  • Transcribed live on the fly, never stored
  • Answer and translation — in real time Sourced from your own documents. In your counterpart’s language when you need it.
  • Deleted after the meeting — no permanent record

Processed in the EU

Answers are generated by Claude models on Amazon Bedrock, eu-central-1. The permitted regions are enforced in the source code — a deployment outside them fails rather than falling back quietly.

Nothing is kept

Audio is transcribed live and deleted. No permanent record of your meetings.

Your documents stay yours

The knowledge base lives and is searched on your device, not on our servers. Scanned PDFs are the one named exception — see the privacy policy.

Encrypted throughout

TLS on every connection, no unencrypted fallback path, and account data encrypted at rest in a private network segment that is not reachable from the internet. The one exception, named rather than buried: if an answer has to fall back to a web search, that single request leaves the European path. You can see which answers did, and you can switch web search off.

Merchant of Record

Payment and VAT handled by Stripe (Managed Payments) on our behalf.

You stay in control

In-app guidance on consent and AI transparency before every call.

Privacy questions? Ask us directly.

Start free trial Contact us