Privacy Policy

When you create a Collr account we collect your email address, the display name and handle you choose, and any profile content you add yourself — bio, avatar, cover image, theme choice, and the links you publish. We also record basic technical data needed to operate the service: sign-in timestamps, and aggregate page-view and link-click counts for your own profile’s analytics.

Account data is used to authenticate you, render your public profile, and show you analytics for your own links. We use your email address to send account-related mail — verification, password resets, and, if you contact us, replies to your message — and the event emails you keep switched on. Every optional email has a one-click unsubscribe, and the weekly digest starts only once you have confirmed it from your inbox. We do not sell your data to third parties.

Your profile page (name, handle, bio, avatar, and any links you add) is public to anyone with the URL once you publish it. Whether you appear in the community directory is a separate, opt-in setting you control from your dashboard. Your email address and sign-in activity are never shown publicly.

Your data is processed and stored on servers located in the European Union. This applies to all users regardless of where you are located. Your profile data, links, analytics, and account information never leave EU-based infrastructure.

Some third-party services we use (listed below) may process data outside the EU — for example, Stripe processes payment data in the US under the EU–US Data Privacy Framework. We only use services that provide appropriate safeguards for international data transfers.

We use a session cookie to keep you signed in and a CSRF token to protect form submissions. We don’t use third-party advertising or tracking cookies.

We keep your account data for as long as your account is active. You can delete your account yourself from Settings → Danger zone: that starts a 30-day grace period during which your profile is hidden and you can change your mind by signing in, after which the data is removed or anonymised and your handle is released. You can also contact us and we will process the request.

Suspended and banned accounts are the exception, and we keep them indefinitely. If we suspend or ban an account for breaching the community guidelines, we retain the account record — including the email address, the handle and the reason — for as long as necessary to keep that decision enforceable. A ban that can be erased by deleting the account and signing up again is not a ban, and the people it protects are other members. For the same reason, an account cannot be deleted while it is suspended or banned.

This is permitted under the UK GDPR, which is the law Collr operates under. Keeping a record of a banned account is processing necessary for our legitimate interests — protecting members from someone we have already removed — under Article 6(1)(f), and the UK GDPR expressly allows personal data to be kept for as long as that purpose requires rather than for a fixed period (Article 5(1)(e)). Your right to erasure under Article 17 is not absolute for the same reason: Article 17(3) allows a controller to refuse it where the data is needed for a purpose of this kind. We keep only what identifies a returning banned account — not the profile itself, which stops being visible to anyone — and we do not use it for anything else.

If you believe an account was banned in error, write to us and we will look at it. Your other rights over your data are set out above and are not affected, and you can complain to the Information Commissioner’s Office if you think we have this wrong.

We use a small number of third-party services to operate Collr. Each processes only the data necessary to provide its function.

Our mail servers are our own. Account email from Collr — verification, password resets, replies — is sent by a mail server we run ourselves, on the Worldstream server above; Amazon SES handles the rest, as described above. Email you send to a collr.app address, such as hello@collr.app, arrives at a mail server we also run ourselves, on the same machine, and no other company holds it.

Our bot protection is not one of them. The sign-up and contact forms ask your browser to solve a small puzzle before they will accept a submission, which is what keeps automated spam off them. It runs entirely on our own servers: nothing about you is sent anywhere else, no fingerprint of your browser is taken, and there is nothing to click or identify. This policy previously named Cloudflare Turnstile here — a service we described but never actually switched on. We have removed it and chosen a self-hosted method instead, so that visiting our sign-up page does not introduce you to a company you did not come here for.

Messages you send to our Telegram support bot are relayed live to the Collr team’s Telegram account so we can reply. We don’t store the message text itself in our database — only your Telegram chat ID, and, if you opened the bot from a link in your Collr account, which account it’s linked to, so replies reach the right chat. This data is used only to operate support, and kept only as long as needed to do so.

Your support messages pass through Telegram Messenger Inc.’s infrastructure (US/EU/Netherlands). Telegram does not offer Data Processing Agreements to bot developers. We minimise the data sent — only your chat ID and the support message text. No sensitive personal data should be sent via Telegram support.

This is the dedicated support line for Premium and Premium+ members and handles data the same way as the regular support bot above: message text is never stored in our database, only your Telegram chat ID and, if linked, the Collr account it belongs to — used to route replies and confirm your membership, and kept only as long as needed to provide support.

Collr posts to its own public Telegram channels: releases and new blog posts to the news channel, and a weekly round-up of what’s on to the events channel. Everything posted there is already public on this site — a release note, a blog post, an event listing — and nothing about a member, their account or their attendance is sent. Events marked as carrying explicit content are never posted, the same rule the site’s feeds follow.

The posting runs on our own server in the Netherlands. Following a channel is between you and Telegram: we are not told who follows, and we receive nothing about you from it. Reading a channel does not create a Collr account or connect to one you already have.

Questions about this policy or your data can be sent through our contact page.