Cookie Policy
Last Updated: May 12, 2026
This Cookie Policy describes how AETC (“we”, “us”) uses cookies and similar technologies on aetconference.com, how they relate to our Privacy Policy, and how you can control non-essential technologies. It is drafted with GDPR transparency expectations in mind (Articles 13–14 and ePrivacy concepts).
1. What are cookies & similar technologies?
Cookies are small text files stored on your device when you visit a site. We also use functionally similar technologies such as local storage (for example to remember your cookie banner choice) and session identifiers in cookies required for secure authentication.
Cookies may be first-party (set by us) or third-party (set by partners whose content or scripts load on our pages — for example during a hosted payment session).
2. Legal bases (GDPR)
Strictly necessary cookies (and equivalent session mechanisms) are used to provide the service you request — for example keeping you signed in and securing attendee areas. Where GDPR applies, these can rely on our legitimate interests in secure delivery of the Services or are exempt from consent requirements under applicable ePrivacy guidance because they are strictly necessary.
Optional analytics loads only when you choose Accept all cookies in our banner — in that case we rely on consent, which you may withdraw at any time by clearing site data / changing preference (see Section 5).
3. How our consent banner works
Our Site displays a cookie banner implemented in the application codebase. Your choice is stored in browser localStorage under the key aetc-cookie-consent with values such as accepted (optional analytics permitted) or essential (essential functionality only). Closing the banner without accepting optional cookies defaults to essential-only behaviour for that browser.
Important: Supabase authentication and ticketing cookies required for sign-in, dashboards, and checkout may remain active independently because they are strictly necessary for those features — they are not switched off by rejecting optional analytics.
4. Technologies we use (overview)
| Category | Purpose | Consent? |
|---|---|---|
| Strictly necessary — authentication & sessions | Cookies set by Supabase / our auth middleware (for example session and refresh tokens scoped to our domain) so you can authenticate, access /dashboard, /my-tickets, attendee forms, and admin tools securely. | Not required |
| Strictly necessary — security & routing | Edge / hosting headers or cookies supporting CSRF protection, load balancing, or bot mitigation where deployed. | Not required |
| Preference storage (localStorage) | Stores your cookie choice (aetc-cookie-consent) so we do not repeatedly ask on every visit from the same browser. | Necessary for preference |
| Analytics (Vercel Web Analytics) | Privacy-conscious, aggregated usage metrics loaded through @vercel/analytics only after you choose Accept all cookies — helps us understand traffic patterns. | Consent required |
| Payment partner cookies | When you initiate checkout, Paystack (or successor processor) may set cookies or similar technologies on its domains to prevent fraud and complete payment — governed by Paystack’s policies while you are on their flow. | Third-party |
5. How to control cookies
You can manage cookies in several ways:
- Use our cookie banner: choose Accept all or limit to Essential only / dismiss to essential defaults as described on the banner.
- Adjust your browser settings to block or delete cookies. Note blocking strictly necessary cookies may prevent sign-in or ticketing features from working.
- Clear site data / localStorage for our domain to reset your banner preference (you will see the banner again).
6. Mobile application
Native apps do not use browser cookies in the same way. The AETC Attendees app stores authentication tokens or preferences using platform-secure storage mechanisms governed by our Privacy Policy. Mobile OS permission prompts (camera, photos, etc.) operate separately from website cookie controls.
7. Retention
Session cookies typically expire when you close your browser or sign out; persistent cookies follow durations set by the issuing party (for example authentication refresh rotation managed by Supabase). Analytics payloads tied to consent are discontinued when consent is withdrawn (future collection stops; historic aggregated datasets held by the analytics processor may remain anonymised).
8. Updates
We may update this Cookie Policy when we introduce new technologies or legal requirements change. Please review this page periodically — material updates will be reflected in the “Last Updated” date above.
Contact
Questions about cookies or this Policy:
privacy@aetconference.com · general enquiries: info@aetconference.com