Cookie and Local Storage Policy

The Service is operated by GPT LLM ORAGLE Ltd. Liability Co., a Wyoming close limited liability company, registered office 30 N Gould St, Ste N, Sheridan, WY 82801, United States. Questions: privacy@oraglegpt.org.

1. Scope

This page covers cookies, browser local storage, session storage, the installable Progressive Web App, and its service worker cache on oraglegpt.org.

It complements Privacy Policy, which explains what we do with personal data generally.

2. What we use, exactly

Name	Type	Purpose	Set by	Expiry
`orbitpost_session`	First-party HTTP cookie	Carries the opaque session token that authenticates you after sign-in. `HttpOnly`, `SameSite=Lax`, `Secure` on any HTTPS deployment, `Path=/`. Cleared on sign-out with `Max-Age=-1`.	The Service	The session's absolute expiry; also subject to an idle-timeout on the server side
Reverse-proxy TLS and routing state	First-party	Terminates HTTPS and routes the request. No behavioural data.	Caddy reverse proxy	Request-scoped

These are required for the Service to function. Blocking them prevents sign-in. Under the EU ePrivacy Directive and equivalent rules they fall within the strictly necessary exemption, so they are not subject to consent.

2.2 Functional - local storage, not cookies

The web application is an installable PWA. It uses browser storage rather than cookies for interface state:

Key area	Storage	Purpose	Lifetime
Active route	URL fragment (`#/…`)	The application uses hash-based routing, so the current screen is in the URL fragment. The fragment is never sent to the server.	Navigation-scoped
Interface preferences (theme, density, last-used workspace, column layouts)	`localStorage`	Remembers your interface choices between visits	Until you clear site data
Draft autosave buffers	`localStorage`	Prevents loss of an in-progress composer draft	Until submitted or cleared
Offline application shell	Service worker Cache Storage (`sw.js`)	Lets the installed PWA load its interface without a network connection	Until the service worker updates or you clear site data

None of this is used for tracking, none of it is shared, and none of it is readable by another site.

2.3 Analytics and performance

Status: none deployed by default in release 3.4.0-fullpower.1.

The Service is self-hostable and ships with no third-party analytics tag. If the operator later enables product analytics or error monitoring, it will be:

listed here with the vendor name, cookie or storage keys, purpose, and retention;
added to Subprocessors;
gated behind consent where the law requires consent.

No product analytics vendor and no error-monitoring vendor is engaged in the current release. The frontend ships with no analytics tag, no session recorder, and no third-party script of any kind. If that changes, the vendor will be named here and added to Subprocessors before it is enabled, and consent will be collected where the law requires it.

2.4 Advertising and cross-site tracking

None. We do not set advertising cookies, we do not embed advertising pixels, we do not participate in real-time bidding, and we do not share identifiers for cross-context behavioural advertising. This is a deliberate product decision and is also required by the platform developer terms we operate under.

2.5 Third-party content

Some screens link out to social platforms so you can complete an OAuth authorisation or view a published post. When you follow such a link, that platform sets its own cookies under its own policy. We do not control them.

Where the interface shows a preview of a post, the preview is rendered from our own stored copy of the content and media. No third-party embed script is loaded, so no platform cookie is set by a preview. If we ever introduce a live platform embed, this page will be updated and consent handling will cover it before the embed ships.

Because the current default configuration sets only strictly necessary cookies and uses local storage for functional purposes only, no consent banner is required for that configuration.

A consent mechanism becomes mandatory as soon as the operator enables analytics, error monitoring that persists an identifier, or any third-party embed that sets storage. In that case the operator must:

present a consent notice before any non-essential storage is written;
make refusing as easy as accepting;
record consent, with a timestamp and the version of this policy shown;
re-ask when the purposes change;
expose a persistent "Cookie settings" control so consent can be withdrawn;
keep the Service fully usable when consent is refused.

No consent banner ships in the current release, because no non-essential storage is written. Showing a consent banner for strictly necessary storage would be misleading. If we introduce non-essential storage, a consent mechanism meeting the six requirements above will be deployed before that storage is enabled, not after.

4. How to control storage

In the Service. Signing out clears the session cookie. "Cookie settings", once a consent mechanism exists, will let you withdraw consent.
In your browser. Every major browser lets you block or delete cookies and clear site data for a single origin. Clearing site data for oraglegpt.org removes local storage, session storage, and the PWA cache, and signs you out.
Uninstalling the PWA. Removing the installed app removes its cache.
Do Not Track and Global Privacy Control. We set no advertising or cross-site tracking storage, so there is nothing for a GPC signal to switch off. We honour GPC as an opt-out of sale or sharing under US state privacy laws, which we do not do in any case.

Blocking the strictly necessary session cookie will stop you from signing in.

5. Changes

We update this page whenever the storage the Service uses changes. The "Last updated" date at the top reflects the current version. Material changes are announced in-product to workspace administrators.

6. Contact

GPT LLM ORAGLE Ltd. Liability Co.
30 N Gould St, Ste N
Sheridan, WY 82801
United States

privacy@oraglegpt.org