Cookie Policy

1.1 Definition

A cookie is a small file that a site stores in your browser so it can recognise it on the next request. Browser local storage and session storage do similar jobs.

1.2 Our approach

We set only what the service needs to work. There are no third-party trackers, advertising pixels or external analytics systems in the service.

2.1 What happens if you delete them

Your session ends: you will need to sign in again and pick your language, theme, colour and feed tab again. Nothing else breaks.

3.1 This data stays on your device

Browser storage contents stay on your device. We do not receive them and keep no copies, so clearing browser data deletes them permanently: ticks, notes, your identity map, Studio materials. They do not exist on another device or in a private window.

3.2 What reaches the server

Only what you send yourself. A note “in your own words” becomes a club post when you press publish in the feed. From the return mark we receive only the fact of a return, as described in 5.2.

4.1 Maps

The map on a provider page loads only after you press the button. Before that press not a single request goes to the map service. After it, Google receives your IP address and may set its own cookies under its own rules.

4.2 Payments

We take no payments at the moment: there are no checkout pages and no payment-provider cookies on the service. When payments are switched on, those cookies will be described here before the first payment.

4.3 The Studio tool

The Studio tool opens in an embedded frame from studio.thalamus.community. It sets no cookies: authentication works through a temporary token and data lives in local storage.

4.4 Anti-bot check

The sign-in and sign-up forms carry a Cloudflare “not a robot” check. It is technically necessary and loads together with the form, so Cloudflare receives your IP address and browser data before you press anything, and may use its own cookies under its own rules. The check protects the forms from automated requests: without it a robot could send confirmation codes in bulk to other people’s email addresses. The mark it issues lives for five minutes and is accepted once.

4.5 The Telegram sign-in button

The Telegram sign-in button is ours. Not a single request goes from this page to Telegram, and Telegram does not know you opened our sign-in form. Pressing it takes you to Telegram’s own site: you confirm the sign-in there, and there Telegram sees you under its own rules. Until 20 September 2026 this place held Telegram’s own button embedded in our page. Telegram moved sign-in to a new protocol and we moved with it — no third-party code runs on this page at all now.

5.1 What is collected

We count anonymous page views: the browser sends the address of the page you opened, the host you came from, for example t.me, and a campaign tag if you followed one of our tagged links. The tag is a channel name such as “telegram”; anything else is stripped from it on arrival. No cookies, no IP address, no identifier.

In the same way we record actions on the pages: filters chosen in the catalog and the number of listings found, sign-up steps and the reason a sign-up did not go through, a press on a contact in a provider’s listing. The record holds codes and numbers; no email, no text, nothing you typed into form fields. Along with the record the browser reports one flag: whether a program is controlling it. The browser sets this flag itself, and we need it to keep our own automated site checks out of the statistics.

5.2 Return marker

To see whether people come back, the browser keeps a list of the dates you visited — up to the last sixty. That list stays on your device and never reaches us. All we receive is the fact itself: “came back on a second separate day” and “came back in a second separate week”, together with their count.

5.3 Why it needs no consent

The records cannot single out a person, so they are not personal data. Everything described in this section is first-party audience measurement: at the page’s request the browser reports a page view, an action and the flag from section 5.1, and it keeps the list of dates from section 5.2 on the device. The AEPD guidance on audience measurement tools exempts such counters from consent provided the data serve only the site’s own anonymous statistics, are not matched with other data, are not passed to third parties, and are described here. These data are shared with no one.

5.4 Retention

Rows older than 12 months are deleted automatically on schedule. The list of dates in the browser keeps up to the last sixty visits and is removed together with the site data.

6.1 In your browser

Cookies and local storage are cleared in browser settings, under privacy and site data. The same place lets you block cookies for a single site — sign-in will then stop working.

6.2 Maps

To take back the permission to load maps, clear the site data in your browser: the confirmation button will appear again. Clearing site data also erases everything else listed in section 3.

6.3 Questions

Questions about cookies and storage: hello@thalamus.community. How personal data is processed is described in the Privacy Policy.