← Beat ID

Cookie Policy

Last updated 12 June 2026

Draft — pending legal review. This is placeholder wording surfaced by the product; the final terms will be reviewed and finalised by counsel before public launch.

This Cookie Policy explains how beatid.me uses cookies and similar browser-storage technologies, under the Privacy and Electronic Communications Regulations 2003 (PECR). It should be read with our Privacy Policy.

1. What we use

beatid.me is deliberately light on browser storage. We do not use third-party advertising or analytics trackers — there is no Google Analytics, no Meta Pixel, and no cross-site advertising cookie. Our own page-view analytics are anonymous (a per-DJ counter only — no IP, no device identifier).

StoragePurposeType
Firebase Authentication (local storage / session)Keeps a signed-in DJ logged in between visitsStrictly necessary
Checkout (Stripe-hosted page)Stripe sets its own cookies on its hosted checkout to process payment securelyStrictly necessary (Stripe)

2. Strictly-necessary storage

Firebase Authentication uses your browser's local storage to maintain your login session. This is essential for the service you have requested (staying logged in) and is exempt from prior consent under PECR's "strictly necessary" exemption. If you are not signed in as a DJ, no such storage is set.

3. Managing storage

You can clear or block browser storage at any time via your browser settings. Blocking the strictly-necessary Firebase Auth storage will prevent you from staying logged in as a DJ but does not affect browsing public profiles or buying music.

4. Updates

This policy is published ahead of a formal cookie audit and will be updated if that audit identifies any additional storage. The "Last updated" date above reflects the latest revision.