Cookie Policy

1. Purpose and scope

This Cookie Policy explains how the official SqueHub website and SqueHub-operated services use cookies and similar device-storage technologies. It should be read with the Privacy Policy.

An independently operated application built with the open-source SqueHub framework controls its own cookies and storage. Its operator must provide its own notice and consent controls. The presence of SqueHub software does not make that deployment part of the official SqueHub website.

2. What these technologies are

A cookie is a small value a website asks a browser to store and return with later requests. A cookie may last for one browser session or until a stated expiry. Local storage is browser storage available to scripts on the same origin; unlike a cookie, it is not automatically sent with each HTTP request.

Similar technologies can include pixels, software development kits, cached identifiers, and other mechanisms that store information on or read information from a device. This policy uses device storage to refer to these technologies collectively.

3. Technologies currently used

The current official website uses a small, first-party set:

Name or category	Technology	Purpose	Typical duration
squehub_session	First-party cookie	Maintains a requested session, protects forms against cross-site request forgery, supports flash messages, and authenticates authorized editorial activity.	Up to the configured session lifetime—currently 120 minutes by default—or until the browser session ends where configured. Server-side session data can expire separately.
squehub-docs-theme	Local storage	Remembers whether documentation should use the light, dark, or system appearance.	Remains until the preference is changed or browser site data is cleared.
squehub-editorial-theme	Local storage	Remembers the appearance selected by an authorized editorial user.	Remains until changed or browser site data is cleared. It is relevant only to the private editorial interface.
Security and infrastructure state	Server-side records and, where necessary, first-party identifiers	Rate limiting, abuse prevention, request integrity, availability, diagnostics, and incident response.	Bounded according to operational and security need; this state is not used for cross-site advertising.

Configuration may change the session-cookie name, secure transport flag, domain, path, SameSite policy, or lifetime for a particular SqueHub-operated service. Where a service materially differs from this public website, it should provide a service-specific notice.

4. Strictly necessary use

The session and security technologies above are used only when needed to provide a requested feature or protect the service. Examples include:

• preserving a secure server-side session;
• generating and validating CSRF tokens for forms;
• authenticating and authorizing an editorial user;
• remembering a one-time success or validation message;
• enforcing request limits and detecting abusive traffic; and
• maintaining application and infrastructure integrity.

Where applicable law exempts storage that is strictly necessary to provide a user-requested service or secure it, SqueHub relies on that exemption. Blocking this storage can prevent sign-in, forms, administrative tools, and other session-dependent features from working.

5. Preference storage

Theme preferences improve presentation but are not used to identify a person across unrelated websites. The documentation preference and private-editor preference stay in the browser on the SqueHub origin. They are not automatically transmitted with web requests and do not contain a name, email address, account ID, or advertising profile.

You can remove these values through the appearance control where available or by clearing local storage for the site. If no value exists, the interface uses its default or the device's color-scheme preference.

6. Analytics, advertising, and third-party cookies

The current public website does not use third-party advertising cookies, retargeting pixels, cross-site behavioral advertising, or analytics cookies that require optional consent. It does not load social-network tracking merely because a LinkedIn, X, Discord, GitHub, or other external link is displayed.

If you follow an external link, the destination service may set its own cookies under its own policy. SqueHub does not control storage placed after you leave the official site.

If SqueHub later introduces non-essential analytics, embedded media, advertising, experimentation, or similar technology, it will review the legal basis, update this policy, identify the providers and duration, and provide a consent choice before enabling it where required. Continuing to browse will not be treated as consent where an affirmative choice is required.

7. Consent choices

Strictly necessary storage cannot ordinarily be disabled through a consent panel because the requested secure feature cannot operate without it. Optional storage, if introduced, will be off until the required consent is obtained and will be as easy to reject as to accept.

Where consent applies, you may withdraw it for future storage through the provided preference control. Withdrawal does not make earlier consent-based processing unlawful. Some previously stored values may remain until removed or expired, but they will no longer be used for the withdrawn optional purpose.

8. Browser and device controls

Most browsers allow you to inspect, block, or delete cookies and site data. You can usually:

• delete all information stored for squehub.com;
• block cookies entirely or only in private browsing;
• block third-party cookies;
• clear local storage;
• configure automatic deletion when the browser closes; or
• use separate browser profiles for different activities.

Browser controls vary by product and version. Blocking first-party cookies may disable session-backed forms and authorized account features. Clearing storage signs sessions out and resets appearance preferences.

9. Server logs are different

Removing cookies or local storage does not erase server logs, submitted forms, account records, or other information already received by SqueHub. Those records are governed by the Privacy Policy and applicable retention duties. A privacy request can be submitted separately where a legal right applies.

10. Review and changes

We review this policy when browser storage, site functionality, or legal requirements change. The public page shows the last-updated date. A service-specific interface may provide additional just-in-time information if it introduces storage not described here.

11. Contact

Questions about cookies or device storage may be sent to hello@squehub.com with the subject Cookie question. Include the page, browser, and storage name involved, but do not include session values, cookies, passwords, or access tokens.