COOKIES
Cookie Policy
Last updated: 11 November 2026
This page explains the cookies and browser storage used by the petslab.it website and the app.petslab.it app. Controller: Matteo Baldelli, a natural person who operates the petslab.it service. Address: 504 Arizona Building, London, SE13 7QQ, UK. Email: hello@petslab.it.
At a glance
- We do not use advertising cookies. Page counts use no analytics cookies; linking them to an account requires separate consent.
- The app stores only what it needs to function in your browser, such as login, language and display preferences. This does not require consent.
- Third-party content that sets cookies includes the Google map. This loads only if you accept it.
This website (petslab.it)
The website does not set cookies or load third-party content; even the fonts are hosted by us. It therefore does not display a cookie banner. The hosting provider may set technical cookies strictly necessary for security, for example to protect against automated traffic.
If you close the registration notice displayed as you scroll, the site remembers your choice only until you close the browser tab, using sessionStorage. It is not a cookie, stays on your device and is not sent to anyone.
Registration links may contain a label identifying the website or blog guide. We do not create cookies or new localStorage or sessionStorage keys to measure browsing. The label is associated with the account at registration and may appear in the authentication session data already stored by the app, as explained in the Privacy Policy.
The app (app.petslab.it)
Technical browser storage (always active)
| Name | Purpose | Duration |
|---|---|---|
petslab.client-context (sessionStorage) | The selected centre in the client area. Each tab keeps its own choice; this is not an access credential. | Until sign-out or closing the tab |
petslab:activity:…, petslab:pending-invitation (sessionStorage) | Activity selected per account in this browser tab and a pending invitation during sign-in or registration. Selection is separate in each tab; neither key is used for tracking. | Selection until tab closure; invitation until acceptance, explicit dismissal or tab closure |
petslab-push (IndexedDB), petslab-push-dismissed:… (localStorage) | Technical binding of the device to the trainer session or to the client area, for push delivery and dismissal of the setup invitation. No access tokens. Push permission is requested separately by the browser. | Binding updated at sign-out/account change or when turned off; dismissal until browser data is cleared |
__Host-petslab-client | Remembers access to the private client area in this browser, separately from the trainer's account. A technical Secure, HttpOnly and SameSite cookie, not readable by JavaScript. | 30 days or until sign-out; changing email revokes only the affected client’s access |
sb-…-auth-token | Keeps the account signed in (authentication session). | Until signing out of the account |
petslab.language | Chosen language, Italian or English. | Until you delete it |
petslab.calendarView, petslab.clientsView | Preferred calendar and client list views. | Until you delete it |
petslab.theme | Chosen theme: light, dark or automatic. | Until you delete it |
petslab.calendarHours | Time range displayed in the weekly calendar. | Until you delete it |
petslab.cookieConsent | Remembers your cookie choice, with its date and version. | Until you delete or change it |
During client sign-in or email changes, sessionStorage retains the email, random request identifier and expiry/resend timings in the current tab only. It does not store the code. This data is removed after verification, changing the address or expiry and is used only to resume the flow after a refresh.
The client area cookie is sent only to the app to verify access. The other entries are data saved in the browser's localStorage, not sent to third parties, and necessary to provide the service you requested. They do not require consent.
Third-party content (only with your consent)
| Provider | Location | Purpose |
|---|---|---|
| Meta (WhatsApp Business / Facebook Login for Business) | Activity WhatsApp connection, requested by the owner | Meta’s login window and SDK may use cookies and receive IP address and browser technical data. They load only after third-party consent and an explicit connection request. Meta Cookie Policy |
| Google Maps (Google Ireland Ltd.) | Programme and event details, and location previews in forms | Displays a map of the location. Google may set its own cookies and receive your IP address. Google Cookie Policy |
Until you accept, a placeholder appears instead of the map. You can load it by selecting “Load the map (Google cookies)”, which constitutes consent. The “Open in Google Maps” button always works and opens Google in a new tab.
Address suggestions based on © OpenStreetMap data do not set cookies. They receive only the search text.
Giving or changing consent
When you first open the app, a banner presents two equally prominent choices: Accept or Necessary only. Closing the page without choosing is equivalent to “Necessary only”. You can change your mind at any time through Cookie preferences in your profile (Settings › Privacy and account) or at the bottom of trainers' public pages. You can also delete stored data through your browser settings.
For information on how we process personal data, read the Privacy Policy.
App statistics (PostHog)
When configured, we collect aggregate counts of page visits, feature usage, browser/OS/device categories, numeric Web Vitals and error categories without analytics cookies, account IDs, error messages or form content. Routes are normalised to remove identifiers, queries and tokens. The separate client portal and public website are not tracked. For these counts PostHog Cloud EU calculates a daily server-side hash from the project, temporary salt, IP address, user agent and hostname. The salt changes daily: visitor counts are approximate and do not recognise the same person across days. The IP is removed before events are stored.
Only with one optional usage-analysis checkbox do we link statistics to your technical account ID and enable masked session recordings. This lets us analyse return visits and interactions to improve the service. The checkbox is not preselected, and refusing does not restrict app functionality. Names, emails and client or dog data are excluded. Earlier cookieless visits are not retrospectively linked to your account. Before transmission we mask all text and attributes that may contain data, block forms, images, documents and media, and remove URL queries, hashes and path identifiers. Automatic interactions retain only their type (click, submit or change), excluding element text. Sign-in, password, auth callback pages and the client portal are excluded from recordings. Console logs and network request/response bodies and headers are not collected. Masked recordings are retained for 30 days.
You can give consent at signup or in Settings → Account → Privacy and data. The choice is independent of newsletters and maps, and saved per account with a timestamp and notice version. Withdrawal immediately stops account linking on this device and on other devices at their next check (every 30 seconds while visible or on resume); cookieless aggregate metrics continue. Withdrawal also stops new recordings and linked interactions; requests sent or queued before withdrawal may still finish sending. Errors suspend account linking. Withdrawal does not automatically erase historical events; contact hello@petslab.it for data requests.
Sandbox builds centrally disable all PostHog functionality and verify that the artifact contains no PostHog configuration. Without consent the SDK stores only a technical choice marker (__ph_opt_in_out_…), not an analytics identifier. With consent the analytics identity stays in memory during the visit; the database preference is retained until account deletion. PostHog privacy policy.
