LoomCreditEvidence to capitalRecorded testnet
Legal and privacy

Cookie notice

What the current prototype stores in browser cookies and what may be controlled by wallet or hosting providers.

Prototype notice

This page describes the current testnet prototype. It is not a final legal agreement or legal advice.

Operator
LoomCredit prototype
Effective date
Pending publication
Public address
Pending publication
Governing law
Pending publication

1. Current first-party cookies

The current web app uses one essential first-party cookie,loomcredit_session, only after wallet sign-in. It is an opaque session token, marked HttpOnly, scoped to the site, and expired or cleared when the session ends. The server stores only a hash of the token. It is required to keep a verified wallet session and is not an advertising or analytics cookie. Optional PostHog analytics is not initialized by default. If the operator enables it and a visitor opts in, the app stores the choice in loomcredit_analytics_consent in local storage. The PostHog SDK uses in-memory persistence and does not set an analytics cookie.

2. What the current app does not use

  • No first-party advertising cookies.
  • No PostHog analytics is initialized unless optional analytics is enabled and the visitor explicitly opts in.
  • The optional analytics path disables autocapture, automatic pageviews, session replay, person profiles, and browser persistence.
  • No local-storage copy of the server session token is created by the app.
  • The deterministic local demo does not need a cookie, model request, wallet transaction, or blockchain call.

Hosting, CDN, security, embedded wallet, explorer, or other third- party services may use their own cookies or similar technologies. Their terms and privacy notices control those technologies. The operator must review consent, retention, vendor terms, and target jurisdictions before enabling optional analytics or adding marketing, experimentation, chat, ads, or other non-essential tracking.

3. Managing cookies

You can clear or block cookies through your browser settings. Blocking the essential session cookie may prevent wallet sign-in from working, but the public product pages and local demo remain available. Signing out revokes the server session and clears the browser cookie.

4. Release requirement

This notice describes the current repository code, not every cookie a future deployment or vendor may set. Before a public release, inventory response headers and third-party scripts in the deployed environment, decide whether consent is required in target markets, and document retention, vendor roles, and withdrawal controls.