Legal
Privacy Policy
What Klibo stores, what it never stores, who else receives data, how long everything is kept, and how to delete it.
Effective date: October 2, 2026
Klibo is an arcade-style math, memory and visual-focus game for iPhone, offered by Nimisha Nagarkoti, the developer/seller identified for Klibo in Apple App Store Connect (the Developer, we, us). Privacy requests go to support@klibo.app or through the Klibo Support page.
| Role | Detail |
|---|---|
| Operator / Data Controller / Data Fiduciary | Nimisha Nagarkoti |
| Registered address | A2301, Atlantic, Pride World City, Pune 412105, Maharashtra, India |
| Contact | support@klibo.app |
| Grievance Officer (India, DPDP Act 2023) | Ritesh Kumar, support@klibo.app |
The short version
- You can play the whole game without an account, and without sending us anything. Detailed gameplay stays on your iPhone.
- A cloud account is optional and adults-only. It exists for leaderboards, challenges and keeping purchases safe.
- What we hold in the cloud is deliberately small: an account identifier, a generated username, score totals, and the records needed for the social features you use.
- Free play is funded by ads for adults, served by Google. Google receives some data when an ad is shown even though we have turned personalisation off — section 7 says exactly what, and how to opt out.
- We do not sell your data, and we do not run cross-app advertising tracking.
- Nothing is kept indefinitely without a reason. Section 8 lists how long each kind of record is kept.
1. Playing without an account
By default Klibo is a local app. Your profile, settings, puzzle attempts, response times, adaptive skill state, unlocks and full gameplay history live in a local database on your iPhone and are not transmitted to us.
At first launch Klibo asks for a coarse age range. It never asks for an exact date of birth. That answer is stored on your device and decides which features are available.
2. Optional adult account
Adults may create an account with an email address, signing in with a password or a one-time sign-in link we email you, or use Sign in with Apple. Authentication is operated by Supabase Auth, which processes your credentials and issues session tokens that Klibo stores in the iPhone Keychain.
If you create an account, our backend stores:
| Data | Why |
|---|---|
| Account identifier (a random UUID) and email address | Authentication and account recovery |
| A generated public username, e.g. SwiftOtter1234 | Your identity to other players |
| Lifetime XP total and per-game best / most recent scores | Leaderboards and rivals |
| Cosmetic ownership and unlock credits | Keeping purchases and earned characters across devices |
| For purchases made while signed in: the App Store transaction identifier, product and date | Delivering what you bought to your account |
| A Sign in with Apple refresh token, if you use Sign in with Apple | Revoking your Apple sign-in when you delete your account, as Apple requires. Readable only by our server, never by the app or other players |
Your email address and password are never shown to other players.
If you sign up with email or ask to reset your password, the message is sent through our email delivery provider (section 11), which receives your email address for that purpose only.
Like any online service, our hosting provider keeps short-lived server and authentication logs, which include IP addresses and request times, for security and troubleshooting.
Usernames are generated, not chosen. They are built from a fixed vocabulary of adjectives and animals plus four digits, and the database rejects anything outside that vocabulary. This is deliberate: a public identity can never contain your real name, an email address or anything else identifying. Once set, your username is fixed so rankings stay attached to a stable identity.
3. Cloud gameplay records
Only aggregate totals are uploaded — lifetime XP, per-game best score, and optionally your most recent score and when you played it. Individual puzzle attempts, your answers, response times and adaptive difficulty state are not uploaded and remain on your device.
4. Social features
These only operate on a connected adult account, and only for the features you use.
- Challenges. When you challenge another player or accept one, we store the two account identifiers, the game, the target score, timestamps and a run identifier. Completed matches produce a head-to-head record (wins, losses, draws and scores) for each player, and a match result — the game and both scores — that both players can see in their Arena.
- Rivals. Your private rivals list stores the players you add and the name you give the list. It is visible only to you. Adding someone does not notify them.
- Awards. If you place in the top 1% of a game's leaderboard, we record that you earned that award.
- Leaderboards. Boards show generated usernames, ranks and scores. Responses replace account identifiers with a one-way hash, so your account ID is never sent to another player's device.
There is no chat, no messaging and no free-text field anywhere in Klibo's social features. The only things one player can send another are a game challenge and a score.
5. Player safety
If you block a player, we store your account identifier, theirs and the time, and immediately delete any invitations, queued notifications and rival entries between you in both directions.
If you report a player, we store your account identifier, theirs, the reason you selected from a fixed list, and the time. Reports are private to Klibo and are never shown to the reported player or to anyone else. A report is reviewed by the operator; a report is not by itself proof of wrongdoing.
Report and block records are deleted when either account is deleted.
6. Notifications
If you enable challenge notifications on a connected account, Klibo registers an Apple Push Notification device token with our backend and queues outgoing alerts until Apple accepts them. A token that moves to a different signed-in account is discarded rather than delivered to, so a queued alert is never sent to someone who has since signed in on your device.
Daily play reminders are scheduled locally by iOS and involve no server.
7. Analytics, diagnostics and advertising
Product analytics is optional, off by default, and adults-only. Nothing is collected until you separately choose "Help improve Klibo". This is a distinct choice from accepting our terms.
When enabled and configured, PostHog receives a random analytics installation identifier, run and session identifiers, app version and environment, event times, and limited properties: the game, mode, score, accuracy, level, streak and timings of a run; which screen section you opened; Quest choices; how you signed in; that a between-game ad was shown; and which store product you viewed or tried to buy, with its price. It does not receive your email address, public username, password, account identifier or answer details, and there is no session recording or screen capture. Geolocation enrichment is disabled; as with any network request, your IP address is necessarily visible to the receiving server in transit.
Queued events are capped at 300 and expire after 72 hours. Turning analytics off cancels pending uploads, erases the local queue and discards the installation identifier. It cannot retract events already received — contact us to request deletion of those. Aggregate crash counts from Apple's MetricKit may be included; raw crash diagnostics are not sent to us.
Advertising
Eligible adult free players may see Google Mobile Ads between games, never during play. Players who have bought Go ad-free or the Ultra Plan see no banner or between-game ads. When a run ends, any adult player — including those who bought — may choose to watch a short rewarded video for one extra life; it plays only if you tap to watch it. All age-protected profiles see no advertising at all: the advertising SDK is never started, and their extra life is free.
What Klibo configures. We request contextual ads only: ad personalisation is disabled, publisher first-party identifiers are disabled, the maximum ad content rating is set to General, and Klibo does not request App Tracking Transparency permission, so no advertising identifier is used for cross-app tracking.
What Google still collects. Disabling personalisation is not the same as collecting nothing, and we would rather be clear than reassuring. When an ad is requested or shown, Google receives and processes:
- your device's IP address, and an approximate location derived from it;
- device and app information, including device type, operating system version and app identifier;
- ad interaction data — that an ad was requested, shown, viewed or tapped;
- identifiers used for frequency capping, aggregated reporting, and invalid-traffic and fraud prevention.
Google acts as an independent data controller for this processing, under its own terms rather than ours. How Google uses this data is described at How Google uses information from sites or apps that use our services. Google's retention periods for it are Google's, not covered by section 8 below.
Klibo receives no advertising data back about you. We see only aggregated revenue and impression reporting in Google's dashboard. No advertising identifier, ad interaction or IP-derived location is stored in Klibo's database, and none of it is linked to your Klibo account.
Your choice, and changing it. Where your region requires consent — including the EEA and the UK — a Google-certified consent form is shown before any ad is requested, listing the advertising vendors involved, and no ads are requested until you have made a choice. You can change that choice at any time in Me → Privacy, support & legal → Ads & going ad-free → Manage advertising privacy options, which reopens the same form. You can also remove banner and between-game ads entirely with the one-time Go ad-free or Ultra Plan purchase.
The only ad-related things we store are a few counters kept in local storage on your iPhone — confirmed between-game ad impressions, when the last one was shown and how many sessions you have played — so the app can space ads out and occasionally offer the ad-free purchase. They never leave your device and are not sent to us or to Google.
8. How long we keep things
Enforced automatically by a scheduled database job.
| What | Kept for |
|---|---|
| Product analytics events | 90 days |
| Rate-limiting counters | 2 days |
| Notification delivery records (once delivered or expired) | 7 days |
| Completed, expired or declined challenge invitations | 30 days |
| Match results (who played whom, the game and both scores) | 180 days |
| Legacy device-sync journal entries | 30 days |
| Legacy practice-challenge records | 7 days |
Pending challenge invitations are never deleted early — they expire on their own 72-hour clock and are removed on the schedule above.
Kept until you delete your account: your account, username, score totals, cosmetic ownership, rivals list, head-to-head records, awards and push registrations.
Purchases. Klibo's own record of a purchase made while signed in (its App Store transaction identifier, product and date) is deleted with your account. Apple keeps your purchase history against your Apple Account under Apple's own terms, and that is what Restore Purchases uses. Backups, security logs and records we are legally required to keep follow their own retention.
Not ours to delete: advertising data described in section 7 is held by Google under Google's own retention periods, not in Klibo's database. Deleting your Klibo account does not reach it.
9. Children and protected profiles
Klibo is not directed at children, and a Klibo cloud account is available to adults only.
If you select an age-protected range, that profile plays entirely locally. It cannot create a cloud account, appear on a leaderboard, send or receive challenges, add rivals, see Klibo-served advertising, make in-app purchases, or enable product analytics. No advertising, tracking or purchase service is initialised at all for these profiles.
The age range is self-declared. Treating every range under 18 as protected is deliberate: India's DPDP Act treats anyone under 18 as a child and restricts tracking and targeted advertising directed at children, so Klibo processes no personal data for those profiles at all.
If you believe a child has created an adult account and provided personal information, contact support@klibo.app and we will delete it.
10. Legal bases for processing (EEA / UK)
| Purpose | Lawful basis |
|---|---|
| Operating your account, cloud scores, leaderboards, challenges and purchases | Performance of a contract (Art. 6(1)(b)) |
| Product analytics; push notifications | Your consent (Art. 6(1)(a)), withdrawable at any time |
| Fraud prevention, rate limiting, abuse handling, service security | Legitimate interests (Art. 6(1)(f)) |
| Keeping accounting and tax records | Legal obligation (Art. 6(1)(c)) |
| Storing or accessing information on your device for advertising, and serving ads, where consent is required | Your consent (Art. 6(1)(a)) with the ePrivacy Directive, via Google's certified consent form, withdrawable as described in section 7 |
| Serving contextual ads where consent is not required | Legitimate interests (Art. 6(1)(f)) — funding a free game — balanced by disabling personalisation and first-party identifiers |
| Measuring ad delivery, capping frequency and preventing ad fraud | Legitimate interests (Art. 6(1)(f)), by Google as an independent controller |
Under India's DPDP Act 2023, processing of your personal data is on the basis of your consent, given when you create an account or opt in to a specific feature, or for the legitimate uses the Act permits.
11. Service providers and international transfers
| Provider | Role |
|---|---|
| Apple | Platform, App Store, StoreKit payments, push notification delivery, Sign in with Apple |
| Supabase | Authentication, database and server functions, hosted in Singapore |
| Brevo | Delivery of account emails such as sign-up confirmation and password reset |
| Google (Mobile Ads / User Messaging Platform) | Advertising and consent controls for eligible adults. For ad serving Google acts as an independent controller, not as our processor — see section 7 |
| PostHog | Optional product analytics, only when you have opted in, hosted in the European Union |
Supabase, Brevo and PostHog act as our processors: they handle personal data only on our instructions, under data-processing terms that require protection of that data at least equal to this policy. Apple and Google process data as independent controllers under their own privacy policies, linked from their services.
These providers may process data outside your country, including outside the EEA, the UK and India. Where required, transfers rely on the European Commission's Standard Contractual Clauses or the provider's equivalent safeguards.
12. Deleting your account
Me → Delete account & data (shown while you are signed in) removes your authentication account and your Klibo cloud records. If you play without an account, the same place offers Delete My Data, which clears everything Klibo stored on your iPhone.
Specifically, it deletes your account totals, per-game scores, username handle, push registrations and challenge history; if you used Sign in with Apple, it revokes Klibo's Apple tokens so Klibo no longer appears under your Apple Account's Sign in with Apple apps; and then it deletes the authentication account itself. Related records — purchase records, cosmetic ownership, rivals entries, head-to-head records, awards, blocks and reports — are removed automatically alongside it.
Two things survive, and we want to be straightforward about them:
- Local progress on your iPhone, which you clear separately in the app or by deleting the app.
- Pseudonymous analytics events, which are keyed to a random installation identifier and not to your account, so they cannot be located by account deletion. They expire on the 90-day schedule, and you can ask us to delete them sooner.
Your purchase history itself stays with Apple, so Restore Purchases still works after you delete your Klibo account. Deleting a Klibo account does not cancel or refund App Store purchases — that is handled by Apple. Signing up again later creates a genuinely new account with no previous progress attached.
13. Security
Klibo uses authenticated server functions, row-level database security, and does not ship any privileged backend secret inside the app. Session tokens are stored in the iPhone Keychain. Public leaderboard responses replace account identifiers with a one-way hash. No online system can guarantee absolute security, and we do not claim otherwise.
14. Your rights
Everyone. You may ask us to access, correct or delete your personal data, to withdraw a consent you gave, or to receive a copy in a portable form. Contact support@klibo.app; we aim to respond within 30 days. Most of this is also available directly in the app. If you write to us, we keep that correspondence only as long as needed to resolve your request.
India (DPDP Act 2023). As a Data Principal you have the right to access a summary of your personal data and our processing, to correction and erasure, to nominate another person to exercise your rights if you die or become incapacitated, and to grievance redressal. Contact the Grievance Officer named above first; if unresolved, you may complain to the Data Protection Board of India.
EEA and UK (GDPR). You additionally have the rights to restrict or object to processing, to data portability, and not to be subject to solely automated decisions with legal or similarly significant effects — Klibo makes none. You may complain to your national supervisory authority, or the UK Information Commissioner's Office.
California (CCPA/CPRA). In the past 12 months Klibo has collected identifiers, commercial information (purchases), and internet or app activity, as described above. We do not knowingly collect personal information from anyone under 16.
Klibo does not sell personal information for money. Klibo's advertising is configured so as not to constitute "sharing" for cross-context behavioural advertising: ad personalisation and publisher first-party identifiers are disabled and no advertising identifier is requested through App Tracking Transparency. Ad serving nonetheless involves Google receiving the data listed in section 7 as an independent controller, so if you would prefer no ad-related data to be processed at all, the reliable routes are the Go ad-free or Ultra Plan purchase (after which an ad plays only if you choose to watch one for an extra life) or declining in the consent form where one is shown.
You have the rights to know, delete, correct, and to opt out of sale or sharing, exercisable at support@klibo.app. We will not discriminate against you for exercising any right.
15. Changes and contact
We will update this notice when our data practices change, and change the effective date above. Material changes will be signalled in the app.
For privacy requests, access, correction, deletion, consent withdrawal or any question about this policy, email support@klibo.app.