Privacy Policy

We collect what you give us, and a little that running the site needs:

• Your account: your email address, your name and handle, and your password, which we store only in a scrambled form we cannot read back.
• Your page: your bio, photos, cover and logo, your links, how your page looks, your about page (pronouns, the town you are based in, time in the scene and your answers), and your badges.
• Who you are on Collr: the parts of the scene and roles you pick, the people you add as relationships, your packs and groups, who you follow and connect with, and vouches you give.
• What you do on Collr: events you list, go to or follow, corrections and reports you send, saved searches, blog pieces if you write for us, and messages you send us.
• Your settings: email and notification choices, display and accessibility options, and your calendar link if you turn it on.
• Payments: whether you subscribe and to which plan. Your card details go to Stripe and never reach us.
• Telegram: your Telegram account number, if you link Telegram to Collr.
• Keeping your account safe: when you signed in, the IP address and browser of each signed-in session, and the IP address behind changes to your account, such as changing your email, so you and we can spot something that was not you.
• Your page’s analytics: counts of visits to your page and taps on your links, with where the visit came from. We do not record who the visitor was.

Some of this is sensitive, and the next section says how we look after it.

Being a pup, wearing leather, going to a Pride or calling somebody your handler is not a statement about your sex life, and Collr never treats it as one. A non-sexual account exists so you can say so outright. Collr never asks about your sexual orientation or your health.

UK data protection law looks at what information could reveal rather than what you meant by it, and asks for extra care with anything that could be read as being about somebody’s sex life, sexual orientation or health. It calls this special category information. So we give the extra care to all of these, whichever way you mean them:

• the parts of the scene and the roles you pick, and the ones you show on your page;
• the people you add as a partner, handler, pup, sir, boy, mistress or sub;
• the events you say you are going to;
• whether an account is marked non-sexual, and which of your accounts belong together;
• photos you mark as explicit;
• the “Tests regularly” badge, if you choose to show it.

We hold this only because you add it, and you can remove any of it whenever you like from your dashboard. The link between your accounts ends when you close the extra account. We rely on your explicit consent to hold it. For your communities, roles and relationships you give it by ticking a box the first time you add one; for the rest, by adding it. You take it back by removing it. Where you put it on your public page, you have chosen to make it public.

Some of it is never shown to anyone. Collr counts how many people are going to an event but never names them. Nothing public links your accounts to each other: only Collr can see that, so that one person cannot hold more accounts than the rules allow. Member profiles are kept out of search engines. We never use any of this for advertising, and we never sell or share it.

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, profile picture, 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. While an account is suspended, we keep it as it is, so it can be given back. A ban can be reviewed for 30 days (bans made before 22 October 2026 were given a fresh 30 days from that date); after that, or sooner if we decide the ban is final, it becomes permanent and we remove the account the same way as a deleted one. For the same reason, an account cannot be deleted while it is suspended or banned.

After a permanent ban we keep only what stops the person joining again: a scrambled, one-way fingerprint of their email address (and of the usual variants of it), a fingerprint of their Telegram account, the fingerprints our payment provider gives for the cards they paid with (never the card itself), and their old handle, which nobody can take again. A fingerprint can be compared with a new sign-up, but it cannot be turned back into the address, the account or the card. So that our moderators can still tell which account was banned and why, we also keep the account’s member number, the reason we gave for the ban and when it was made and made final; none of that is public. Events they added stay listed without their name, and anything they wrote for the blog stays as a Collr community piece with no writer named. Everything else about them is removed.

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 use the fingerprints for nothing except recognising a returning banned account.

If your account is suspended or banned, you can still sign in to download your data and ask us to review it through the support desk. If you believe an account was banned in error and can’t sign in, 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 Collr’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.