Guest conversations
Guest history belongs to a browser-session identity with a configured expiry. Losing its cookie can make the history inaccessible earlier. Cleanup of expired data is bounded and may occur during later activity.
Choose how catalog prices and estimates appear. Checkout and account records remain in IDR.
GALACTRE / COOKIES, CONSENT & SESSIONS
Learn what keeps chat and sign-in working, how browser storage differs from server records, and whether Galactre may remember your chat appearance.
01 / YOUR CHOICE ON THIS BROWSER
The controls apply to this Galactre origin and browser. They do not change account permissions or another service’s cookies.
Required for browser identity, request protection and session-dependent functions. Manage browser cookies if you want to block them, understanding that those functions may fail.
Allow local storage of light/dark chat preference. Disabled by default; changing appearance still works for the current page.
No optional analytics or advertising integration is configured by the current Galactre public page scripts. These controls do not enable one.
02 / WHAT IS STORED AND WHY
This inventory describes the current application behavior. Cookie lifetimes and third-party controls must also be checked in the actual deployment.
03 / WHAT A SESSION DOES
A restored browser tab or cookie does not make a server session permanent. Expiry and authorization remain independent checks.
Guest history belongs to a browser-session identity with a configured expiry. Losing its cookie can make the history inaccessible earlier. Cleanup of expired data is bounded and may occur during later activity.
Account identity is verified through IAM Central and current access checks. Remembered-device/PIN behavior belongs to the identity flow, not this preference choice. Guest history does not automatically migrate.
Signing out ends the applicable account access flow. Clearing cookies removes browser state. Neither action by itself promises deletion of stored conversations, invoices or operational records.
Cookies are scoped by host/path, not port. Local projects use distinct session names; local storage is scoped by origin, including port. Do not treat a shared localhost host as a production isolation guarantee.
04 / CHOOSE THE RIGHT CONTROL
Save a new choice above. Disabling preferences removes the saved chat theme. Reset removes the choice too. No server record is deleted.
Use the account sign-out and identity-service device controls. This page does not inspect or revoke your credentials.
Account access guideUse the owned conversation deletion controls. Clearing site data may lose your guest access before you can delete its history.
History and deletion guidance05 / COOKIE AND SESSION QUESTIONS
No. A model version is a product selector, not an authentication credential. Guest and account sessions, CSRF protection, remembered devices and session revocation keep their existing responsibilities regardless of the selected GT release.
Session-dependent functions require essential browser session state. You can block cookies in the browser, but chat, account access and request protection may stop working. Optional theme storage can remain disabled.
No. No optional analytics or advertising integration is configured by the Galactre public page scripts in this release. The preference below controls saved chat appearance only. It does not load a tracker.
The appearance changes for the current page. It is not saved for a later visit. Allow preference storage here if you want the selected theme to persist.
No. Reset removes this local consent choice and saved chat theme. It does not revoke a server session, log you out of IAM Central, remove a remembered device or delete server-side conversation/payment records.
A cookie is only a reference. The server session, guest expiry, account authorization or identity credential can still expire or be revoked. Browser session restoration does not override server checks.
No. The session is configured HttpOnly with a valid SameSite policy; Secure follows the detected HTTPS request. Plain HTTP local development does not provide HTTPS transport protection. Deployment settings and proxy trust must be verified for production.
READ THE RELATED POLICIES
Galactre Studio