Cookie Policy — PETADD
Last updated: 2026-06-04 (v1 draft — reviewed by Claude; AK + legal counsel finalize before public launch.)
This page explains the cookies and similar browser-storage technologies PETADD uses, why we use them, and how you can control them. For the wider treatment of your data, see the Privacy Policy.
What is a cookie?
A cookie is a small text record a website asks your browser to store. We also use localStorage, which is not a cookie but works similarly. We classify both as “browser storage” below.
What we store
PETADD sets only what is strictly necessary to run the service. No third-party trackers, no advertising cookies, no analytics cookies.
| Name | Storage | Purpose | TTL |
|---|---|---|---|
web_app_demo_refresh | HTTP cookie (HttpOnly, Secure, SameSite=None, Path=/) | Refresh-token reference — keeps you logged in across page loads and tabs. | 30 days |
cookie_notice_acked_v1 | localStorage | Remembers that you dismissed the cookie banner so we do not show it again. | Until you clear browser storage |
access token | in-memory (JavaScript) | Short-lived access token used by the cabinet for API calls. Held only in the page's memory, never in browser storage. | Cleared when you close or reload the tab |
Why these are essential
Without web_app_demo_refresh you would be signed out on every page navigation. Without the in-memory access token the cabinet cannot call our API. The banner-dismissal flag prevents an obviously broken UX where the same notice reappears on every visit.
What we do not set
- No advertising or retargeting cookies.
- No Google Analytics, Meta Pixel, Hotjar, or similar third-party trackers.
- No cross-site cookies beyond the refresh-token reference described above.
Anonymous visit counting
We count page views on our own server, without cookies or any other browser storage and without third-party services. When a page opens, your browser tells our server which page it was and, if any, the site that sent you there. The server turns your IP address and browser user agent into a one-way daily fingerprint with a random key that is replaced every 24 hours and then deleted, so visits cannot be linked across days or traced back to you. The IP address and user agent themselves are not stored; the country is looked up on our own server from a local database. If your browser sends Do Not Track or Global Privacy Control, nothing is counted. Aggregated counts are kept for 13 months.
If we add other analytics or marketing tooling in the future, we will update this page first and ask for consent where required.
Third-party services
When we send transactional email (verification, password reset, claim invitation, Tier-2 decision) we use Resend. Resend may set its own cookies on its dashboard at resend.com, but it does not run any script on PETADD pages and cannot set cookies on the pet.brave-robots.com domain.
How to control or remove cookies
- Sign out — clicking Logout in the cabinet immediately invalidates and clears
web_app_demo_refreshon our side and asks the browser to drop it. - Browser settings — every modern browser lets you block or delete cookies and storage per site. See instructions for Chrome, Firefox, Safari, or Edge.
- Opt out of the refresh cookie — you can refuse it, but the cabinet will not work: every protected page would log you out. The cookie is only ever set after a successful sign-in.
Do Not Track
We do not run advertising or behavioural tracking, so the DNT header has nothing to disable on our side. We treat all users the same regardless of whether the header is present.
Changes to this policy
We may update this page as the product changes. Material changes (new cookies, new third parties, change of legal basis) will be highlighted in the banner the next time you visit.
Contact
Questions about cookies or storage? Write to hello@petadd.com.