Cookie Policy
Which cookies WeaveSpec sets, what each one is for, and how to turn off the ones that are optional.
Last updated: August 4, 2026
1. What cookies are
Cookies are small files a site stores in your browser. Some are required for the site to work at all — without them we cannot tell one signed-in visitor from another. Others are there to remember a preference or to measure how the product is used.
We use no advertising cookies, and we do not sell or share cookie data with advertising networks.
2. Strictly necessary
These cannot be switched off. Blocking them means you cannot sign in or stay signed in.
- Session cookies (set by Supabase, our authentication provider) — keep you signed in and let the server tell who is making a request. They are cleared when you sign out.
- Security cookies — protect sign-in and form submissions against cross-site request forgery.
3. Preferences
These remember how you like the interface. Blocking them costs you nothing but the setting.
- Interface settings — light or dark mode, layout, colour and font choices from the settings panel.
- Language — the language you selected.
4. Analytics
We use PostHog to understand which parts of the product are used and where they fail. It sets cookies that give your browser an identifier so repeat visits can be counted as one person rather than several. We use this to fix problems and decide what to build; we do not use it to build advertising profiles.
5. Cookies set by others
When you sign in with Google, or connect GitHub or Jira, those providers set their own cookies on their own domains as part of that flow. They are governed by those providers' policies, not by ours.
6. Controlling cookies
Every major browser lets you view, block and delete cookies in its settings, and most offer a "do not track" signal. Blocking preference or analytics cookies leaves WeaveSpec fully usable. Blocking strictly necessary cookies does not — you will not be able to sign in.
7. Changes and contact
If we add or remove a cookie, we will update this page and the date above. How the resulting data is handled is set out in our Privacy Policy.
Questions: [email protected].