Cookie Notice
Essential storage for sign-in, protection, and your saved work.
Effective September 29, 2026
The application has no optional advertising or marketing-cookie category to enable. The notice is informational; dismissing it does not authorize additional tracking.
| Name / storage | Purpose | Duration |
|---|---|---|
| __Host-symlab-access | Authenticated access to the private Studio. Secure, HttpOnly, SameSite=Lax cookie. | Up to 1 hour; renewed during session refresh. |
| __Host-symlab-refresh | Renew the signed-in session. Secure, HttpOnly, SameSite=Lax cookie. | Up to 7 days from the last refresh; cleared from this browser on sign-out. |
| __cf_bm | Cloudflare bot detection and abuse protection. Observed on the public site. | Cloudflare documents 30 minutes of continuous inactivity. |
| cf_clearance, when issued | Remember completion of a Cloudflare security challenge. Not observed on every visit. | Set by the hosting security configuration. |
| symlab-cookie-notice-v1 | Local-storage preference remembering that you dismissed the notice. | Until you clear browser storage or the notice version changes. |
| fatty… / FATTY… local-storage keys | Engineering scenarios, model settings, and locally saved studies. | Until reset in the relevant tool or cleared from browser storage. |
Manage storage
You can inspect, block, or delete cookies and site data in your browser settings. Clearing site data signs you out and may delete locally saved scenarios. Save an first if you need to retain your work.
Infrastructure providers can change security cookies as protection needs change. Their operational traffic collection is separate from the engineering scenario data stored locally. See Cloudflare's cookie documentation and our Privacy Policy.
Contact SymLab
Questions about this page? Contact SymLab support. Requests are saved in the SymLab App project within the SymLab Studio Supabase organization for review by the application owner.