cuemark.

Privacy Policy

Last updated: 2026-06-17

cuemark is built and operated by Mike Bradshaw (sole developer; reachable at [email protected]). This policy explains what data the app and backend collect, why, where it lives, and what your choices are.

It's written in plain English on purpose. If something isn't covered here, ask — we'll either tell you or update the policy.

1. What we collect

Account

Activity you save in the app

Device + usage

What we do NOT collect

2. Where data lives

Third-party APIs cuemark calls but never sends your personal data to: TMDb (film metadata + posters), YouTube Data API (trailer playlists), SerpAPI (Google Showtimes results), and cinema chain sites / Fandango (showtime cross-checks). These see no user identifiers — just anonymous backend requests.

3. Sharing

We don't sell or rent your data. We share only when:

4. Your choices

5. Crash + diagnostic data

When the app crashes, we record: the stack trace, iOS version + device model, and the cuemark build number.

We do not record: the contents of your watchlist or itinerary, your email address, or your location at time of crash.

If we add a crash reporter (Sentry/Bugsnag), this policy will be updated to name it. As of this version, crash data is whatever TestFlight / App Store Connect exposes by default.

6. Children

cuemark is not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has signed up, email [email protected] and we'll wipe the account.

7. International users

The cuemark backend runs on Cloudflare's network, which has data centers globally. By using cuemark from outside the US, you consent to your data being processed in the US and/or the UK.

If you're in the EU/UK and want to exercise GDPR rights (access, deletion, portability), email [email protected] and reference the email on your account. We'll respond within 30 days.

8. Changes

If we change this policy materially, we'll notify TestFlight + App Store users via in-app banner before the change takes effect.


Questions: [email protected]. We read every one.