Cookies and browser storage

1. Current storage choice

Notice and inventory version: 2026-07-28.2.

2. Public pages and Firebase Hosting

The landing, privacy, terms, cookies, support, unsubscribe, account-deletion, and not-found pages are static. They do not set first-party cookies or use sessionStorage, IndexedDB, Cache Storage, or a service worker. The language selector writes one localStorage item named color-hunter.locale only after you explicitly select a language; the website does not force a redirect from browser language. The pages do not load pixels or analytics, advertising, experimentation, or social-media SDKs.

Firebase Hosting delivers these files. Like most hosting services, it receives request data such as IP address, user agent, requested path, time, and technical diagnostics. Google states that Firebase Hosting retains IP data for a few months. This processing occurs on Google infrastructure and is used to deliver, secure, and operate the requested website; it is not an advertising or audience-measurement feature configured by Color Hunter.

3. Account-deletion browser state

• Public Firebase configuration: the account-deletion page requests /__/firebase/init.json from colorhunter.app. It contains public project and application identifiers, is not a cookie, and is kept only as page memory.
• Firebase Authentication state: after you choose Google sign-in, the Firebase user and credentials needed to complete deletion are held only in JavaScript memory. Color Hunter configures in-memory persistence, so the state is cleared on reload, sign-out, identity deletion, or tab closure and is not written to first-party localStorage, sessionStorage, or IndexedDB.
• Deletion-complete fragment: after successful deletion, the page uses #deletion-complete in the address. It is a non-sensitive completion flag, contains no account identifier or token, and may remain in the current URL and browser history until you navigate away, replace it, or clear that history.

These technologies are used only to provide the authentication and deletion steps you request. Blocking first-party persistent storage does not remove the public instructions or the in-memory deletion design.

4. Google sign-in and provider cookies

Google sign-in starts only after you select “Sign in with Google” or “Verify with Google.” It opens a Google-controlled popup and may use cookies already present on, or set by, Google domains to authenticate the Google Account and protect against fraud and abuse. Color Hunter cannot read those Google-domain cookies.

Google identifies SID and HSID as examples of authentication and security cookies. Google states that they contain encrypted and signed records of a Google Account identifier and recent sign-in time and can last for up to two years. Other provider cookies, domains, and expiry periods can vary with your Google session, settings, and Google’s current service configuration.

Firebase Authentication may receive the Firebase user identifier, email address, display name, optional profile image URL, ID-token data, IP address, user agent, and authentication diagnostics. Google states that Authentication runs from United States data centers, retains logged IP addresses for a few weeks, and retains other authentication information until the customer deletes the user, after which removal from live and backup systems may take up to 180 days.

5. Your choices

• There are no analytics, advertising, or tracking categories to accept, reject, manage, or withdraw from on the current website. Not selecting or storing a language has no effect on core content or account-deletion instructions.
• Selecting English, Română, Русский, or Español writes only the selected locale code to color-hunter.locale. You can remove it by clearing this site’s browser storage, and every language remains directly available through its URL.
• Google authentication requests occur only after you actively choose the sign-in or verification control. If you do not choose it, you can still read the deletion instructions and contact support for the manual deletion route.
• You can close or reload the deletion page to clear Color Hunter’s in-memory Firebase session. You can also use Google Account and browser controls to manage Google-domain cookies, although doing so can require you to sign in to Google again.
• If Color Hunter introduces optional technology, it must be blocked until any legally required consent is obtained. This notice, the versioned inventory, and the website controls must be updated before that technology is released.

6. Providers, destinations, and transfers

SRL Filosoft Company uses Firebase Hosting, Firebase Authentication, and Google sign-in. Website files and hosting request data are processed on Google’s global infrastructure. Firebase Authentication is processed in the United States. The safeguards and contracting roles that apply to international processing are described in the Privacy Policy and must be confirmed for the countries where the service is offered.

• Color Hunter Privacy Policy
• Firebase privacy and security information
• Firebase authentication persistence documentation
• How Google uses cookies
• Google Privacy Policy

7. Changes to this notice

We review the storage inventory when website routes, providers, purposes, or technology change. We will update the notice version and last-updated date before a material change. If a future change requires consent, optional technology will remain off until the visitor makes a clear choice, and a persistent settings control will allow that choice to be changed or withdrawn.

8. Controller and contact

SRL Filosoft Company is responsible for the Color Hunter website. Contact us with questions about cookies, browser storage, providers, or privacy: