SELLTICKETS Ltd (operating as SellTickets.Net) · Innovation City, Ras Al Khaimah, United Arab Emirates
Licence No. 07011340 · Effective Date: 6 September 2026
This Privacy Policy explains how SELLTICKETS Ltd (“SellTickets.Net,” “we,” “us,” or “our”) collects, uses, shares, and protects personal information in connection with the selltickets.net platform — both on our own websites and through the ticketing websites we host for Event Organizers. It also contains the disclosures required for our integrations with Google, Facebook, and Instagram, including our use of OAuth sign-in, the Google Ads API, the Meta Pixel, and Meta developer applications.
1. Who This Policy Covers — Our Two Roles
SellTickets.Net is a multi-tenant Software-as-a-Service platform. Event Organizers (“Organizers” or “Tenants”) use our software to run their own ticketing websites — on a subdomain of selltickets.net or on their own custom domains — and members of the public (“Ticket Buyers”) buy tickets on those websites. Because of this, we act in two distinct roles:
- Acting for ourselves (data controller). For visitors to our own marketing website (selltickets.net), for Organizer accounts, billing, and support, and for the security and operation of the platform itself, SELLTICKETS Ltd decides how and why data is processed and is the data controller.
- Acting for Organizers (data processor / service provider). For personal information collected on Organizer-hosted pages — such as a Ticket Buyer’s name, e-mail, orders, seats, and attendance — the Organizer is the data controller and we process that data only on the Organizer’s behalf and instructions, as a service provider. Each Organizer is responsible for its own privacy notice and for having a lawful basis for the data it collects on its pages. If you bought a ticket on an Organizer’s website, that Organizer is your primary point of contact for privacy matters; we will assist where required.
2. Information We Collect
- Organizer account information: name, e-mail address, password (stored hashed), organization details, subscription plan, billing records, and support correspondence.
- Ticket Buyer information (processed for Organizers): name, e-mail address, phone number, ticket and seat selections, order and payment status, check-in/attendance status, and customer-account details where the Buyer creates one on an Organizer’s site.
- Advertising click identifiers: where a visitor reaches an Organizer’s page from an advertisement, the link carries an identifier added by the advertising platform (for example Google’s
gclid). Where the visit results in an order, that identifier is stored with the order so the Organizer can see which advertising produced the sale, whatever cookie choice the visitor made. It identifies the click, not the person. Sharing it with the advertising platform is a separate step and requires marketing consent (Section 6.1).
- Technical and security data: IP addresses, browser and device characteristics, request logs, approximate visit counts, anti-abuse signals (including Cloudflare Turnstile bot-detection results), and cookie-consent choices (Section 5), collected automatically to keep the platform secure, available, correctly localized, and aligned with the choices visitors make.
- Connected-service data: if an Organizer connects a third-party account (Google, Facebook/Instagram, or a payment gateway), we receive and store the data described in Sections 6, 7, and 9.
3. How We Use Information
- To provide, operate, and maintain the platform and the Organizer websites we host.
- To process ticket orders and payments securely and send transactional e-mail (order confirmations, tickets, account messages).
- To protect the platform: fraud and bot prevention, seat-inventory abuse detection, security monitoring, and debugging.
- To operate the specific features an Organizer has enabled (for example SEO tools via Google, or the Meta Pixel and related Facebook/Instagram features).
- To advertise an Organizer’s performances on Google Search where the Organizer has asked us to, and to measure the ticket sales those advertisements produced (Section 6.1).
- To provide customer support, measure aggregate platform usage, and improve the product.
- To comply with legal, tax, and accounting obligations.
4. What We Do Not Do
- We do not sell or rent personal information — not ours to begin with, and never our Organizers’ or their Ticket Buyers’.
- We do not combine Ticket Buyer data across different Organizers to build cross-tenant marketing or advertising profiles.
- We do not use Ticket Buyer e-mail addresses for our own marketing.
- We do not store full payment-card numbers on our servers (see Section 9).
- We do not use data obtained from Google APIs or from Meta’s platform (Facebook/Instagram) to develop or train artificial-intelligence or machine-learning models.
- We do not send a Ticket Buyer’s name, e-mail address, telephone number, or seat to Google’s advertising systems — not even in hashed form (Section 6.1).
- We do not place our own advertising, or any third party’s advertising, on Organizer-hosted pages. Tracking technologies on those pages run only when, and because, the Organizer enabled them (Section 8).
5. Cookies and Similar Technologies
We use cookies and similar technologies that are strictly necessary to operate the platform: session cookies (sign-in state, shopping cart, checkout integrity), language preference, and security cookies set by our edge provider, Cloudflare. On our own website we additionally measure visits using a privacy-conscious, server-mediated analytics setup (Cloudflare Zaraz); identifiers sent to analytics are pseudonymized. Our own website also runs a Google Ads conversion tag, but only for visitors who accept marketing cookies — see Section 6.2. On Organizer-hosted pages, additional cookies or pixels may run if the Organizer has enabled them — see Section 8. You can control cookies through your browser settings; blocking strictly necessary cookies may break sign-in or checkout.
Consent banner. Organizer-hosted pages show a cookie-consent banner: strictly necessary cookies (including the operational analytics above) run in any case, while preference and marketing cookies run only if the visitor consents — per category, if they wish. The choice, including a decline, is stored in a small consent cookie (st_cc) for about six months so the banner is not shown again, and is asked afresh when it expires or when the Organizer’s cookie practices change.
6. Google Services — Advertising and Limited Use
This section is the disclosure required by the Google API Services User Data Policy. The application it describes is SellTickets.Net, operated by SELLTICKETS Ltd — the same name shown on Google’s OAuth consent screen — reachable at selltickets.net. It sets out, for each Google integration separately, what Google user data the application accesses, why, where it is stored, who it is shared with, how long it is kept and how to have it deleted.
We use Google in three separate ways, and the difference matters: in the first the Organizer connects their own Google account; in the second the advertising account is ours; in the third, described in Section 6.3, a Ticket Buyer signs in with their own Google account.
6.1 Advertising on Google (Google Ads API). Organizers may ask us to advertise their performances on Google Search. The most important thing to understand about this service is that the advertising account is ours, not the Organizer’s. SELLTICKETS Ltd holds its own Google Ads manager account and its own Google Ads API credentials, and creates one advertising sub-account per Organizer beneath it. The Organizer does not connect a Google account for this feature and never receives Google Ads credentials; we are the advertiser of record and Google invoices us. Running this feature gives us no Google user data belonging to the Organizer or to any Ticket Buyer.
- What the advertisements are built from. Campaigns, ad text and keywords are generated from the Organizer’s own published event information — the act, venue, date, time and ticket price already shown on their public ticketing pages. We bid only on the Organizer’s own shows, acts and venue.
- Measuring ticket sales. When a Ticket Buyer reaches an Organizer’s page from one of these advertisements, the link carries a Google click identifier. If that visit leads to a completed order, we report the sale to Google so the Organizer can see which advertising worked. We send only the click identifier, the time of the order, its value and its currency. We do not send the Buyer’s name, e-mail address, telephone number, seat or any other identifying detail — not even in hashed form.
- Consent first. A sale is reported to Google only where the Ticket Buyer accepted marketing cookies on the Organizer’s page (Section 5). The choice is recorded with the order, and an order placed without that consent is never reported.
- Refunds. If a ticket is refunded, we send Google a matching correction, so the reported figure follows the money rather than the checkout.
- The Google account this runs on. The application authenticates to the Google Ads API through Google OAuth on SellTickets’ own Google Account, using the
https://www.googleapis.com/auth/adwords scope. That grant reaches exactly one account — ours — and is used only to create advertising sub-accounts under our manager account, to build and manage the campaigns described above, to report settled ticket sales as conversions, and to read back the resulting cost and performance figures. The refresh token is stored encrypted on our servers, is never exposed in a browser, and is used only by scheduled server-side tasks. No Organizer and no Ticket Buyer authorizes anything, and none of their Google account data is accessed by this integration.
- Aggregate comparison across Organizers. To give a newly advertised performance a sensible starting budget, we compare it against the aggregate advertising results of comparable performances across the platform, grouped only by category, city and ticket-price band. This uses campaign cost figures — never Ticket Buyer data — and a group is used only where it contains at least five comparable performances, so that no individual Organizer’s figures can be inferred from it.
Google’s own processing of advertising data is described in the Google Privacy Policy and governed by Google’s advertising and data-processing terms.
6.2 Advertising SellTickets itself. Separately from the service described above, we advertise our own product to event organizers, and our own website selltickets.net carries a Google Ads conversion tag so that we can tell which of our advertisements produced an enquiry. It runs only where the visitor accepted marketing cookies, and only on selltickets.net — never on an Organizer’s ticketing pages, where the measurement described in Section 6.1 is server-side and sets no advertising cookie. The one conversion it records is a submitted “express interest” enquiry, and it carries the page and the enquirer’s self-declared business profile; the name, e-mail address and telephone number given in that form are not sent to Google.
6.3 “Sign in with Google” for Ticket Buyers. An Organizer may offer Ticket Buyers the option of creating an account and signing in with their Google account, instead of choosing a password. This is a sign-in feature only: it establishes who the Buyer is so they can reach their orders and tickets, and it does nothing else.
- What we receive. Only Google’s three basic sign-in permissions —
openid, email and profile. In practice that is a stable Google account identifier, the Buyer’s e-mail address, and the display name on their Google account. We request no other permission, and we therefore have no access to the Buyer’s Gmail, Drive, Contacts, Calendar or any other Google service.
- What we store. The Google account identifier, the e-mail address, the name, and the time the account was linked — held on the Buyer’s account with that Organizer. We store no Google access or refresh token: the credential is used once, during sign-in, and discarded. We do not store a Google profile picture.
- Why the identifier and not just the address. The identifier is stable, whereas a Google e-mail address can be reassigned to a different person within an organisation. Matching on the identifier is what prevents one person’s ticket history being shown to whoever later inherits their address.
- One Organizer, one account. A Google sign-in creates an account with the Organizer whose page it was used on, and only that Organizer. A Buyer who uses the same Google account on two Organizers’ storefronts has two separate accounts, with separate order histories. Signing in on one storefront gives no access to the other.
- Sharing. Nothing received from Google is sold, and it is not shared with any third party. It is not used for advertising, for audience building, or for any profiling. It is not sent to Meta, to Google’s advertising systems, or to any other Organizer.
- Retention and deletion. The linked Google details live for as long as the Buyer’s account with that Organizer does, and are deleted with it (Section 15). A Buyer can unlink at any time by asking the Organizer, which removes the stored identifier and leaves the account reachable by e-mail; and can revoke our access independently at myaccount.google.com/permissions. Because we hold no token, revoking simply means the next sign-in asks for permission again.
- Roles. The Ticket Buyer is the Organizer’s customer. The Organizer is the controller of the account and its order history; we process it on their instructions as their service provider.
Whose name appears on the Google screen. Where the Organizer has their own verified Google application — which requires their own domain, logo and registered company details — the permission screen carries the Organizer’s name and logo, because the application is theirs; SellTickets operates the sign-in on their behalf, and the Organizer’s storefront says so beneath the button. Every other storefront uses SellTickets’ own application, and the permission screen says SellTickets.Net. The data described above is the same either way.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements, as stated in Section 6.4.
6.4 Limited Use of Google user data. SellTickets.Net’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This applies to every integration in this section, and specifically:
- We use Google user data only to provide and improve the user-facing features described above — the advertising services in Sections 6.1 and 6.2 and the sign-in feature in Section 6.3. We do not use it for any other purpose.
- We do not transfer Google user data to others, except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to the affected users. We do not sell it, and we do not pass it to data brokers or information resellers.
- We do not use Google user data to serve advertising of any kind, including retargeting, personalized advertising, or interest-based advertising.
- We do not use Google user data to develop, improve or train generalized or non-personalized artificial-intelligence or machine-learning models.
- We do not allow humans to read Google user data, unless we have your affirmative agreement for specific messages, it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or the data has been aggregated and anonymized so that it no longer identifies anyone.
Organizers may install our Meta & Instagram integration and connect their Facebook and Instagram professional assets through Meta’s OAuth login. Depending on the permissions the Organizer approves during that flow, we may receive and store (“Platform Data”):
- basic profile information of the connecting user (name, ID, e-mail);
- the identity and metadata of the business assets the Organizer selects — Facebook Pages, Instagram professional accounts, Meta Pixels/datasets, and ad accounts;
- OAuth access tokens, which we store encrypted and use only server-side.
How we use Platform Data. Solely to provide the features the Organizer has enabled: serving the Organizer’s own Meta Pixel on the Organizer’s ticketing pages, and — where the Organizer uses them — features that publish content or manage advertising on the Organizer’s behalf, on the assets the Organizer selected. We act as the Organizer’s service provider in doing so; we do not use Platform Data for our own advertising or analytics, we do not sell it, and we do not share it with third parties except as needed to operate the feature (that is, exchanging it with Meta itself via its APIs).
Consent first, hashing always. On Organizer pages, the Organizer’s Meta Pixel loads only after the Ticket Buyer grants marketing consent on the cookie banner (Section 5); declining keeps it off entirely. Where the Organizer uses server-side purchase confirmation (Meta’s Conversions API), events are sent only for orders placed with that consent — the choice is recorded with the order — and the buyer’s e-mail address is transmitted solely as an irreversible SHA-256 hash, with the order number as the deduplication event ID. Plain e-mail addresses are never sent to Meta.
A dedicated privacy policy for this application — covering its Platform Data handling in full — is published at selltickets.net/privacy/meta.
Compliance and control. Our use of Platform Data is subject to the Meta Platform Terms and Developer Policies. The Organizer can disconnect the integration at any time from the SellTickets.Net admin panel (Marketplace → Meta & Instagram), which deletes the stored tokens and the associated Platform Data from our systems. The connection can also be revoked on Meta’s side under Facebook Settings → Business Integrations (or Instagram Settings → Apps and Websites). See Section 15 for full deletion instructions. Meta’s own processing is described in the Meta Privacy Policy.
8. Tracking Pixels on Organizer Pages
When an Organizer connects its Meta Pixel (and, similarly, any analytics the Organizer configures), our platform loads that Organizer’s pixel on the Organizer’s hosted pages and sends it standard events — such as page views and purchase confirmations relating to that Organizer’s events. The pixel runs consent-first: it loads only after the Ticket Buyer accepts marketing cookies on the page’s consent banner (Section 5), and a decline keeps it off entirely. These events go to the Organizer’s own Meta dataset (or analytics property), not to any property of ours. The Organizer, as the data controller of its pages, is responsible for disclosing this tracking in its own privacy notice and for obtaining any consent its jurisdiction requires; to help with that, the platform publishes a ready-made pixel disclosure notice on the Organizer’s pages when a pixel is activated. Where an Organizer advertises through us on Google Search, the click identifier described in Section 6.1 is recorded with the resulting order in every case, as part of the Organizer’s own record of which advertising produced which sale. Reporting that sale to Google is a separate step and is consent-first: an order placed without marketing consent is never reported. Ticket Buyers can also limit this tracking through browser controls, ad-preference settings on the relevant platform (for Meta: Ad preferences), or by contacting the Organizer.
9. Payments
Card payments are processed by PCI-DSS-certified payment gateways (currently iyzico and PayTR, chosen per Organizer). Card details are either entered in an interface controlled by the gateway or transmitted directly to the gateway over encrypted channels for 3-D Secure authentication; full card numbers are never stored on our servers. We retain transaction metadata (amount, currency, status, gateway reference, and masked card details where provided by the gateway) as needed for order fulfilment, refunds, fraud prevention, and financial record-keeping.
10. When We Share Information
We share personal information only with service providers that help us run the platform, under contracts limiting their use of it, and only as needed:
- Hosting & infrastructure: Amazon Web Services (servers and database located in the EU — Frankfurt, Germany; media storage on Amazon S3).
- Edge, security & analytics: Cloudflare (TLS termination, WAF, bot protection, server-mediated analytics).
- Payment gateways: iyzico, PayTR (to process the payments described in Section 9).
- E-mail delivery: transactional e-mail providers (Resend, Amazon SES), including delivery/bounce tracking.
- Google and Meta: only in the circumstances and directions described in Sections 6–8.
- The relevant Organizer: Ticket Buyer data is, by design, available to the Organizer whose event the Buyer purchased for — the Organizer is its controller.
- Legal: where required by law, regulation, or valid legal process, or to protect the rights, safety, and integrity of the platform, its users, or the public.
We may also disclose information as part of a corporate transaction (merger, acquisition, or asset sale), subject to this policy continuing to apply.
11. International Data Transfers
Platform data is primarily stored and processed in the European Union (Frankfurt, Germany). SELLTICKETS Ltd is established in the United Arab Emirates, and some service providers listed above operate globally. Where personal data is transferred across borders, we rely on appropriate safeguards such as contractual data-protection commitments with our providers.
12. Data Retention
- Organizer accounts: retained for the life of the subscription and deleted or anonymized after account closure, except records we must keep for legal, tax, or accounting purposes.
- Ticket Buyer and order data: retained on behalf of the Organizer for as long as the Organizer uses the platform, and thereafter as required by statutory financial record-keeping periods.
- Meta OAuth tokens: retained only while the integration is connected; deleted when the Organizer disconnects or uninstalls it, or on request.
- Our own Google Ads credentials: held by SELLTICKETS Ltd for as long as we operate the advertising service. They belong to our account, not to any Organizer, and contain no Organizer or Ticket Buyer personal data.
- Security and technical logs: retained for a limited period appropriate to security investigation and then deleted or aggregated.
13. Security
We protect data with TLS encryption in transit (with HSTS), encryption of stored credentials and third-party tokens, strict per-tenant data isolation enforced at the application layer, web-application-firewall and bot protection at the network edge, least-privilege access controls, and continuous security monitoring. No system is perfectly secure; if we learn of a breach affecting your personal data we will notify affected parties and authorities as required by law.
14. Your Rights and Choices
Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, or receive a copy of your personal data, and to object to certain processing.
- Organizers: exercise these rights through your admin panel or by contacting us (Section 18).
- Ticket Buyers: because the Organizer you bought from is the controller of your data, please direct requests to that Organizer first; we support Organizers in fulfilling them. You may also contact us directly and we will assist or forward your request.
- Connected accounts: you can revoke our access at any time via Google Account permissions or Facebook Settings → Business Integrations / Instagram Settings → Apps and Websites.
15. Data Deletion Instructions
You can have data deleted from our systems in any of the following ways:
- Facebook / Instagram integration data: in your SellTickets.Net admin panel, open Marketplace → Meta & Instagram and disconnect or uninstall the integration. This deletes the stored OAuth tokens and associated Platform Data from our systems. You can additionally remove the app under Facebook Settings → Business Integrations, which immediately invalidates our access on Meta’s side; e-mail us (below) if you also want any remaining stored data purged without uninstalling from the admin panel.
- Google advertising data: ask us to stop advertising your events and we will pause the campaigns and close the advertising sub-account. The click identifiers stored with your orders are your own sales records and are deleted with them; to have a specific order’s advertising attribution removed sooner, e-mail us as below.
- Any other data, or full account deletion: e-mail [email protected] with the subject “Data Deletion Request” from the e-mail address associated with the account (Organizers), or with proof of the order/e-mail used (Ticket Buyers). We action verified deletion requests within 30 days, subject to data we are legally required to retain (for example financial transaction records).
16. Children
Our platform and websites are not directed at children. We do not knowingly collect personal data from anyone under 16 (or the higher minimum age of digital consent where one applies). Purchases must be made by adults; if you believe a child has provided us personal data, contact us and we will delete it.
17. Changes to This Policy
We may update this policy as the platform, law, or our third-party integrations evolve. The effective date at the top reflects the latest revision; material changes will be announced to Organizers through the platform. The English version of this policy is the authoritative version.
SELLTICKETS Ltd (operating as SellTickets.Net)
Office A, Innovation City Business Centre, RAK BANK ROC Office, Ground Floor, Al Rifaa, Sheikh Mohammed Bin Zayed Road, Ras Al Khaimah, United Arab Emirates
E-mail: [email protected]
