Privacy notice
What GigTag knows about you, and why
Last updated 7 October 2026.
The short version
- Fans never need an account. Scanning a tag and requesting a song leaves a random session token and, if you choose to type them, a first name and a message for the performer. Those are removed after 30 days.
- Performers have an account, opened with an email address and password or with Google or Apple, and a public page they fill in themselves. That page is public because that is its purpose. The account can be deleted from the app or the website at any time.
- Money is handled by Ziina and Stripe. Tips go straight to the performer, through Ziina in the UAE or the performer’s own Stripe account elsewhere; Pro and custom tags are paid on Stripe. We never see or store card numbers.
- We do not sell data, run advertising, or build profiles of fans across acts. Google Analytics runs only on our own marketing, sign-in and sign-up pages, never on an act’s page or inside the dashboard or the app. The performers’ app uses PostHog to show us how it is used.
Who we are
GigTag is run by Oasis Digital LLC, Sharjah Media City, Sharjah, United Arab Emirates. We are the controller of the personal data described here. To ask us anything about it, use the contact form.
If you are a fan who scanned a tag
You can use an act’s page without telling us who you are. Here is exactly what happens when you do.
A session for this act
When you open an act’s page we set a cookie holding a random token, so that a request you send can be shown back to you and cancelled by you, and so that a performer can block a session that is abusing them. We store only a hash of the token, tied to that one act. It expires 24 hours after the act’s live session ends and is not reused to recognise you anywhere else.
Song requests
A request is the song, an optional first name and an optional message. Only the act you sent it to can see the name and the message; they are never listed publicly, never ranked, and nobody can pay to move a request up. Performers can hide a message. Thirty days after a request is made, the name and message are deleted and only the song and the outcome remain, as a count.
Tips
Tipping is optional and only offered where the act has switched it on. You pay on Ziina’s payment page, straight into the performer’s own Ziina account: Ziina collects your card or wallet details under Ziina’s privacy policy. We receive and keep the amount, the currency, Ziina’s fee and whether the payment succeeded, so that the performer can see their tips. We do not receive your card number, and the money never passes through us. A tip never changes where a request sits in the list.
Booking enquiries
If you use the booking form we store the name, email address, event details and message you type, and show them to the act so they can reply to you by email. An enquiry the act has closed, or marked as spam, is deleted 12 months later.
Counts, not tracking
An act sees how many times its tag was scanned, its page viewed, its links clicked and its forms opened. Those are event counts. They carry no name, no IP address and no identifier that follows you between acts or across the web. When you tap one of an act’s links we record the kind of destination (for example “Spotify”) and send you on; the destination sees you as any other visitor.
If you are a performer with an account
Your account
You can sign up in one of three ways. We use the email address to sign you in, to confirm changes to your account and to send the emails listed below. We do not send marketing email.
- Email and password. We get your email address and a password, which is stored only as a hash by our authentication provider.
- Sign in with Google. Google tells us your email address, your name and your profile picture if you have one. We never see your Google password.
- Sign in with Apple. Apple tells us your email address, and your name the first time if you choose to share it. If you pick “Hide My Email”, we only ever get a private relay address from Apple, and our emails reach you through it. We keep a sealed token from Apple so that when you delete your account we can also tell Apple to disconnect GigTag from your Apple ID.
Your act and your page
Everything on your public page is there because you put it there: the act’s name, photo and banner, biography, links, gigs, song list, and for a duo or band the names and photos of its members. Publishing makes it visible to anyone with the link or the printed tag, including search engines. Unpublishing takes it down; the printed code then leads to a safe holding page rather than to someone else.
Members of a duo or band
Inviting someone stores their email address, encrypted, with a single-use invitation. Each person keeps one profile across every act they play in and edits it themselves. The admin of an act sees members’ names and their share of the act’s counts, nothing more.
Billing
The Pro subscription is paid on Stripe. Stripe holds your card and billing address; we keep a customer reference and the state of the subscription so we know which features to switch on. Managing or cancelling happens in Stripe’s billing portal.
Receiving tips with Ziina
You connect your own Ziina account with Ziina’s sign-in; we never see your Ziina password. Ziina then tells us the account’s id, its type, your Ziina username and display name, and whether it can take payments, and gives us a token that lets us create tip payments into it and refund them. It cannot move or withdraw your money. The token is stored encrypted and deleted when you disconnect. Tips go straight into your Ziina wallet; we keep the record of each tip for as long as accounting law requires, even after the act is deleted.
Ordering a custom GigTag
Anyone can design a custom tag and buy it. We store the design (colour, text, and any logo you upload) and the print-ready artwork. Payment happens on Stripe’s checkout page, which gives us your name, email address, phone number and the delivery address, so that we can make the tag, post it and send you a receipt and a shipping notice. A paid order is kept with our sales records; a design that is never paid for is deleted after 30 days.
Emails we send
Confirming your address, a sign-in link, a password reset, a change of email address, an invitation to an act, a new booking enquiry for your act, and, if you order a custom tag, its receipt and shipping notice. They are sent through Resend. That is the full list.
The GigTag app for iPhone and Android
The app signs in to the same account and shows the same data. It keeps your session on the device so you stay signed in. It contains no advertising software. It does not ask for your location, camera, microphone or contacts.
- Photos. Only when you choose a picture for your page, and only the picture you pick is uploaded.
- Push notifications. Only if you allow them. We then keep the phone’s push address, whether it is an iPhone or Android, and the name the phone gives itself (so you can tell two phones apart), and which kinds of notification you want: song requests, tips, bookings, gig reminders and invitations. You can switch each kind off in the app. Signing out on that phone switches its notifications off. Notifications are delivered through Expo’s push service and Apple or Google.
- Crash reports. If the app or the website hits an error, a report goes to Sentry so we can fix it: what went wrong, where in our code, the app version and the kind of phone or browser. From the app it carries your account’s ID number, not your name or email. The report has no screenshots, cookies or form contents.
- How the app is used. The app sends PostHog, an analytics service, the screens you open, which buttons you tap (by the button’s name, never the words on screen), what you do, such as adding a gig or marking a request played, when the app is opened, closed, installed or updated, and the kind of phone, so that we can see which parts get used and where people get stuck. It also records what happens on screen during a session, so that when you tell us about a problem we can see it the way you did; every text field and picture, and everything a fan wrote, such as their name, message or booking enquiry, is blanked out on the phone before anything is sent. It is linked to your account’s ID number and email address. The data is held in PostHog’s EU cloud and is not used for advertising.
Who processes data on our behalf
We use a small number of providers, each for one job. They act on our instructions and under their own security commitments.
| Provider | What for |
|---|---|
| Supabase | Database, sign-in, and storage of the photos you upload. |
| Netlify | Hosting the website, and delivering the contact form to us. |
| Ziina | Tip payments, straight into the performer’s own Ziina account. |
| Stripe | Pro subscriptions and custom tag orders; outside the UAE, tip payments straight into the performer’s own Stripe account. |
| Resend | Sending the emails listed above. |
| Sign in with Google, if you use it; analytics on our marketing, sign-in and sign-up pages only. | |
| Apple | Sign in with Apple and its private email relay, if you use them. |
| PostHog | How the app is used, and recordings of app sessions, as described above. |
| Sentry | Crash and error reports from the website and the app. |
| Expo | Delivering push notifications and app updates. |
| Apple and Google | Distributing the app through their stores, and delivering push notifications to phones. |
Some of these providers store data outside the United Arab Emirates, including in the European Union and the United States. Each is bound by its own published terms and data-protection commitments.
How long we keep things
| Data | Kept for |
|---|---|
| Fan session tokens | 24 hours after the live session ends; sooner if blocked. |
| Request names and messages | 30 days, then removed. The song and outcome stay as a count. |
| Booking enquiries | Until the act deletes them, or 12 months after they are closed or marked spam. |
| Act analytics counts | For as long as the act exists. They contain no personal data. |
| Invitations | Until accepted or expired. |
| Audit and security records | 12 months. |
| A deleted act | Purged 3 days after deletion, which gives time to change your mind. |
| Tips and their fees | As long as accounting law requires. |
| Ziina connection tokens | Until you disconnect Ziina or delete the act. |
| Custom tag orders | Paid orders: as long as accounting law requires. Unpaid designs: 30 days. |
| Push notification addresses | Until you sign out on that phone or delete your account. |
| Crash and error reports | Up to 90 days, in Sentry. |
| App usage events | As long as our PostHog plan keeps them, currently one year. |
| App session recordings | 30 days, in PostHog. |
| Backups | Our providers’ documented backup windows, after which deleted data is gone from those too. |
What you can do
- See and correct everything about your act and profile in the dashboard.
- Export your song list and your analytics as CSV from the dashboard.
- Delete an act from its settings. Its page, tag, songs, gigs, requests and enquiries go with it after the 7-day grace period. Financial records stay as described above.
- Delete your account yourself: in the app, tap Delete my account; on the website, it is at the bottom of an act’s Settings. Your account, your profile and every act you own go with it; bandmates keep their own accounts. If you signed in with Apple, we also disconnect GigTag from your Apple ID. If you pay for Pro, deleting the account cancels it straight away, so Stripe stops charging you. If one of your acts has taken tips, those financial records must be kept, so contact us and we will delete everything else.
- Turn off notifications for each kind in the app, or for the whole app in your phone’s settings.
- As a fan, cancel a request you sent from the same phone while it is waiting. If you want a name or message removed sooner than 30 days, ask the act or ask us.
- Complain. If you think we have handled your data badly, use our data-protection complaint form: we confirm we have it straight away, reply within 30 days, and put it right. You can also raise it with the data-protection authority where you live (in the UK, the Information Commissioner’s Office).
How we protect it
Everything travels over TLS. Data is separated per act in the database with row-level security, so one act cannot read another’s. Session tokens and invitation tokens are stored as hashes. Uploaded images land in a private quarantine and only processed copies are published. Access to the operator tools is limited to named staff and logged.
Children
Accounts are for performers who are 18 or over. Anyone can look at a public act page, but if you are under 13 please do not type your name or a message into a request or a booking form. If we learn we hold a child’s personal data we will delete it.
Changes to this notice
When the product changes in a way that changes what we collect, this page changes with it and the date at the top moves. Material changes that affect performers are also announced in the dashboard.