Privacy
How 9ja Season handles personal information.
This product notice explains the data flows implemented by the application. Your organisation must add its registered entity details, data-protection contact and approved retention periods before launch.
Information we use
Account identity and contact details, booking guests, payment-provider references, support communications, saved experiences, request preferences, fraud and security events, consent choices and optional location details supplied for custom plans.
Why we use it
To operate accounts, fulfil bookings, issue and validate tickets, process refunds, provide support, meet legal obligations, protect the platform and—only with the relevant choice—send marketing.
Payments and providers
Card details are handled by enabled payment providers and are not stored by this application. We store transaction references, amounts, states and signed webhook evidence needed for reconciliation.
Retention and rights
Financial and audit records are retained according to approved statutory schedules. Other records must be deleted or anonymised when no longer necessary. Customers may request access, correction, objection or deletion where applicable through the support centre.
Security
Access is role-scoped; sessions and ticket credentials are hashed or signed; financial and audit ledgers are append-only; and administrative changes are logged.