GigTag

Privacy notice

What GigTag knows about you, and why

Last updated 7 October 2026.

The short version

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.

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.

Cookies and similar things

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.

ProviderWhat for
SupabaseDatabase, sign-in, and storage of the photos you upload.
NetlifyHosting the website, and delivering the contact form to us.
ZiinaTip payments, straight into the performer’s own Ziina account.
StripePro subscriptions and custom tag orders; outside the UAE, tip payments straight into the performer’s own Stripe account.
ResendSending the emails listed above.
GoogleSign in with Google, if you use it; analytics on our marketing, sign-in and sign-up pages only.
AppleSign in with Apple and its private email relay, if you use them.
PostHogHow the app is used, and recordings of app sessions, as described above.
SentryCrash and error reports from the website and the app.
ExpoDelivering push notifications and app updates.
Apple and GoogleDistributing 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

DataKept for
Fan session tokens24 hours after the live session ends; sooner if blocked.
Request names and messages30 days, then removed. The song and outcome stay as a count.
Booking enquiriesUntil the act deletes them, or 12 months after they are closed or marked spam.
Act analytics countsFor as long as the act exists. They contain no personal data.
InvitationsUntil accepted or expired.
Audit and security records12 months.
A deleted actPurged 3 days after deletion, which gives time to change your mind.
Tips and their feesAs long as accounting law requires.
Ziina connection tokensUntil you disconnect Ziina or delete the act.
Custom tag ordersPaid orders: as long as accounting law requires. Unpaid designs: 30 days.
Push notification addressesUntil you sign out on that phone or delete your account.
Crash and error reportsUp to 90 days, in Sentry.
App usage eventsAs long as our PostHog plan keeps them, currently one year.
App session recordings30 days, in PostHog.
BackupsOur providers’ documented backup windows, after which deleted data is gone from those too.

What you can do

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.