These pages describe the current Oplut website, account surfaces, CLI/runtime, device evidence sync, catalog, and planned product direction reflected in the public codebase.
How Oplut uses cookies
Oplut uses cookies and similar browser storage to keep the public site, account sessions, authentication, device approval, billing redirects, and dashboard surfaces working. Cookies are not how Oplut collects hardware baseline evidence.
Essential cookies
Authentication cookies keep you signed in and help Better Auth connect browser sessions to your Oplut account.
Security cookies and session identifiers help protect account actions, password reset flows, device approval pages, and API-adjacent account surfaces.
Device approval flows may use browser session state while you approve a CLI/runtime device code from the web app.
Local storage and browser state
The web app may use local storage or similar browser state for interface preferences, in-progress flows, cached client state, and session support. The CLI/runtime stores local hardware evidence on the device filesystem, not in browser cookies.
Billing and external redirects
When you start checkout or manage a subscription, Stripe may set its own cookies or use browser storage to process payment, prevent fraud, and manage the billing portal. Oplut stores only the Stripe customer and subscription identifiers needed by the app.
Analytics
Oplut may use limited first-party analytics to understand which pages, docs, catalog entries, setup paths, and account flows are useful. Analytics should be used to improve product clarity and reliability, not to collect raw hardware evidence.
OAuth and email providers
If you sign in with Google or GitHub, those providers may use their own cookies during authentication. Email links, such as password resets, may include tokens or parameters needed to complete the requested action.
What cookies do not do
Cookies do not collect raw camera frames, video, audio, full sensor logs, calibration image sets, or private project files.
Device evidence sync happens through explicit CLI, SDK, API, upload, setup, baseline, check, health, or artifact workflows.
Clearing browser cookies does not delete local CLI evidence files on a device or records already synced to your Oplut account.
Your choices
You can block or clear cookies in your browser, but essential account, device approval, dashboard, and billing flows may stop working. To remove synced device evidence, use product deletion/revocation controls where available or contact hello@oplut.com.
In plain language: cookies keep the account and website working. They are not the baseline engine, the hardware scanner, or the raw artifact uploader.