Security and privacy

You hand Thalamus your relocation plans and your documents. Here is the short version, without legal language: what we collect, what we never collect, where it lives and how we make money. The full wording is in the privacy policy.

What we collect

Your email and password, so you can log in. The password is stored as a hash — nobody sees it in the clear, us included.
Telegram sign-in, if you use it: your account number, name and photo from Telegram. Telegram never gives us your messages.
Your passkey, if you added one: the public part of the key, its name, and the dates it was added and last used. Your fingerprint and face stay on your device.
The "not a robot" check on sign-in is run by Cloudflare: it receives your IP address and browser data. The check stops robots from sending codes to other people's email addresses in bulk.
Your profile: name, city, where you are moving from and to, languages. That is what an expert is matched against.
Your goals and requests: what exactly you are asking for. A human works the request, not an algorithm.
A business's verification documents — license, registration. They sit in a private bucket; only the card owner and we can reach them.
A visit counter: the page address and the site you came from. No IP, no cookie, no identifier — that row cannot identify a person.
An action log: which filter you chose in the catalog, how far sign-up got, whether you pressed a contact on a listing. Codes and numbers only — no email, no text, nothing you typed into fields. That row cannot identify a person either.
A record of what we sent you: about what, through which channel and when. It shows what went out in our name and keeps us from writing twice.
Communities: where you belong and what you wrote in posts and comments. In a public community your posts are visible to everyone, including people who are not signed in; your name next to them is shown only to members of communities you share, and everyone else sees you as “member”. The same goes for your name in a mention and on a post from a Telegram group. A post you mark “show in Jobs” also appears in the Jobs section, without your name or contacts.
Follows: which authors and public communities you follow. Only you see the list — the author and the community owner do not know who follows them, and there is no follower count.
The course you teach: lesson texts and checklists, with your name and credential next to them. A published course is visible to everyone, including people who are not signed in.
The end-of-session check in Learning: only a mark that you answered it. The answers themselves are kept as a total count per option, without your name — nobody can tell who chose what, us included.
Your answer to “How did you hear about the cohort?”, if you gave one when joining a club: one option from a list. You and we see it; the club owner and members do not.

What we never collect

No third-party analytics: no Google Analytics, no pixels, no ad networks.
We do not sell data and do not pass it to advertisers.
We build no advertising profiles and score no one algorithmically.
Fonts are hosted by us. The map and the Telegram sign-in button load only after your click — before that not a single request goes to Google or Telegram.
No advertising or analytics cookies. There are technical ones — for signing in and choosing a language — and appearance cookies once you pick a theme, a color or a feed tab. That is why there is no consent banner.

Where the data lives

Database and files — Supabase, Paris region, European Union.
The site runs on Vercel (US), email goes through Brevo (France). Transfers outside the EEA are covered by the EU-US Data Privacy Framework and the European Commission's standard contractual clauses.
Notifications — about an answer to your question, about your request, about a matching position in Jobs, about new posts in your clubs — go through the channel you chose in your profile: Telegram or email. The choice is followed literally: we will not write anywhere else.
The Spain-residency checklist emails go only to people who ticked the box on the signup form. That list is kept separate from service email in Brevo, and one click in any of those letters unsubscribes you.

How we store your information

You delete your account yourself, with one button in the profile. Goals, requests and favourites go with it.
The «looking for work» card in Jobs you delete yourself, with a button. Introductions, recommendations about you, complaints about recommendations and restriction marks go when you delete the account — the 6-month limit does not apply to them.
Verification documents are erased 30 days after the decision. A daily job on the server does it — not a person's memory.
Visit-counter and action-log rows are deleted after 12 months, also on a schedule.
A request with no movement lives 24 months, then a monthly job on the server erases it along with the deal history. Any activity counts: a stage change, a note, a call, a task.
Reports and the decisions on them are erased 6 months after the decision, and the line about yourself next to “looking for company” — after the meetup. A daily server job erases both.

How we make money

Businesses pay — for a place in the catalog and for working the requests. It costs you nothing.
Ranking cannot be bought. There is no paid promotion in the catalog; if it ever appears, those cards will be labelled as ads.
Payments are switched off right now: the service runs as a test launch and no payment data exists on our side.

Found a vulnerability? Email us at hello@thalamus.community or leave feedback

Write to hello@thalamus.community. We answer within three working days.
Describe what you found and how to reproduce it. A screenshot helps.
What we ask: do not run load tests against the site and do not touch other people's accounts. There is no permission for that.
We do not pay for findings yet. We will name you in the credits if you want.