skink.devverified
Sign up

Cookie Notice

Last updated: 2026-09-14

skink itself does not set cookies for authentication, analytics, advertising, or tracking, on either the public site (skink.dev) or the dashboard. The one exception is the optional "Sign in with Google" button, described below.

What we actually use

  • Dashboard sign-in. The dashboard authenticates API requests with a bearer token stored in your browser's local storage, not a cookie. It stays on your device and is never sent to a third party; clearing it (or signing out) ends your session.
  • "Sign in with Google" button. Visiting our sign-in or sign-up page automatically loads Google's own Identity Services script, which renders the Google sign-in button shown there alongside the email option. This is Google's code, not ours: it sets a cookie of Google's own (g_state) and may contact Google's own endpoints as soon as that page loads, regardless of which sign-in method you end up using — governed by Google's privacy policy, not this notice. You are never required to use Google sign-in; choosing the email option instead does not involve Google beyond that script already having loaded on the page.
  • No analytics or advertising scripts of our own. We run no third-party analytics, advertising, or session-replay scripts, and set no cookie, pixel, or similar tracker for those purposes.
  • No cross-site tracking. We use nothing on skink.dev or in the dashboard to track you across other websites.

We don't show a cookie-consent banner because we don't set any non-essential cookie ourselves — Google's sign-in cookie is set by Google's own code, only when you actively choose that sign-in method, for the sole purpose of completing that sign-in. If we ever add our own analytics or advertising tracking, we will update this notice and add consent controls before any such non-essential cookie or tracker is set.

Contact

Questions about this notice: privacy@skink.dev.