Cookies and storage

Sign-in cookies

Perka uses Supabase authentication with cookie-backed sessions to keep you signed in and check account access. Cookies may be split into several parts and refreshed as the session changes. The exact production names and lifetimes have not yet been confirmed, so this draft does not give an invented expiry period.

During Google sign-in, Perka briefly stores a one-time verification value in a cookie so it can safely complete the sign-in when Google returns you to the app. While you are on Google's pages, Google may use its own cookies under its own policy.

Authentication storage supports the sign-in experience. Blocking it can prevent sign-in or stop the app remembering your session.

Installed-app storage

The production service worker caches an anonymous public app shell, app files and selected same-origin images and icons. Up to three published public guides are stored on this device for up to 24 hours. Session bookmarks are stored separately in this browser, do not sync across devices, and remain until removed or site data is cleared. This storage is separate from cookies; browser eviction or clearing site data may remove it sooner.

Authenticated API responses and organiser previews are not cached by the service worker. Downloaded public vendors, programme and map details can be browsed offline.

While you are signed in to an event app, a copy of your account for that event is kept in this browser's local storage so the app opens and works without signal: your registration (name, email and preferences), saved makers, agenda, ticket, entry pass code, and saves or agenda changes still waiting to sync. The server's copy replaces it each time the app connects. It is removed when you sign out, leave the event, delete your account or another account signs in on this device, and after 30 days without a connection. Your account itself stays on the server; clearing site data removes only this copy.

Organiser staff using gate check-in: passes scanned without signal are kept in this browser's local storage (the pass code and scan time) until they sync, then removed. The gate screen itself is stored for offline use and holds no visitor or organiser data.

Analytics and optional tracking

Perka's own aggregate reporting counts event visits, vendor profile views and visible offer cards. A random token is stored in session storage for each event and SAST day; it is not linked to your account. Temporary server receipts use the token to deduplicate activity. Receipts older than the previous SAST day are pruned when that event next receives activity; daily totals remain. Quiet events can retain receipts until collection resumes or maintenance removes them.

Activity collection is skipped when the browser sends Do Not Track or Global Privacy Control, when session storage is blocked, and while offline. There are no advertising integrations. Optional browser push notifications are available at enabled events after permission. Production providers, operational logs, retention decisions and any required choice controls still need verification before launch. Organiser reports also count current registrations and saved vendors from existing service records; those records are managed through event privacy controls.

Your browser controls

Sign out in Perka when using a shared device. Your browser's site settings let you review or clear cookies and stored website data; the wording differs between browsers. Clearing site data may sign you out and remove downloaded assets or install preferences.

Removing an installed shortcut or clearing cookies does not delete the account, event registrations, or organiser-held exports. Use the event privacy controls or make a separate data request.

• Data rights
• Privacy notice