Overview
This Cookie Policy explains how Pàdéyáuses cookies and similar technologies to keep the Platform signed-in, secure, and useful. On this page, “cookies” includes:
- HTTP cookies set in your browser
- localStorage and sessionStorage (browser storage that persists on your device)
- Other comparable on-device storage used for the same purposes
For broader data practices, see the Privacy Policy.
Essential storage
Essential storage is required for core functions: security, load balancing, fraud prevention basics, checkout flow continuity, and remembering choices the site needs to work. This includes critical localStorage and sessionStorage entries (for example sign-in state and checkout hints), not only HTTP cookies. Disabling or clearing essential storage can break login, checkout, or account access.
Pàdéyá does not currently rely on a separate in-product cookie consent banner; when we introduce optional analytics or marketing tags, we will describe them here and in the product.
Auth & session
Pàdéyá currently uses browser localStorage to keep you signed in and sends authentication tokens to our API using Authorization headers. We do not use traditional login session cookies for normal account access.
Clearing site data for Pàdéyá (including localStorage) will sign you out. Blocking HTTP cookies alone may not remove localStorage tokens or end your session.
Preferences & UX
We use localStorage and sessionStorage to remember UI and workflow choices so you do not reset them every visit. These are not traditional cookies but behave like browser storage used to remember preferences or improve the experience. Examples include:
- Theme preference (including dark mode)
- Host workspace context (active host, workspace mode)
- Notification sound preferences
- Discovery and location preferences where you opt in
- Short-lived checkout or registration hints in sessionStorage
- Progressive Web App (PWA) offline display cache for tickets or merch pickup where enabled
- Merch draft cart state while you browse an event store
Ambassador referrals
When you visit an event or checkout link with an ambassador referral parameter, Pàdéyá may set an HTTP cookie to attribute ticket or merch sales fairly to ambassadors.
- Name:
padeya_amb_ref_v1 - Purpose: stores ambassador referral codes for event attribution
- Set when: you land with
?ref=or?amb=on an event or merch page (including checkout URLs that carry those parameters) - Behavior: last click wins per event; expires after 30 days;
SameSite=Lax;path=/
At checkout, referral credit uses this order of precedence:
- Explicit ambassador code entered by the buyer
- Referral code from the link (
ref/amb) - The referral cookie, if still valid
An explicit code at checkout always overrides a link or cookie. You can remove this cookie through browser cookie controls or by clearing site data for Pàdéyá.
Analytics
First-party product analytics (Pàdéyá) measure page views, discovery, checkout funnels, and reliability signals so we can operate and improve the marketplace. These events are sent to Pàdéyá APIs and use on-device IDs in localStorage / sessionStorage (for example anonymous visitor and session IDs). They are not sold as advertising profiles.
Optional Google Analytics (GA4) may be enabled in production when a measurement ID is configured. GA4 does not load until you explicitly allow it on this page (or an equivalent in-product control). If you deny or have not decided, GA4 stays off. Non-production environments never load GA4.
Marketing
Ambassador referral attribution (see above) supports outreach and commission programs you interact with through referral links. We may also use analytics or marketing technologies where enabled to measure campaign effectiveness, subject to the same privacy principles in our Privacy Policy.
We do not claim exhaustive ad-tech coverage here. Optional marketing tags, when used, will be described in product notices and updated on this page.
Third-party services
Payment partners, hosting, messaging delivery, and similar processors may set their own cookies or use browser storage when you use their flows.
Paystack (and similar payment providers) may set their own cookies or use browser storage during payment processing on checkout. Pàdéyádoes not control Paystack’s browser storage; those services are governed by their policies in addition to ours.
Your controls
- Use your browser’s cookie settings to block or delete HTTP cookies (including ambassador referral cookies).
- Clear site data for Pàdéyá to reset sign-in, preferences, localStorage, sessionStorage, and cookies together. This typically signs you out.
- You can clear localStorage and sessionStorage separately in developer or site-data tools if your browser supports it.
- Manage notification and email preferences in your account where available.
- Manage discovery location preference in the product or by clearing site data.
- Opt out of marketing communications where we offer those controls (for example email preferences).
- When optional GA4 is configured, use the control below to allow, deny, or reset that choice.
- Questions: Support or Contact.