Privacy, in plain language.
This notice describes the current Hapnin discovery service. It will be updated before new data uses are introduced.
Last updated 14 September 2026
Information you provide
If you create an account, Hapnin stores authentication and profile information such as your display name, city, and selected interests. Saving an event stores the link between your account and that event. Event suggestions and optional correction correspondence contain only what you choose to send.
Information kept on your device
Hapnin uses a city preference cookie, authentication session data, and browser storage for your appearance choice and short-lived Discover-page restoration.
Operations and analytics
Operational logs are used to run, secure, and diagnose the service. To understand whether discovery leads to useful provider handoffs, Hapnin keeps daily aggregate counts of event-detail views and outbound ticket, source, map, and ride actions. These product counters do not contain an account ID, cookie ID, session ID, IP address, or per-interaction timestamp.
Provider handoffs
Opening a ticket, RSVP, map, or ride link takes you to a third party. That service receives the information your browser normally sends when visiting it and applies its own privacy terms.
Access, correction, and deletion
You may ask about personal data linked to you, request correction of inaccurate information, object to processing, or request deletion where applicable. Use Corrections & contact. Kenya’s Office of the Data Protection Commissioner also explains data-subject rights.
Account and save data remain linked to your account unless they are deleted. Operational records and public-source evidence may be retained when needed to secure the service, investigate problems, or keep an auditable listing history.