The words we use, and what they mean.

The narrow window the answers appear in. It sits above your other windows, is kept out of screen shares, and can be moved, dimmed and hidden. Distinct from the application.

The large window holding your account, preparation, knowledge base and settings. Two separate surfaces with different jobs: you prepare in the application and work in the assistant window.

The summary built from your own documents before a conversation: what it is about, which numbers are in play, where it gets difficult.

The structured description of a specific case or customer that preparation and answers are based on.

The property of being absent from screen recordings. Technically two different calls, one to Windows and one to macOS; the application shows whether it is active. It works against screen capture, not against a camera pointed at your screen.

What remains after the conversation: open points, commitments made, an assessment of how it went. The transcript itself is deleted.

The kind of conversation, which shapes the form of the answer: sales, advisory, interview, examination and others.

A prepared set of typical questions and objections for one kind of conversation. Eight ship with the product; you can add your own.

The reverse case: Thalassa asks you the uncomfortable questions, at an adjustable severity, with no conversation running.

Playing through "what if the other side says X" before the meeting.

The sound your computer plays — that is, the other person’s voice out of the meeting. Distinct from the microphone, your own voice. Thalassa hears both, separately.

The decision about when an answer is generated. Not every sentence is a question; what gets recognised are questions and objections directed at you. Sensitivity is adjustable, and you can always request an answer yourself.

Replacing names, file numbers, figures and absolute dates with placeholders. It is fail closed: if recognition fails, nothing is passed on.

A switch that replaces personally identifiable details with placeholders before anything goes to a model, and translates the answer back afterwards.

The rule that figures and claims must come from a source. If nothing is found, the knowledge base is skipped for that answer rather than padded. In the Legal module this is tightened into a citation requirement: no source, no answer.

Your own documents, which you add and which answers are drawn from first. They are read, indexed and searched on your device. Not to be confused with the library. One named exception at ingest: a scanned PDF has each page sent once for text recognition.

The source collection we maintain, intended to belong to the specialist plans. Empty today.

Running translation of what is said, as text to read along, not as an interpreter’s voice. Billed separately.

Four graded language models, from fast to thorough. Which one answers is decided by the system from the task and your plan; the choice is not the user’s.

An identifier that stands in for a person without naming them, and that cannot be reversed without a server-side secret.

A single capture of the screen for exactly one answer, on explicit request. Not continuous, not in the background.

Turning sound into text, in 17 languages including automatic detection.

The configurable rule for the balance at which more is bought automatically, with a spending cap.

The billing unit. One minute of running conversation is one minute, regardless of how many answers came in it.

Minutes bought in advance. They expire 365 days after their purchase; subscription minutes do not carry over.

Not a ticket but a window of time: 14 days of full capability, for interviews only.

The hourly cap of a plan. The only quantity in the system allowed to end a conversation in progress — an empty balance does not.

The price shown, including VAT. There is no separate net price list.

90 minutes. A ticket is built from two of them, which is why a shorter conversation can cost half a unit.

The seller in the legal sense. For Thalassa that is the payment provider: it issues the invoice, remits the VAT and enters into the purchase contract. This is why cancellation and invoices live in their portal and not with us.

The monthly number of answers per model tier. Separate from minutes: you can have minutes left and a quota exhausted.

A one-off purchase without a subscription: one conversation of up to three hours.

Whoever decides the purpose and means of processing. For the contents of your conversations, that is you, not us.

The commitment that processing happens in the EU (Frankfurt), with named exceptions: answers that use web search, optional live translation, and text recognition for scanned files at ingest.

Building something to refuse rather than pass through when it fails. An anonymiser that returned the original text on error would be more dangerous than none at all.

The EU General Data Protection Regulation. Governs who may process personal data under what conditions.

Several valid keys at once: the first encrypts new values, all of them can read old ones. This is what lets a key be rotated without destroying existing connections.

Whoever processes on instruction without deciding the purpose. That is the role Thalassa takes for conversation content; the providers we use are sub-processors.

The cap on requests per period, against overload and automated guessing.

The certificate a maker uses to identify an application as theirs, and Apple’s additional check. Without them the operating system warns. Thalassa has neither yet.

The mechanism that bypasses a repeatedly failing provider instead of continuing to ask, then tests it with exactly one probe.

Protection of data on the wire (HTTPS). To be distinguished from encryption at rest, on the storage medium.

The service in the data centre that receives requests, talks to the model providers and keeps account and usage. The application on your device holds no provider credentials.

Keeping usage as a sequence of bookings rather than as a counter. Every minute can be derived, and parallel requests cannot confuse the balance.

Searching your own documents on your device. A search query reaches no external server.

The design in which keys exist only server-side. Take the installed application apart and there is nothing worth extracting.

The principle behind the Legal module: one sign-in, one bill, one interface — but a separate database, speech recognition, model path and retention.

Reading text out of images, needed for scanned PDFs. Switchable off, because a page image leaves your device for it.