Privacy Policy

PENDING_SECP_REGISTERED_NAME ("we") determines how personal data collected through SceneOnHe is used. Our registered office is PENDING_REGISTERED_OFFICE_ADDRESS. For anything in this policy, write to privacy@sceneonhe.com.

We handle personal data in line with the laws of Pakistan, including the Prevention of Electronic Crimes Act 2016 and — on the basis that it will apply to us — the draft Personal Data Protection Bill. We apply the Bill's standards now rather than waiting for it to pass, because the data we hold does not become less sensitive in the meantime.

Buyers. Your name, email address and mobile number; the attendee name where you give one; your order history and the tickets issued to you; the payment method used and the payment provider's reference (never your card number or wallet PIN — those go directly to the provider and we never see them). For bank-transfer and cash orders we also record who confirmed receipt and when.

Organisers and their team. Your name, email, role within the organisation, and business records needed to verify you and to pay you: registered legal name, National Tax Number, province for sales tax, payout account or Raast alias, and contact details.

Identity documents (organisers only). For business verification we collect a CNIC of the principal, an NTN certificate and a bank account letter. These are stored in a private bucket, accessible only to the specific organiser organisation and to the small number of staff who review verification. They are never served from a public URL and never indexed.

Door scanning. When a ticket is scanned we record the scan time, the device that performed it, the gate, and whether the ticket was valid. This is how duplicate entry is detected and how an organiser reconciles attendance.

Technical data. IP address, browser type and the pages you request, recorded by our edge provider in ordinary server logs for security and abuse prevention. We do not run advertising trackers and we do not build behavioural profiles.

• To perform our contract with you — processing your order, issuing and validating tickets, taking and refunding payment, paying organisers.
• To meet legal obligations — tax and accounting records, business verification (KYB), and responding to lawful requests from authorities.
• Legitimate interests — preventing fraud and ticket touting, keeping the platform secure, detecting duplicate or forged tickets, and resolving disputes. We balance this against your rights and you may object at any time.
• With your consent — marketing email, which is opt-in and one click to leave. Buying a ticket does not sign you up for marketing.

We do not sell personal data, and we do not share it for anyone else's marketing. We use a small number of processors who act on our instructions:

• Supabase — database and private object storage, including the KYB document bucket.
• Cloudflare — CDN, TLS, and the compute environment that serves this site, including security and abuse-prevention logging.
• Our email provider — transactional mail only: ticket delivery, one-time codes, refund and settlement notices.
• Payment providers — once card, wallet and Raast rails are live, the provider processes the payment itself and returns only a reference to us.
• Professional advisers and authorities — where we are legally required to disclose, or where disclosure is necessary to establish or defend a legal claim.

Where a payment requires manual confirmation, the organiser sees the order reference and the amount — not your card details.

Our database and storage are hosted by Supabase and our edge is Cloudflare. Both operate infrastructure outside Pakistan, so your data may be processed in jurisdictions other than Pakistan.

We require our processors to apply protections equivalent to those described here, and we keep the number of jurisdictions involved to a minimum. Identity documents are held in a private, access-scoped bucket with no public route to them regardless of which region serves them.

• Orders, tickets and settlement records: 6 years after the end of the financial year they relate to, because tax and company law require us to retain accounting records for that period.
• KYB identity documents: while the organiser account is active and for 6 years afterwards, to satisfy anti-money-laundering and record-keeping expectations.
• Abandoned checkout data: the hold and any personal details attached to an unpaid order are cleared within 48 hours plus one sweep interval once the hold expires.
• Server and security logs: up to 90 days.
• Marketing consent records: until you withdraw consent, plus a short period to prove we honoured it.

Where you ask us to delete data we are required to keep by law, we will tell you which categories we must retain and why, rather than deleting silently or refusing outright.

Subject to our legal obligations, you may ask us to:

• tell you what personal data we hold about you, and give you a copy;
• correct anything inaccurate, including your contact details on an order;
• delete data we no longer have a legal reason to keep;
• restrict or object to processing based on our legitimate interests;
• provide your data in a portable, machine-readable format;
• withdraw marketing consent at any time.

Write to privacy@sceneonhe.com. We respond within 30 days. We will ask enough to verify that you are the person the data belongs to — we will not hand an order's contents to someone who merely knows the order number, and we will not ask you for a password or a full CNIC number by email.

If you are unhappy with our response you may complain to the relevant authority in Pakistan; we would rather you told us first so we can fix it.

Access to buyer and organiser data is enforced by row-level security in the database, not only by the interface: a signed-in user's queries are constrained by policy, so one organiser cannot read another's orders or documents even with a crafted request.

Identity documents sit in a private bucket. System-level credentials that could bypass those protections exist only in server environments and are never shipped to a browser. Tickets are signed so a forged one fails verification, and scanning works offline so a venue network failure does not degrade into manual entry.

If a breach affects your personal data, we will notify you and the relevant authority without undue delay, and we will tell you what was affected rather than issuing a vague reassurance. Our reporting channel for security issues is described at /security.

The platform is not intended for anyone under 18. We do not knowingly collect data from children. If you believe a child's data has been provided to us, contact us and we will remove it.

We use a strictly limited set of cookies — an authentication session cookie and a short-lived, signed proof cookie that binds a guest browser to its own checkout. We do not use advertising or analytics cookies. The detail is at /cookies.

The version and effective date at the top of this page identify the text in force. Material changes will be notified to registered users by email before they take effect.