Integritetspolicy

Privacy policy — English

Last updated 10 November 2026. The Swedish text above is the original; this is a translation of it.

In short

Klinq is for meeting up. You tell people you are out — a coffee, lunch, a glass of wine — and they can join you. Some of those people are friends you already have. Some you have not met yet.

That means we handle location data and profile data. The short version:

• Your exact location is shared only while a check-in is active, and only with people you have accepted as friends.
• When you post publicly, other people see an area, not your exact spot: the point is offset by 100–150 metres before it is stored.
• We never track you in the background. Your position is read at the moment you check in, and not otherwise.
• We do not sell your data and we do not run ads.
• You can download everything we hold about you, and delete your account and all of it, from inside the app.

1. Who is responsible

The data controller is Mikael Drenner, a private individual, Sweden. Contact: [email protected]. Klinq is run by an individual today; before the app is released publicly, responsibility moves to a company and this page is updated with its name and registration number.

2. What we collect, and why

Your account. Your email address, or the identifier we receive from Apple when you sign in with Apple, plus the username and name you choose. Legal basis: our contract with you.

Your date of birth. Klinq is for adults, and people you have not met need to know roughly who they are meeting. We store your date of birth and show other people only your age — never the date. You cannot change it in the app once it is set; write to support if it is wrong. Legal basis: our contract with you, and our obligation to keep under-18s off the service.

Your gender. Required when you sign up: woman, man, or other in your own words. It is shown as a small symbol next to your name and age, and it is used for the filters in Discover — nothing else. We ask because Klinq shows your profile to people you have not met, and your name, age, photo and that symbol are all anyone gets to know before you meet. It never leaves the app: not to analytics, not to advertising, not to anyone else. Legal basis: our contract with you.

Your check-ins. What you are doing, the time, the place if you selected one, your caption and photo if you added them, and your location. We store the location twice: the exact position, and an approximate one offset by 100–150 metres. Friends you have accepted see the exact position while the check-in is active. If you post publicly, everyone else sees only the approximate position and the place name. Once the check-in ends or expires, nobody but you can see it. The exact position is deleted within 24 hours of the check-in ending or expiring — a job in the database runs every hour and removes it; the approximate one stays with your history so you can look back.

Legal basis: our contract with you for friends-only check-ins; your consent for public ones. That consent is given one check-in at a time — never pre-selected, never carried over to the next — and you can withdraw it while a check-in is still running by setting it back to friends.

Plans. If you post something ahead of time we store the place or area, the time and what it is — the same data as a check-in, with a start time that has not arrived yet. If someone asks to join, we store who asked and your answer. Legal basis: contract.

Your profile. Bio, interests, profile photos and your favourite drink, if you add them. Visible to friends and to anyone who can see one of your public check-ins. Legal basis: contract.

Photos. We remove embedded metadata, including any GPS coordinates the camera recorded, on your device before the photo is uploaded. Our server checks as well, and refuses a picture that still carries a location. A photo you add to a check-in stays on your profile until you remove it, and never shows where you were: it carries the name of the place only if you chose one, never a position or a street address. You choose whether your profile photos are visible to friends or to anyone who can see your profile. Legal basis: contract; consent for the "everyone" setting.

Messages. Content and timing of messages you send. We do not read them except when acting on a report. They are not end-to-end encrypted. Legal basis: contract.

Klinqs. Who sent it, who received it, and which check-in it related to. The sender is never told that a Klinq was declined or ignored. Legal basis: contract.

Finding friends from your contacts. Optional, off by default. Your phone turns each number and address into an irreversible code and sends only those codes to us, where they are compared against people who chose to be findable. Codes that do not match are discarded immediately and never stored. Your contacts never leave your phone, and we never contact anyone in them. Legal basis: your consent, withdrawable in settings — withdrawing deletes your own code at the same moment.

The filters in Discover. Distance and age range are stored as a setting. If you also choose which genders to see, that is information about who you want to meet, and it is stored only with your explicit consent: it is empty until then, the app works without it, and it is never shown on your profile or to any other user. It never leaves the app — not to analytics, not to advertising, never to a third party. Legal basis: explicit consent.

Notifications. A device token from Apple. We keep notification content minimal — "someone you know is out" reveals less than a name and a place. Legal basis: contract.

Analytics. Anonymous usage events: which screens open, whether a check-in succeeded. No names, no location. You can turn it off in settings. Legal basis: our legitimate interest in understanding how the app is used.

Crash reports. When the app crashes we receive the technical details: what the code was doing, which version, which kind of device. We deliberately strip everything that could say who it happened to — no account identifier, no IP address, no device name, no log lines, and no coordinates. Legal basis: our legitimate interest in finding and fixing faults that affect the people using Klinq.

Safety and abuse. Reports, blocks, and limited technical logs, including the counters that stop someone sending a hundred codes or signals in a row. If we are investigating a report we may keep the material involved until the investigation is finished, even if the account is deleted. Legal basis: our legitimate interest in keeping people safe, and our legal obligations.

3. What we never do

• We do not read your location in the background, or when the app is closed.
• We do not sell your personal data.
• We do not run advertising, and we do not build advertising profiles.
• We do not share your exact position with anyone who is not an accepted friend.
• We do not upload your address book.
• We do not show your date of birth to anyone.

4. How long we keep things

Every row with a clock on it is a job in the database. The two that are about a day run every hour, precisely so that "within 24 hours" is true rather than approximate. The longer periods are cleared nightly.

5. Who we share data with

Each provider is bound by a data processing agreement and may only act on our instructions: Supabase (database, accounts, photo storage and the email carrying your sign-in code; EU, Frankfurt), Google (place search; global), Expo (push notifications; United States), PostHog (anonymous analytics; EU), Sentry (anonymous crash reports; EU), Apple (sign-in, if you use it; global) and Cloudflare (serving this website; global).

The place search at Google: Google receives the coordinates of where you are standing at that moment, and the text you typed if you searched — never your name, your username or anything about your account. The call is made from our server, not from your phone, so Google sees neither your IP address nor your device.

This website uses no cookies, no JavaScript and no tracking. Cloudflare, which serves the page, sees your IP address in its operational logs, as every web server does.

Status on 10 November 2026: analytics (PostHog) and crash reporting (Sentry) are not switched on in the version of the app that exists today — no key is configured, so nothing is sent to them. They are listed because they are turned on before the App Store release. The email carrying sign-in codes is sent by Supabase today; before external testers are invited we move to a dedicated email provider inside the EU (Resend) and update this list.

We may also disclose data if the law requires it, or to protect someone's safety.

6. Your rights

You can ask us for a copy of your data, correct it, delete it, restrict how we use it, or send it to another service. You can object to processing based on legitimate interest, and withdraw any consent you have given — withdrawing is as easy as giving it.

Most of this works inside the app, under Profile → Settings: Download my data gives you one file with everything we hold, in a format another service can read, and Delete account removes all of it, photos included — see the support page for the steps. You can also edit your profile, turn off public mode for a check-in that is already running, and turn off contact matching. For anything else, write to [email protected]; we answer within one month.

If you think we are handling your data wrongly you can complain to your national data protection authority. In Sweden that is Integritetsskyddsmyndigheten (IMY), imy.se.

7. Age

Klinq is for people aged 18 and over. We ask for your date of birth when you sign up and we do not create accounts for anyone under 18 — the limit is enforced in the database, not only in the app. We cannot verify that what you tell us is true, so we do not claim that ages on Klinq are verified. If we find out someone under 18 has an account, we delete it.

8. Security

Who can see what is decided in the database itself and checked on every single request, rather than trusted to the app. Photos live in private storage reachable only through short-lived links. The offset that makes public positions approximate is derived with a secret that never leaves our servers. Traffic is encrypted in transit. No service can promise it will never be breached; if a breach affects you and the risk is serious, you will hear it from us.

9. Changes

If we change this policy in a way that matters, we will say so in the app before the change takes effect. The date at the top is always the version in force.