The list
OpenRouter
EU / USRoutes your messages to the language model that answers them, and receives their content in order to do so. Our account is set to zero data retention, which is what limits where it may route: see below.
The model provider
VariesWhichever provider serves the model, reached through OpenRouter: today that is Google, serving Gemini. It receives the message content, may hold it only for as long as it takes to answer, and may not train on it. Which model answers can change; this line changes with it.
LiveKit
EU / USCarries voice-call audio and runs the speech-to-text and text-to-speech behind it. Audio is not recorded by us or by them.
Cloudflare
EUStores the images and PDFs you attach to a message. The bucket is EU-jurisdiction and nothing in it is publicly readable.
Google
USOnly if you use “Continue with Google” to sign in. It learns that you signed in here; it does not receive your conversations.
Resend
EU / USSends verification and password-reset email, and the internal notification that a lead record or scope note was written. For the first kind it receives your email address; for the second, the content of that record on its way to Nicolas, never to you. The mail itself leaves from Ireland; Resend’s own records of it live in the US, under standard contractual clauses.
Prelude
EUSends and checks the SMS code if you verify a phone number. It receives the number and the address you asked from (its fraud scoring uses both), and it generates the code itself: no code ever exists on our side. The message then travels the phone network to wherever the number is.
Cal.com
USRuns the booking calendar at the foot of the homepage. It loads when you scroll down to it, and they see your address at that point; the name, email and time you enter reach them only if you go on to book.
Sentry
EURecords the technical details of an error when something breaks: which page, which line of our code, which browser. It is not told who you are, and the content of your messages is not part of what it receives. Your address reaches it only as the sender of that report, and it is instructed not to keep it.
Langfuse
EU / USOur diagnostic record of how the assistant handled a conversation: how long each reply took, which of its tools ran, how many tokens it used, so a fault can be found and fixed. It does not receive the conversation itself: what you type and what the assistant answers are removed before anything is sent. The traces are stored in Ireland; Langfuse is run by ClickHouse, Inc. in the US, whose staff can reach them for support, under standard contractual clauses.
Our own servers
EUPostgres and Valkey: the profile, the sessions and the conversations themselves.
Why this page exists
Under the GDPR, anyone processing personal data has to say who else receives it. For an AI product the model provider is the recipient nobody expects, so it is named first rather than buried: what you type into the assistant is read by a company that is not us, and you should know which one before you type it.
T3CHNICO does not sell data, does not share it for advertising, and engages no processor beyond this list. Each one is bound by a data processing agreement, and we remain answerable for what they do with it.
Zero data retention
The model that answers you is reached through OpenRouter, and our account there is configured for zero data retention. OpenRouter will only send a request to a provider that guarantees it keeps nothing once the answer is returned and trains on nothing it receives.
This is a restriction on us rather than a promise about them, which is the part worth understanding: a model whose providers do not offer those terms is simply unavailable to this site: the request fails rather than quietly going somewhere with weaker ones. Some capable models cannot be used here for exactly that reason. What reaches a model provider is therefore governed by the setting, not by our intentions or theirs.
It does not make the conversation private from us: what you type is stored on our own servers so the assistant can remember your context, and the privacy page is where that, and how to erase it, is set out.
When it changes
Adding or replacing a processor is announced here before it takes effect, and the date above changes with it. Upstream lists move on their own schedule (the companies above have their own processors, and they revise those without telling anyone), so this page is reviewed rather than assumed.
To be told directly instead of having to check, or to object to a change, write to [email protected]. What is held about you, and how to take it back, is on the privacy page.
