Privacy Policy
The short version. CONTINUE? has no accounts and no sign-in. Your game pile, your coins, your rankings and your settings live on your phone, not on a server. We never ask for your name, email, phone number, contacts, photos library or location.
Three things do involve other companies: Google AdMob serves the optional rewarded ads you choose to watch, RevenueCat and Google Play process purchases (and RevenueCat checks that a rewarded ad was really watched before its reward is given), and our own small server looks up game information for you. What each of them receives is spelled out below.
CONTINUE? is an independent app built and operated by Mikhil Naika. For anything in this policy — questions, complaints, or a data deletion request — contact naikamikhil@gmail.com.
The following is stored locally on your phone. It is not uploaded, backed up to us, or visible to us in any form:
Images you share into the app are processed entirely on your device. When you share a screenshot to CONTINUE?, the text in it is read by Google ML Kit's on-device text recognizer. The image is never uploaded to us or to anyone else, and the app never requests access to your photo library.
Uninstalling the app deletes all of this. Your pile, rankings and the friends' piles you follow are included in your own Android device backup (which Google stores for you, not us), so they can be restored to a new phone.
CONTINUE? talks to a small backend of ours at
continue-worker.gamestoplay.workers.dev, hosted on Cloudflare Workers. It exists so
that game data can be fetched without shipping API keys inside the app. It sends:
| What | When | Why |
|---|---|---|
| The search term you type | When you search in DISCOVER | To look the game up and return matches |
| Text you deliberately share into the app (for example a video caption) | Only when you use the Android share sheet to send something to CONTINUE?, and only if the app cannot already identify the game offline | To work out which game the text refers to |
| A game's numeric ID | When a screen needs details or key art for a game | To fetch that game's information |
No identifier is attached to these requests. There is no user ID, no device ID, no advertising ID and no cookie in them, so we cannot tie one request to another or build any profile. We do not log the contents of your requests.
As with any internet request, our host (Cloudflare) sees the originating IP address. It is used only to enforce rate limits that stop the service being abused, and it is not stored by us or joined to anything. Search results are cached for up to 24 hours, keyed by the search term itself, so that repeated lookups are fast and cheap.
If you are offline, the app falls back to its on-device index and database and sends nothing at all.
CONTINUE? can share a game with a friend, and can make an image summarising your pile, a game you cleared, or your all-time top ten.
Nothing about a share reaches us. The image is drawn on your phone from data already on your phone, saved into the app's own private cache, and handed to whichever app you choose in Android's share sheet. The message and the link are assembled on your device too. Your phone does not contact our server in order to share anything, and we are never told that you shared, what you shared, or who you shared it with.
What you share is your choice, and it is visible to whoever receives it. A pile card shows your total hours and game count; a cleared card shows a game, its length and its position in your ranking; a high-scores card shows your top ten. Once you send it, it is in the hands of the app and the people you sent it to, exactly like any other photo or message. Nothing is posted anywhere on your behalf and nothing is shared automatically.
Game links you send are public. A shared game link looks like
continue-worker.gamestoplay.workers.dev/g/1942 — a game's numeric ID and nothing
else. It contains no identifier for you, so it cannot be traced back to you or to your pile,
and anyone holding the link sees the same page as anyone else. When someone opens it, their
device (or their messaging app, generating a preview) requests that page from our server and
loads the game's artwork from IGDB, as described in section 6. That request comes from
their device, not yours.
You can share your whole pile with a friend who also uses CONTINUE?, and follow theirs. This works without accounts and without our server storing anything.
What a pile link contains. When you tap SHARE on the "Share your pile" screen, the link in the message lists every game in your pile (as numeric game IDs), which state each one is in, your ranked top games, the time you shared, a sequence number, and a public key. It does not contain your name, an account, a device ID or an advertising ID. The app says this on the share screen before you send it. Anyone you send the link to — and anyone they forward it to — can see that list.
The link never reaches our server with your pile in it. The pile is placed
in the part of the link after the # (the "fragment"), which web browsers do not send
to servers. If someone without the app opens the link, their browser requests a static page from
our server that is identical for everyone; the game list stays in their browser. When someone
with the app opens it, the app reads the list on their phone.
The public key. Your phone creates a random key pair the first time you share your pile. The public half is included in your links so your friends' phones can tell that a newer link really came from the same person, and so nobody else can overwrite your pile on their phone. It is not derived from anything about you or your device, it is never sent to us, and it is excluded from device backups. You can replace it at any time with FRIENDS → Start a fresh share link; friends who followed the old key keep the last copy you sent and cannot connect it to the new one.
When you follow a friend. Nothing is saved until you choose a name for them. That name is stored only on your phone. Their pile is stored on your phone and is updated only when you open a newer link from them — it is not live. To show their games, your phone asks our server for game details by numeric game ID, exactly as described in section 3; no identifier for you or your friend is attached. You can rename or remove a friend at any time, and removing them deletes their pile from your phone.
Purchases are handled by Google Play Billing. We never see or receive your payment details — Google does not share them with us.
We use RevenueCat to manage subscriptions and entitlements. RevenueCat issues your install an anonymous app user ID (a random string, not linked to your name, email or Google account) and records your purchase history against it, so the app knows whether Pro is active. We do not send RevenueCat your name, email address or any other personal identifier.
See RevenueCat's privacy policy and Google's privacy policy.
CONTINUE? shows rewarded ads only. There are no interstitials, no banners and no ads that appear on their own. An ad plays only after you tap a button that says what you get for watching it, and you can always decline.
Ads are served by Google AdMob. Per Google's published disclosure, the Google Mobile Ads SDK collects and shares the following for advertising, analytics and fraud prevention:
This data goes to Google and its advertising partners, not to us.
RevenueCat verifies rewards and records ad events. When you choose to watch a rewarded ad, the app gives AdMob a one-time token from RevenueCat. When you finish the ad, AdMob tells RevenueCat, and RevenueCat grants the reward you were promised (a coin, or an hour of Pro) — this is what stops rewards being faked. RevenueCat also records that an ad loaded, was shown or was tapped, the ad network's estimate of what it earned, and which button it was offered from, all against the same anonymous app user ID described in section 4. No advertising ID, name, email or location is sent to RevenueCat. We use these records only to understand how the optional ads perform, alongside purchases.
If you are in the EEA, the UK or Switzerland, CONTINUE? shows you Google's consent form the first time you open the app, and requests no ads until you have answered it. You can change your answer whenever you like: open the YOU tab and tap AD PRIVACY CHOICES.
If you consent, the ads you choose to watch may be personalised using the identifiers described above. If you decline, you will still be offered rewarded ads, but they will be non-personalised — chosen from general context rather than from anything about you or your past activity, and your advertising ID is not used to profile you. Either way the ad is optional: nothing plays unless you tap a button that first tells you what you get for watching it.
Declining changes nothing else in the app. Your pile, the draw, ranking, sharing and offline use all work identically, and you can still earn coins by clearing games, or receive them with Pro.
Your controls: on Android, open Settings → Google → Ads to delete or reset your advertising ID, or to opt out of ad personalisation entirely. The app keeps working if you do. See how Google uses data from apps that use its services.
Buying Pro removes ads from the app entirely.
Game titles, cover art, release dates, ratings and playtime estimates come from IGDB.com. The data was freely provided by IGDB.com.
Game data — titles, dates, genres, playtime estimates — is requested by our server, never by your device, so IGDB's data API never sees anything about you.
Cover art and key art are different. Those images are served from IGDB's
image CDN at images.igdb.com, and your device loads them from there directly, the
same way any app or web page loads an image hosted elsewhere. That means IGDB's CDN sees your
device's IP address and the images you requested, as any image host would. We do this because
proxying every cover through our own server would be slower, would cost far more, and would not
meaningfully change what IGDB could infer. IGDB's own
privacy policy governs what they do
with it. No identifier of ours travels with those requests.
CONTINUE? is not directed to children. It is rated for users aged 13 and over, and we do not knowingly collect any data from children under 13. If you believe a child has provided data through this app, contact us and we will delete it.
GPA.0000-0000-0000-00000). We will action the request within 30 days.We hold no server-side account for you, so there is nothing else of yours for us to delete.
Cached search results expire within 24 hours. We keep no request logs containing your queries. RevenueCat retains purchase history for as long as the app is in service or until you ask for deletion. Data on your device is kept until you delete it.
All network traffic uses HTTPS; the app explicitly disables cleartext networking. Our backend holds no personal data, so there is no user database to breach. No method of transmission is perfectly secure, but the strongest protection here is structural: we do not collect the data in the first place.
Depending on where you live — for example under the GDPR in the EEA and UK, or the CCPA in California — you may have rights to access, correct, delete or port your personal data, and to object to its processing. Because we hold no personal data about you beyond an anonymous purchase record, most such requests are satisfied by the deletion steps in section 8. Write to naikamikhil@gmail.com and we will help. We do not sell or share your personal information as those terms are defined by the CCPA.
If this policy changes materially, the date at the top will be updated and the change will be noted in the app's release notes. Past versions are visible in the app's public source repository, since this page is committed alongside the code.
Mikhil Naika · naikamikhil@gmail.com · source code