Cookie Policy
This Cookie Policy explains how Geostrategy International Unlimited and Geostrategy LLC (“we”, “us”, “our”) use cookies and similar technologies on www.geostrategy.com (the “Site”). It should be read together with our Privacy Policy.
1. What cookies are
Cookies are small text files stored on your device when you visit a website. Similar technologies may also store information on your device; this Policy explains the technologies used by the current Site.
2. Categories of cookies we use
| Category | Purpose | Requires consent? | Retention |
|---|---|---|---|
| Necessary | Site functionality, secure client sign-in, security and recording your cookie-consent choice | No, where strictly necessary | Consent cookie: six months. Other necessary cookies: provider-managed |
| Analytics | First-party measurement of visits and usage | Yes, off by default | Visitor cookie: 390 days maximum; session: 30 minutes of inactivity |
| Marketing/Enhanced | Attach the verified signed-in Clerk account ID to analytics only when Analytics is also enabled | Separate consent, off by default | No separate cookie; linked analytics retained for up to 14 months |
Cookie and browser-storage inventory
Necessary items support consent, authentication and requested functionality. Analytics items require opt-in. Clerk manages authentication cookies and their deployment-specific lifetimes; its client may initialise on public pages even before sign-in.
| Cookie | Provider | Purpose | Domain/scope | Retention | Security attributes | Category |
|---|---|---|---|---|---|---|
GAESA, where present | Hosting provider / Google App Engine | Session affinity for load balancing and request routing | Hosting, not app-controlled | Up to 30 days | Provider-managed | Strictly necessary |
gs_visitor | Geostrategy, first-party | Random returning-visitor UUID | Site host | 390 days maximum from creation; removed on withdrawal | SameSite=Lax; Secure over HTTPS | Analytics |
gs_session | Geostrategy, first-party | Random session ID and last activity timestamp | Site host | 30 minutes of inactivity, renewed on activity; removed on withdrawal | SameSite=Lax; Secure over HTTPS | Analytics |
gs_consent_outbox (localStorage) | Geostrategy, first-party | Retries unsent consent audit choices | Site origin | Removed after successful delivery; expired or obsolete-version entries discarded on next processing. Storage has no native expiry. | Browser origin isolation | Necessary |
geostrategy-registration-profile (sessionStorage) | Geostrategy, first-party | Preserves the submitted registration profile during account creation | Site tab | Removed after successful completion or when the browser tab session ends | Browser origin isolation | Necessary |
geostrategy:react-runtime-recovery (sessionStorage) | Geostrategy, first-party | Limits automatic recovery reloads after a runtime error | Site tab | Browser tab session | Browser origin isolation | Necessary |
gs_consent | Geostrategy | Stores categories, policy version, timestamp and a random anonymous consent ID | Site host; first-party | Six months | SameSite=Lax; Secure when served over HTTPS; readable by the Site | Necessary |
__session, __session_* | Clerk | Short-lived session JWT used to validate requests in the Site or API; a suffixed variant may be used for the active Clerk instance | Clerk authentication domain; Site host when Clerk is proxied through the Site | Short-lived and renewed while the session is active | Secure in production; SameSite and HttpOnly are Clerk-managed | Strictly necessary |
__client_uat, __client_uat_* | Clerk | Helps Clerk determine whether the client session is still valid; a suffixed variant may be used for the active Clerk instance | Clerk authentication domain; Site host when Clerk is proxied through the Site | Clerk-managed session lifetime | Secure in production; SameSite and HttpOnly are Clerk-managed | Strictly necessary |
__client | Clerk | Long-lived HttpOnly cookie used to issue short-lived session JWTs | Clerk Frontend API/authentication domain; Site host when Clerk is proxied through the Site | Clerk-managed session lifetime | HttpOnly; Secure in production; SameSite is Clerk-managed | Strictly necessary where emitted |
__clerk_db_jwt | Clerk | Synchronises a development browser session between the development instance, Clerk Frontend API and account portal | Development Clerk/account domains and localhost; not a production Site cookie | Development session; Clerk-managed | Development only; attributes are Clerk-managed | Strictly necessary in development only |
__clerk_* | Clerk | Transient authentication handshake and security state | Clerk authentication domain; Site host when Clerk is proxied through the Site | Short-lived | Secure in production; SameSite and HttpOnly are Clerk-managed | Strictly necessary where emitted |
clerk_active_context | Clerk | Keeps the active authentication context consistent in the browser | Site host | Browser session | Secure in production; SameSite=Lax; readable by Clerk on the Site | Strictly necessary where emitted |
__cf_* / _cfuvid | Cloudflare | Infrastructure security and abuse prevention | Cloudflare or hosting domain | Provider-managed session or short-lived lifetime | Provider-managed | Strictly necessary where present |
The cookie-preferences panel, available through “Cookie settings” in the footer, lists necessary cookies. Saving a choice sets gs_consent for six months. A changed consent-policy version requires a new choice. Optional categories are off by default and may be withdrawn at any time. Clerk authentication cookies are independent of optional consent categories.
Consent choices and withdrawals are recorded for two years, with a random anonymous consent ID, categories, policy version, action, server timestamp and a truncated user-agent string. These records contain no IP address or signed-in account identifier. The necessary gs_consent_outbox local-storage entry retries unsent consent records; sent records are removed, and invalid or six-month-old entries are discarded when the outbox is next processed. localStorage does not itself expire.
Our hosting provider sets GAESA for Google App Engine session affinity, load balancing and request routing. This strictly necessary cookie lasts up to 30 days and is managed by the hosting provider, not the application.
3. Consent
The first time you visit the Site you will see a cookie banner. You can:
- Accept all — record consent for all categories;
- Reject non-essential — record consent only for strictly necessary cookies;
- Manage preferences — choose which optional categories to allow.
You can change or withdraw your choices at any time via “Cookie settings” in the footer. Save choices, Accept all and Reject all are available in the preferences centre. Nothing non-essential implemented by this application runs or sets analytics cookies before opt-in. Rejecting or withdrawing Analytics stops its tracker and deletes gs_visitor and gs_session; withdrawing Marketing/Enhanced stops subsequent account linkage. Necessary items remain. Existing server records follow the Privacy Policy retention periods.
No advertising-network tracking is implemented. The legacy geostrategy_cookie_consent cookie is deleted when a new consent choice is saved, not used as a tracking identifier. Infrastructure cookies are conditional, not guaranteed on every visit: GAESA is hosting-managed, its duration is not controlled by this application, and it is not evidence of consent. The reusable sidebar component contains a sidebar_state cookie setter but is not mounted by the current app, so it is not an active site cookie. Clerk testing cookies are test instrumentation, not production analytics.
4. Managing cookies in your browser
Most browsers let you refuse or delete cookies through their settings. Disabling strictly necessary cookies may cause parts of the Site to malfunction. Guidance for the major browsers:
- Chrome
- Safari
- Firefox
- Edge
5. Do Not Track
Because there is no consistent industry or legal standard for interpreting Do Not Track signals, we do not currently respond to them. You can control our use of non-essential cookies through the cookie banner instead.
6. Changes
We may update this Cookie Policy to reflect changes in the cookies we use or in applicable law. The “Last updated” date shows when it was most recently revised.
7. Contact
Questions about this Policy: hq@geostrategy.com.