WrengleWrengle

Legal

Cookie and Storage Notice

Wrengle uses a small amount of browser storage for essential account and preference functions. Optional analytics and diagnostics stay off until you explicitly accept them.

Effective 1 August 2026

Essential storage

Essential storage is used because the site cannot provide the relevant function without it. It is not used for advertising.

Provider or keyPurposeDuration
Clerk authentication storageMaintain an optional sign-in session and protect account routesSession or the expiry set by Clerk
wrengle-themeRemember light or dark appearanceUntil cleared
wrengle-sign-up-acknowledgement-v1Avoid repeating the pre-sign-up 18+ notice; Clerk Legal Compliance becomes the durable acceptance record when public registration is enabledUntil cleared or the acknowledgement version changes
__Host-wrengle-legacy-app-cleanup-v1Record that the retired app.wrengle.com origin cleared older PostHog cookies and Web Storage before redirectingOne year on the retired origin
wrengle-telemetry-consent-v1Remember accepted or rejected optional telemetryUntil cleared, withdrawn, or the consent version changes

Optional telemetry

  • PostHog: initialized only after acceptance. It uses memory-only analytics persistence, sends manual allowlisted events, and has autocapture, pageviews, replay, profiles, surveys, experiments, external scripts, and feature flags disabled.
  • Sentry: initialized only after acceptance. Default integrations, breadcrumbs, tracing, replay, logs, PII collection, request data, local variables, and frame context are disabled; remaining error fields are scrubbed before sending.

Production configuration is restricted to these vendors’ EU data regions. No optional vendor request is made before acceptance. The browser keeps PostHog identifiers only in memory for the page session. On first load, before applying your current choice, Wrengle removes legacy PostHog identifiers that older website builds may have stored in cookies, local storage, or session storage. A one-time page on the retired app.wrengle.com origin performs the same local cleanup there before redirecting to wrengle.com; an older HTTP bookmark first upgrades to HTTPS on that same retired host so the secure origin can be cleaned. This cleanup makes no vendor request. Current pseudonymous identifiers are transmitted with accepted events. PostHog also receives the network metadata needed to deliver the request; public deployment is blocked until the production EU project discards IP data and caps analytics retention at no more than 12 months. Sentry does not set an application analytics identifier.

Manage or withdraw your choice

Select “Privacy choices” in the footer at any time. Rejecting or withdrawing leaves optional telemetry off, clears PostHog’s in-memory identity and opts it out, removes any recognized legacy PostHog browser identifiers on load, and closes Sentry. Refusing optional telemetry does not affect downloads, documentation, local desktop features, or accounts.

You can also clear site data in your browser. Doing so signs you out, resets appearance and acknowledgement preferences, and causes Wrengle to ask for a telemetry choice again. Browser “Do Not Track” is respected by PostHog in addition to this explicit consent control.

Contact

For questions about cookies, storage, or privacy, email support@wrengle.com or read the Privacy Notice.