Cookie policy

Describe the browser and device, the page or action involved, and what happened after you signed in, changed a preference or returned from checkout. Mention whether you recently cleared site data or changed cookie settings. You can report the visible message without copying cookie values, authentication tokens or private key contents. The name of a setting is usually more useful than its secret value. Explain whether the problem occurs only in one browser so the team can distinguish local behavior from the workspace's server-side state. Do not assume that resetting all site data is necessary before the issue has been understood.

Use the appropriate account for your workspace, keep credentials out of ordinary browser notes or shared messages, and sign out when your work is complete. Browser storage and external provider sessions have their own controls, so leaving a page or closing one tab should not be treated as a universal sign-out from every service you visited. Review the browser's site-data options when you intend to remove local information. Clearing that information can reset preferences and interrupt sessions, but it does not replace workspace membership management, provider-key revocation or the account and data processes described in the other policies.

The sections above identify the purposes of authentication storage, the temporary billing-intent cookie, the active-workspace cookie and local preferences. Read the section that matches the action you are investigating rather than treating every stored value as interchangeable. The browser can show site storage, while Spek's policy supplies the product context for its use. Exact browser controls can differ by device and version. If the observed behavior appears inconsistent with this description, contact the team with the task and browser context, keeping secret values out of the report so the discrepancy can be checked without exposing account access.

Clearing site cookies or local storage removes information held by that browser. It can end a session or reset a local preference, but it does not itself delete the account, workspace or server-side records described in the Privacy policy. Account and data requests follow their own product and policy processes. If your goal is simply to troubleshoot a browser issue, first note which workspace and task you were using so you can return to the right context after signing in again.

Authentication storage helps the service maintain a session and complete supported sign-in callbacks. Blocking or removing that essential storage can interrupt the requested flow, even when the account itself remains valid. Review the browser's settings for this site and the behavior described in this policy. A sign-in problem does not require sending a password or private key to support. Describe the browser, the step that failed and the visible message while keeping authentication secrets out of the report.

The active-workspace cookie remembers which workspace an authenticated user selected. It does not contain a store private key and it does not replace the membership checks required to use that workspace. This is why remembering a workspace and having permission to operate in it are different concepts. If you belong to more than one team, check the selected workspace before editing drafts or reviewing billing. Clearing browser data can lose the selection without deleting the workspace itself.

The billing-intent cookie described in this policy carries temporary checkout context rather than a card number or payment secret. Payment-card entry happens in the supported Stripe-hosted flow. Deleting or blocking the cookie can interrupt a checkout that you requested, but it should not be used as evidence that a charge succeeded, failed or was canceled. Check the actual payment and workspace billing state for that outcome, and keep full card details and authentication information out of support messages.

Local storage belongs to the browser and device that holds it. A preference stored there should not be assumed to update every other browser you use. The policy distinguishes browser storage from account and server-side data for this reason. Use the relevant preference controls on the device you are using and review the browser's own site-data controls if you want to remove local values. A change to local settings does not independently revoke a connected store credential or alter a workspace subscription.

The destination provider controls storage under its own domain according to its policies and controls. A link from Spek to a store console, payment provider or another service does not make that provider's browser storage part of Spek's own settings. Review the destination's policy and the browser controls for that site when managing it. This policy explains Spek's use of browser storage; the Privacy policy and the relevant provider documentation supply the separate context for personal-data handling and third-party services.