What we measure
We use Vercel Web Analytics for aggregate page visits and a small set of product events, such as starting or completing a tutorial, copying or downloading example source, choosing catalog filters, and opening a search result.
What we do not send
We do not send raw site-search text, Grid model source, clipboard contents, names, email addresses, or account identifiers. Search events use a fixed high-level topic such as simulation or validation. Query strings and URL fragments are removed before analytics events are sent.
Browser privacy signals
Analytics is disabled when your browser sends Global Privacy Control or Do Not Track. Vercel Web Analytics is designed without analytics cookies and reports aggregated data. Vercel may process the route visited, referring site, timestamp, broad location, and device or browser category as part of that service.
Local tutorial progress
If you mark a tutorial complete, its public tutorial identifier is saved in local storage on this browser so the completion state can be shown again. Session storage is used only to avoid counting the same tutorial start repeatedly during one browser session. This local progress contains no model data or identity.
Learn more
Read Vercel's Web Analytics privacy and compliance documentation, or return to the Grid learning paths.
Last updated August 24, 2026.