Cookie and Storage Policy

1. What Cookies and Local Storage Are

Cookies are small text files stored in your browser by a website. Modern web apps also use browser storage such as localStorage and sessionStorage. This page explains what OpenThorn stores in your browser and why.

2. Essential Authentication Storage

OpenThorn uses Supabase Auth to keep you signed in and protect account-only pages. Depending on browser and Supabase behavior, session information may be stored in browser storage and related authentication cookies. This storage is necessary for login, logout, account security, and session restoration.

3. Essential App Storage

OpenThorn also uses localStorage for product features that need to survive page reloads on the same browser:

• seen_shared_projects_* - remembers which shared-project notifications you have already seen, so the dashboard does not repeat the same notice after every refresh.
• github_repo_* - stores per-project GitHub repository owner, repository name, and auto-sync preference for the browser you are using.
• openthorn.memory.* - stores local user-memory entries such as inferred design preferences, recurring fixes, and useful facts across projects.
• Preview storage polyfills - generated project previews may use in-memory replacements for localStorage or sessionStorage when sandboxed previews cannot access normal browser storage.

4. Cookieless Analytics and Performance Monitoring

OpenThorn uses Vercel Web Analytics to count anonymous page views and Vercel Speed Insights to measure anonymous web performance metrics (such as page load and responsiveness timings). Both services are cookieless: they do not set cookies, do not store identifiers in localStorage or sessionStorage, and do not track you across sites or sessions. Because nothing is stored on your device for analytics or performance-measurement purposes, this does not require cookie consent under the ePrivacy rules. See the Privacy Policy for details on how this data is processed.

5. Consent Banner

OpenThorn does not use analytics cookies, advertising cookies, retargeting pixels, or third-party social media tracking pixels. Because the current browser storage is used for authentication, security, and requested app functionality — and our analytics stores nothing on your device — we do not show a cookie consent banner. If we add non-essential cookies or tracking, we will update this page and request consent where required.

6. External Resource Requests

OpenThorn's fonts are self-hosted and served from our own infrastructure — no font requests are made to Google or other third parties. Generated project previews may load runtime packages, type definitions, or WebAssembly resources from third-party CDNs. These requests are not used by OpenThorn for advertising or behavioural tracking, but the third-party provider may receive technical request data such as your IP address, browser information, requested URL, referrer, and request time.

We describe these providers and data flows in the Privacy Policy. If we add analytics, profiling, advertising, or other non-essential tracking, we will update this notice and request consent where required.

7. How to Control Storage

You can clear cookies and localStorage through your browser settings. Clearing storage may sign you out, remove local preferences, reset notification state, and disconnect browser-local GitHub repository settings. Server-side account, project, provider-key, integration, collaboration, and community records are handled as described in the Privacy Policy.

8. What We Do Not Use

• No analytics or tracking cookies (our analytics is cookieless).
• No advertising or retargeting cookies.
• No third-party social media tracking pixels.
• No data shared with or sold to data brokers.

9. Contact

For questions about our use of cookies or local storage, contact us at btalabs.contact@gmail.com.