Privacy Policy

Effective date: 24 September 2026 · Last updated: 24 September 2026

Klack is a scorekeeping app for the game of Mölkky, published by Suuntio (“we”, “us”), based in Finland. This policy explains what data Klack handles, why, and what control you have over it. It also covers the klack.club website and its live-screen page (section 3.10).

The short version: Klack works on your device by default. You do not need a Klack account, and there is no advertising, no analytics, and no third-party tracking. Data leaves your phone in three cases: when you choose a feature that needs it (sharing a game or joining one, streaming a game to a live screen, backing up to the cloud, subscribing to Klack Pro, creating a Klack account, or moving your data to a new phone), when the app sends us a crash report, which you can turn off in Settings, and once in the background, when the app first reaches the network and creates the random player identifier described in section 3.1.

Creating a Klack account also sets up your Klack profile: a username, your name and an initials avatar that other Klack users can see. While you have a profile, your app also keeps a summary of your own statistics (your stat card) and a list of the Klack players you have played with up to date on our servers, so that your friends and the people you play with can see how you are doing. By default, your friends and the people you have played with can see your profile and statistics; you choose who can in Settings → Privacy (sections 3.11–3.15). Your games themselves stay on your phone.

1. Who is responsible for your data

Suuntio
Business ID (y-tunnus): 3634040-2
Louhentie 13 D 32
02130 Espoo
Finland
Email: support@klack.club
Phone: +358 45 869 1204

Suuntio is the data controller for the personal data described in this policy, within the meaning of the EU General Data Protection Regulation (GDPR).

2. Data stored on your device only

By default, everything Klack records stays on your phone in a local database. None of it is transmitted anywhere unless you use one of the online features described in section 3:

• Games you have played: throws, scores, rules used, timestamps, outcomes
• Your player roster and saved teams: the names you give the people you play with
• Statistics and skill ratings derived from those games
• App settings: language, theme, and your own display name

This data is not accessible to us. If you delete the app without ever using an online feature or creating a Klack account, this data is deleted with it and no copy exists anywhere else.

If you have a Klack profile, some of this is published: your own display name appears on your profile (section 3.11), and a summary of your own statistics and your skill rating is published as your stat card (section 3.13), together with the Klack user ids of the people you have played with (section 3.14). Your games, their throws and your roster are not part of either.

Your phone also keeps what other Klack users share with you, such as their profile names and stat cards, so the app keeps working offline (section 3.13).

3. Data processed when you use online features

Klack’s online features are optional and user-initiated, and the data described in sections 3.2–3.7 and 3.9–3.17 is processed only when you use one. Two things happen without you choosing a feature: the app creates its pseudonymous device identity in the background the first time it can reach the network (section 3.1), and it sends crash reports unless you switch them off (section 3.8). Beyond those, no personal data is sent to our servers unless you use a feature that needs it. The Klack profile is one such feature: once you have one, your app keeps your stat card and played-with list up to date by itself, after games and when you open the app (sections 3.13 and 3.14).

3.1 Pseudonymous device identity

The first time the app can reach the network, Klack automatically creates an identifier for your device in the background: a random UUID. It carries no name, email, device fingerprint, or advertising identifier, and it is not derived from anything about you or your hardware.

This identifier exists so that a person can be recognised across games and devices: it is how your history follows you, and how the app knows that “Anna” on your friend’s phone and “Anna” on yours are the same player. Because its purpose is to recognise a person, it is pseudonymous personal data in GDPR terms, not anonymous data. We refer to it in the app as your Klack user id.

• Purpose: enabling multiplayer, player identity, subscriptions, backup, and, with a Klack account, the profile and friends features
• Legal basis: legitimate interest (GDPR Art. 6(1)(f)) in providing a functioning app; for the features you actively choose, performance of a contract (Art. 6(1)(b))
• Retention: signing out or reinstalling the app discards the identity from your device, and the app starts over with a fresh one. That alone does not delete the server-side record of the old identity, or its appearances in games other players have recorded; section 7 describes exactly what deletion covers. Deleting your Klack account deletes the identity and every record we hold that belongs to it.

The app is fully usable if this identity is never created, for example if the device is permanently offline.

3.2 Sharing a game

When you share a game, or join a game someone else shared, the following is sent to our backend:

• A game record (its rules, its status, and a short join code)
• The list of participants: their Klack user ids and the display names they chose, and in a team game, the teams and who plays in each
• An ordered log of the throws recorded during the game, and the final result
• Skill-rating values reported by participants, so ratings can be settled
• Whether a participant chose to rate their own throws themselves (a yes/no flag; the ratings themselves stay on that participant’s phone)

This serves two things: while the game is running, participants can follow the score in real time, and once it ends, the finished game is delivered to every participant so it lands in each player’s own history. The data is readable only by the people who are members of that game session, including any live screen the host paired (section 3.10).

• Purpose: delivering the shared-game features you requested: live score following during the game, and delivery of the finished game to its participants afterwards
• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: the relay record of a shared game is kept until the Klack identity that recorded it is deleted (section 7), which removes the game, its throws, and its participant list together. We do not yet run an automatic clean-up of finished games on the relay; when we introduce one, we will update this policy with the retention period it applies. Only session members can read the record at any time.

3.3 Creating a Klack account

A Klack account is optional. It makes your player identity durable: your name, statistics and skill rating stay yours across your devices and in games other people record. It is also what cloud backup attaches to, and it comes with your Klack profile (section 3.11). A Klack Pro subscription does not need an account (section 3.6). Every local feature of Klack (scoring, history, statistics, ratings, the roster) works with no Klack account.

If you create one, we process:

• Your email address, if you sign up with email and password
• The identifier supplied by Apple or Google if you use their sign-in. With Sign in with Apple you may choose Apple’s private relay address, in which case we never see your real email address.
• An encrypted password hash, if you use email and password

Before an account exists. When you type an email address on the sign-in screen, the app asks our backend whether a Klack account already uses that address, so it can show you either sign-in or sign-up. That check returns a yes/no answer. It stores nothing and does not log the address.

We use your email address only to authenticate your Klack account and to send essential service messages: a one-time code to confirm your address, to confirm an address change, and to reset your password. These messages are delivered by our email processor, Resend (section 5). We do not send marketing email. Your email address is never shown to other Klack users.

• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: until you delete your Klack account

3.4 Cloud backup of your games (Klack Pro)

If you are a Klack Pro subscriber with a Klack account and you switch on backup, your completed games are uploaded to your private cloud library: the game’s rules, its players’ names and Klack user ids (and its teams, in a team game), the throws, the final scores and the resulting ratings. Only you can read your library: it is protected at the database level by row-level security keyed to your Klack account.

Restoring your own games from the cloud is always free and remains available even if your subscription lapses.

• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: for as long as your Klack account exists. If your subscription lapses, your cloud games are retained for a further 6 months and then deleted by an automatic daily sweep; we warn you in the app, with the date, before this happens. Deleting your Klack account deletes them immediately.

3.5 Push notifications

If you accept notifications, your device’s push token is stored against your Klack identity (your account, or the pseudonymous identity of section 3.1) so we can notify you. Klack never asks for notification permission at launch: it asks only after you first confirm an invitation or join a hosted game, and only after explaining why.

We send four kinds of notification:

• Game invitation: someone added you to a game. You get none from a person you have blocked (section 3.16).
• Session ended: a session you were watching has finished, so your copy of the game is ready
• Throw ready to rate: for Klack Pro members who chose to rate their own throws during a shared game, a prompt that one of their throws is waiting
• Friend request: another Klack user sent you a friend request. The notification names them by their profile’s display name. Each request is announced once; accepting, declining or removing a friend sends no notification to anyone.

The app may also schedule a reminder on your device to finish rating your throws. That reminder is created and shown locally and never leaves your phone.

Notifications are delivered through Expo’s push service and then by Apple or Google’s platform push service. We send no promotional notifications. Declining permission breaks nothing: invitations, finished games and friend requests still reach you inside the app.

• Legal basis: consent (Art. 6(1)(a)); you may withdraw it at any time in your device settings
• Retention: until you revoke permission, delete your Klack account, or the token becomes invalid (invalid tokens are removed automatically)

3.6 Subscriptions

If you purchase Klack Pro, the purchase itself is handled by Apple or Google. We never see or receive your payment card, billing address, or any financial details. You do not need a Klack account to subscribe. Cloud backup is the only Pro feature that needs one.

To know whether your subscription is active, we process, via RevenueCat, a purchase record: your subscription status, product, purchase and expiry dates, whether you are in a free trial, and the platform. RevenueCat identifies you by an app-user identifier. If you have no Klack account, that identifier is a random value RevenueCat assigns; our backend records your entitlement against your pseudonymous Klack identity (section 3.1) and stores the RevenueCat identifier next to it. If you sign in to a Klack account, the identifier becomes your Klack account id, so your subscription follows you to your other devices. RevenueCat’s SDK also collects a device identifier by default (on iOS, Apple’s identifier for vendor, IDFV) to tell devices apart. The record carries no name, email, or payment details, but because it is linked to your identity it is pseudonymous personal data, not anonymised data.

Our backend also uses your entitlement for one social purpose: the Klack Pro numbers on your stat card are shown to other users only while your subscription is active (section 3.13). Other users never see your subscription details.

Both plans may begin with a free introductory trial. Whether you are eligible is decided by Apple or Google, and the app asks the store before it shows you a trial. We keep no record of our own about who has used a trial.

• Legal basis: performance of a contract (Art. 6(1)(b)) and compliance with legal obligations (Art. 6(1)(c))
• Retention: for the life of the subscription and thereafter as required for accounting and tax purposes

3.7 Camera

Klack can scan a QR code to join a game, to pair a live screen, to move your data to a new phone, to claim your history, or to add a friend by their friend code. The camera feed is processed live on your device and is used only to decode the code. No image, video, or frame is ever stored, transmitted, or retained. Camera access is optional; a join code can also be typed in by hand, the phone’s own camera app can read the live-screen code, and a friend can be added by username instead.

3.8 Crash and error reports

When Klack crashes or hits an unexpected error, it sends a diagnostic report so we can find and fix the problem. This is on by default and can be switched off at any time under Settings → Privacy → Send crash reports. Switching it off stops reporting entirely: the app does not collect reports and hold them back; it does not start the reporter at all.

A report contains the error and where in the code it happened, your app version, the over-the-air update your app was running, your device model and operating system version, and your pseudonymous Klack identifier (section 3.1).

A report never contains player names, scores, game records, your statistics, your email address, or anything you have typed. Reports are processed by Sentry, on servers in the European Union (Germany).

• Legal basis: legitimate interests (Art. 6(1)(f)): keeping the app working for the people who use and pay for it. You can object at any time by switching the setting off.
• Retention: 30 days, after which reports are deleted automatically

3.9 Moving your data to a new phone

Klack can move everything on your phone to a new phone by showing a QR code on the old phone and scanning it with the new one. This is free and needs no account. To do it, the old phone uploads a snapshot of its local data to our backend: your games, the game in progress if any, your roster and its ratings, your session names, your settings, and your Klack user id. The snapshot never contains your sign-in credentials.

The snapshot is stored in a private bucket that no app can read directly. Only the phone that scans the code can fetch it, once. It is deleted as soon as the new phone confirms the import, and in any case it expires 30 minutes after it was created; expired snapshots are swept automatically within minutes. The old phone keeps all its data.

• Purpose: moving your history to a new device you choose
• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: until the import completes, and at most 30 minutes

3.10 The klack.club website and the live screen

The klack.club website is a static site. It sets no cookies, runs no analytics, and contains no trackers. If you choose a language on the site, that choice is remembered in your browser’s own storage and is never sent to us.

The live screen (klack.club/live) turns a browser, for example on a tablet or TV beside the pitch, into a read-only scoreboard for a game you are scoring in the app. When you open it:

• The browser creates its own pseudonymous identity with our backend, of the same kind as the one in section 3.1, and keeps its session in the browser’s storage.
• The page requests a pairing code from our backend. We store only a hash of it. An unpaired code is valid for 10 minutes and is then replaced.
• When the host scans the code from the app, the browser is added to that game session as a screen member. It then reads the same game data the participants see (section 3.2): player names, throws, and scores. It writes nothing.
• The page’s address becomes a stream link. Anyone who has that link can open the same scoreboard until the host stops the stream or ends the session. Share it only with people you want to see the game.

Pairing a live screen requires the host to hold a Klack Pro entitlement. The website’s hosting provider records the IP address of visitors in short-lived request logs (section 5).

• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: the screen’s membership row is part of the shared-game record and follows its retention (section 3.2). The browser’s own identity stays in that browser until its site data is cleared.

3.11 Your Klack profile

When you create a Klack account, the app asks you to choose a username and sets up your Klack profile: the identity other Klack users see. (A Klack account created before profiles existed is invited to set one up and may skip it.) The pseudonymous identity of section 3.1 never has a profile: without a Klack account, there is no profile or stat card of yours for other users to see.

Your profile holds:

• Your username, which you choose: 3–20 lowercase letters, digits or underscores, unique across Klack. The app suggests one based on your name or your email address, and you can change it at any time by tapping it on the You tab. When you change it, the old one is released at once for anyone else to take.
• Your display name: the name you gave yourself in Klack. It is one name, kept in step, so renaming yourself in the app renames your profile too. Other people will see it, so use a name you are comfortable sharing.
• Your avatar: your initials on a colour the app picks for you. Klack does not offer photo avatars.
• Your friend code: a random code, created the first time you open Show my friend code, which your friend QR code carries instead of your username. It does not change. If it has spread further than you meant, contact support@klack.club.
• Your visibility setting (section 3.12), and when the profile was created and last changed.

When you choose a new username or display name, our backend checks it against a short list of offensive words, in English and Finnish, and refuses a name that contains one. Names already stored are not checked again.

Your username, display name and avatar together are your profile summary. Other Klack users see it as your visibility setting allows (section 3.12): on your player card in their app, in their Friends screen and on friend leaderboards. Someone who knows your exact username can look you up, but only if your setting admits them; there is no search by partial name and no list of users, and every lookup is counted against a limit (section 3.17). Anyone who scans your friend code in the app sees your profile summary whatever your setting, unless you have blocked them (section 3.16), so show it only to people you want to hear from. Your email address and sign-in method are never part of your profile and are never shown to other users.

• Purpose: giving you an identity other Klack users can recognise and add as a friend
• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: until you delete your Klack account. Signing out keeps it, and signing back in restores it. Only your current username is stored in your profile.

3.12 Who can see your profile and statistics

You choose who can see your profile summary and your stat card (section 3.13) under Settings → Privacy → Who can see my stats:

The default is “Friends & people I’ve played with”. The profile setup step tells you so and where to change it. It means the people who have finished a game with you in Klack can see your profile and statistics without you adding them as friends. If you would rather they did not, choose Friends or Only me.

At every setting:

• Only people signed in with a Klack account can see another user’s profile or statistics. A device without a Klack account sees no one.
• Your setting is enforced on our servers, not by the app, every time someone asks. Another user’s app can ask only about a person it already knows of, by username, friend code or Klack user id; nothing can be listed or browsed.
• Two things you do yourself show your profile summary whatever your setting, though neither shows your statistics on its own: sending someone a friend request (they see your name and avatar while it waits for their answer), and letting someone scan your friend code.
• A person you have blocked cannot see your profile or statistics at all (section 3.16).

A change takes effect the next time anyone asks. Lowering your setting deletes nothing: your profile, stat card, played-with list and friendships stay on our servers, hidden, and are visible again if you raise it. To remove them, delete your Klack account (section 7). Other users’ apps keep a copy of what they last received, so they work offline; a stat card you no longer share with someone is removed from their app the next time it asks for it, though a friend’s Friends screen may keep showing the name it last received for you.

• Purpose: letting you decide who sees your profile and statistics
• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: stored with your profile, until you delete your Klack account

3.13 Your stat card

While you have a Klack profile, your app computes a summary of your own statistics on your phone and publishes it to our servers as your stat card, so that the people your visibility setting admits can see how you play. It contains:

• for each of four groups of your games (official-rules games, all individual games, games under the I.M.O. tournament rule, and team games): the number of games and the same summary numbers your own statistics screens show you, such as throws, points, time played, hit rate, points per throw, five-throw finishes, faults and elimination rate
• your skill rating: its value, its uncertainty and the number of rated games
• when it was published, and which version of the app’s statistics and rating calculations produced it

If you have recorded throw details for the Klack Pro statistics, five more numbers travel in a separate record: your single-skittle attempt rate, and your results broken down by throw quality, distance, blocker and style. Other users can see them only while you have an active Klack Pro subscription; when it lapses they are hidden automatically, and they are shown again if you resubscribe.

A stat card never contains a game, a throw, the score of a single game, or the names of the people you played with. Your games stay on your phone.

When it is published. Your app publishes an updated card after you finish a game (once for a run of games, after a short pause), when you open the app with an update waiting, when you change your visibility setting, and after an app update that changes how statistics are calculated. Games that reach your history another way (a shared game you joined, a restore from your cloud library, a phone transfer), and games you edit or delete, also update it. There is no separate switch for publishing; to keep your card from being seen, choose Only me. If you use Klack on more than one phone, a phone that holds fewer of your games does not replace a card published from more of them. The numbers are computed by your phone and published as they are: we do not check them, and we do not have your games to check them against.

Who reads it. Klack account holders your setting admits see your card on your player card in their app, in their Friends screen, and on friend leaderboards, which their app ranks on their own phone. Their app keeps the last card it received so it works offline. Head-to-head records between two players are computed on the viewer’s phone from the viewer’s own games and are never sent to us.

• Purpose: showing your statistics to the people you choose, on friend profiles, player cards and friend leaderboards
• Legal basis: performance of a contract (Art. 6(1)(b))
• Retention: only your latest card is kept, until you delete your Klack account. Signing out or choosing Only me does not delete it.

3.14 Your played-with list

Beyond your friends, who can see you at the default setting is decided by your played-with list. While you have a Klack profile, your app publishes it together with your stat card: the Klack user ids (section 3.1) of the other people in the completed games on your phone who have one, whether the game was shared live or entered by hand with a linked roster entry, team-mates included, each with the date you last finished a game together. It keeps at most the 500 most recent. It contains no names, no games and no scores.

The list only ever widens who can see you; it gives you no access to anyone else’s data. No one else can read it, including the people on it. Our servers use it only to answer one question: may this person see this profile?

Each of your phones adds to the list, and an entry is not removed when you delete a game, because one phone cannot tell which games your other phones hold. To stop the list from widening who sees you, choose Friends or Only me. An entry is removed when the person it names deletes their Klack account or blocks you.

It is also about other people. The list records that someone played with you and when you last did. For the people on it, we process this on the basis of legitimate interests (Art. 6(1)(f)): letting people who have actually played together see each other’s Klack statistics without first swapping usernames, which is what both you and they get from it. We keep it to the minimum this needs: a pseudonymous identifier and a date, which the games on your phone already hold. No one can read it, and it gives the people on it nothing except the view of your profile your setting allows. Someone who plays without a Klack account gets nothing from it unless they later create a Klack account under the same identity. To take yourself off someone’s list for good, block them: open their player card and choose ⋯ → Block. The block removes you from their list and keeps you off it (section 3.16). If you think you should not be on someone’s list, you can also object (section 7).

• Purpose: deciding who may see your profile and stat card at the “Friends & people I’ve played with” setting
• Legal basis: for you, performance of a contract (Art. 6(1)(b)); for the people on the list, legitimate interests (Art. 6(1)(f)), as explained above
• Retention: until you delete your Klack account; only the 500 most recent entries are kept, and an entry is removed when the person it names deletes their Klack account or blocks you

3.15 Friends

You can add other Klack users as friends in the Friends screen, which you open from the You tab. A friendship exists only when one of you sends a request and the other accepts. You can send a request by typing someone’s exact username, by scanning their friend code in the app, or from the player card of someone whose profile you can see, including the people you have played with, whom the Friends screen suggests from the games on your phone. A request by username, from a card or from a suggestion reaches someone only if their visibility setting admits you. There is no way to add someone by an identifier, and no directory of users.

For each request or friendship we store the two Klack user ids, whether it is pending, accepted or declined, and when it was sent, answered, withdrawn and announced by notification. Only the two people involved can see it; your friends list is visible to no one else.

• Sending a request shows the person you asked your profile summary while they decide, and notifies them if they allow notifications (section 3.5). It does not show them your stat card unless your setting admits them. You can cancel it at any time.
• Declining is silent. The sender is not told, and the request keeps looking pending to them until they cancel it. Once they cancel a declined request, they cannot send you another one until 30 days after you declined it. To make that pause work, we keep the declined request and its date, shown to neither of you, and we delete it automatically once the sender has cancelled it and 30 days have passed since you declined it.
• Removing a friend is silent too, and either of you can do it at any time.
• Blocking someone (section 3.16) ends your friendship and every open request between you, in both directions.
• Limits: a Klack account can send at most 20 requests in 24 hours and have at most 50 waiting for an answer (section 3.17).
• Leaving Klack: if a friend deletes their Klack account, your app shows once that they left Klack, with the name it last had for them, until you dismiss it.

The suggested people you have played with are shown with their profile summary when their visibility setting lets you see it, and otherwise with the name they had in your game.

• Purpose: the friends features you use: requests, your friends list, friend profiles and friend leaderboards
• Legal basis: performance of a contract (Art. 6(1)(b)). Keeping a declined request rests on legitimate interests (Art. 6(1)(f)): protecting the person who declined. The kept request keeps the decline silent, because the sender sees it as pending until they cancel it, and it holds the 30-day pause against repeated requests.
• Retention: a pending request until it is answered or cancelled; a friendship until either of you removes it; a declined request until the sender has cancelled it and 30 days have passed since you declined it; it is then deleted automatically. Deleting your Klack account removes every request and friendship you are part of.

3.16 Blocking

You can block another Klack user from their player card: open the ⋯ menu and choose Block. You need to be signed in to a Klack account, but you do not need a profile. A block applies whatever your visibility setting (section 3.12):

• It ends your friendship, if you have one, and every open friend request between you, in both directions.
• The person you blocked can no longer find you by username or see your profile and statistics, and cannot send you a friend request by username, from a suggestion or with your friend code.
• It takes you off their played-with list (section 3.14) and keeps you off it.
• Their game invitations no longer reach you, and neither do notifications about them (section 3.5).

They are not told. To them, you look like a profile they are not allowed to see, the end of a friendship looks like an ordinary removal, and an invitation they send you looks like one you have not answered yet.

You can see your blocks and undo one under Settings → Privacy → Blocked people, or from the person’s player card (⋯ → Unblock). Unblocking does not bring back a friendship.

The same menu also offers Report. It opens an email to support@klack.club in your own mail app, with the person’s username (or the name on their card), their Klack user id and your app version filled in, so we can find the account. The app sends nothing itself: nothing reaches us unless you send the email.

Your block list. For each block we store your Klack user id, the Klack user id of the person you blocked, and the date: this is your block list. It holds no names. Only you can read it; the people on it cannot. Our servers use it only to enforce your blocks.

It is also about the person you block. The block list records that you blocked someone and when. For them, we process this on the basis of legitimate interests (Art. 6(1)(f)): protecting users from unwanted contact. We keep it to the minimum this needs, a pseudonymous identifier and a date, and it is never shown to them.

• Purpose: letting you stop unwanted contact from another Klack user
• Legal basis: for you, performance of a contract (Art. 6(1)(b)); for the person you block, legitimate interests (Art. 6(1)(f)): protecting users from unwanted contact
• Retention: until you unblock the person, or until one of you deletes your Klack account

3.17 Abuse-prevention counters

To stop guessing and spam, our backend counts some attempts per Klack identity: username and friend-code lookups (at most 30 in 10 minutes; choosing a username that is already taken counts too), friend requests (at most 20 in 24 hours), and attempts to use join codes and phone-transfer codes. Each counter holds only your Klack user id, a number of attempts, and when the current counting period began. It does not record what you looked up, which code you tried, or whom you asked, and no app can read or change it.

• Purpose: protecting Klack users and the service from guessing, the harvesting of usernames, and spam
• Legal basis: legitimate interests (Art. 6(1)(f)) in keeping the service secure
• Retention: deleted automatically one day after the counting period began (two days for friend requests), and at once when your Klack account is deleted

4. What Klack does not do

To be explicit, Klack contains:

• No advertising and no ad networks
• No analytics, telemetry, or attribution SDKs. Klack does send crash reports (see section 3), which are not analytics: they record that something broke and what the device was, never what you did, who you played with, or how you scored. Nothing measures your usage or behaviour, and you can switch crash reports off in Settings.
• No third-party trackers, pixels, or fingerprinting
• No cross-app or cross-site tracking, and no use of the advertising identifier (IDFA). We do not request App Tracking Transparency permission because we do not track.
• No collection of location, your phone’s contacts or address book, photos, health data, microphone audio, or your browsing activity. Your Klack friends are the people you add inside Klack (section 3.15); the app never reads your phone’s contacts.
• No directory of users. Other Klack users cannot browse or search for you: they can reach your profile only by your exact username, your friend code, or a game you played together, and only as your visibility setting allows (section 3.12). Someone you have blocked cannot reach you in any of these ways (section 3.16).
• No sale or sharing of personal data with data brokers, ever, under any circumstances

We do not use your data to train machine-learning models.

5. Who else processes your data

Processors. We use a small number of processors. They handle data only on our instructions, and each is bound by a data-processing agreement:

Push notifications are carried to your device by Apple’s and Google’s platform push services, which act under their own terms.

You can obtain a copy of the safeguards covering these transfers (for example the Standard Contractual Clauses incorporated in a processor’s data-processing agreement) by emailing support@klack.club.

Independent controllers. Apple and Google distribute the app, operate their sign-in services, and process payments. In those roles they are independent data controllers under their own privacy policies, not our processors, and their processing is governed by the terms you have with them.

Other Klack users. When you use the profile and friends features, the people your visibility setting admits receive your profile summary and stat card (sections 3.11–3.15). Whatever your setting, a person you send a friend request to receives your profile summary in the app, and your display name in a notification if they allow notifications (sections 3.5 and 3.15); anyone you let scan your friend code receives your profile summary too (section 3.11). They are private individuals, not our processors.

Request logs. Like almost every internet service, the infrastructure of the providers above records the IP address of incoming requests in short-lived technical server logs. These logs exist to route and secure traffic and to prevent abuse; we do not use them to identify you. Requests from the app also carry the app’s version number, which our backend functions log, without any identifier, so we can tell when old versions of the app are no longer in use.

6. How long we keep things

7. Your rights

Under the GDPR you have the right to access, rectify, erase, restrict, object to, and port your personal data, and to withdraw consent where processing is based on it.

You can exercise the most important of these yourself, in the app:

• Rectification: rename yourself and any player from their player card; your own card is the You tab. Renaming yourself also renames your Klack profile. Change your username by tapping it on the You tab.
• Restriction and objection in the social features: choose who sees your profile and statistics under Settings → Privacy → Who can see my stats; Only me hides them from everyone else. Decline or cancel friend requests in the Friends screen, and remove a friend from their player card. To take yourself off someone’s played-with list and stay off it, block them from their player card (⋯ → Block); undo a block under Settings → Privacy → Blocked people.
• Erasure: on the You tab, open the ⋯ menu → Klack account → Delete Klack account (in older versions of the app, the account icon next to your name). This deletes your Klack account credentials and every record we hold that belongs to you, including your entire cloud library, the shared games you recorded, your Klack profile and username, your stat card, your played-with list and your place on other people’s lists, every friendship and friend request you are part of, your block list and your place on other people’s block lists, your push tokens, and your entitlement record, and returns the device to a fresh, unused identity. It is immediate and irreversible. It does not cancel a store subscription; cancel that in the App Store or Google Play.
• Local erasure: deleting the app removes all local data.

Access and portability: your own profile is on the You tab and your friends are in the Friends screen. For a copy of everything we hold about your Klack identity, in a machine-readable format, email us.

For anything else, including an objection to processing based on legitimate interests, or to make a request in writing, email support@klack.club. We respond within one month.

What deletion does not do. Deleting your Klack account does not reach into other people’s data. Games your friends recorded on their devices remain theirs, including the pseudonymous player identifier that links your appearances in them. That record of games you played together is theirs, and removing it would destroy their history. The identifier carries no name, email, or contact detail of yours. Your former friends’ apps show once that you left Klack, with the name they last had for you, until they dismiss it.

If you believe we have handled your data unlawfully, you may lodge a complaint with the Finnish Data Protection Ombudsman (Tietosuojavaltuutetun toimisto, tietosuoja.fi) or your local supervisory authority.

8. Security

Data in transit is encrypted with TLS. Cloud data is protected by database-level row-level security: most records are readable only by their owner or by the members of the game session they belong to. The social features are the one place where one user’s data is read by another, and there every read goes through a server function that applies the owner’s visibility setting, and the two exceptions described in section 3.12, to each record, and never lists records. Friendships are readable only by the two people involved, played-with lists and block lists only by their owner, and abuse-prevention counters by no app at all. So knowing someone’s identifier grants no access beyond what their visibility setting already shares. Transfer snapshots and pairing codes are held only as hashes or in storage no client can list. Authentication sessions are held in the device’s secure storage (iOS Keychain / Android Keystore).

9. Children

Klack is not directed at children under 13 (or under the applicable age of digital consent in your country, which is 13 in Finland). We do not knowingly collect personal data from children. Klack is safe for family use offline, where it collects nothing at all. A Klack account, and with it the Klack profile and the friends features, is only for people aged 13 or over. Klack has no chat or messaging: in the social features other users see only a profile’s username, display name, initials avatar and game statistics, and a friend request carries no text. If you believe a child has created a Klack account, contact support@klack.club and we will delete it.

10. Changes to this policy

We publish each new version of this policy at this address with a new date.

If a change uses your data in a new way — for a new purpose, shown to people who could not see it before, kept longer, or under a less private default — we tell you at least 30 days before it takes effect, in the app and in a “What changed” box at the top of this page. Other changes, such as a new optional feature that starts only when you choose to use it, clearer wording or a corrected mistake, take effect when we publish them. A change the law requires may take effect sooner.

This policy is information about how we handle your data; we do not ask you to accept it.

11. Contact

Questions, requests, or complaints:

Suuntio
Business ID (y-tunnus): 3634040-2
Louhentie 13 D 32, 02130 Espoo, Finland
Email: support@klack.club
Phone: +358 45 869 1204

Effective 24 September 2026 · Published by Suuntio · support@klack.club