Privacy Policy
This policy explains how FREEDOM LLP ("we", "us") handles personal data when you play Knowtilus: Trivia Quiz Game (the "app"). It is written to be read. If anything is unclear, write to us at office@freedomgaming.co.
Effective date: 4 November 2026.
In short.
- You can play as a guest, with no email address, name or password. If you save your player, we store the email address and a scrambled form (a hash) of the password you chose, or the ID of the Google, Apple, Game Center or Google Play Games account you signed in with. We never ask for your name, phone number, date of birth, contacts, photos, camera, microphone or location, and the app does not ask your device for them.
- Opening the app for the first time creates nothing. When you tap I agree on the first screen, our server creates a player with a random ID and a generated nickname such as "Brave Narwhal 42". You cannot type a nickname. Logging in never makes a player, and nothing else does: every player is made by your own tap on I agree.
- We store the answers you type, with their scores and how long you took.
- An answer that is new to us is checked by an AI model run by OpenAI. What is sent is the prompt and the answer only, with nothing that identifies you or your device.
- The base game is free. Depending on your app version and whether the features are enabled, automatic ads may appear between levels and optional rewarded ads may be offered in eligible situations. Any consent required for ads must be provided first. When a compatible version and store offer them, one-time purchases may include No Ads, 100 Jewels and 5 Bonus Air. The store processes payment, and we do not receive your card or bank details. We verify store transactions and link each purchase to the recoverable player account signed in at purchase. We retain a minimal transaction tombstone after account deletion to prevent replay (section 7). The shop requires a recoverable player account before starting a new purchase. After you tap I agree it counts how the app is used and records its own errors, in our own database and in an analytics service that FREEDOM LLP runs itself. Before that tap it collects and sends nothing for analytics, and the app does not start the advertising software.
- You can delete your data yourself, in the app, at any time. That deletes your sign-in details too.
1. Who is responsible#
The controller of your personal data is FREEDOM LLP, the publisher of Knowtilus: Trivia Quiz Game.
- Company registration: company number OC407608, registered in England and Wales
- Address: 101 King's Cross Road, London WC1X 9LP, United Kingdom
- Privacy requests and questions: office@freedomgaming.co
- Data-protection contact: no data protection officer is appointed; write to office@freedomgaming.co
2. What we collect#
A guest player does not tell us who you are. The data below is still personal data under laws such as the GDPR, because it is tied to an identifier that lives on your device. A saved player is also tied to an email address or to an account at Google, Apple, Game Center or Google Play Games, which can tell us which player is yours. We treat all of it as personal data.
| Data | What it is and where it comes from | What we use it for |
|---|---|---|
| Player ID and sessions | When you tap I agree on the Terms screen (the first screen of the app, and the screen the app shows again before it makes any new player), our server creates a player and sends back a random player ID and two signed sign-in tokens: an access token that lasts 1 hour, and a refresh token that lasts up to 60 days and is replaced every time it is used. The app keeps them in your device's secure storage (the iOS Keychain, or the Android Keystore) and sends the access token with each request. Of a refresh token we store only a one-way hash (SHA-256) with the time it was made and when it ends, never the token itself. If an old refresh token is used again, we treat it as stolen and end every session of that player. | To recognise your device from one day to the next, keep your progress and rank, keep other people's requests away from your data, and end your sessions: on this device when you log out of a saved player, and on every device when you reset your password or delete your data. |
| Account details | Whether your player is a guest or saved, when it was saved, and a credential counter that ends old sessions when a password is reset. | To run accounts and keep them secure. |
| Email address | Only if you save your player by email, or sign in with Google or Apple. The address you typed, or the address that Google or Apple vouches for (Apple may give a private relay address that forwards to you). Stored in lower case with the time it was confirmed. An address counts only once it is confirmed. | To sign you in, to send the one-time codes you ask for (section 5) and to protect the account. We do not use it for marketing and send no newsletters. |
| Password | Only if you chose email and password. We store a salted bcrypt hash, from which the password cannot be read. We do not store the password itself. | To check your password when you log in. |
| Sign-in IDs from Google, Apple, Game Center and Google Play Games | Only for the services you use. The ID that the service gives your account for our app: Google's account ID (we ask Google only for it and for your email address, not for your name, picture or contacts); Apple's user ID for Sign in with Apple; the Game Center player ID, which Apple scopes to a developer team, so the same person has the same Game Center ID in every title published by FREEDOM LLP (our Apple developer team); Google's Play Games player ID. We do not read your Game Center or Google Play Games name, picture, friends or achievements. | To recognise the same account on another device, and so that one account cannot be attached to two players. We use these IDs only to recognise your player in this app. |
| Emailed codes | When you ask to save your player by email or to reset a password, a short-lived record: a hash of the 6-digit code, the address, the time, and, when you save by email, a bcrypt hash of the password you chose. A Google link, or a Google log in to a player that exists, leaves a similar record, with the Google account ID and email address, that lives for minutes. A Google log in that finds no player keeps nothing at all: no record is stored and no player is made. | To check that you control the address, and to attach a Google account to the player that asked. |
| Generated nickname | Chosen by our server when the player is created: an adjective, a sea creature and two digits. Nicknames are not unique and say nothing about who you are. Other players see yours on the daily leaderboard. | To show your place on the leaderboard. |
| Activity times | When the player was created and when it was last seen (refreshed at most every ten minutes while you use the app). | To run the service, to delete inactive players (section 7) and to count how many players we have. The usage events below record more. |
| Your answers | For every prompt: the text you typed (the first 100 characters), a normalised form of it (lower case, no punctuation or accents, typos and plurals merged with known answers), which prompt and day it belongs to, whether you skipped it, whether it fitted the prompt, and the result: depth in metres, the estimated share of players who gave the same answer, and the rarity tier. Also the time you took, as measured by the app. | To score your dive, work out how rare an answer is, build the daily leaderboard and the "what others said" lists, keep the game fair, and handle reports. |
| Anonymous answer statistics | Per prompt: how many players gave each answer, and whether an answer fits the prompt (the verdict of section 4). Neither is linked to a player. | To estimate how rare an answer is, and to avoid asking the AI model the same question twice. |
| Technical data | Your IP address and the usual details of a network request (time, address requested, result, the app's user-agent text). The app does not send an advertising ID, the IDFA or IDFV, or any other identifier of your device to our game server. It makes one random identifier of its own for our analytics service (see the row "Analytics identifier" below). The advertising service's own software is another matter: see "Advertising" below. Your IP address is used for rate limiting, held in memory in windows of up to 15 minutes (the limits on emailed codes use the longest), and appears in the access logs of our web server. Our software does not store it in the game database or attach it to your player. | To answer your request, to stop flooding and abuse, and to diagnose faults. |
| Usage events | Short records of what you do in the app, with your player ID, the platform and the app version. They exist only after you have agreed to version 3 or later of the Terms. What a record holds and what it never holds: "Usage analytics, error reports and our analytics service" below. | To count daily and returning players, see how long visits last and where players stop, compare app versions, find and fix faults, and improve the game. |
| Error reports | When the app's own code fails: the kind of error, a short filtered message and the top line of its stack trace, a fingerprint, the screen and the app version. Sent as usage events. | To find and fix crashes and other faults. |
| Analytics identifier | A random identifier that the app makes on your device for our analytics service, when you first tap I agree to version 3 or later of the Terms. It is not your player ID, not an advertising ID and not an identifier that Apple or Google gives your device, and it is never sent to our game server. | To key the copy of the usage events and error reports at our analytics service, which does not know your player ID. |
| Advertising | The ads come from AppLovin, an advertising service run by another company, whose software is part of the app. If ads are enabled, from your device it may receive your IP address, the advertising ID of the device where you allow it, details of the device, its operating system and the app, how the advertising software itself runs, and what happens to an ad (requested, shown, clicked, closed); from the IP address it works out an approximate location (country and region). The full list is under "Advertising" below. The data goes from your device to AppLovin, not through our servers; our API does not receive this device-level ad-serving data. The app gives the software no player ID, nickname, email address or answers. If a rewarded ad is enabled, the SDK also receives a random claim value that contains no player ID or sign-in details; our API separately links that claim to your player. Details: "Advertising" below. | To show and measure ads, and to prevent ad fraud, if ads are enabled. |
| Rewarded ad claims | If optional rewarded ads are enabled, our API stores an authenticated claim linked to your player ID, its placement and context, a random claim value, status and times. The app reports whether its SDK reported an earned view. In the current client-attestation mode, our server accepts or rejects that report against the player's open, eligible claim and daily limits; it does not receive an independent AppLovin confirmation. | To enforce eligibility and daily limits, issue the reward once and prevent replay. |
| In-app purchases | Where a compatible store and app version offer an item, the store processes the payment. The app sends our API the store, product ID and store proof (a signed transaction or a Google purchase token), plus an opaque account token that binds the purchase to the signed-in Knowtilus player. The shop requires a recoverable player account before starting a new purchase. Our server verifies the proof with the store. We store the store and product, purchase state, whether it was sandbox or production, a SHA-256 hash of the store transaction key, verification/fulfilment/refund dates, and an encrypted copy of the proof while the player account exists. We do not receive card or bank details or store the localized price. | To verify and deliver each purchase once, restore No Ads, reconcile store status, process store refunds/revocations and prevent a transaction from being replayed or credited to another game account. |
| Reports | If you report an answer: which answer, the reason you chose, the time, and your player ID. | To review the report and act on it, as the Terms of Service describe. |
| What you send us | If you write to us: your email address, your message, and anything you attach or tell us. | To answer you and to handle your request. |
We do not collect your name, phone number, postal address, date of birth, precise location, contacts, photos, files, audio, health data, payment card or bank details, or browsing history. We do collect the store transaction information described above. Our game server and our analytics service never receive an advertising ID. The advertising service's software in the app reads the advertising ID itself, where you allow it (see "Advertising" below). The only permission prompt is Apple's tracking prompt on iPhone; on Android the app declares the advertising ID permission and the usual network permissions, none of which needs a prompt. The only location data is the country that our analytics service works out from an IP address, and the country and region that the advertising service works out from it, as the table above says: neither the app nor our game server reads where you are. We collect an email address only in the cases of the table above, and when you write to us.
What other players can see#
- The daily leaderboard shows the nickname, total depth and rank of every player who finished the day's dive. It never shows a player ID.
- "What others said" lists the most common answers to a prompt and how many players gave each. It names nobody. An answer typed by players is shown to others only if it is on our list for that prompt or has passed the check of section 4 and our safety check for offensive text. If the safety check cannot run, the answer is still scored but is not shown.
- Sharing. The Share button opens your device's share sheet with a short text (your total depth and your rarest answer). It contains neither your nickname nor your player ID, and it goes only where you send it.
- Your sign-in details. Nobody else sees your email address, your password hash or your sign-in IDs.
Usage analytics, error reports and our analytics service#
- What a usage record holds. The name of an event from a fixed list (for example: the app was opened, a screen was shown, a dive was started, finished, left or shared, a result was shown, a report was sent, you signed in or out, you changed the language or a setting, a version notice was shown, and, in versions that have them, chests, the shop and duels); the time on your device (UTC) and the time our server received it; your player ID, which our server takes from your sign-in token (the app does not send it as a field); the platform (iOS or Android); the app version and build number; the identifier of the update the app is running, when it was updated over the air; and a few properties chosen from a fixed list for that event, for example the screen, the kind of dive and its category, which prompt, the depth and rarity tier an answer reached, how long it took, how many answers of a result were scored, skipped or ran out of time, or one of our own error codes. A random key of each record, stored only as a one-way hash, lets our server ignore a record that arrives twice.
- What a usage record never holds. The text you typed, your nickname, your email address, your IP address or an identifier of your device. The app sends only events and properties of the fixed list, and our server refuses anything else.
- Advertising usage records. If ads are enabled, the fixed event list records the ad format (between-level or optional rewarded), where an offer appeared, and whether an ad was requested, shown, failed, skipped or the SDK reported it earned; it also records whether our API accepted the client report or paid the reward. Reasons come from a fixed list (for example not ready, closed early or air full); development stand-ins are marked separately. These usage events go to our game server and analytics service. They contain no advertising ID, ad-unit ID, claim ID, one-time proof or provider event ID. Separately, our API stores rewarded claim and payout records described in section 12; it does not independently verify a video with an AppLovin server callback in the current client-attestation mode.
- Error reports. When the app's own code fails (a screen that cannot be drawn, an error that nothing handled), the app records the kind (fatal, not fatal, an unhandled promise, a screen error), the type of error, a short message (at most 200 characters), the first line of the stack trace (at most 120 characters), a 16-character fingerprint made from them, the screen you were on and the app version. A fatal error is saved on your device and sent the next time you open the app. If the app was closed while you were using it, without going to the background first (a crash, the system closing it, or you closing it from the app switcher), the next start records that as an "unclean exit" with the time. Before an error text leaves the app, the app removes control characters, email addresses, web addresses, IP addresses, user names in file paths, secrets and long numbers, and our server does the same again. That filter does its best and is not a guarantee: in rare cases an error message could still contain a fragment of something you typed. The app does not collect crashes inside the phone's own code (native crashes); Apple and Google may pass us such reports if you chose to share diagnostics with developers (section 5). An error report is a usage event: it is kept, erased and copied like the others.
- Our analytics service. A copy of the usage events and error reports goes to an analytics service that FREEDOM LLP runs itself. It is keyed by the analytics identifier, not by your player ID. It receives the same events with the same properties (the text of an error report is the filtered text), the platform and the app version on every event, the version of your operating system when the app is first started or updated and, on Android only, the model name of your phone, a marker that names this app's own analytics code, and its own start and end times of a visit (a visit ends when the app has been in the background for more than 10 seconds). It never receives your player ID, nickname, email address, the text you typed, an advertising ID or an IDFV.
- Country, and the access logs there. The service works out a country from the IP address of each request. It keeps the country, not the address, with your events and in a summary per device (first and last seen, number of visits, platform, app versions, country). The server that receives the requests also writes ordinary access logs, which contain IP addresses; they are rotated on that server's own schedule and are not covered by the 90 days of section 7.
- Why we treat it as personal data. FREEDOM LLP runs both our database and the analytics service, and the events carry the same times, so we treat the data at our analytics service as personal data too, although it is not stored under your player ID. Delete my data replaces the analytics identifier with a new one; section 7 says what happens to what was sent before.
When the analytics start and stop#
- Nothing before you agree. Until you tap I agree on the Terms screen, the app does not collect usage events or errors, does not make the analytics identifier and sends nothing to our analytics service. Before that tap the app asks our server only for its public settings (see "When your player is made" below). An event or an error that happens before that tap is thrown away: it is not kept to be sent later.
- It starts when three things are true: you have tapped I agree to a version of the Terms that describes it (version 3 or later), a player is signed in on the device, and the player is not banned. The app also waits, at every start, until it has heard from our server which version of the Terms applies now. The Terms screen is shown on each device where you have not yet seen it say so (also when you sign in to a player that agreed on another device), and nothing is collected on that device before you tap I agree on it. The first record is that you agreed, made when you tap; when you open the app later, the first record of that visit is that the app was opened.
- It stops when you log out, when your session ends, when you delete your data, when you are banned and when the Terms change again, until you agree again. The records that were waiting on your device to be sent are deleted. The app may send one last record that you signed out or deleted your data.
- No switch. The app has no setting to turn these records off in this version. They are limited as this section says, you can have everything held under your player ID deleted with Delete my data, and you can object under section 9.
- Limits. Our staff see totals and charts, never a list of one player's events. The filtered text of error reports is visible only to the administrators who run the service. A player can send only a limited number of events a day.
- Your copy. The copy of your data that you can ask for (section 9) includes your most recent usage events (up to 5,000), each with everything the record holds about you except the one-way hash of its key: its name, the time on your device and the time our server received it, its properties, and the platform, app version and update identifier of the build that recorded it.
- Deleting. Delete my data deletes the usage events and error reports held under your player ID together with the rest of the player. The copy at our analytics service is not under your player ID: section 7 says what happens to it.
Advertising#
Ad availability depends on your app version and whether the advertising feature is enabled. The following disclosures describe processing when ads are enabled. Rewarded claims currently use client attestation: the app reports an SDK-earned completion to our API, which enforces eligibility and daily limits and records an accepted claim and payout. Our API does not receive independent confirmation from AppLovin. AppLovin server-to-server verification is deferred.
- What and when. If enabled, automatic full-screen ads may appear between levels after the result of a level you passed, from the fourth passed level on. They are not shown during a dive, in the daily dive, in duels or on the Home screen.
- Who. The ads come from AppLovin (AppLovin Corporation, Palo Alto, California, USA), an advertising service run by another company. Its software is part of the app and runs on your device. It talks to AppLovin directly: the data goes from your device to AppLovin, not through our servers, and our API does not receive this device-level ad-serving data. The separate rewarded-claim data sent to our API is described in the next row. AppLovin decides how to use what it receives for advertising under its own privacy policy (https://legal.applovin.com/privacy/). The app shows ads from AppLovin's own advertisers; it contains the advertising software of no other company. In the EEA, the UK and Switzerland the consent form is Google's (User Messaging Platform, also part of the app): when it loads, Google receives your IP address and details of your device and the app, under Google's privacy policy (https://policies.google.com/privacy).
- What it may receive. Your IP address; the advertising ID of your device where you allow it (the IDFA on iPhone, the Google advertising ID on Android) and, on iPhone, the vendor ID (IDFV), on Android an App Set ID; the model and operating system of your device, its language, country and time zone, screen size and orientation, battery level, storage and memory, mobile carrier, accessibility settings, and network type and speed; the name and version of the app; how the advertising software itself runs (sessions, installs, performance); and what happens to an ad (that it was requested, shown, clicked or closed). From the IP address it works out an approximate location (country and region). This list follows AppLovin's own and may change. It never receives your name, email address, player ID, nickname or answers: the app does not give the software any of them.
- What we receive. If ads are enabled, the app sends limited ad-event records to our API and analytics service, such as the placement and whether the SDK reported an impression or earned view. In the current mode we receive no independent AppLovin server report or callback confirming a view.
- When it starts. If ads are enabled in your version, the app starts the advertising SDK only after you tap I agree to version 4 or later of the Terms, and only from a quiet screen. During SDK initialization, it may contact AppLovin and, where applicable, Google to determine the consent flow and present a consent form; on iPhone, the flow may also present Apple's tracking prompt. The app waits for initialization and any consent flow to finish before it requests or loads an ad. Ads are not requested or loaded during a dive.
- Your choices. On iPhone, Apple's tracking prompt asks whether the app may track you across other companies' apps and websites. If you say no, the advertising ID is not available and the ads are not personalised with it; you can change your answer at any time in Settings, Privacy & Security, Tracking. In the EEA, the UK and Switzerland the app asks for your consent in a consent form before ads are personalised, and you can change your choice from Ad privacy in About and support; if you do not consent, the app tells AppLovin so, and AppLovin decides under its own policy what it serves and collects; the app has no switch that stops the software. On Android you can delete your advertising ID or turn off ads personalisation in your phone's settings (usually Settings, Privacy, Ads). AppLovin lets you opt out of interest-based ads at https://max.applovin.com/p/how-applovin-shows-you-ads; if your advertising ID changes you may need to opt out again. Section 10 has more for residents of US states, and section 9 says how to reach AppLovin about the data it holds.
What stays on your device#
Only the session and what the sign-in screens need, in secure storage: your player ID, nickname and the two sign-in tokens; the version of the Terms you accepted, and notes that this device showed you the Terms screens that describe the analytics and the ads; the guest players you logged out of on this device, so that you can continue them from the welcome screen; the last Game Center or Google Play Games player ID the app saw, to notice when you switch game account; and whether you logged out on purpose. Once the analytics have started (above), also in secure storage: the random analytics identifier; a short queue of usage events and error reports that have not been sent yet; the record of an error that ended the app, until it is sent; and a note of whether the app was in the foreground or in the background, which is how an "unclean exit" is noticed. For our analytics service the app also keeps three small notes of its own analytics code: the app version it last reported, the start and last-seen times of the current visit together with visit records that have not been sent yet, and which events the service already received. The queue, the error record, the foreground and background note, and the notes of visits and received events are deleted when the analytics stop. The analytics identifier, and with it the note of the app version last reported, are kept until you delete your data. The iOS Keychain usually keeps items when an app is deleted, so on an iPhone the identifier can survive deleting and reinstalling the app, and a reinstalled app goes on using it; on Android it normally goes with the app. These items are kept on this device only: a backup restore or a transfer to a new phone does not carry them over. A small counter for the ads (how many levels you passed, how many since the last ad, the last result counted and when you last saw an ad) is kept in secure storage too; it holds nothing about you and stays on this device. The app itself uses no cookies and does not read the advertising ID. The advertising service's software, which is part of the app, may read the advertising ID where you allow it and keeps data of its own on your device to deliver ads, as "Advertising" above describes.
Signing in with Google, Apple, Game Center or Google Play Games#
- When your player is made. Opening the app for the first time creates no player and no sign-in. The first screen shows our Terms of Service, and until you tap I agree the app does not sign you in, does not contact Game Center, Google Play Games, Apple or Google, and asks our server only for its public settings (a request that, like every request, appears in the access log described under "Technical data" in section 2). Separately, each time it starts, the app asks Expo's update service whether a newer update of the app's code exists, which does not depend on your tap (section 5). On Android the Google Play Games component built into the app is not started before that tap either. Tapping I agree is what creates your player, and a player can do nothing until it has agreed to the Terms. Every player is made by your own tap on I agree, and nothing else makes one or agrees for you. After you log out, after we end a session or after you delete your data, the welcome screen's Continue as guest only shows you the Terms again, whatever the app remembers of an earlier agreement; the player is made when you tap I agree there. Log in only opens a player that already exists. If you log in with a Google, Apple or game account that has no player, no player is made, our database keeps no record of the attempt, and the app tells you so; you start from the Terms screen. When the app signs you in again without a tap (see below) it only opens the player that account already has; it never makes one. If our server has deleted your player, for example after 400 idle days, the app does not make a new one: it shows the Terms again, as on a first launch, and nothing is made until you tap I agree.
- Game Center and Google Play Games. On a device that is already signed in to one of them, the app uses that game identity when you tap I agree: it opens the player that game account already has, or creates one if it has none, and asks you nothing more for that. The app asks Apple to sign your Game Center player ID for our app and sends us the signature, which our server checks by downloading Apple's public certificate. For Play Games the app gets a one-time code from Google, and our server asks Google whom the code belongs to. Without such an identity, the tap on I agree creates a guest player. Once you have agreed and the game is open, the app also checks, when it starts, when you come back to it and (on iPhone) when Game Center reports a change, which game account is signed in on the phone. If it is a different account from the one your player was made for and that account already has a player, the app switches to that player; if the account has none, nothing is made and you stay where you are. If your sign-in ends (for example after a password reset on another device) and your player was made with a game account, the app signs you back in to the same player through that game account without a prompt; it asks our server for that one player only, and if another game account is on the phone, or none, nothing is opened or made and you log in again. If the app cannot reach our server for that, it keeps trying later and does not sign you out. The Log in screen also has a button for your game account, which opens the player that account already has and, if it has none, makes nothing.
- Google. The app opens Google's own sign-in page in a secure system browser window. You type your Google password there, never in the app. Google tells our server your account ID and your email address, and Google learns that you signed in to our app.
- Apple. Sign in with Apple uses Apple's own dialog, where you choose what to share. Apple gives our server your Apple ID for our app and, the first time, your email address or a private relay address.
This website#
The legal and support pages are static web pages. They set no cookies and load no scripts, fonts or images from other sites. The company that hosts them, DigitalOcean, may keep ordinary access logs.
3. Why we use your data, and our legal bases#
If the GDPR or the UK GDPR applies to you, these are the legal bases we rely on.
| Purpose | Legal basis |
|---|---|
| Creating your player (guest or saved), signing you in with the method you chose, running the daily dive, scoring, the leaderboard and the answer lists | Performance of our contract with you: the Terms of Service (Article 6(1)(b)) |
| Keeping accounts secure: checking passwords, sending codes, limiting sign-in attempts and emails, ending sessions | Performance of the contract, and our legitimate interest in keeping accounts safe (Article 6(1)(b) and (f)) |
| Checking whether a new answer fits its prompt (section 4) | Performance of the contract, and our legitimate interest in scoring fairly (Article 6(1)(b) and (f)) |
| Keeping the game secure and fair: rate limiting, preventing cheating and abuse, moderating answers, handling reports, enforcing the Terms, defending legal claims | Our legitimate interests in a safe and fair game (Article 6(1)(f)); a legal obligation where the law requires it (Article 6(1)(c)) |
| Verifying and delivering purchases, restoring No Ads, handling store refunds/revocations, preventing replay or duplicate grants, and reconciling store status | Performance of our contract with you (Article 6(1)(b)) and our legitimate interest in preventing fraud and keeping accurate purchase records (Article 6(1)(f)) |
| Counting daily and returning players, measuring how the app is used (the usage events and our analytics service), recording and fixing errors, improving the game | Our legitimate interest in running and improving the service (Article 6(1)(f)). We weigh it against your interests by keeping to a fixed list of events, allowing no free text except the filtered error message, using no advertising ID for it, starting only after you have agreed to the Terms that describe it, and keeping the data for 90 days |
| Showing you ads between levels, and the advertising service's measurement and fraud prevention (section 2, "Advertising") | Where the law asks for consent to personalise ads with your advertising ID or similar identifiers (Apple's tracking prompt; the consent form in the EEA, the UK and Switzerland): your consent (Article 6(1)(a)), which you can withdraw at any time. For ads that are not personalised, for measurement and for fraud prevention: our legitimate interest in funding the game (Article 6(1)(f)); where the ePrivacy rules ask for consent to read information on your device, we ask for it in the same form. If you refuse, the app tells AppLovin, which decides under its own policy what it serves and collects; the app has no switch that stops the software. AppLovin's own use of what it receives is governed by its privacy policy |
| Answering your messages and requests | Our legitimate interest in supporting you, and legal obligations for rights requests (Article 6(1)(f) and (c)) |
| Complying with legal requests | Legal obligation (Article 6(1)(c)) |
| Optional features that ask your permission (section 12) | Your consent, which you can withdraw at any time (Article 6(1)(a)) |
We do not make decisions about you that have legal or similarly significant effects. The AI check of section 4 decides only whether an answer counts in the game.
4. Answer checking with OpenAI#
Rarity is only fair if an answer really fits its prompt: "papaya" is a rare answer to "Name a type of pasta", but it is not pasta. So when an answer is new, an AI model checks it.
When. Only when the answer is not on our prepared list for that prompt and we have no stored verdict for it yet. Every distinct answer to a prompt is judged once, ever, and the verdict is stored and reused. Most answers never leave our servers.
What is sent. Our fixed instructions, the text of the prompt (for example "Name a type of pasta"), and the normalised form of the answer (at most 40 characters and five words). The request is made by our server to OpenAI's chat completions service (api.openai.com).
What is not sent. Your player ID, nickname, email address, IP address, sign-in tokens, device details, the time you took, or anything else about you. OpenAI sees the network address of our server, not of your device.
What comes back. A yes-or-no verdict: the answer fits the prompt or it does not. We store the verdict with the prompt, the normalised answer, the model's name and the date, with no link to you.
OpenAI's role and retention. OpenAI processes this data for us as a service provider under its own API terms. When we wrote this policy, OpenAI's published terms said that it may keep API inputs and outputs for up to 30 days to provide the service and to detect abuse, and that it does not use API data to train its models unless the customer opts in. Our service does not opt in, and it does not use OpenAI's optional zero-data-retention or modified abuse-monitoring controls. We therefore cannot promise that OpenAI deletes a request immediately. Read OpenAI's current terms and privacy policy at https://openai.com/policies/ for the details, which OpenAI can change.
If the check is not possible. When OpenAI cannot be reached, the app tells you to try again or to type a different answer. We do not store or score that answer in the meantime.
Your choices. There is no switch to turn the check off, because it is what decides whether a new answer counts. If you do not want a particular answer to be sent, skip that prompt: an empty answer scores 0 m and sends nothing. Please do not type personal information into an answer.
Mistakes. The model can be wrong. If you think an answer was judged wrongly, write to us with the prompt and the answer. A person can correct the stored verdict, and it then applies to everyone.
5. Who we share data with#
- Hosting. Our servers and database are run by DigitalOcean, in Frankfurt, Germany (EU). It stores and processes the data described in section 2 on our behalf.
- OpenAI. Only what section 4 describes.
- Our analytics service. Run by FREEDOM LLP, the company that issues this policy. It receives the copy that section 2 describes. It is our own service, not another company's, and the app contains no analytics or crash-reporting software from any other company.
- AppLovin (advertising). If ads are enabled, AppLovin's software sends the device and ad-interaction data listed under "Advertising" in section 2 from your device to AppLovin. A rewarded offer also uses a random claim value supplied by our API to connect the app's earned-view report to the pending claim; it contains no player ID or sign-in details, though our API separately links the claim to your player. Our API does not receive an independent AppLovin callback in the current client-attestation mode. AppLovin's privacy policy applies to its processing: https://legal.applovin.com/privacy/.
- Google (consent form). In the EEA, the UK and Switzerland the consent form of the ads is Google's User Messaging Platform, which is part of the app. When it loads, Google receives your IP address and details of your device and the app, and learns your choice. Google's privacy policy applies: https://policies.google.com/privacy.
- Expo (update checks). Each time the app starts, it asks Expo's update service (u.expo.dev), which delivers fixes to the app's code over the air, whether a newer update exists. The request carries the platform, the app's runtime version, the update channel, the identifier of the update the app is running and an identifier that Expo's software makes for this installation, and Expo sees the IP address of the request. It happens before you tap I agree, and it sends Expo nothing about your player or your answers. Expo acts for us as a service provider; Expo's own privacy policy applies to what it keeps.
- Email. If you write to us, the provider of the mailbox behind office@freedomgaming.co handles your message on our behalf.
- Email delivery. Resend (sending from Ireland, EU) sends the emails that carry your codes. It receives your email address and the text of the message, and keeps delivery logs for the provider's own retention period for delivery logs (we do not control it).
- Google. If you sign in with Google, Google receives your sign-in and tells us your account ID and email address. If you use Google Play Games, our server asks Google whom a one-time code belongs to. Google's privacy policy applies to what Google collects.
- Apple. If you use Sign in with Apple or Game Center, Apple tells us your Apple ID for our app, or signs your Game Center player ID for us. Our server downloads Apple's public certificate to check that signature. Apple's privacy policy applies to what Apple collects.
- Apple and Google as stores. They distribute the app and, if you have chosen to share diagnostics with app developers, may pass us reports that do not contain your player ID. Their own privacy policies apply to what they collect.
- Apple and Google Play (in-app purchases). The store you use processes the payment and receives its transaction and opaque account-binding information. Our server sends the store proof to its verification service and receives the verified product, transaction state, environment and refund/revocation status. We do not receive your card or bank details. Apple and Google handle their store data under their own privacy policies: https://www.apple.com/legal/privacy/ and https://policies.google.com/privacy.
- Other players. Only what section 2 lists under "What other players can see".
- Authorities and advisers. When the law requires it, to answer a valid legal request, or to establish, exercise or defend legal claims, and to our professional advisers under a duty of confidentiality.
- A successor. If we sell or reorganise the business, the data may move to the new owner, who must respect this policy.
We do not sell the data of your player (your account, nickname, email address, answers and scores) to anyone, and we give none of it to the advertising service. The data that AppLovin's software collects from your device to show you ads is another matter: under some laws, making such data available to an advertising service counts as "sharing" for cross-context behavioural advertising, or as a "sale". Section 10 says what you can do.
6. Transfers outside your country#
Your data may be processed in countries other than the one where you live.
- OpenAI may process answer checks in the United States: we use OpenAI's standard endpoint and have not selected a regional data-residency option.
- Google (sign-in, Play Games and the consent form of the ads), Apple, Expo (update checks) and our email delivery provider may process what they receive from you or from us in other countries, including the United States, under the safeguards they provide.
- AppLovin may process what its software receives in the United States and in other countries. According to its privacy policy it complies with the EU-US Data Privacy Framework and its UK and Swiss extensions.
- Our analytics service is run by FREEDOM LLP on a server of its own, which is separate from the game's server in Frankfurt and may be in another country. What it receives is described in section 2.
- Our hosting is in Frankfurt, Germany (EU).
- The app connects to our servers from wherever you are.
Where the GDPR or the UK GDPR requires a safeguard for a transfer, we rely on one that the recipient provides: an adequacy decision or a certification under the EU-US Data Privacy Framework, or standard contractual clauses, with the UK addendum where needed. Ask us for a copy of the safeguards at the address in section 14.
7. How long we keep data#
| Data | How long |
|---|---|
| Player record (ID, nickname, times), the sign-in details (email address, password hash, sign-in IDs) and the scores, answer keys and timings linked to it | While you keep playing. If we have verified or delivered a store purchase that has not been refunded or revoked, inactivity does not automatically delete the player. Otherwise, it is deleted automatically after 400 days without activity. You can request deletion at any time. |
| Purchase records linked to your player | The store, product, state, environment, dates and encrypted store proof are kept while the player record exists, to deliver once, restore No Ads, reconcile store status and handle refunds/revocations. When you delete your player, we clear its link and encrypted proof. We retain a tombstone containing the store, product, hashed transaction key, state, environment and dates to prevent a purchase from being replayed for another player. The current code sets no automatic expiry for these tombstones, so no fixed end date is currently defined. |
| Rewarded ad claims, if that feature is enabled | Claim rows expire from our database 7 days after creation. An open claim is valid for 10 minutes; after accepted completion, it may be collected for up to 30 minutes. Deleting your player deletes its claim rows. Rewards are part of your progress and are deleted with your player. |
| Sessions (refresh tokens) | Each lasts up to 60 days from the last time it was used. Logging out of a saved player ends the session on that device at once; a password reset or deleting your data ends your sessions on every device at once. A guest that you log out of keeps its session on your device, so that you can continue it from the welcome screen: that session ends when its 60 days run out, or when you delete your data. The record of an ended session is removed when its 60 days run out (deleting your data removes the records at once). |
| Emailed codes and pending requests | A code and its pending request (the address you typed and, when you save by email, the bcrypt hash of the password you chose) are marked as used when you use them, and are removed by the database when they expire: 15 minutes after they were made, plus the minute or so the database takes to sweep expired records, so at most about 16 minutes. A pending Google link lasts 5 minutes and a Google sign-in code 2 minutes, and they are removed the same way. |
| The text you typed, exactly as you typed it | 12 months from the day you submitted it, then erased. The score, normalised answer and timing stay with the player record. |
| Anonymous answer statistics and AI verdicts | Indefinitely. They contain no player ID. |
| Usage events and error reports under your player ID (our database) | 90 days from the time our server received each one, then the database deletes it. Deleted at once, with the player, when you delete your data. |
| Usage events and error reports at our analytics service | The events themselves: 90 days. A summary per device (first and last seen, number of visits, platform, app versions, country): for as long as the service runs. Delete my data replaces the identifier on your device with a new one. It does not delete what was already sent under the old identifier: those events expire after 90 days, and the summary of the old identifier stays. |
| Data held by AppLovin | Under AppLovin's own privacy policy, which at the time of writing says it typically keeps data for up to two years. We do not hold it and do not control it |
| Access logs of the server of our analytics service (these hold IP addresses) | On that server's own log rotation, which is not part of the 90 days above |
| Reports and moderation records | 24 months after the case is closed. A report you filed is deleted sooner if you delete your data. |
| Web server access logs (these hold IP addresses) | 30 days |
| Application logs (these hold normalised answers and prompt IDs, never a player ID) | 30 days |
| Backups | Rolling 30 days. Data you delete leaves the backups when they expire, at most 30 days later. If we ever restore a backup, we delete again what has been deleted since. |
| Emails you send us | 24 months after the last message in the conversation |
| Delivery records of the emails we send you (codes) | the provider's own retention period for delivery logs (we do not control it), at the email provider |
| The record that a deletion or rights request was made (date, player ID, outcome) | 24 months, to show that we answered it and to re-apply it after a backup restore |
| The copy at OpenAI | Up to 30 days, under OpenAI's terms at the time of writing (section 4) |
We may keep data longer when the law requires it, or when we need it to establish, exercise or defend a legal claim.
8. Security#
- All traffic between the app and our servers, our analytics service and Expo's update service uses HTTPS.
- On your device, the session is kept in secure storage (the iOS Keychain or the Android Keystore).
- Sign-in tokens are signed and short-lived (an access token lasts 1 hour). Refresh tokens are stored only as hashes. A password reset ends every session of the player, on every device.
- Passwords are stored only as bcrypt hashes. The API limits how many requests, sign-in attempts and emails one address can make.
- Access to the database and the admin tools is limited to the people who run the service, needs a login with a role, and every change made in the admin tools is written to an audit log.
No system is perfectly secure. If a breach puts your rights at risk, we will tell the people concerned and the authorities as the law requires.
9. Your rights#
If the GDPR or the UK GDPR applies to you, you have the right to:
- ask whether we hold data about you and get a copy (access);
- have wrong data corrected (rectification). The nickname cannot be edited, but you can delete your data and start again;
- have your data deleted (erasure);
- ask us to restrict how we use it;
- receive the data you gave us in a common electronic format (portability);
- object to processing that rests on our legitimate interests;
- withdraw a consent at any time, without affecting what was done before;
- complain to a data-protection authority: in the UK the Information Commissioner's Office (https://ico.org.uk), in the EU the authority of the country where you live, work or believe the problem happened.
How to use them.
- The fastest way to delete: open the app and choose Delete my data. See Delete your data.
- For anything else, write to office@freedomgaming.co and include the player ID shown in the app (the About and support screen, reached with About on the home screen). Because we hold no name for you, the player ID is how we know the data is yours. If you saved your player with an email address, write from that address. A nickname alone is not enough: nicknames are public and can be shared by several players.
- The usage events and error reports under your player ID are part of your data and are found with the player ID. The copy at our analytics service is stored under a random identifier that our game server never holds, and we keep no link between that identifier and your player ID, so we have no routine way to tell which of its rows are yours. Because both are run by FREEDOM LLP and the events carry the same times, a match could be made by comparing times, which is why we treat that copy as personal data too (section 2). After you delete your data the identifier is no longer used, and its events expire as section 7 says.
- The data that AppLovin's software collects from your device is not held by us and is not under your player ID, so we cannot find it or delete it for you. Use AppLovin's own channels, which its privacy policy describes: its Privacy Management app (App Store, Google Play) for data tied to your advertising ID, and its request portal (https://applovin.com/en/privacy-data-request) for data tied to an email address or phone number.
- We answer within one month. We can extend that by two months for complex requests, and we will tell you why.
- It costs nothing, unless a request is clearly unfounded or excessive.
10. California and other US states#
This section is for residents of California and of other US states whose laws give similar rights.
- What we collected in the last 12 months. Identifiers (player ID, generated nickname, IP address in server logs, a random identifier that the app makes for our analytics service, and for a saved player the email address and the Google, Apple, Game Center or Google Play Games ID); account log-in credentials (the hash of a password); internet or other electronic network activity (your answers, their scores and timings, activity times, usage events, error reports); approximate geolocation (the country that our analytics service works out from an IP address). The software of the advertising service in the app, AppLovin, collects directly from your device, and we do not receive: identifiers (the advertising ID and, on iPhone, the vendor ID, on Android an App Set ID, and your IP address), internet or other electronic network activity (how you interact with ads, device and network details, and how the advertising software runs) and approximate geolocation (country and region from the IP address); section 2, "Advertising", lists them. The account log-in (email address with a password hash) is the one item that California law may class as sensitive personal information: we use it only to give you the service and to keep the account secure. We collect the rest directly from your device, and the sign-in IDs and a vouched email address from Google or Apple at your request.
- Why, and who receives it. For the business purposes in section 3. Our service providers (hosting; OpenAI, which receives no personal identifiers; the mailbox provider; the email delivery provider; Expo, which delivers app updates) receive it under contracts that limit their use. Our analytics service is run by FREEDOM LLP itself and is not a third party. The advertising service, AppLovin, receives the advertising data above to show and measure ads.
- Sale and sharing. We do not sell your account details, purchase records or answers, or give those to the advertising service. If rewarded ads are enabled, the SDK receives a random claim value that contains no player ID or sign-in details; our API separately links the claim to your player. Under some US state laws, making the advertising data above available to AppLovin so that it can show you ads counts as "sharing" for cross-context behavioural advertising, or as a "sale". You can opt out: on iPhone, say no to Apple's tracking prompt or switch Tracking off for the app in Settings, Privacy & Security, Tracking; on Android, delete your advertising ID or turn off ads personalisation in your phone's settings (usually Settings, Privacy, Ads); and you can opt out of interest-based ads from AppLovin at https://max.applovin.com/p/how-applovin-shows-you-ads. AppLovin describes the rights it gives residents of US states in its notice at https://legal.applovin.com/multistate-privacy-notice/. The app has no separate switch for this; the device settings above apply to every ad in the app. You can also write to us and we will tell you what we can do. We do not know players' ages, so the choices above are the same for every player.
- Your rights. To know what we collected, to have it deleted, to have it corrected, and not to be treated worse for using these rights. Use the routes in section 9. An authorised agent can write on your behalf; we will ask for the player ID and for proof of the agent's authority.
- Signals. An app does not receive the Global Privacy Control or Do Not Track signal that a browser can send. Use the device settings above.
- We give residents of other US states the same rights.
11. Children#
Knowtilus: Trivia Quiz Game is for people aged 13 and over and is not directed to children. We do not ask for your age and we do not knowingly collect data from anyone under 13. If we learn that a player is under 13, we will delete the data we hold about them (data that the advertising software sent to AppLovin is not held by us; section 9 names AppLovin's channels). If you are a parent or guardian and think your child is playing, write to us and we will delete the data we hold about them. Where the age of majority is above 13 in your country, you need the permission of a parent or guardian to accept our Terms. The app does not collect your age. If ads are enabled, the feature is not personalized based on age. If you are under 16, please ask a parent or guardian before you allow tracking or personalised ads.
12. Features that are not in the app yet#
The app today has none of the features below. Each one is described here so that you can see what would change before it does. We will update this policy, and where the law requires it ask for your permission, before a feature goes live. The usage events and error reports of section 2 cover these features too, once they are in the app.
When enabled: daily reminders and push notifications. A reminder that you set up in the app is a local notification: your device shows it at the time you chose, and no data leaves your device. If we later add notifications sent from our servers (for example a challenge from another player), we will store a push token that Apple or Google gives your device, linked to your player ID, and use it only to send notifications you allowed. The token is deleted when you turn notifications off, when Apple or Google reports it as invalid, or when you delete your data. Legal basis: your consent.
When enabled: rewarded ads. You may be offered an optional AppLovin ad to double the original jewels of an eligible wooden or iron-bound chest, or add one bonus air when your available free and bonus air total is below 3. Skipping costs nothing. A chest bonus does not change chest contents or odds, and ads do not change answer scoring. The app first asks our server for a claim linked to your player, the placement and the offer context. A random claim value is passed to the ad SDK; it contains no player ID or sign-in details. Our API separately associates the claim with the player who requested it. After the SDK reports an earned view, the app sends our API a completion assertion for that claim. In the current client-attestation mode, our server accepts or rejects that report using the claim owner, eligibility, expiry and daily limits; it does not receive independent confirmation from AppLovin. The server checks reward and balance rules, records the accepted claim, and issues the inventory grant once. The limit is up to 4 rewarded claims per UTC day, including no more than 3 extra-air claims; a lower configured limit may apply. A verified claim may be collected for up to 30 minutes, and air that becomes full can be collected after some is spent during that window. Claim records expire from our database after 7 days and are deleted with your player; the reward is in your progress ledger and is deleted with it.
When enabled: progression, collections and streaks. We will store, linked to your player ID, your level and depth record in each category, your daily streak, your collection (trophies, chests, in-game currency and cosmetics), and a ledger of what you earned. When you are the first player ever to give a valid answer, we may record you as its discoverer and show your nickname next to that answer. This data is deleted with your player.
When enabled: playing against other people. In a match, your opponent sees your generated nickname and, after each round, your answer. Bots may fill seats and are always labelled as bots. We may store a recorded match so that another player can later face a replay of your answers, under your generated nickname and labelled as a replay. You will be able to report and block players. A block is stored on our server against your player ID. Matches use the same player, guest or saved; there is no chat and no free-text name.
13. Changes to this policy#
We will change this policy when the app or the law changes. The date at the top shows when it was last updated. If a change matters to you, for example a new kind of data or a new recipient, we will tell you in the app before it takes effect and, where the law requires it, ask for your permission. We do this by raising the version of the Terms: the Terms screen then reads "We updated our terms" and the app asks you to agree again before it goes on, as it did for version 3, the version that describes the usage analytics and error reports, and for version 4, the version that describes the ads.
14. Contact and complaints#
Write to office@freedomgaming.co, or by post to 101 King's Cross Road, London WC1X 9LP, United Kingdom. For help with the game itself, see Support. If you are not happy with our answer, you can complain to the data-protection authority named in section 9.