PRIVACY NOTICE
Privacy Policy
Last updated: 11 November 2026
This notice explains how petslab.it processes the personal data of people visiting this website, people using the app.petslab.it application (dog trainers and educators), and people whose data trainers enter in the app (their clients and people registering for events). It is provided under Regulation (EU) 2016/679 (the “GDPR”).
Optional WhatsApp Business connection: the owner can authorize Meta to connect the professional number to the activity in Petslab. We store WhatsApp account and phone identifiers, display number, verified name, connection dates and status. The access token is encrypted and accessible only on the server; exports contain connection metadata, never the token. Authorization attempts are valid for 10 minutes. When the integration is enabled and the client has authorized the channel, the activity can send operational notifications from its own WhatsApp number using Meta Cloud API. We record the preference, consent date, source and phone number; changing the number requires a new choice. The recipient number and operational content needed for the notification are sent to Meta. Delivery outcomes and deduplication keys are retained for 400 days, and private delivery data for 30 days; credentials and message content are excluded from exports. Signed callbacks update delivery outcomes and disable the channel when the client replies STOP; other reply text is not stored. Preferences can be changed in the client record or client area; we do not import contacts or chat history. Disconnecting deletes credentials and connection details from Petslab, without deleting the WhatsApp account or automatically revoking Meta permissions, which can be managed in your Meta business integrations. A deauthorization notice from Meta deletes the token. Data is also deleted with the activity. Meta processes authorization data under its own privacy policies and may operate outside the EEA. WhatsApp payment methods are managed directly by Meta.
1. Who the data controller is
The data controller is Matteo Baldelli, a natural person who operates the petslab.it service. Address: 504 Arizona Building, London, SE13 7QQ, UK.
For questions about privacy or to exercise your rights, write to hello@petslab.it.
2. Two different roles, explained simply
- The trainer's account data (name, email, profile and settings): petslab.it decides how and why to process this data and is therefore its controller.
- Data trainers enter about their clients (names, contacts, dogs, programmes, lessons, Pet Sitting stays, events, prices and payments): the trainer decides on this data and uses it for their work, so the trainer is the controller. petslab.it stores and processes it only on their behalf, to operate the app, as a data processor (Article 28 GDPR). If you are a trainer's client and have questions about this data, contact the trainer first; we will help them respond.
Invitations and affiliate programmes: if you sign up through an invitation link, we associate the referrer’s code with your account to award free Pro months or calculate partner commissions on payments during the first year. Attribution is fixed at signup and does not require tracking cookies. We retain this association and payment and reward information while your account is active, include them in your data export and delete them with your account. Referrers see aggregate counts only, without invited users’ names, email addresses or payment details. Partner settlement records retain the invoice reference, amounts and a code distinct from the account identifier, without names or email addresses. They remain after account deletion to manage payouts, refunds and disputes and meet applicable accounting obligations. Refunds and disputes are considered in these calculations. The legal basis is our legitimate interest in operating the programme and preventing abuse (Article 6(1)(f) GDPR); you can object by writing to hello@petslab.it.
3. What data we process
- Website visitors: this website does not use profiling cookies or external analytics services. Registration links indicate only whether the click came from the website or a blog guide. Hosting services record technical data, such as IP addresses, to operate and protect the service.
- Trainers: first and last name, email, password (stored as a hash: we cannot see it), chosen language, plan (Free or Pro) and, if you subscribe to Pro, subscription data (status, expiry and Stripe identifiers; only Stripe processes card details and we cannot see them); profile and business information (business name, tax details and contact details for programme printouts, biography, photos, CV, certificates and awards in PDF, social links, public page and public contacts if enabled); app settings.
- Trainers' clients (entered by the trainer): name, email, phone number, address and tax code (optional), contact preference, notes, membership renewal, expiry and cancellation dates if the centre enables membership management (with technical history of sent reminders), dog data and records (name, breed, sex, date of birth or age, photo, dog record answers and notes), participation in programmes, lessons and events, and Pet Sitting stays (day care, boarding and pet sitting) and their updates for the owners (messages and photos). If the trainer uses Payments, this includes amounts due and payments they record (amount, date, payment method and notes). petslab.it does not collect or manage these payments: the trainer only records them.
- People registering for an event from a trainer's public page or an event link: name, email, phone number (optional), answers to the form selected by the organiser (dog details and other custom questions), shared only with the event organiser.
- Address searches: when you search for a location in the app, the text you enter is sent to an address suggestion service based on OpenStreetMap data, without cookies.
Registration source: if you create an account through a website or blog link, we store a short source label and, for the blog, the guide's slug in private authentication data. We do not collect browsing history, the URL of the website you came from, advertising identifiers or new cookies. We use this information together with account confirmation and the presence of clients and programmes for aggregate summaries about the usefulness of the guides. The label remains while the account is active, is included in your data export and is deleted with the account. It does not appear on your public page.
Trainer push notifications require explicit browser permission on each device, separately from the account preference, which is enabled by default. We store subscription endpoints and encryption keys, trainer and session references, and delivery records for 30 days; these data are included in the export and deleted with the account. The browser push service (Google, Apple, Mozilla or Microsoft) processes technical delivery data under its own privacy notice and may operate outside the EEA. Messages contain only activity type and time, without client names or private notes. You can disable all deliveries in settings or disconnect one device.
Private client area: each client can view activities linked to their relationship with a trainer, their participating dogs and the trainer's contact details, without registration or a password. Internal notes, tax details, health records, payments and other participants are not visible. Clients can correct their name, phone number and address and choose Email or None for notifications; changing an email address requires verification of the new address. New-participation and activity emails respect the Email preference; emails requested for access and address verification are necessary technical communications.
Access uses a single-use, eight-digit code sent by email, valid for 10 minutes and limited to five attempts. Clients enter it on the page where they requested it. The database stores only hashes of the random request and its associated code, never the readable code. The pending request (email, random identifier and timings, never the code) is temporarily retained in the browser tab using sessionStorage to resume after a refresh; it is removed after sign-in, changing the address or expiry. The browser can retain access for 30 days using a protected technical cookie. If the same address is associated with several centres, one code authorizes the relationships present at verification, keeping their data separate. The selected centre is remembered only in the browser tab (sessionStorage). Changes to contacts and preferences affect only the selected centre; other relationships are unchanged. Changing an email requires verification of the new address and revokes previous sessions for that client in the selected centre; the current browser retains access and other centres remain available. To limit abuse, we store temporary counters with identifiers derived from IP addresses, email addresses and requests, deleted after one day. New participations send activity details and a regular link to the client area, subject to the Email preference; codes are sent only at the client’s request. Trainers do not manage issuing or resending codes, or revoking access. Operational notification records remain until the relationship or trainer’s account is deleted and are included in the trainer’s export.
Pet Sitting updates: during a Pet Sitting stay the trainer can send the owners messages, photos and short videos (up to 30 seconds, with the recorded sound unless the trainer removes it). Each update is visible only to the owners of the dogs the trainer chooses, in their client area; a group photo or video may also show other dogs. Clients cannot reply. Before sending, photos and videos are resized and re-encoded in the browser, which removes the location and the other metadata of the shot or recording; the server refuses videos that still contain metadata. Photos and videos are kept in private storage and open only through temporary links, valid for 15 minutes, created after access is checked. The email announcing new updates contains only the link to the client area, never the messages, photos or videos, and follows the Email preference. Clients can also turn on, with explicit browser permission, a push notification on their own device: it shows only the activity’s name and their dogs’ names, never the messages, photos or videos, and opens the updates in the client area. To deliver it we store the subscription endpoint and encryption keys, bound to the client-area session: they are deleted when the client turns it off, signs out or the session expires. With several centres, the device receives updates for all verified relationships that remain valid: an email change or deletion of a client or centre stops deliveries for that relationship; when none remain, the device is removed. The trainer’s export shows how many devices each client turned on, without endpoints or keys. The browser push service (Google, Apple, Mozilla or Microsoft) processes technical delivery data under its own privacy notice and may operate outside the EEA. The purpose is to keep the owner informed during the stay and give them time to view and download messages, photos and videos: they are therefore deleted all together 30 days after the end of the stay or, for recurring stays, of the single visit. An update deleted by the trainer disappears for everyone at once but is kept until the same deadline, to document what was communicated in case of disputes. Deleting the stay, the dog, the client or the account also deletes its updates immediately. We record which account of the activity sent or deleted each update. Messages and photo and video details, without the files, are included in the trainer’s export; the trainer is their controller. To understand how many phones can prepare videos we count each day, anonymously, how many videos are sent with or without sound and how many times preparing one fails: the counts contain no reference to activities, people or devices and are deleted after 90 days.
The petslab.it newsletter: at registration you may choose, through an optional checkbox that is initially unticked, to receive occasional emails with service news and tips. We keep the choice, date, source, language and version of the consent wording in a private table; this data is included in your export and deleted with the account. You can withdraw consent through the link in newsletters or by writing to hello@petslab.it. Your choice does not affect technical emails necessary for your account. After address confirmation, we synchronise subscribers' email addresses and their subscription to the “Novità petslab.it” topic with Resend. Unsubscribes are reflected in our database; changes to a confirmed email address and account deletion also update the newsletter list. We separately retain technical references and any synchronisation errors without changing the original evidence of consent.
Client attachments: the activity can upload PDFs and images to client records. Files are stored privately on Supabase and accessible to authorised operators according to Client permissions. Opening a file creates a temporary link valid for 60 seconds. Files are not published or shared in the client area. Exports include metadata; files are removed when the attachment, client or account is deleted.
4. Purposes and legal bases
- Providing the app and the trainer's account: performance of a contract (Article 6(1)(b)).
- Sending the petslab.it newsletter: optional, withdrawable consent (Article 6(1)(a) GDPR).
- Sending service emails (account confirmation, password reset and welcome): performance of a contract.
- Managing the Pro subscription (payment, renewal and cancellation) and retaining invoices: performance of a contract and a legal obligation (Article 6(1)(c)) to retain tax documents.
- Sending lesson reminders, change notices, programme details and event registration confirmations to clients on the trainer's behalf: processing on behalf of the trainer, who is the controller.
- Assessing in aggregate whether the guides help people start using the app: legitimate interest in improving the service (Article 6(1)(f)). You may object by writing to hello@petslab.it.
- Security and abuse prevention, such as email sending limits: legitimate interest (Article 6(1)(f)).
- Displaying the Google map: only with your consent (see the Cookie Policy).
- Sending commercial communications about events, programmes and news to event registrants: only with your optional consent (Article 6(1)(a) GDPR), which may be withdrawn at any time.
5. Who we share data with
We do not sell personal data or use it for advertising. To operate the service, we rely on selected technical providers processing data on our behalf as processors or subprocessors. An up-to-date list is available on request at hello@petslab.it:
- Cloud infrastructure, databases and communications: providers of hosting, databases, authentication, file storage and service email and notification delivery, with main servers in the European Union, and OpenStreetMap-based address search services without cookies.
- Stripe: Pro subscription payments and invoicing (checkout, cards, invoices and subscription management). It receives the name, email and payment details only of subscribers. Stripe also acts as an independent controller for its own legal, fraud prevention and anti-money-laundering obligations.
- Optional services enabled by the user: Google Maps to show programme and event locations, loaded only with your consent (see the Cookie Policy), as well as any external calendar app you choose when enabling calendar synchronisation.
Some providers are based in the United States or may operate outside the European Union. In those cases, transfers rely on the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses.
The team receives numerical service usage summaries in a private Telegram group, and a notice when a new account is confirmed that includes the account's email address for operational management and abuse prevention. Reports remain aggregated. Names, account identifiers and client or dog data are not sent. Messages already sent to Telegram are not automatically removed when you delete your account; you may request their deletion by writing to hello@petslab.it. This does not add any browsing tracking.
6. How long we keep data
Data remains while the account is active. When a trainer deletes the account in the app, the account, clients, dogs, programmes, events, Pet Sitting stays, registrations, recorded payments and uploaded files are deleted immediately. Only technical backup copies may remain and are automatically deleted over the following days. Pet Sitting updates (messages, photos and videos) are deleted automatically 30 days after the end of the stay or of the single visit; their copies in the database backups expire within the following 7 days. Trainers can also delete individual clients, dogs, programmes, stays and events at any time. If they have a Pro subscription, deleting the account cancels it; billing data remains with Stripe for the period required by tax law.
7. Your rights
You have the right to access, correct and erase your data, restrict or object to processing and receive it in a readable format (portability). In the app, under Profile › Settings › Privacy and account, trainers can:
- download all their data in a JSON file;
- delete the account and everything it contains.
For any other request or question, write to hello@petslab.it. We will respond as soon as possible.
8. Security
Connections are encrypted using HTTPS. Each trainer can see only their own data thanks to access rules applied directly in the database. Passwords are stored in protected form by the authentication system.
9. Changes
If the way we process data changes, we will update this page and the date above. For significant changes, we will notify trainers by email.
Shared activities and the Centres plan
On Centres, team members access shared activity data according to their assigned role, including permissions for internal notes and client data. Invitations store email address, sender, expiry and outcome. The owner manages billing and closure. Leaving or removing a collaborator revokes access without deleting centre data; any owned activities and other collaborations remain separate and available. A new user registering from an invitation does not automatically receive an owned activity; they can create one when they choose. Selection is stored per account within the current browser tab only (sessionStorage); a pending invitation is also retained in that tab until acceptance, explicit dismissal or tab closure. When a Centres plan ends, collaborator access is suspended while data, memberships and roles remain available for reactivation. Authorized reminders may come from all activities with calendar access and identify their context. Pro remains individual and is never automatically converted to Centres.
Working hours and absences are personal to each activity: each team member manages their own, and users with calendar read access can consult them. They are included in data exports and deleted with the account or activity.
Educator assignments to courses and individual lessons belong to the centre, with a history of changes to the main educator. Users with calendar read access can consult current team member names. Removing a collaborator does not delete assignments: their identity remains in operational records, but their name is no longer shown when they leave the team. Filtering by educator does not restrict read permissions.
Your personal profile contains your account name and email and is separate from the shared business details, qualifications and public page. It lists all your memberships, including suspended ones. You can leave a centre without deleting its data, or delete an activity you own once its subscriptions have ended. Activity deletion removes its data and files and revokes team access while preserving your account and other memberships. Deleting the entire account is a separate action with explicit confirmation; centres owned by other people are not deleted.
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.
