1const e=`--- 2title: Cookies, browser storage and tracking 3section: Your browser 4order: 75 5summary: Every cookie and browser-storage key Vera and the Summit Outfitters demo site set, what each is for, how long it lives and how to clear it. No advertising or cross-site tracking technologies, no sale or sharing of personal information, fonts served from Vera's own address, and your browser's Global Privacy Control signal honored. 6updated: 2026-10-01 7--- 8 9> **The short version.** Vera sets a handful of first-party cookies that are strictly necessary to sign you in and keep you signed in, plus a few browser-storage keys that remember choices you made (appearance, panel widths, dismissed tips). There are no advertising cookies, no analytics cookies, no beacons or pixels and no cross-site tracking. Vera does not sell or share personal information, and a browser that sends the Global Privacy Control signal is honored. Because nothing optional from a third party is set, there is no consent banner to click through â there is nothing to consent to. 10 11## What is and is not set 12 13Everything in the table below is set by Vera itself on Vera's own address (first-party). Signed out, a page from Vera or from the Summit Outfitters demo site makes requests only to that address: the fonts, scripts and stylesheets are served from Vera's build, not fetched from Google Fonts or a content-delivery network. Vera does not train AI models on your data, and no cookie or storage key described here is used to build a profile of you or to follow you to other sites. 14 15Three things Vera does **not** have: 16 17- **Advertising or cross-site tracking technologies.** No ad networks, no tracking pixels, no beacons, no third-party analytics script, no fingerprinting. The build is checked by an automated test that fails if a third-party script, stylesheet or font host, or an undeclared cookie or storage write, is introduced. The public marketing sites do record each visit on the server, from the request itself (IP address, approximate location, device class, browser and operating-system family, referrer, campaign parameters) â without a cookie or script; [What the public websites collect](/privacy/public-website) describes that record and how long it is kept. 18- **A sale or share of personal information.** Vera does not sell personal information and does not share it for cross-context behavioral advertising, in the sense those terms carry under the California Consumer Privacy Act and the other US state privacy laws. 19- **A consent banner.** The ePrivacy rules and the state laws require consent (or an opt-out) for c
19ookies that are not strictly necessary and for tracking that crosses sites. Vera sets neither, so it asks for neither. If that ever changed, this article, the [Privacy Notice](/legal/privacy) and the subprocessor annex of the [Data Processing Addendum](/legal/dpa) would change first. 20 21## Global Privacy Control 22 23[Global Privacy Control](https://globalprivacycontrol.org/) (GPC) is a browser setting that tells every site you visit that you opt out of the sale or sharing of your personal information. Vera reads the signal in two places â the \`Sec-GPC\` request header on the server and \`navigator.globalPrivacyControl\` in the page â and treats it as a valid opt-out request. Because Vera does not sell or share personal information and loads no optional analytics or advertising technology, honoring the signal changes nothing you would see; it is honored all the same, and the status box on this page shows whether your browser is sending it right now. 24 25GPC does not switch off the strictly-necessary cookies (you could not sign in without them) and does not switch off the usage reporting a workspace runs for itself; that reporting is first-party, processed for your workspace under the Data Processing Addendum, and is controlled by your workspace's administrators, who can turn per-person detail off entirely. See [Who at Vera can see your data](/privacy/who-can-access) for how those switches work. 26 27## The table 28 29The table below is generated from the same catalog the application is built against, so it cannot drift from the code without failing the build. Names in angle brackets are variable parts (a user id, a workspace slug). Keys marked \`:t:<workspace>\` carry a workspace suffix when the page is inside a workspace path, so two workspaces on the same address never read each other's preferences. 30 31Categories: 32 33- **Strictly necessary** â the service cannot be provided without it: the session, the sign-in handshake, a security marker, or a choice you just made on this page. 34- **Functional** â a convenience you can live without, such as a panel width or a dismissed hint. Nothing in this category leaves your browser. 35 36## Third-party frames 37 38One kind of third-party content can appear inside Vera, and only when a person opens it: a lesson or chat message that embeds a YouTube video. Those videos load through YouTube's privacy-enhanced address (\`www.youtube-nocookie.com\`), which sets no cookie until you press play. Pressing play is a visit to YouTube under Google's privacy policy. Nothing on a signed-out page, and nothing at start-up, loads a third-party frame. 39 40## How to clear everything 41 42- **Cookies** â sign out (Vera removes the session cookie) or delete cookies for this site in your browser settings. 43- **Browser storage** â use your browser's "clear site data" for this site. That also signs you out and forgets your appearance and layout choices; nothing else is lost, because every record that matters is kept on the server. 44- **Session storage** â closing the tab discards it. 45 46## Where this is promised 47 48The binding statements are in the [Privacy Notice](/legal/privacy) (the "Cookies and similar technologies" section) and the [Data Processing Addendum](/legal/dpa). This article explains them in plain language and is kept in step with the code by the checks described above. 49`;export{e as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.