Privacy Policy

Information the service handles

• Accounts: email address, Supabase Auth user ID and authentication/session metadata.
• Following and preferences: private followed-artist records, alert rules, product state and catch-up cursor.
• Push notifications: the device's push endpoint and public subscription keys, delivery outcomes and requested alert preferences.
• Community Hype voting: a randomly generated browser voter ID, rumour ID, vote and timestamps. It is not connected to an account.
• Community discussion voting: public handles, posts, comments and votes, plus private reports, moderation records and sanction state.
• Submitted signals: artist, URL, explanation, optional source and date, moderation status and timestamps. The form does not store an IP address in the submission table and does not attach an account email.
• Artist research requests: artist, aggregate demand and queue state. A private keyed one-way hash derived from an account ID or anonymous browser token prevents repeated requests without retaining the original identifier.
• Voluntary feedback and problem reports: survey answers or the problem details you choose to submit, limited diagnostic context such as page, build, device category and browser versus installed-app mode, and optional contact details when you ask for a reply. Survey answers are not attached to a persistent visitor or account identity.
• First-party product analytics: when analytics is globally enabled and this browser has not switched it off, a random short-lived tab session ID, bounded event name, server timestamp and limited context such as rumour ID, feature or screen. Product analytics does not store a persistent account identity. Search text, private Follow lists, comments, signals, evidence text, URLs, emails and raw IP addresses are not analytics-event properties.
• Google Analytics: only after you allow it, Google's tag uses cookies and receives page location, page title, device/browser information and interaction measurements supplied by Enhanced Measurement. Worthy Watch does not send Google email addresses, Auth IDs, private Follow data, submissions, Community content or other custom private data.
• Operational security: limited error information is retained where needed. Rate-limit counters store a keyed one-way hash derived from an account ID or request IP. Hosting and authentication providers also process request and security logs.

Purposes and UK GDPR lawful bases

• Contract: account creation, authentication, Following, requested alerts, account settings and deletion are processed where necessary to provide the service the user asks for.
• Legitimate interests: protecting the service, preventing abuse, moderating Community, maintaining proportionate audit records, reviewing signals and artist requests, and publishing or preserving public discussion context. The interests are operating a safe, reliable festival-intelligence service and protecting users and the service from misuse.
• Legitimate interests: understanding aggregate feature use and reliability so Worthy Watch can improve the service. The analytics design is minimised for statistical use, and the internal assessment records necessity, user expectations and safeguards.
• Consent: Google Analytics runs only after you make an affirmative choice in this browser. You can withdraw that choice at any time below.
• Legal obligation: information may be processed where necessary to meet applicable data-protection duties or binding lawful requests. Legitimate interests may also support establishing, exercising or defending legal claims.

Worthy Watch does not use either analytics system for advertising, marketing, profiling or automated decisions about users.

Analytics and browser storage

The app has no advertising analytics. Essential browser storage supports login, security, theme, voting, return navigation and service-worker operation. Worthy Watch's separate first-party analytics remains privacy-minimised and does not use analytics cookies.

When first-party product analytics is globally enabled, it is on by default. You can reach this page through Privacy & analytics in the navigation and switch it off at any time. The off preference persists in this browser. It immediately prevents future analytics events and analytics-session creation without affecting authentication, theme, security or other essential storage.

The random analytics session rotates after 30 minutes of inactivity or 24 hours and is not an account or cross-device identity. Worthy Watch uses these events only to understand aggregate product use, including public page views, forecast views, searches, sharing, feature use and PWA installation signals. Page-view events use a coarse category and, for public artist pages, the existing artist forecast ID; full URLs and query strings are not stored. It does not use them for advertising, profiling or browser fingerprinting.

Google Analytics is off unless you affirmatively allow it. When allowed, Google's tag and cookies measure page loads, client-side navigation and Enhanced Measurement interactions. The choice is stored in this browser. Withdrawing it stops future Google Analytics collection from Worthy Watch and attempts to remove the Google Analytics cookies set for this site.

Suppliers, recipients and international processing

• Supabase: provides the database, authentication and Auth email infrastructure as a service provider.
• Vercel: hosts the application and processes requests, network information and operational logs. Vercel may also act as a controller for service-generated data under its own terms.
• Google Analytics: after consent, provides third-party website measurement and processes device, cookie, page and interaction data under Google's terms and privacy information. Worthy Watch does not enable Google Analytics advertising features through this integration.
• Browser and operating-system push services: when push is enabled, the service selected by the user's browser or device receives the push endpoint and encrypted notification traffic under its own terms.
• External websites: opening a source or social-sharing destination sends a request to that third party, which applies its own privacy information.

These services may process information outside the UK.

Worthy Watch does not sell account information.

Retention and account deletion

Raw product events are kept for 35 days, the shortest practical window that preserves exact Today, 7-day and 30-day reporting with a small aggregation safety buffer. Older history is kept only as anonymous daily statistics without account IDs or raw session IDs.

Public Community contributions remain while they are useful to the discussion or until removed under the Community rules. Account deletion removes the Community profile and its private state and votes, while posts and comments may remain without the deleted profile so discussions remain coherent. Open reports and necessary moderation records may be retained until resolved and then for the period above.

Self-service account deletion removes the Supabase Auth account and cascades deletion of saved follows, alert rules, push subscriptions, user-specific delivery records, reply notifications and personalised product state. New product analytics is not linked to the Auth account, and anonymous aggregate statistics cannot be used to identify and remove one person's activity. Legacy analytics rows may retain their historical account reference until the approved raw-retention cleanup runs. Anonymous Community Hype votes, signal submissions and private artist-request deduplication hashes are not linked back to the Auth account.

Problem reports and voluntary survey responses are retained only while they remain useful for investigating problems and improving Worthy Watch. A final retention period has not yet been approved. If a signed-in person asks to be contacted about a report, deleting the account removes the account link but does not automatically remove the report itself. Anonymous survey answers cannot be linked back to an account.

Provider backups and security logs expire under the configured provider plan and retention settings. Those settings must be verified before launch.

Security

Passwords, password hashes and reset tokens are handled by Supabase Auth and are not stored in Worthy Watch application tables. Private records use ownership-based row-level security or server-only access. Administrative access is separate from ordinary accounts. No online service can promise absolute security.

Your rights

Depending on the circumstances and lawful basis, you may have rights of access, correction, deletion, restriction, objection and portability. You can switch product analytics off at any time using the control above. Send requests or complaints to festivalsocials1966@gmail.com.

You can also complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint or telephone 0303 123 1113. The operator should normally be given an opportunity to resolve the concern first.

Changes and contact

Material changes will be shown here with an updated date. Contact festivalsocials1966@gmail.com.