Cookies.
Skew uses a small set of cookies. Two are required for the service to work; a third is optional and off by default. We do not use third-party advertising cookies.
1. What cookies are
A cookie is a small file a website stores on your device to remember you between page loads. Related storage mechanisms (localStorage, sessionStorage, IndexedDB) work the same way for this policy’s purposes. When we say “cookies,” assume we mean all of them.
2. Required — authentication
Clerk session cookies. Set by our authentication vendor. They keep you signed in across page loads and protect against session hijacking. Without them, you cannot stay signed in.
- Purpose: session state, sign-in persistence.
- Duration: session, plus a rolling 7-day refresh token.
- First or third party: first-party (set on skew.site).
- Required: yes. You cannot use the authed app without them.
3. Required — live data
Convex WebSocket session. Our application data layer maintains a live connection so your generations appear in the library the moment they finish. The session identifier is kept in memory plus a small cookie for reconnection.
- Purpose: real-time data sync between the app and our data layer.
- Duration: session.
- First or third party: first-party.
- Required: yes. Without it, the library does not update live.
4. Optional — analytics
If analytics are enabled, we record aggregated page views, route transitions, and performance metrics to understand where the service is slow or where people drop off. Analytics are anonymized at collection; we do not tie them to identifiable accounts.
- Purpose: aggregate usage and performance measurement.
- Duration: 13 months.
- First or third party: first-party.
- Required: no. If you are in a jurisdiction that requires opt-in consent (EU/UK/CA), we ask before setting them.
If we add a new analytics vendor at any point, we will update this document and, where required by law, ask for consent before activating it.
5. What we do not set
- Advertising cookies. We do not run ads.
- Third-party tracking pixels from ad networks.
- Cross-site identifiers shared with data brokers.
- Social-media pixels (Facebook, LinkedIn, etc.).
6. How to control cookies
Most browsers let you block or delete cookies from their settings. Blocking the required cookies above will break sign-in and break the live library. Blocking the optional analytics cookie does not affect anything except our ability to see aggregate usage.
Browser-level “Do Not Track” and “Global Privacy Control” signals are respected for the optional analytics cookie. We treat either signal as an opt out.
7. Changes
We update this policy when we add or remove a cookie. The “last updated” date at the top reflects the current version.
8. Contact
Questions about cookies or related storage: privacy@skew.site.