Cookie and Browser Storage Policy
Last updated: July 16, 2026
Contact email: contact@finalscore.app
This policy describes FinalScore's current use of cookies, localStorage and sessionStorage, and supplements the FinalScore Privacy Policy.
1. Scope and Definitions
1.1 This policy explains how FinalScore uses browser-side storage on the FinalScore website and application, including cookies, localStorage and sessionStorage.
1.2 In this policy, “browser storage” means information stored on or accessed from your browser or device through these technologies.
1.3 This policy covers browser-side storage on FinalScore-controlled origins, including finalscore.app and authorized preview environments. Server-side collection and processing are described in the FinalScore Privacy Policy.
2. Current Storage Practices
2.1 FinalScore currently uses first-party browser storage only. The items are set through the FinalScore origin and are used to operate and secure the service, maintain authenticated sessions, continue workflows requested by users, preserve unfinished registration drafts and remember limited interface preferences.
2.2 FinalScore does not currently use third-party cookies, advertising cookies, analytics cookies, ad pixels, behavioural tracking, cross-site tracking or session-replay technology.
2.3 Because FinalScore does not currently use optional analytics, advertising or tracking storage, FinalScore does not currently provide an optional-cookie consent banner or preference manager. If optional technologies are introduced in the future, they will not be activated until this policy and any consent mechanism required by applicable law have been updated.
3. Browser Storage Used by FinalScore
| Name or key | Storage type | Purpose and personal data | Retention |
|---|---|---|---|
sidebar_state | Cookie | Remembers whether the application sidebar is open or closed. Preference only; no personal data. | 7 days. |
sb-<project-ref>-auth-token | localStorage | Maintains the Supabase authentication session and account access. Contains authentication tokens and user/session fields, which may include user ID and email address. | Until sign-out or refresh-token expiry. The session may be refreshed automatically while active. |
finalscore.regdraft.v2.<eventSlug> | localStorage | Preserves an unfinished public registration form in the same browser. May contain the information entered by the competitor, such as email, stage name and registration answers. Uploaded files are not stored in this draft. | Up to 30 days; cleared after successful submission. |
doe:header-collapsed | localStorage | Remembers whether the Day Of Event header is collapsed. Preference only; no personal data. | Until the preference is changed or browser storage is cleared. |
finalscore.account_deleted_notice | localStorage | Displays a one-time account-deletion confirmation on the login page. No personal data. | Cleared on the next login-page load. |
finalscore.pending_registration.<eventSlug> | sessionStorage | Continues a pending registration process across login. Stores an opaque continuation token and no directly readable personal information. | Until the browser tab is closed or the registration flow is completed. |
finalscore.pending_event_invite | sessionStorage | Continues an event-member invitation across login. Stores an opaque invitation token. | Until the browser tab is closed or the invitation flow is completed. |
finalscore.pending_participant_invite | sessionStorage | Continues a participant invitation across login. Stores an opaque invitation token. | Until the browser tab is closed or the invitation flow is completed. |
The exact Supabase project reference is intentionally omitted from this policy. The authentication key appears in the browser in the general format shown above.
4. Why FinalScore Uses This Storage
- Authentication and security: to keep users signed in, maintain secure sessions and protect access to accounts.
- Workflow continuation: to continue registrations and invitations that the user has chosen to complete.
- Registration drafts: to reduce the risk of losing information entered into an unfinished public registration form.
- Interface preferences: to remember limited display choices, such as sidebar and header state.
FinalScore does not use these items to build advertising profiles, track users across unrelated websites or sell browsing activity.
5. First-Party Storage and Service Providers
5.1 All browser storage listed in this policy is first-party and origin-scoped. It is written or accessed through the FinalScore website or application.
5.2 FinalScore uses Supabase technology to manage authentication. In the current implementation, Supabase Auth persists the session in localStorage and does not set authentication cookies. Authentication tokens are attached to FinalScore server-function requests through an authorization header.
5.3 Other service providers may process information on FinalScore’s behalf on the server side. Their processing is described in the FinalScore Privacy Policy. They are not listed here unless they store or access information in the visitor’s browser.
6. Your Controls
6.1 You can delete cookies, localStorage and sessionStorage through your browser settings. Browser controls vary by browser and device.
6.2 Clearing or blocking FinalScore browser storage may sign you out, remove an unfinished registration draft, interrupt a pending invitation or registration flow, or reset interface preferences.
6.3 FinalScore does not currently offer an in-product cookie preference manager because no optional analytics, advertising or tracking categories are active.
7. Shared Devices and Security
7.1 Authentication session information and registration drafts may contain personal information. If you use a shared or public device, sign out when finished and consider clearing FinalScore browser storage.
7.2 Browser storage is not intended to be permanent document storage. Anyone with access to the same browser profile or device may be able to view an unfinished registration draft.
8. Retention and Deletion
8.1 The retention periods shown in Section 3 describe the current implemented behavior. Items may be removed earlier when a workflow is completed, the user signs out, a token expires, the user changes a preference or browser storage is cleared.
8.2 FinalScore may update technical key names or storage methods as the service develops. Material changes to the purposes, categories or retention periods will be reflected in an updated version of this policy.
9. Future Analytics or Tracking Technologies
FinalScore will review and update this policy before introducing analytics SDKs, advertising pixels, session recording, cross-site tracking or other optional browser-storage technologies. Where applicable law requires prior consent, those technologies will remain disabled until the required consent is obtained.
10. Updates and Contact Information
10.1 FinalScore may update this policy from time to time. The current version will be published on the Website and will take effect on the stated last-updated date.
10.2 For questions about this policy or FinalScore’s browser-storage practices, contact us at contact@finalscore.app.
© 2026 FinalScore. All rights reserved.