SafeGuard

Cookie and device storage policy

Draft · Last updated 8 November 2026

This is a technical disclosure draft. The operator must verify the actual browser storage and third-party scripts in the deployed build before launch.

Essential storage

Sign-in may use browser storage or cookies managed by Supabase Auth to keep an approved session active and protect authenticated requests. These are necessary for the service to work. Do not share a signed-in device with other users; sign out on shared devices.

Optional analytics

Optional analytics and advertising trackers are not intentionally enabled in the current landing page. If analytics are added later, they must remain off until the required consent is obtained and a clear choice is offered.

Third-party requests

Google may be contacted during Google sign-in. Supabase provides authentication and database APIs. OpenStreetMap tile servers may be contacted when maps are displayed. Third-party providers may receive technical request data such as IP address and browser details under their own policies.

Managing storage

You can clear browser site data or sign out, but clearing essential session storage may sign you out and require authentication again. Browser controls can block some storage, which may affect sign-in and portal features.

Changes

This policy should be revised whenever scripts, authentication configuration, maps, analytics or storage mechanisms change.