Legal
Cookie Policy
Petnote uses cookies for two things: keeping you signed in, and taking a payment when you make one. There is no analytics package, no advertising pixel and no third-party tracker anywhere in the product — which is also why you have never seen a consent banner here.
Last updated August 12, 2026.
2. What is actually set
Session cookies, from us
When you log in, Supabase — the authentication system behind Petnote — sets cookies whose names begin with sb-. They hold the tokens that prove your browser is signed in, and they are refreshed as you move around the app. They are strictly necessary: without them there is no way to stay logged in between page loads, and every screen in the dashboard would be unreachable.
They are cleared when you log out, and they expire on their own if you stop using the site.
Payment cookies, from Paddle
Paddle processes payments for Petnote as merchant of record. When the checkout overlay opens, Paddle may set its own cookies to run the transaction, keep it secure and prevent fraud. These are Paddle's, governed by Paddle's own policies, and they are set only when you actually open a checkout.
Local storage and the offline app
Not a cookie, but worth stating in the same place. Petnote can be installed as an app, and a service worker keeps a copy of the site's static files — stylesheets, scripts, the logo — so it loads quickly and shows a proper page when you are offline.
It never caches pages. Dashboard pages are specific to one person and an Emergency Mode page carries somebody's phone number; neither is written to a cache that could outlive the session. Clearing site data removes the cached files.
3. What is not here
To be unambiguous, Petnote does not use:
- analytics of any kind — no Google Analytics, no Plausible, no self-hosted tracker;
- advertising or retargeting pixels, from any network;
- social media tracking widgets;
- session recording, heatmaps or scroll tracking;
- cross-site or cross-device identifiers;
- any cookie that would be sold, shared or matched with a data broker's profile.
4. Controlling cookies
Every browser lets you see, block and delete cookies, usually under Settings → Privacy. You can block ours if you want to.
The consequence is straightforward rather than punitive: blocking or clearing the sb- cookies signs you out, and you will not be able to sign back in until you allow them. The public parts of the site — the landing page, the blog, an Emergency Mode page — work perfectly well with cookies blocked entirely, because none of them needs to know who you are.
5. More detail, and questions
The Privacy Policy covers everything else we hold, why, and how to have it deleted. Anything this page does not answer goes to codezun@gmail.com.