Legal
Cookie Policy
Plain English: The Later Android app uses no cookies. This website (thelater.app) sets no analytics cookies, no advertising cookies, and no tracking cookies. The only local storage used is the app's own database on your device.
01What are cookies?
Cookies are small text files placed on your device by a website or app. They can store preferences, session identifiers, or tracking data. Related technologies — such as local storage, IndexedDB, and shared preferences — serve similar purposes in mobile apps.
This policy covers all such technologies used by Later and the thelater.app website.
02Cookies in the Android app
The Later Android app does not use browser cookies. It does not embed a web view that sets cookies, does not use an advertising SDK, and does not use any analytics cookie.
The app interacts with Firebase over HTTPS. Firebase may use its own session tokens internally to maintain an authenticated connection; these are managed by the Firebase SDK in memory and are not accessible as browser cookies.
03Cookies on the thelater.app website
The thelater.app marketing website sets no cookies of any kind. It does not load Google Analytics, Meta Pixel, or any other third-party tracking script. It does not use a cookie consent banner because there is nothing to consent to.
The site loads fonts from Google Fonts (fonts.googleapis.com). This request is made by the browser and is subject to Google's own privacy policy. Google Fonts does not set cookies in response to font requests from third-party sites.
| Category | Used on this site? | Notes |
|---|---|---|
| Strictly necessary | None | Static site; no login, no shopping cart, no session state |
| Analytics / performance | None | No analytics SDK of any kind |
| Functional | None | No preference storage required |
| Advertising / targeting | None | No ad network, no retargeting pixel |
| Social media | None | No embedded social widgets |
04Local storage in the app
The app uses the following device-local storage mechanisms. These are not cookies, but are disclosed here for completeness.
| Storage | What's stored | Purpose | Type |
|---|---|---|---|
| Room database later_database.db |
All task content, states, reminder times | Core app functionality | Required |
| DataStore Preferences app_settings |
Theme mode (Light / Dark / Auto), last-sync timestamp | Persisting user preferences across launches | Required |
| Firebase SDK storage | Anonymous auth token, FCM device token, install ID | Anonymous authentication and push notification routing | Required |
| Crashlytics SDK storage | Crash session data, device model, OS version | Crash diagnostics (stability monitoring only) | Diagnostic |
All local storage lives inside the app's private data directory, sandboxed by Android. Other apps cannot read it. Uninstalling the app removes the Room database and DataStore preferences from your device.
05Third-party storage
Google Firebase stores your anonymous user ID and task content in Firestore (Google Cloud). Firebase may use its own cookies or tokens internally. Firebase's cookie and data practices are governed by Google's Privacy Policy.
No other third-party services are used by the app or this website that could set cookies or store local data on your device.
06Your choices
Because Later uses no analytics or advertising cookies, there is nothing to opt out of for the marketing website.
For the Android app:
- Delete all synced data: Settings → Account → Delete all my data. This clears your Firestore data and revokes the anonymous auth token.
- Crash diagnostics: Post-launch, an opt-out toggle will be available in Settings. Until then, crash data collection is on by default.
- Notifications: You can revoke notification permission at any time in Android Settings → Apps → Later → Notifications.
You can also clear the app's local storage at any time via Android Settings → Apps → Later → Storage → Clear Data. Note: this removes all locally stored tasks that have not yet synced.
07Changes to this policy
If we introduce analytics or other cookies in the future — for example, if we add aggregate, privacy-preserving usage stats to the website — we will update this policy before doing so and add a cookie consent mechanism if required by applicable law.
The version number and effective date at the top of this page are updated with each revision.