Privacy

T3CHNICO (Nicolas Arnouts, Belgium), registered in the Crossroads Bank for Enterprises under BE 1014.668.005. For anything on this page, including the requests below, write to [email protected].

Profile

Name, email, avatar URL, and whether the email is verified.

Sign-in

Which methods you use. For Google, the tokens that keep you signed in. For email sign-up, a hash of your password, never the password.

Conversations

Every message you send the assistant and every reply, so it remembers context across visits. A conversation also records which country its connection appeared to come from: the two-letter country code only, derived at our network edge and stored without the address it came from.

Attachments

Images and PDFs you attach to a message, kept so the assistant can read them again later in the same conversation. They are stored privately and served only to you and to the model answering you, never at a public URL.

Lead record

If a conversation or a booking surfaces a real project, a short record of it: the problem in your own words, how the decision would be made, a budget band, a timeline, the technical context, and, only if you offer them, a name and email for follow-up. Writing one sends a single notification to Nicolas, so a real project is seen by a person; nothing ever emails you. A record that never becomes a booking is deleted 12 months after the conversation last moves. One that does is kept as the record of that working relationship.

Scope note

If the assistant writes your problem up as a note you can share, the note itself: the problem in your words, an agreed first step, and, once Nicolas has reviewed it, his approach and its boundary. It lives at an unguessable link, and the link is the only key: anyone you forward it to can read it. The page counts when it is opened, which is how a forwarded note gets noticed. It follows its lead record: deleted with it, and with your account.

Voice calls

That a call happened, when it started and ended, which conversation it belonged to, and the address you called from. Audio is not recorded. The timings are what meter call time against your allowance, and the address is what keeps that allowance from resetting when a guest clears their cookies.

Phone number

Only if you verify one (it is optional, and raises your weekly call allowance). Verifying stores the number on your account, and a keyed digest of it in a ledger of numbers that have already claimed that allowance, so one phone cannot farm it across many accounts. The code is sent and checked by Prelude; no code is ever stored here.

Contact permissions

If you answer the “may call you” or “may message you on WhatsApp” checkboxes: every grant and every withdrawal, with the exact wording you were shown and when you answered. Asking permission creates its own record: it is the proof the permission existed. Both are optional, start unticked, and change nothing about your allowance.

Sessions

For each signed-in browser: IP address, user-agent string, and when it was created. Used to keep you signed in and to rate-limit abuse.

Running the assistant means your messages leave our servers. They are answered by a language model we do not host, and a voice call is carried and transcribed by infrastructure we do not own. Every company that touches your data on our behalf is named, with what it does and where it does it, on the processors page. Nobody outside that list receives it, and none of it is sold.

• Your conversations are not used to train AI models. They are stored only so the assistant remembers your context. This is enforced rather than promised: the account that reaches the model is set to zero data retention, so a provider that will not agree to keep nothing and train on nothing cannot be routed to at all: the processors page explains what that rules out.
• The assistant is software, not a person. It will tell you so if you ask.
• Nicolas can read a conversation: it is how a real project gets a considered follow-up rather than an automated one. Every such read is logged: which conversation, by whom, and when.
• Conversations and attachments are kept until you delete them or delete your account, whichever comes first. Sign-in sessions expire after 30 days of disuse. Guest accounts that are never signed into are deleted once they go quiet. A lead record that never became a booking is deleted, with its scope note, 12 months after the conversation last moves, where “moves” means you or Nicolas acting on it, not someone opening the shared link, so that nobody with the link can keep your record alive past its time.
• The only cookies we set are the ones that keep you signed in. There is no analytics, advertising or tracking on this site. The one exception is not ours: the booking calendar at the foot of the homepage belongs to Cal.com, and loading it lets them set their own cookies inside that frame. It loads when you scroll down to it, and nothing else on the site behaves that way.

A machine-readable copy of everything held about you, including the full text of every conversation, downloads in one click from your privacy settings. Conversations delete one at a time from Conversations, and deleting the account from Account takes every one of them with it. None of this goes through us, and none of it costs anything.

Deleting the account is honoured in full, and two things deliberately outlive it. Call records stay, with everything that pointed at you removed; they meter a shared monthly budget, and a deleted duration belonging to nobody is all that remains. And the keyed digest of a verified number stays: for 30 days it keeps the same phone from immediately re-claiming the extra allowance, and it is forgotten entirely after at most 400 days, a period set by our judgement of how long that abuse stays worth preventing, since no carrier publishes a number-recycling rule to anchor it to. The digest cannot be turned back into a number without a secret held apart from the database, and identifies nobody on its own, which is also why it is not in the export, where the number itself already is.

One more thing sits outside the delete button's reach for the ordinary reason email does: the single notification a lead record or scope note sent to Nicolas when it was written is a message in a mailbox, not a row in this database. Deleting the account deletes the record and the note themselves, but it cannot unsend that mail. It is treated as ordinary correspondence, and it is never used to contact you.

The GDPR also gives you the right to correction, to object to processing, and to restrict it. Ask by email and you will get an answer within a month. If that answer is unsatisfactory you may complain to the Belgian Data Protection Authority.

When this page changes, the date above it changes. Material changes to who processes your data are announced on the processors page before they take effect.