1. Who We Are
SAINTSINNERS LTD ("PartyRadar", "we", "us", "our") — a company registered in Scotland under number SC821579, registered office 1/2 31 Tobago Place, Glasgow, G40 2RT, United Kingdom, trading as PartyRadar — is the data controller for personal data collected through the PartyRadar app and website (partyradar.org).
We are committed to protecting your privacy and handling your data in an open and transparent way. This policy explains what data we collect, why, and how we use it. It applies to all users of the Service in the United Kingdom and European Economic Area (EEA).
Our lead supervisory authority under UK GDPR is the Information Commissioner's Office (ICO).
2. Data We Collect and Why
We collect and process the following categories of personal data:
| Data | Purpose | Legal Basis (UK GDPR) |
|---|---|---|
| Name, email address, username | Account creation and identification | Contract (Art. 6(1)(b)) |
| Date of birth | Age verification (18+ requirement) | Legal obligation (Art. 6(1)(c)) |
| Profile photo | Profile display and community features | Consent (Art. 6(1)(a)) |
| Location data (approximate) | Showing nearby events and users | Consent (Art. 6(1)(a)) |
| Device token (FCM) | Push notifications | Consent (Art. 6(1)(a)) |
| Payment information | Ticket purchases, subscriptions, wallet top-ups | Contract (Art. 6(1)(b)) |
| Event and RSVP history | Core Service functionality | Contract (Art. 6(1)(b)) |
| Messages and DMs | In-app messaging (end-to-end encrypted) | Contract (Art. 6(1)(b)) |
| IP address and device info | Security, fraud prevention, analytics | Legitimate interests (Art. 6(1)(f)) |
| Usage data (pages viewed, taps) | Product improvement | Legitimate interests (Art. 6(1)(f)) |
We do not collect special category data (e.g. health, biometric, racial or ethnic origin data) except where you voluntarily disclose it in your profile bio, which is publicly visible.
3. Location Data
PartyRadar uses your device location to show you events and users near you. Location access is optional — you can use the Service without granting location permission, but nearby features will be unavailable.
- We request "While Using the App" permission on iOS and "Foreground" permission on Android.
- We do not request background location access.
- Your precise coordinates are used server-side to calculate distances; we store only your last approximate city, not a continuous location history.
- Location data is not shared with advertisers.
4. Cookies, Analytics and Tracking
Our website and our iPhone and Android apps (which load the same interface from partyradar.org) use the technologies below. You can switch the optional measurement off at any time, without signing in, with this control:
Analytics choices
Analytics and affiliate tracking on this device
Covers Google Analytics, PostHog, our ticket-link click log and the affiliate-network redirects (Impact, Awin) on ticket links. Your choice is saved on this device and works without signing in.
Checking this device…
Not affected: essential sign-in storage, Sentry error reports, Vercel page-speed measurement, and the tags that stay on ticket links (see below).
- Essential storage: the pr_auth cookie that keeps you signed in, sign-in data that Google Firebase stores on your device, and preferences saved in your browser’s local storage (for example your language, theme and the analytics choice above). These are needed for the Service to work and are not affected by the analytics choice.
- Google Analytics 4 (Google LLC): records the pages and screens you open and some of the actions you take, using cookies set on partyradar.org that hold a random identifier. We do not pass your PartyRadar account id to Google Analytics.
- PostHog (PostHog, Inc.): records page views, when you leave a page, and the buttons, links and forms you use (including the text shown on them), using a cookie and local storage on partyradar.org that hold a random identifier. This data is sent to PostHog’s servers in the United States. If you are signed in, it is linked to your account id, email address, username, display name, plan, account mode, role, age-verification status and sign-up date, so we can support you and measure retention. Visitors who are not signed in do not get a PostHog profile.
- We do not record session replays (video-like playback of what you do on screen).
- Error reports (Sentry, run by Functional Software, Inc.): if the website, the app or our servers hit an error, a report describing the error, the page or request involved and your browser and device type is sent to Sentry’s EU data region, together with a small sample of page and request timings. We use it only to find and fix faults. It is not affected by the analytics choice.
- Page-speed measurement (Vercel Speed Insights, Vercel Inc.): measures how quickly our pages load so we can keep them fast. It is not affected by the analytics choice.
- Ticket-link click log (our own): when you tap a ticket link we record the event, the seller’s website, whether the link was an affiliate link, which button you used, the kind of page the button was on (for example an event page or a city page), whether you were on the website, the iPhone app or the Android app (worked out from your browser identifier, the user agent), a one-word source for your visit (search, social media, a paid advert, a shared link, email, another website, direct, the app, or unknown), the language of the translated city page your visit started on, if it started on one (for example sv for /sv/city/milan), and the time. We also store a shortened one-way hash of your IP address and user agent, which we use to avoid counting one tap twice. It is not linked to your account, and we do not follow you onto the seller’s site.
- How the one-word source is worked out: when you arrive on the website, your browser looks at the site you came from and at any campaign tags on the link you followed (such as utm_source or a click id like fbclid or gclid) and keeps only the resulting word, in this tab’s session storage under pr_landing_channel, until the tab is closed. The address of the site you came from and the campaign names are never stored or sent to us. While analytics is turned off, the word is not worked out or stored, and no click is logged.
- How the starting language is worked out: when you arrive on the website, your browser checks whether the first page you open is a translated city page (for example /sv/city/milan) and keeps only its language code (sv), or a dash (-) if you arrived anywhere else, in this tab’s session storage under pr_landing_locale, until the tab is closed. The page address and the city are never stored or sent to us. While analytics is turned off, the language is not worked out or stored.
- Tags on ticket links: most ticket links carry utm_source=partyradar and utm_medium=web or app, so the seller can see that the visit came from PartyRadar. Skiddle links also carry PartyRadar’s Skiddle affiliate tag and a campaign name that says whether you came from the website, the iPhone app or the Android app and which button you used; Skiddle uses it to pay us a commission on tickets bought through the link. These tags are part of the link to the seller’s own website and stay on it even when analytics is turned off. What a seller does with them is covered by that seller’s own privacy policy. Links to See Tickets’ UK website carry none of our tags: Awin’s redirect adds its own instead (see below), and without the redirect they go to See Tickets untagged.
- Affiliate-network redirect (Impact): links to Ticketmaster and the other sellers in its affiliate programme (for example TicketWeb, Universe, Front Gate, Moshtix, Biletix and Quicket) first go to Impact’s redirect at ticketmaster.evyy.net. Before sending you on to the seller, Impact may pass you through other Impact domains, sets cookies on its own domains and adds its own click reference to the seller link, so that a purchase can be credited to PartyRadar. The link tells Impact which button, platform (website, iPhone or Android) and kind of page you came from — never who you are — and Impact does not give us your name or contact details. With analytics turned off, these links go straight to the seller instead.
- Affiliate-network redirect (Awin): links to See Tickets’ UK website first go to Awin’s redirect at www.awin1.com. Before sending you on to See Tickets, Awin sets cookies on its own domains and adds its own click reference and tags to the See Tickets link, so that a purchase can be credited to PartyRadar. The link tells Awin which button, platform and kind of page you came from — never who you are — and Awin does not give us your name or contact details. With analytics turned off, and, for now, in the iPhone and Android apps, these links go straight to See Tickets instead.
- What turning analytics off does: on that browser or in that app, it stops Google Analytics and PostHog, stops the ticket-link click log, and sends links that would go through an affiliate network’s redirect (today, Impact and Awin) straight to the seller. It does not remove the tags on ticket links described above, does not switch off essential storage, Sentry or Speed Insights, and does not delete cookies that were already set — you can clear those in your browser settings. The choice is stored on your device, so it is reset if you clear this site’s data. In the PartyRadar app the same switch is also under Settings → Privacy.
- We do not load advertising pixels (such as Meta, TikTok, Snapchat or Google Ads tags). Apart from the affiliate attribution described above, we do not track you across other companies’ apps or websites for advertising, and we do not sell your personal data to advertisers or data brokers.
5. How We Use Your Data
- Providing, maintaining, and improving the Service
- Processing payments and managing subscriptions
- Sending transactional notifications (booking confirmations, payment receipts)
- Sending push notifications about nearby events (with your consent)
- Detecting and preventing fraud, spam, and abuse
- Complying with legal obligations
- Resolving disputes and enforcing our Terms of Service
We do not use your data for automated decision-making that produces legal or similarly significant effects, except for fraud prevention scoring where we may suspend accounts pending manual review.
6. Sharing Your Data
We share personal data with the following categories of recipients:
- Stripe, Inc. — payment processing. Stripe is a certified PCI DSS Level 1 service provider.
- Google Firebase / Google LLC — authentication and push notifications (FCM).
- Mapbox, Inc. — map tiles and geocoding for the discovery map.
- AudD Ltd. — music recognition for Song Radar. When you start a Song Radar session, short microphone clips are sent to AudD solely to identify the track playing; PartyRadar does not keep the audio, and only the identified song (title, artist, time) is stored in your history.
- Google LLC (Google Analytics 4) — product analytics: page and screen views and in-app events, keyed to a pseudonymous cookie identifier, not your account id.
- PostHog, Inc. — product analytics and feature usage, processed in the United States; for signed-in users linked to the account details listed in section 4 so we can support you and measure retention.
- Functional Software, Inc. (Sentry) — error and crash reports, stored in Sentry’s EU data region.
- Hosting providers (Railway.app, Vercel) — infrastructure; Vercel also measures page-load speed (Speed Insights).
- Ticket sellers and affiliate networks (for example Skiddle, Impact for Ticketmaster and its partner sellers, and Awin for See Tickets) — when you follow a ticket link your browser goes to them directly, as described in section 4. We do not send them your account details.
- Event hosts — when you RSVP to an event, the host sees your display name and profile photo.
- Law enforcement or regulatory authorities — only where required by law or court order.
We do not sell, rent, or trade your personal data with third parties for marketing purposes.
Where we transfer data outside the UK/EEA (e.g. to US-based processors), we ensure appropriate safeguards are in place, including Standard Contractual Clauses (SCCs) or adequacy decisions.
7. Data Retention
- Account data: retained for the lifetime of your account, plus 30 days after deletion to allow recovery.
- Transaction records: retained for 7 years for tax and accounting purposes.
- Messages: retained until deleted by you or until account deletion.
- Location history: not stored beyond the current session.
- Device logs and crash reports: retained for 90 days.
- Moderation records (content violations): retained for 3 years for safety purposes.
8. Your Rights
Under UK GDPR and the Data Protection Act 2018, you have the following rights:
- Right of access — request a copy of the personal data we hold about you.
- Right to rectification — request correction of inaccurate data.
- Right to erasure ("right to be forgotten") — request deletion of your data, subject to legal retention obligations.
- Right to restrict processing — request that we limit how we use your data.
- Right to data portability — receive your data in a structured, machine-readable format.
- Right to object — object to processing based on legitimate interests.
- Rights related to automated decision-making.
- Right to withdraw consent — where processing is based on consent, you can withdraw it at any time without affecting past processing.
To exercise any of these rights, please contact us at hello@partyradar.org. We will respond within one calendar month. You may also complain to the ICO at ico.org.uk.
You can delete your account at any time from Settings → Delete Account. Deletion is irreversible and removes your profile, events, and messages within 30 days.
You can switch analytics off at any time, on each device and without an account, with the analytics choice in section 4.
9. Children's Privacy
The Service is not directed at, and we do not knowingly collect personal data from, anyone under the age of 18. If you believe a minor has created an account, please contact us immediately at hello@partyradar.org and we will promptly delete the account.
10. Security
We implement industry-standard security measures including:
- TLS encryption in transit for all API communications.
- End-to-end encryption for direct messages.
- Passwords are never stored — authentication is handled by Google Firebase.
- Payment data is handled exclusively by Stripe; we do not store card numbers.
- Access to production databases is restricted to authorised personnel only.
- Regular security audits and dependency vulnerability scans.
Despite these measures, no system is completely secure. We encourage you to use a strong, unique password for your Google or Apple account used to sign in.
11. Third-Party Links
The Service may contain links to third-party websites or services. This Privacy Policy does not apply to those third parties. We encourage you to review their privacy policies before sharing any personal data with them.
12. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting a notice in the app or by email at least 14 days before the change takes effect. The "Effective date" at the top of this page indicates when the policy was last revised.
13. Contact Us
For general privacy enquiries:
For data protection officer enquiries:
SAINTSINNERS LTD (company number SC821579, registered in Scotland)
1/2 31 Tobago Place, Glasgow, G40 2RT, United Kingdom