Knowtilus: Trivia Quiz Game

Privacy Policy

Last updated 4 November 2026

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.

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.

DataWhat it is and where it comes fromWhat we use it for
Player ID and sessionsWhen 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 detailsWhether 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 addressOnly 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.
PasswordOnly 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 GamesOnly 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 codesWhen 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 nicknameChosen 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 timesWhen 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 answersFor 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 statisticsPer 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 dataYour 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 eventsShort 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 reportsWhen 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 identifierA 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.
AdvertisingThe 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 claimsIf 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 purchasesWhere 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.
ReportsIf 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 usIf 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#

Usage analytics, error reports and our analytics service#

When the analytics start and stop#

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 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#

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.

If the GDPR or the UK GDPR applies to you, these are the legal bases we rely on.

PurposeLegal 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 listsPerformance 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 sessionsPerformance 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 claimsOur 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 statusPerformance 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 gameOur 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 requestsOur legitimate interest in supporting you, and legal obligations for rights requests (Article 6(1)(f) and (c))
Complying with legal requestsLegal 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#

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.

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#

DataHow 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 itWhile 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 playerThe 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 enabledClaim 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 requestsA 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 it12 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 verdictsIndefinitely. 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 serviceThe 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 AppLovinUnder 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 records24 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
BackupsRolling 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 us24 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 OpenAIUp 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#

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:

How to use them.

10. California and other US states#

This section is for residents of California and of other US states whose laws give similar 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.