Privacy Policy — Anticipy

Last updated: 09/10/2026

Anticipy ("the app", "we", "us") is a countdown app built around anticipation and excitement for events you're looking forward to. This policy explains what happens to your data. It applies to the Anticipy apps for Android and iOS, the Anticipy web app, and the anticipy.app website.

Anticipy is currently operated by Marko Burkic, an individual developer based in France, not a registered company, who is the data controller for the processing described here. This section will be updated if that changes.

The short version

Anticipy is local-first. Your countdowns, photos, notes, and settings are stored on your own device — not on our servers, because we don't have any. We don't have your account, we can't see your data, and we can't lose it in a breach, because we never had it.

There are no ads in the app, and it does not use your device's advertising ID.

The only things that currently leave your device are:

• Crash and error reports and basic performance measurements, sent automatically so we can fix bugs (see "Crash Reporting" below)
• A request to Firebase Remote Config each time you open the app, to fetch a small set of app configuration values (see "Remote Configuration" below)
• If you buy Premium, the purchase itself, which is handled by Apple or Google, not by us (see "Purchases" below)
• Nothing else, at this time

If you use the optional calendar feature, the app also writes events to the calendar you choose on your device. Those events don't come to us — but if your calendar is an online one (iCloud, Google, Outlook), your own calendar provider will sync them the same way it syncs anything else you put there. See "Device permissions" below.

What data the app stores, and where

In the web app, "on your device" means your browser's own storage on that device. Clearing your browser's data for anticipy.app deletes it.

None of this is transmitted to us, sold, or shared with third parties. We simply don't have access to it.

Sharing countdowns

When you share countdowns, the app either creates a .anticipy file or a link (anticipy.app/i#…). Both are sent only where you choose to send them, using your device's own share options.

A share link carries the countdowns inside the link itself, after the #. Browsers never send that part of a link to a website, so the content of a shared countdown never reaches our servers or our hosting provider: the recipient's app or browser reads it directly. Anyone who has the link can see what it contains, so share it only with people you want to see it.

Device permissions

The app asks for a small number of device permissions. Each is optional, each is requested only when you first use the feature that needs it, and none of the resulting data is sent to us.

Notifications

Used to remind you about your countdowns. Reminders are scheduled by your device's operating system and are not sent from a server.

Camera and photo library

Used only when you choose to add an image to a countdown or save a Share Card. Images you select are stored on your device and are never uploaded. Adding a Share Card to your photo library requires a separate permission, which is only requested at the moment you save one.

Calendar

Entirely optional, and off by default. If you turn it on for a countdown, the app can:

• Create an event in a calendar you choose
• Update that event if you change the countdown's date, time or name
• Remove that event if you delete the countdown
• Create a separate calendar named after the app, if you enable that option, so your countdowns stay visually separate from the rest of your schedule

The app also reads a limited part of your calendar, and we want to be clear about why. If you added a countdown to your calendar before granting access — through your device's own "add event" screen — the app never receives a reference to the event that was created, so it cannot keep it up to date afterwards. When you later grant calendar access, the app looks for those events so it can reconnect them rather than creating duplicates. That search is deliberately narrow: it looks only in the calendar you selected, only within a short window around that countdown's date, and only for an exact match on the title and date. Anything it reads is used for that comparison and immediately discarded. It is never stored, never analysed, and never transmitted.

The app stores a local reference (an event identifier and a calendar identifier) so it knows which event belongs to which countdown. These references stay on your device, are deliberately excluded from exports, shared files and backups, and are never sent to us.

Events created in an online calendar leave your device by way of your own calendar provider. If the calendar you choose is an iCloud, Google or Outlook calendar, the event you create will sync to that provider exactly as any other event would. That is your existing relationship with them, not a transfer by us, but it is worth knowing before you pick a calendar.

You can revoke calendar access at any time in your device settings. Events already created stay in your calendar — the app simply stops being able to update or remove them, and will tell you so.

Purchases

Anticipy Premium is a one-time in-app purchase in the Android and iOS apps. The payment is processed entirely by Google Play or the Apple App Store. We never receive your name, email address, or payment details.

To unlock Premium, and to restore it later ("Restore purchases"), the app asks the store whether the account signed in on your device owns Premium. The store's answer is kept on your device. Google's and Apple's own privacy policies apply to the purchase itself.

Crash Reporting

Anticipy uses Sentry, a third-party error-monitoring service, to automatically detect and report crashes and technical errors. This helps us catch and fix bugs before they affect more people.

When an error occurs, we may receive:

• A technical description of the error (e.g. what code failed and why)
• Device/OS/browser information relevant to debugging
• App version
• A random identifier created when the app is installed, so we can tell whether several reports come from the same installation. It is not linked to you, your account, or your device's advertising ID, and a new one is created if you reinstall the app

The app also sends basic performance measurements (for example, how long the app takes to start), with the same technical details.

We do not configure Sentry to capture the content of your countdowns (titles, notes, images, dates), your calendar entries, or the names of your calendars as part of error reports. Where an error could technically expose a filename derived from something you named — for example if saving a file fails — the app automatically removes that information before the report is sent, keeping only the technical reason for the failure.

Reports are stored in Sentry's European data centre (Germany) and deleted automatically after 30 days. We rely on our legitimate interest in keeping the app working and fixing its bugs (GDPR Article 6(1)(f)).

If you believe an error report may have inadvertently included personal content, contact us using the details below and we'll investigate and delete it.

Sentry's own privacy practices are described at sentry.io/privacy.

Remote Configuration

Anticipy uses Firebase Remote Config, a Google service, to fetch a small set of app configuration values each time the app launches. This lets us adjust certain in-app behavior without shipping an app update.

The request contains a random installation identifier generated by Firebase, the app version and the platform. We do not send any of your countdowns, settings, or other personal content as part of that request. As with any network request, it does reach Google's servers and reveals your device's IP address, the same way visiting any website would. We rely on our legitimate interest in running and adjusting the app (GDPR Article 6(1)(f)).

Google's own privacy practices are described at firebase.google.com/support/privacy.

Website and web app hosting

anticipy.app and the web app are hosted on Firebase Hosting (Google). Like any web host, Google processes visitors' IP addresses and basic browser information to deliver the pages and protect the service. We do not use cookies, trackers or analytics on the website.

Transfers outside the EU

Google and Sentry are based in the United States and may process the technical data described above outside the European Union. Where they do, the transfer relies on the safeguards approved by the European Commission (the EU–U.S. Data Privacy Framework and/or Standard Contractual Clauses).

Analytics

No usage analytics are active in the app or on the website. If that ever changes, this policy will be updated before it goes live, and a consent choice will be added where the law requires one.

Your rights

Because your data lives on your device, you already have full control over it:

• Access & portability: Use the in-app Export feature to save your data as a .anticipy file at any time (a standard zip archive containing your data as JSON, plus any photos).
• Erasure: Use the in-app Trash and database-wipe options in Settings to delete individual countdowns or all app data. Uninstalling the app also removes all locally stored data from your device.
• Correction: Edit any countdown directly in the app at any time.
• Calendar: Events the app created remain in your own calendar and are yours to edit or delete there at any time, independently of the app. Uninstalling the app does not remove them.

If you're in the EU/EEA, these map to your rights under the GDPR (Articles 15, 16, 17, and 20) — though because we don't hold your data on a server, most of these are things you can already do yourself, instantly, in-app, without needing to contact us.

For the crash reports and technical data described above, you can also ask us for access or deletion, or object to their processing (GDPR Article 21), by writing to the address below. You also have the right to lodge a complaint with your data protection authority — in France, the CNIL (cnil.fr).

Children's privacy

Anticipy is not directed at children under 13 (or the relevant age of digital consent in your country), and we do not knowingly collect data from children, consistent with the "local-first, no account" design described above.

Changes to this policy

If Anticipy's architecture changes — for example, if we introduce optional cloud sync, user accounts, advertising, or analytics — this policy will be updated before that feature goes live, not after, and the "Last updated" date above will reflect that change.

Contact

Questions about this policy or your data? Reach us at:

privacy@anticipy.app