Privacy Policy
Effective Date: 11 May 2026
Last Updated: 19 October 2026
This Privacy Policy describes how Deuce Creative Limited (“we”, “us”, “our”), trading as Grofomo, collects, uses, and shares information across the Grofomo platform.
1. Who We Are
Deuce Creative Limited, a company registered in England and Wales, company number 07991249. VAT number GB935707211.
Registered office: Unit 8 Great Bramshot Farm Barns, Bramshot Lane, Fleet, Hampshire, GU51 2SF, United Kingdom.
For any privacy question or request, contact privacy@grofomo.com.
1.1 What this policy covers
This policy applies to:
- the Grofomo mobile app;
- events.grofomo.com, the console event organisers use;
- artists.grofomo.com, the portal artists use;
- grfm.to and m.grfm.to, where tickets are sold and managed;
- affiliates.grofomo.com, the portal Ambassadors and affiliates use (see §3.3);
- api.grofomo.com, the service behind the app;
- grofomo.com, developers.grofomo.com, and docs.grofomo.com;
- event websites we host on an organiser behalf.
Organisers and artists each have a separate agreement covering their use of the platform: the Organiser Terms and the Artist Terms. Organisers are additionally covered by our Data Processing Addendum.
2. Information We Collect
2.1 Information you provide
- Account and sign-in email: an account is created only when you sign in, and how you can sign in depends on where you are. In the Grofomo mobile app the only method is a magic link sent to your email address: the app does not offer Google or Apple sign-in, or a password. On our web surfaces – the organiser console, the artist portal, and the Ambassador portal – you can use the same email magic link, an email address and password, or sign in with Google or Apple. Where you choose Google or Apple, they confirm your identity to us and we receive your email address; your password for them never reaches us. We then store that email and an account record so you can sign in across devices, see your tickets, and manage or delete your data. Buying a ticket does not create an account on its own: your purchase is recorded against the email you used, and is linked to your account if and when you sign in with that email. If you are a member of an organiser account, signing in to the app also shows the events of that organiser, with the same figures and the same access you have in the organiser console. Much of the app works with only a device identifier (see §2.2). You can delete your account at any time (see §10).
- Nickname and avatar choice (if you set one). Used to identify you to friends within the app.
- Ticket purchase details: your name, email address, and where the organiser asks for it a phone number, together with the details of what you bought. Where you buy merchandise we also collect a delivery address. Card details go directly to our payment provider and never reach us.
- Answers to questions the organiser asks at checkout or on their forms. The organiser decides what to ask; see §4.
- Photos and videos you choose to share with an event organiser, at an event you have joined. You pick the files yourself from your device library and they are uploaded to us for that organiser to review. We also record the usage-rights terms you accepted, word for word as they were shown to you, with a timestamp, your device identifier, and your IP address and browser. See §2.3 for what happens to them.
- Reward claim details: where you claim an Ambassador reward that the organiser posts out to you, the name and postal address the item should go to, including city, postcode and country, and where a reward comes in more than one version, the option you picked, such as a size. See §3.3.
- Email address (if you submit a Grofomo web form, for example a marketing opt-in form, a pre-sale registration, or a similar interest form). Used, with your separate opt-in at the form, to send marketing email about events, ticket releases, and related news.
- Phone number (only if you submit a Grofomo web form and choose SMS or WhatsApp as a contact channel). Used only to send the communications you opted in to.
- WhatsApp messages you send to an organiser, where they use WhatsApp through Grofomo. The message content and your WhatsApp display name are stored so the organiser can reply.
- Friend invite tokens (when you accept an invite from another user).
- Marketing notification preference (device-level): whether you have toggled marketing push notifications on for this device. This is a per-device preference, like any other notification setting, and is stored against your device identifier only. You can flip it at any time from Settings → Notifications in the app or from your device system Settings.
- Marketing consent records (named): if you submit a Grofomo web form that captures marketing choices (e.g. a pre-sale registration, marketing opt-in form, or ticket checkout), we record, at the point of submission, which channels you agreed to (email, SMS, WhatsApp), the exact wording of each choice as it was shown to you (including, for a clearly-labelled pre-ticked box, that you did not opt out), a timestamp, and the form and version you submitted through, so we can demonstrate the basis for any message we send and honour any later withdrawal or objection.
2.2 Information collected automatically
- Device identifier: a randomly-generated identifier created when you first open the app. Used to associate your local data (favourites, reminders, nickname) with your device.
- Push notification token: an Expo Push Token issued by our push-delivery processor, Expo. The token is derived from the underlying Apple (APNs) or Google (FCM) token but is scoped to our Expo project; we never see the raw APNs or FCM token. Used to deliver event reminders, friend-invite notifications, and any marketing pushes you have opted into.
- App and device metadata: platform (iOS or Android), app version, device locale, and approximate last-seen timestamp. Used for compatibility checks and to identify inactive sessions.
- IP address and browser: recorded at specific moments where we need to be able to evidence what happened. Those moments are: placing an order, recording a marketing consent choice, requesting a ticket-recovery code, granting media consent, and being checked in at an event. It is also processed transiently for security, rate limiting, and bot protection. We do not keep a general log of your browsing.
- Referral source: where you followed a tagged or affiliate link to a ticket page, we record which campaign, post, advert or referrer sent you, so the organiser can see what led to the sale and the right person is credited. Clicks are counted against the link. If you buy, the referral source is saved with your order, so it is linked to your order like the rest of it. We only remember it between visits, in a cookie, if you accept cookies on the ticket page. Whoever shared the link sees a short version of your name with the order (see §6).
- Clipboard (read on launch): when you open the app, we briefly inspect the system clipboard to detect a pasted friend-invite link. We act only on values matching our invite-link format; we do not retain, transmit, or otherwise process clipboard contents. (iOS may display a system banner when this read occurs.)
2.3 Camera, photos and videos
The app asks for two separate permissions here, and they do very different things. One never sends an image anywhere; the other exists in order to.
The camera, for scanning QR codes. The app requests camera access solely to scan QR codes that link to events, artists, or friend invites. The camera feed is processed on-device in real time and never stored, uploaded, or transmitted. The app cannot take a photograph: there is no capture button anywhere in it, and the camera is never used to produce a file.
Your photo library, for sharing with an organiser. At an event you have joined, the app can invite you to share photos and videos from it with the organiser. Choosing to do so opens your device photo picker, and the photos and videos you select are deliberately uploaded to us so that the organiser can see them. This is the one place in the app where images leave your device, and it happens only for files you have picked, only for an event you have joined, and only after you have accepted the usage-rights terms shown at that moment.
What we do with them, and what you keep control of:
- Uploads land in a private staging area, not on the public internet. Nothing you share is shown publicly unless the organiser approves it for their gallery or website.
- The organiser may reuse what they approve in their own marketing, which is the substance of the terms you accept when you share. They are the controller for that reuse; see §4.1.
- You can remove anything you have shared, from the app, up until the organiser saves it to their own library. After that, ask them or ask us and it will be removed.
- Location data is handled differently for photos and for videos, because of where it can be removed. A photo is re-encoded on your device before it is uploaded, without its EXIF metadata, so no GPS coordinate from a photo ever leaves your phone. A video is uploaded exactly as your camera recorded it, because the app cannot re-encode video, so any location metadata written into the file does leave your device with it. We strip it as soon as the upload arrives, before the clip is queued for the organiser to review, so no organiser ever sees it and it never reaches the published file. We never read it and never use it.
- We do not run face recognition on what you share, and we do not use it to identify anyone appearing in it.
2.4 What we do not collect
- We do not collect your precise or approximate location. The app contains no GPS or location code and never asks for location permission, and our own analytics resolve no finer than country. The one qualification is location metadata already written into a video you choose to share with an organiser, which we neither read nor use, and which leaves your device inside the file rather than being removed first; see §2.3.
- We do not access your contacts, and we do not access your microphone. The app asks for neither permission: it has no address-book feature and records no audio.
- We do not browse your photo library. The app can ask for photo-library permission, because sharing photos and videos with an organiser is a feature of it, but it receives only the individual files you pick in your device photo picker, at the moment you pick them. It does not read, index, or scan the rest of your library, and it cannot take a photograph of its own. See §2.3.
- We do not access the iOS advertising identifier (IDFA) or the Android advertising ID, and Grofomo does not request App Tracking Transparency consent.
- Grofomo does not track you across other apps or websites, and we do not sell your information or share it with advertisers. One qualification: an event organiser can add their own Meta advertising pixel to their event site and ticket page, which is third-party tracking by that organiser. It only runs if you accept analytics cookies, and where you do, a purchase is also reported to that pixel from our server with your IP address, the advert click id and a hashed copy of your email address, so Meta can match the sale to the advert. Both are described in our cookie policy.
- We do not collect financial, biometric, or government-issued identifier information, and we do not ask for health information. Note that an organiser can add their own questions to a checkout or form, so what an organiser asks you for is their decision, not ours. See §4.
3. How We Use Information
We use the information above to:
- Provide the core app experience: showing events, lineups, favourites, friends, and reminders.
- Sell you tickets, deliver them, and support you if something goes wrong.
- Pass the photos and videos you choose to share to the organiser of the event you shared them from, and keep a record of the terms you accepted when you did (see §2.3).
- Run an organiser Ambassador rewards programme: attribute ticket sales to the right share link, work out which rewards are unlocked, and get a claimed reward to you (see §3.3).
- Authenticate your device and your account with our Service.
- Deliver transactional messages that are part of the service you asked for: ticket confirmations, receipts, event change notices, payment plan reminders, event reminders you have scheduled, friend-invite notifications, and, for organisers who switch them on for an event, alerts in the app when that event sells tickets.
- Deliver marketing communications (push notifications, and for users who have submitted a Grofomo web form or bought a ticket: email, SMS, or WhatsApp) only on the basis described in §3.1 and §3.2.
- Keep the platform secure and prevent fraud and abuse, including bot protection on public forms and rate limiting.
- Find and fix crashes and errors. When the app or a Grofomo website hits an error, it sends a crash report to our error-reporting provider, Sentry: the error message, where in our code it happened, your device model, operating system, and app or browser version. Crash reports carry no name, email address, or account identifier, we do not store your IP address with them, and we do not record your screen or track how you use the app. We also use any diagnostic information you choose to share with us when reporting a problem (for example, by emailing support).
- Meet our legal obligations, including keeping accounting and tax records of sales.
We do not sell your information, share it with advertisers for their own purposes, or use it for behavioural advertising. We do not use your personal data to train machine learning models.
3.1 Marketing in the app
Separately from transactional notifications, Grofomo may send you marketing communications about future events, ticket releases, lineup announcements, and related offers. Marketing is never required to use the app or to buy a ticket. In the app, marketing is opt-in only and is captured in two stages, so that you only ever receive what you have specifically agreed to. Marketing choices shown at ticket checkout are described separately in §3.2.
Stage 1 – Marketing push notifications. An in-app banner may invite you to enable marketing push notifications. Push notifications of any kind can only reach you if you have granted Grofomo push permission via your device system dialog: that operating-system permission is the underlying consent. The in-app Marketing notifications toggle then sits on top as a granular preference that controls whether your device is included when we send a marketing push (about future ticket releases and related news).
At this stage your preference is tied only to your device identifier: we do not yet hold your name, email, or phone number for marketing purposes. You can opt out at any time by:
- Toggling Marketing notifications off in Settings → Notifications within the app, or
- Revoking Grofomo push permission entirely in your device system Settings (this also stops transactional notifications).
Stage 2 – Web form opt-in. A marketing push notification (from Stage 1), or a link from elsewhere, may invite you to submit a web form that Grofomo operates on an event organiser behalf, for example a pre-sale (“prelaunch”) registration form. These forms collect your first name, email address, and optionally a mobile number. The organiser named on the form is the controller for the marketing you sign up to, just as with marketing at ticket checkout (see §3.2); Grofomo runs the form and keeps the records on their behalf. Where the form says so plainly at the point of submission, submitting the form itself signs you up for the organiser email updates about the event named on the form (such as on-sale alerts, presales, and related news). Any SMS, WhatsApp, or postal marketing is separate and strictly opt-in, sent only if you actively tick that box. At the point of submission we record:
- the channels you signed up to and the exact wording you were shown for each,
- the timestamp, your IP address and browser,
- the form and version you submitted through, and
- where you arrived from a marketing push, the link between your submitted personal data and the device identifier that opened the form, so we can recognise you across the app and our mailing lists.
You can withdraw consent for email, SMS, or WhatsApp marketing at any time by:
- using the unsubscribe link included in every marketing email,
- replying STOP to any marketing SMS,
- using the WhatsApp “stop messages” option, or
- emailing privacy@grofomo.com to withdraw across all channels at once.
Withdrawing marketing consent stops the relevant communications. You will continue to receive transactional push notifications (e.g. reminders you have scheduled, friend-invite notifications) unless you disable those separately.
3.2 Marketing at ticket checkout
When you buy a ticket through a Grofomo-powered checkout, up to three separate marketing choices are shown, each as its own clearly-labelled box:
- The event organiser emails (soft opt-in). The organiser you are buying from is the data controller for their own marketing. Because you provide your details in the course of buying a ticket from them, they may email you about their own similar events, presales and announcements on the basis of their legitimate interests, under the UK “soft opt-in” rule (PECR Regulation 22(3)). The checkout shows this as a clearly-worded, pre-ticked box that you can untick at the point of purchase, and every such email contains an unsubscribe link. You have the right to object at any time: untick the box at checkout, use the unsubscribe link in any email, or email privacy@grofomo.com.
- The organiser SMS and WhatsApp messages are strictly opt-in: they are sent only if you actively tick the messaging box, and you can opt out at any time by replying STOP to any SMS or using the WhatsApp “stop messages” option.
- Grofomo own emails. Grofomo runs the checkout and delivers your tickets, and acts as an independent controller for its own marketing about similar events available on Grofomo. Depending on the checkout version shown, this choice is captured either as an unticked opt-in box (consent), or (where we rely on legitimate interests under the same soft opt-in rule) as a clearly-worded pre-ticked box you can untick at the point of purchase. Every Grofomo marketing email contains an unsubscribe link, and you can object at any time via that link or privacy@grofomo.com.
In every case we record which boxes were shown and their exact wording, your choice, a timestamp, your IP address and browser, and the form version, so we can demonstrate the basis for any message we send and honour any withdrawal or objection.
3.3 The Ambassador rewards programme
An organiser can run an Ambassador rewards programme on their event. An Ambassador gets their own ticket link; tickets bought through that link are attributed to them, and passing a number of tickets unlocks a reward. Taking part costs nothing and does nothing unless you choose to share your link.
How you become one. Most Ambassadors are enrolled automatically on buying a ticket, where the organiser has left automatic enrolment on, which is the default: the ticket confirmation then carries your share link. An organiser can also email an invitation to people who have bought from them before, add someone by hand, or accept an application. If you would rather not take part, ignore the link, or email us and we will take you out of the programme.
What is recorded. Your name and email address against that organiser event, the code in your share link, running totals of the orders and gross sales attributed to it, and which rewards you have unlocked, claimed, and been sent. The attribution itself works the way any tagged link does and is described in §2.2 and §5: it is the link that is counted, not the person who clicked it.
Claiming a reward. What we need from you depends on the kind of reward:
- Collected at the venue – a drink, a meal, or anything else handed over on the night. The app issues a single-use code, good for minutes rather than days, which venue staff scan. We store only a hash of that code, never the code itself. Staff who scan it see your name and which reward it is. Nothing further is collected from you.
- Posted out to you – merchandise the organiser sends on afterwards. We ask where to send it, and where a reward comes in more than one version, which one you want, such as a size. You can leave the delivery details blank if the organiser already has your address, but nothing can be posted without them.
- A refund of your own ticket, where an organiser offers that as a reward. It goes back to the card you paid with, through our payment provider, and needs nothing new from you.
A posted reward means giving your address to the event organiser. That is a disclosure to someone other than us, so it is better stated plainly than left to be inferred. The delivery details you give – the name the item should go to, the address, city, postcode and country, and the option you picked – are read by the organiser of that event, because they are the ones who put the parcel in the post. They appear in that organiser console next to the control they use to mark the reward as sent, and members of their team with access to the event can see them. You can see and change them yourself, in the app or in the Ambassador portal, until the reward is marked as sent.
We ask for an address only when you claim a reward that has to be posted. We use it only to get that item to you. It is never added to a mailing list and never used for marketing, and the only people who read it are the organiser sending the item and, where you ask us for help, us. If you have unlocked a reward and not finished claiming it, we may send you a push notification saying so; that notification names the event and the reward, never your address. Give only what is needed to address a parcel: whatever you write there, the organiser reads.
4. Who is responsible for your data
Grofomo is a platform that event organisers use to run their events, so for some data we decide what happens to it and for other data the organiser does. Under data protection law the party who decides is the “controller”, and it is the party you exercise your rights against. This matters in practice, so here it is plainly.
4.1 The event organiser is the controller
When you buy a ticket, register for a pre-sale, fill in an organiser form, message an organiser on WhatsApp, share photos from their event, claim an Ambassador reward, or volunteer for an event, the organiser decides what to collect and what to do with it. Grofomo processes it on their instructions. That covers:
- your order and ticket records for their event;
- any custom questions they choose to ask you;
- their marketing to you, and the consent you gave them;
- your messages with them;
- the photos and videos you share with them, and their reuse of what they approve;
- your Ambassador record for their event, the rewards you unlock, and any delivery address you give to claim one;
- volunteer, guest list, and supplier records.
The organiser name is shown on the event page, on the checkout, and on your receipt. For requests about that data you can contact them directly, or contact us and we will help.
4.2 Grofomo is the controller
We decide what happens to, and are responsible for:
- your Grofomo account and how you sign in;
- the Grofomo mobile app: your device record, nickname, favourites, reminders, and friend connections;
- marketing that Grofomo sends about Grofomo, where you agreed to it separately (see §3.2);
- the public artist and event directory, including entries compiled from public sources (see §11);
- keeping the platform secure, and our own accounting and tax records.
4.3 Both, separately
At checkout you may agree to hear from the organiser and, separately, from Grofomo. Those are two different relationships with two different controllers. Unsubscribing from one does not unsubscribe you from the other, and each of us is responsible only for our own messages.
5. Cookies
We use cookies to keep you signed in, to remember your preferences, and to hold your basket while you buy. These are necessary for the service to work.
Two things are not necessary, and neither runs unless you accept it on the ticket page: our cookie that remembers which link brought you to an event, so the sale can be credited if you come back later to buy, and an event organiser’s own advertising pixel, where they have added one. Declining changes nothing about your ability to buy a ticket.
Full detail, including every cookie name and how to change your choice, is in our cookie policy.
6. How We Share Information
Service providers. We use third-party providers to run the platform: to host it, store data, take payments, send email, deliver push notifications, and protect forms from abuse. They act on our instructions, may use the data only to provide their service to us, and are bound by written data protection terms.
We publish the complete, current list, including what each one can access, where it processes, and the safeguard we rely on, at https://events.grofomo.com/subprocessors. That page is kept up to date as the authoritative record rather than as a summary.
The event organiser. When you buy a ticket or interact with an event, the organiser of that event receives the details they need to sell to you and admit you, as described in §4.1. Two further disclosures to them are worth naming on their own, because they are not obvious from buying a ticket: the photos and videos you choose to share go to them for review and possible reuse (§2.3), and the delivery address you give to claim a posted Ambassador reward goes to them so they can send it (§3.3).
Whoever shared the link you bought through. If you buy through an affiliate link (an artist, an Ambassador, a partner and so on), whoever shared it sees your first name and surname initial (for example “Matt S”), how many tickets you chose, when, and whether you finished buying. Nothing else: not your email address, phone number or anything you paid with. It is there so they know who is coming and who they might still remind, because people usually share these links with friends one message at a time. The checkout tells you this before you pay, with a box to hide your name, and you can also ask us to hide it later at privacy@grofomo.com. We rely on our legitimate interest, and theirs, in letting the person who brought you know you came, which we have weighed against the small amount shown and the fact that you followed their own link. An order placed through a checkout that did not show you this notice, including every order from before we added it, is never shown with a name.
Services an organiser has connected. An organiser can connect their own advertising, messaging, or notification tools. Where they have, data may flow to those tools on their instructions. These are identified separately on the subprocessors page.
Legal disclosures. We may disclose information if required by a valid legal process, or to protect our rights, safety, or property.
Business transfers. If Deuce Creative Limited is acquired or merges with another entity, your information may transfer as part of that transaction, subject to this policy.
7. Where your data is processed
Our database is in the United Kingdom. Everything the platform stores about you, including your account, orders, tickets, consent records, and uploaded media, is held in London.
Some processing happens elsewhere. Our hosting provider currently runs server code in the United States, holding data only in memory for the moment it takes to serve a request before writing it back to the United Kingdom. Payments, email delivery, push notifications, and some other services also involve providers outside the United Kingdom. The subprocessors page states, for each provider, exactly where it processes.
Where data leaves the United Kingdom we rely on one of: the UK International Data Transfer Agreement; the EU Standard Contractual Clauses together with the UK Addendum; or the UK Extension to the EU-US Data Privacy Framework where the provider is certified under it. We assess these transfers and can provide our assessments on request.
8. Data Retention
We keep information only as long as we need it, and delete or anonymise it on a schedule:
- Your app device record persists for as long as the device is active. If the app has not contacted the Service for 24 months, the associated record is deleted. The period spans two years because many people use the app for one annual event, and we would rather your friends, reminders and history were still there when that event comes round again.
- Push notification tokens are invalidated and removed from active use once APNs or FCM (via Expo) signals that they are no longer valid, for example after you uninstall the app or revoke push permission. Tokens are deleted together with the associated device record.
- Ticket purchases are kept for the retention period the organiser sets, which defaults to 7 years to match tax record-keeping requirements. At the end of that period your personal details are removed and only an anonymous record of the sale remains.
- Abandoned checkouts, where you entered details but never purchased, are anonymised after 180 days.
- Pre-sale registrations are deleted after the period set for that event, which defaults to 2 years.
- WhatsApp message content is redacted after the organiser retention window, which defaults to 24 months.
- Link click records are deleted after 400 days, and checkout analytics 180 days after the event ends.
- Ticket recovery codes are deleted after 24 hours.
- Photos and videos you shared are kept while the organiser has them. If you withdraw an item, or the organiser declines it, the file itself is deleted at that point; a record that the item existed is kept without it, so the consent trail still makes sense. An item the organiser has approved and kept has no timer of its own: it stays in their library until they remove it, or until you ask for it to be removed. The usage-rights record of what you agreed to is kept as evidence for as long as the organiser may rely on it, and cannot be altered after the fact.
- Ambassador reward records are kept for as long as the organiser record of that event exists, because they are the evidence of what was owed and what was sent. The delivery address you gave to claim a posted reward is treated differently from the rest of that record. It is erased when you delete your account, even though it sits on the organiser record rather than on yours. It is also deleted 180 days after the reward was sent, along with the size or other option you chose, which leaves room for a parcel to go missing and be sent again but is far short of how long the record of the reward itself lasts. You can ask us to erase it sooner, once your reward has arrived.
- Data from a Grofomo web form (name, email, optional phone, channel consents) persists until you withdraw consent across all channels or request deletion, at which point it is removed from active marketing use and deleted from our records within 30 days.
Two things deliberately survive an erasure request. The financial record of a sale, stripped of your details, is kept because we are legally required to keep accounting records. Consent records are kept because they are the only evidence that a message we sent you was lawful, and destroying them would remove your own ability to challenge it. Neither is ever used to contact you again.
Backups are overwritten on a rolling cycle and are fully replaced within 60 days.
9. Your Rights
You have the right to:
- Access the personal data we hold about you, and receive a copy.
- Correct inaccurate data.
- Delete your data (“right to erasure”).
- Object to or restrict processing of your data.
- Port your data to another service, in a structured, commonly used, machine-readable format.
- Withdraw consent to marketing communications (per channel, see §3.1), object to marketing sent under legitimate interests (see §3.2), withdraw from all push notifications (via your device system notification settings), or from the use of the app entirely (by uninstalling).
To exercise any of these rights, email privacy@grofomo.com. We acknowledge within 3 business days and respond within 30 days. Exercising a right is free, and we will never make you give a reason.
Where the request concerns data an event organiser controls (see §4.1), we will either pass it to them or help you reach them, and tell you which we have done.
You have the right to complain to the Information Commissioner’s Office at ico.org.uk. We would rather you came to us first, but you do not have to.
10. Data Deletion
You can delete your Grofomo account from Settings → Sign out and delete account in the app, or by emailing privacy@grofomo.com from the address you registered with. Deleting your account signs you out and removes the personal data linked to it: your device record, nickname and avatar, your magic-link email and auth record, your favourites and reminders, and friends entries naming you.
If you have bought tickets, deleting your account also anonymises your personal details (name, email, phone) on those past purchases, so the organiser keeps only a de-identified record of the sale for their own accounting and legal obligations. The exception is tickets for events that have not yet taken place: the organiser retains the details needed to admit you until after the event, after which your details are removed by routine cleanup. Deleting your account does not cancel or refund tickets you have already bought.
Deleting your account also erases the delivery address you gave to claim an Ambassador reward and the size or other option you chose with it, even though they sit on the organiser record of that reward rather than on your account, and it deletes anything you shared that an organiser never approved.
One thing attaches to an event rather than to your account. A photo or video an organiser has approved stays with them, because they hold a licence to use it and may already have printed or published it. Your name is removed from it, so it is no longer linked to you. Until an organiser approves it you can remove it yourself in the app; after that, ask them or ask us.
If you have submitted a Grofomo web form (e.g. a marketing opt-in or pre-sale registration), you can have the data captured there deleted by emailing privacy@grofomo.com from the address you registered with.
Full detail is on our data deletion page.
11. Information we hold that you did not give us
Grofomo maintains a public directory of artists and events, so that organisers can build lineups and audiences can find gigs. Some entries are compiled from publicly available sources rather than provided by the person concerned. That can include a performing name, a real name where it is publicly associated with the act, a biography, a location, publicly listed booking or press contact details, links to public social profiles, and publicly posted images.
Where it comes from. Public event listings and venue websites, public music and event databases including Resident Advisor, MusicBrainz, Wikidata and Spotify, and publicly accessible social media profiles.
Why we do it. Our legitimate interest, and that of the organisers who use the platform, in maintaining a usable directory of who performs where. We balance that against the interests of the people listed, which is why entries hold professional information only and never anything private.
Counting click-throughs. When someone follows a ticket link from a directory listing, we count that click so we can tell a venue how much traffic the directory sends it. We record the listing, which seller was clicked, the time, the website you came from, a broad device type and a two-letter country. We do not record your IP address, your full browser details or anything that identifies you, and we do not store anything on your device to do it.
What you can do. If you are listed, you can claim your profile and take control of it, correct it, ask us to restrict how it is used, or object to the listing entirely and ask us to remove it. Email privacy@grofomo.com and we will action it. We do not require you to justify the request.
12. Children
Grofomo is not directed at children under 13, and you must be 18 or over to buy a ticket. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with information, contact privacy@grofomo.com and we will delete it.
Data about a child can still reach the platform: a parent naming a child on a ticket they bought, or an organiser recording an under-18 volunteer. Where that happens the organiser is the controller and is responsible for handling it appropriately.
13. Security
All traffic between your device and the Service is encrypted with TLS, and data is encrypted at rest. Every table in our database enforces row-level access control, so a request can only ever return data the requester is entitled to. Device authentication uses signed tokens, and third-party access tokens are separately encrypted before storage. Provider credentials are held in environment-scoped secrets and never in our source code. Access by our staff follows least privilege and is removed when a role ends.
A fuller description of our technical and organisational measures is published as Annex 2 of our Data Processing Addendum. No system is perfectly secure, but we follow industry-standard practices, and if a breach ever affects your data we will tell you where the law requires it.
14. Changes to This Policy
We may update this policy. Material changes will be announced via in-app notification, push notification, or email at least 14 days before they take effect. The “Last Updated” date at the top of this page always reflects the most recent revision.
15. Contact
Deuce Creative Limited
Unit 8 Great Bramshot Farm Barns
Bramshot Lane
Fleet
Hampshire
GU51 2SF
United Kingdom
Privacy enquiries: privacy@grofomo.com
By using Grofomo, you acknowledge that you have read and understood this Privacy Policy.