Skip to main content

Legal

Privacy Policy

Last updated · 2026-11-11

OnePass Africa Privacy Policy

This Policy explains how OnePass collects, uses, and shares personal data when you use our platform, whether as an event organizer, a ticket buyer, or a visitor to onepassafrica.com. OnePass is a product of Blache, the trading name of Wired Intelligence Ltd ("we", "us"), which is responsible for your personal data.

1. The data we collect

  • Account data: your email, name (optional), and the events / organizers your account is associated with.
  • Organizer applications: when you apply to sell on OnePass, your name, email, phone number and company details, so our team can review the application and contact you about it. Kept after a decision, including a declined one, and never shown on your storefront.
  • Buyer data: name, email, phone, and tickets purchased. Collected by the organizer at checkout and stored on our platform on their behalf.
  • Wallet card data: a unique cross-network MemberCard identifier and the QR rotation history. This is the data that lets one pass work across every gate on OnePass.
  • Entry records: each time your ticket or wallet card is scanned at an event on OnePass, we record the event, the time, the gate (when the organizer names one) and whether entry was allowed. These records are tied to your ticket and your wallet card, so together they show which events you attended and when you walked in.
  • Payment data: handled by Paystack. We see references, amounts, and outcomes. We never see card numbers or PIN data.
  • Operational data: IP addresses for rate limiting and fraud signals, audit logs of privileged actions, basic device info for accessibility (reduced-motion preference).
  • Optional inputs: anything you add to your storefront (organizers) or your account profile (buyers).

2. How we use it

  • Provide the platform: render storefronts, process checkouts, scan tickets, route platform-fee splits, send transactional email.
  • Keep the platform safe: rate limiting, abuse detection, audit trails of who did what on which tenant.
  • Entry records: to check tickets at the door, stop a ticket being used twice, look into fraud, and show you your own history of the events you've attended in your wallet.
  • Improve the platform: anonymized usage analytics. We never use buyer data to train external AI products.
  • Honor your requests: the event concierge ("ask in plain English…") sends the prompt to a hosted LLM; we do not store the prompt with your account beyond the URL parameters needed to remount the filtered listing.

3. Cookies and similar tech

We use first-party cookies for sign-in and rate-limiting. We use Plausible Analytics, which is cookieless and aggregates without an individual buyer identifier. We do not use ad-network cookies. We do not sell your data to third parties.

4. Sharing

  • With Organizers: each Organizer can see the buyers who purchased their tickets, and the entry records for their own events. We don't share buyer data or entry records across Organizers.
  • Within OnePass: our staff can see entry records to run the platform, answer support requests and investigate fraud. You can see your own.
  • With Paystack: charge initiation and refund requests carry the buyer's email and the amount.
  • With email providers (Resend): transactional email contains the recipient's email address.
  • With Cloudflare R2: admin-uploaded media (logos, hero images, event photos) is stored on R2's public-read bucket.
  • With law enforcement: only on a valid order, and only the minimum necessary.

5. Retention

  • Audit logs: kept indefinitely for the lifetime of the tenant; archived for a defined period after tenant deletion.
  • Tickets and orders: kept for as long as the Organizer's account remains active, plus a reasonable period for accounting and refund-window compliance.
  • Entry records: kept with the event they belong to, and deleted if the event or the Organizer's account is deleted.
  • Account data: kept until you close the account; we honor erasure requests subject to legal-retention overrides (tax, accounting, refund disputes).

6. Your rights

You can access, correct, export, or delete your data. Buyers do this through the Organizer where they bought the ticket; Organizers do this through their admin console, or by emailing hi@onepassafrica.com.

You have the right to lodge a complaint with your local data-protection regulator. In Ghana, that's the Data Protection Commission.

7. Cross-border transfers

Our infrastructure runs on Vercel and Neon (Postgres), with media on Cloudflare R2 and email through Resend. Some of these vendors host data outside Ghana. Where required by law we put appropriate transfer safeguards (standard contractual clauses) in place.

8. Security

We encrypt sensitive secrets at rest (Paystack credentials are AES-encrypted with a per-platform key). All traffic uses HTTPS. We run rate limiting on authentication and checkout endpoints. No system is perfectly secure; if we identify a breach affecting your data we will notify you and the regulator on the statutorily required timeline.

9. Children

OnePass is not intended for users under 16. Organizers must apply their own age-verification at the door for events with age restrictions; we do not collect age data automatically.

10. Changes

We will post any revision with an updated "Last updated" date. Material changes to how we handle buyer data will be notified through the platform.

11. Contact

Wired Intelligence Ltd (trading as Blache), hi@onepassafrica.com: for data-subject requests, security questions, and anything else this Policy doesn't cover.