This policy describes what Comeback ("the app") does and does not do with information related to you. It is written to be read, not skimmed past. If anything here is unclear, that's a bug in the writing, not in the app.
Comeback stores your sessions, your Gap Log entries, and everything you write on your device only. There is no account. If you never turn on the optional "Help improve Comeback" setting, nothing about your use of this app ever leaves your phone.
If you do turn that setting on, the app sends a small number of anonymous counts. Never anything you wrote, never your session data, never identifiable to you personally. The rest of this document explains exactly what that means.
If you're on the free tier, Comeback also shows a small number of ads, served by Google AdMob, starting one week after you install the app. Never in your first week, and never at all if you're a Pro subscriber. Section 5 below covers exactly what that involves and what Google's ad SDK can access.
The following stays on your device, is never transmitted anywhere, and is never accessible to us in any form, under any setting:
There is no account to create, so there is no server-side profile of you to begin with. If you export your data (a feature in Settings), that export file is created and stored by your device's own share/save mechanism; we never receive a copy.
This setting is off by default. You choose it during onboarding, and you can change your mind at any time in Settings.
If it's on, the app sends small event records so we can tell whether people are still using the app a week after installing it, nothing more granular than that. Each event contains only:
session_complete), which numbered session it was: 1st, 2nd, 3rd, and so onThe complete list of six events. Nothing else is ever sent:
| Event | What it means |
|---|---|
install | The app was opened for the first time, ever, on this install. |
app_open | The app was opened today (sent at most once per day). |
onboarding_complete | The welcome screens were finished. |
session_complete | A session ended. Carries only the session number, never its duration, its anchor, its rep count, or anything about how it went. |
track_day_complete | A day of the 28-day track was completed. No further detail. |
paywall_view | The upgrade screen was shown. |
You can see this exact list, the same table above, inside the app at any time: Settings → "What's sent?"
What is never included in any of these events, under any circumstance: anything you wrote in the Gap Log, your session's duration or rep count or anchor or timing, your onboarding answers, your device's advertising identifier, your device model or OS version tied to you personally, your location, or anything that would let us reconstruct what a specific session or day was actually like for you.
If you opt in, the app generates a random identifier, not derived from your device, your account (there isn't one), or anything about you, and stores it only on your device. This identifier is what lets us tell "the same install opened the app on day 1 and again on day 7" apart from "a different install opened it once." It cannot be used to look up who you are, because nothing connects it to your name, email, or any other identifying information; we never collect any of those in the first place.
Resetting the app (Settings → Reset) generates a new identifier. A fresh install always gets a new one.
Event data (if you opt in) is sent directly to a server we operate. There is no third-party analytics company, advertising network, or data broker in this chain: no Google Analytics, no Firebase, no Meta SDK, nothing. We are the only party that ever receives this information, and we do not sell, rent, or share it with anyone else.
This is a separate, unrelated data flow from the advertising described in §5 below. The anonymous usage events above go only to our own server, in the form described in §2, regardless of whether you ever see an ad.
If you're on the free tier, Comeback shows a small number of ads, served through Google AdMob. This section describes exactly when, and what that involves.
When ads appear. Never in your first 7 days on the app, regardless of how much you use it. After that, a free-tier user may see a full-screen (interstitial) ad after finishing a session. Separately, at your own choice, you can watch a short rewarded video ad in Settings in exchange for a bonus credit. This one is entirely opt-in; nothing plays without you tapping to start it.
Pro subscribers never see ads, in any form, from day one of a subscription.
What Google AdMob can access. Ads are served by Google's own AdMob SDK, running directly on your device. This is Google's software, operating under Google's own privacy policy, not something that passes through our server or that we can see. Depending on your region and the choices you make in the consent prompt described below, AdMob may use your device's advertising identifier (Android's Advertising ID, or Apple's IDFA on iOS), general device and app information, and ad interaction data, to select and measure ads. None of this is the same identifier as §3's installation identifier, and none of it is ever combined with your session data, your Gap Log entries, or anything else described in §1.
Consent. If you're in the UK or EEA, Google's User Messaging Platform presents a consent request before any ad can be requested, as required under GDPR. You choose what AdMob is allowed to use before the first ad ever loads. You can review Google's own advertising and privacy practices at Google's Ads Privacy & Terms and How Google uses data in AdMob.
What we, Comeback, never receive from advertising, regardless of region or consent choice: we do not see which ads you were shown, whether you tapped one, or any advertising identifier. That all stays inside Google's SDK and Google's own systems. The only thing Comeback's own code records about ads is whether you've unlocked a rewarded-ad credit, stored the same way as the rest of your on-device settings (§1).
What's deleted vs. kept: everything described in §1 (session history, Gap Log, onboarding answers, settings, track progress) lives ONLY on your device and is deleted the moment you do a local Reset; we never had a copy to begin with. The only thing that can exist on our server at all is the anonymous event data described in §2, and only if you opted in; that's what the email process above removes. There is no retention period beyond what you request removed. We don't keep anonymous events indefinitely by policy, but nothing is automatically purged after a fixed number of days either, which is why giving an approximate date range in your request matters.
Comeback is not directed at children and we do not knowingly collect information from anyone under the age of 13 (or the relevant minimum age in your jurisdiction). If you believe a child has provided us information, contact us and we will address it.
If this policy changes in a way that affects what's collected or why, we'll update the "Last updated" date above and, for material changes, surface a notice in the app itself.
Questions about this policy or your data: comebacktheapp@gmail.com
This policy is written to be an accurate, plain description of what the app actually does, grounded directly in its source code and internal specification. It is not a substitute for legal advice. A qualified lawyer familiar with your jurisdiction (GDPR if you have EU users, DPDP if you have Indian users, CCPA if California) should review this before you rely on it for App Store / Play Store submission, particularly the children's-privacy and data-subject-rights sections, which vary meaningfully by jurisdiction.