Privacy policy

Last updated: July 3, 2026

ConcertPrep is a non-commercial fan project. It collects the minimum it needs to work, shows no ads, runs no third-party analytics or trackers, and never sells or shares your personal data.

What we collect

Your account — if you sign in with Google, we receive your name, email address, and profile image from Google. Browsing and predictions work fully without an account.
Your follows — the artists you choose to follow (stored as an artist identifier and name).
Your concert log — shows you mark as attended (stored as show references and dates), plus any ratings and notes you write.

That's the whole list. We don't collect your location, contacts, or browsing history.

Cookies

A theme preference cookie — remembers your display theme.
Session cookies — keep you signed in. Set only when you sign in.

No advertising or tracking cookies, ever.

Where your data lives

The app runs on Cloudflare Workers; account data, follows, and your concert log are stored in a Neon (Postgres) database. Setlist data itself comes live from setlist.fm and is held only in a short-lived server cache — ConcertPrep does not keep a permanent copy of it, and your concert log stores references to shows, not the setlists themselves.

Requests to setlist.fm are made by our server, not your browser — setlist.fm never sees your IP address or identity.

Third parties

Google — sign-in only, under Google's own privacy policy.
Cloudflare & Neon — hosting and database infrastructure that processes data on our behalf.
setlist.fm — the source of concert data; it receives our server's queries, never your personal data.
Ticketmaster — the source of upcoming tour dates; it receives our server's queries, never your personal data. Ticket links open on Ticketmaster's own site.

Your data, your call

Want a copy of your data, or everything deleted? Email adnan.reza@outlook.com from the address on your account and it'll be handled — deletion removes your account, follows, and concert log.

Changes

If this policy changes in a way that matters, the date above changes with it. Continued use after a change means the new version applies.