REVELA

Cookie Policy

Version 2026-11-01. This page describes technologies identified in the current application. It does not claim a complete audit of external infrastructure.

Cookies and similar technologies

Cookies are small records a browser may send to a website. localStorage and sessionStorage store browser data; IndexedDB stores structured records and files; Cache Storage stores resources for offline use. These technologies serve different purposes.

Necessary and functional technologies

REVELA and Supabase Auth use local storage for sign-in sessions and secure authentication recovery (PKCE). Names follow patterns such as sb-<project>-auth-token and associated verifiers. Token expiry alone does not determine the lifetime of all session data.

REVELA stores guest credentials, event bindings, upload receipts and recovery information. These support safe continuation; they do not grant access beyond server authorization.

The revela-offline-v1 IndexedDB database and photo-queue may hold original photos and pending uploads on this device. The service worker stores only the generic shell and verified static resources in revela-private-shell-v3-<version>; private navigation responses and guest photos are not stored in that cache.

REVELA also stores language (revela_locale), camera selection and session, draft and export recovery state. Local/demo mode may store its own event and photo data in the browser.

Optional categories

In this version, optional analytics collection is disabled and no marketing trackers are integrated. We do not offer controls for nonexistent categories or introduce a tracking provider.

Accept all and Reject optional therefore have the same technical effect in this version: only necessary/functional storage remains in use. A future change requires a policy update and a new consent assessment before optional technologies execute.

Your preference and retention

REVELA stores your choice in localStorage under revela_consent_v1, with the policy version, necessary category, disabled analytics and choice timestamp. It contains no credentials, photos or guest identifiers. This version has no automatic elapsed-time expiry: the choice is reassessed when the policy changes or the browser no longer retains the record.

sessionStorage generally follows the tab session. The revela_pending_event_v1 draft is checked against a maximum age of 24 hours when read. No single automatic deletion period has been verified for other sessions, queues, caches and preferences. Browsers may remove data because of settings, storage pressure or user cleanup.

External services

The interface requests DM Sans and DM Serif Display from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). This sends network requests to Google; we have not identified an application-created tracking cookie for that delivery. We do not claim an unverified Google retention period.

Vercel hosts the site and Supabase supplies authentication and application services. Vercel preview protection may use access cookies separate from your REVELA session. Infrastructure-set cookie names, lifetimes and behavior vary by environment and have not been fully inventoried in this implementation.

Changing your choice

Use Cookie preferences in the footer to review and save your choice. Rejecting optional technologies does not erase authentication, PKCE, guest credentials, originals, queues or session recovery. If your browser blocks preference storage, the choice applies to the current page and the banner may return on your next visit.

Browser settings can also block or delete data. Be careful: deleting site data may sign you out and remove photos that have not uploaded. REVELA’s consent panel does not perform that cleanup.

Details awaiting owner review

The controller’s formal identity and contact, legal grounds for individual functional preferences, supplier retention and infrastructure-set cookie inventory still require confirmation by REVELA’s owner. This page is not a certification of legal compliance.