Cookie Policy

Last updated September 15, 2026

In short: SnipRender sets only the cookies needed to sign you in and keep you signed in. There are no analytics, advertising or tracking cookies, so there is nothing to opt out of. Projects you open may use cookies or storage of their own on their preview and shared addresses.

1. What cookies are

Cookies are small pieces of data a website asks your browser to store and send back on later requests. Similar technologies include local storage and service workers. This policy covers all of them, and is part of our Privacy Policy.

2. Cookies SnipRender sets

We use only strictly necessary cookies. They are first-party, set on sniprender.com, marked HttpOnly so scripts on the page cannot read them, sent only over encrypted connections, and restricted with SameSite=Lax. Because the Service cannot work without them, they do not require consent.

NamePurposeDuration
access_tokenProves you are signed in on each request to the editor and its API.About 30 minutes, renewed while you use the Service
refresh_tokenIssues a new access token so you stay signed in without signing in again.7 days
oauth_stateProtects signing in with Google from forgery: it ties the sign-in to the browser that started it and holds the one-time values that prove it. Sent only to the sign-in callback.10 minutes, deleted as soon as sign-in finishes

Signing out deletes the first two. We set no analytics, advertising, social-media or other tracking cookies, and we do not use local storage on sniprender.com.

3. Preview and shared pages

Projects run on separate addresses, such as <project>.sniprender.net. SnipRender sets no cookies there. To run a project, those addresses install a service worker in your browser, which holds the project’s files while the page is open and is needed for the page to work.

The code inside a project belongs to its owner and may use cookies, local storage or other technologies of its own. That use is the project owner’s responsibility, not SnipRender’s.

4. Third parties

  • Google — when you choose to sign in, you use Google’s sign-in pages, where Google sets its own cookies under its own policies.
  • esm.sh — pages of React projects load npm packages from esm.sh. Your browser requests them directly, so esm.sh receives those requests; SnipRender does not set cookies for it.

5. Managing cookies

You can see and delete cookies in your browser’s settings, and block them for sniprender.com. If you block the cookies above, you will not be able to sign in. Removing site data for a preview or shared address also removes its service worker; it is installed again the next time you open the page.

6. Changes

If we ever add a cookie that is not strictly necessary, we will update this policy first and ask for your consent where the law requires it. The date at the top shows the latest version.

7. Contact

Questions about cookies: [email protected].