Petdocus
EN
Version 2026-10-02 (rev. 3) · free pilot

Data processing agreement

This agreement applies between each organization using Petdocus (a rescue or a vet clinic — the controller) and the operator of Petdocus (the processor), for the personal data the organization enters about other people. An organization's admin accepts it in the app.

1. Parties

Processor: Condria Eduard-Dragos, Alexandru Vlahuță, bl. 19, ap. 15, Focșani, jud. Vrancea, Romania, operator of Petdocus during the free pilot (contact: condriaeduarddragos@gmail.com). Controller: the organization whose admin accepted this agreement in Petdocus.

2. Subject, duration, nature and purpose

The processor stores and processes personal data on the controller's behalf to provide Petdocus: keeping pet records, managing the organization's members, sending the pet files the controller chooses to send, and the change history. The processor never gives another organization access to the controller's data. The agreement lasts as long as the organization uses Petdocus.

For vet clinics the processor also keeps the clinic's appointments and, when the clinic switches reminders on, sends reminder emails on the clinic's behalf to owners the clinic marked as having agreed (appointments, vaccinations and deworming due). The clinic is responsible for having the owner's agreement. An owner can stop the reminders through the link in every email; the processor then stops sending to that address for that clinic.

3. Types of data and data subjects

  • Members of the organization: name, email, role, permissions; for clinics, vets' licence numbers.
  • Owners and adopters: name, phone, email and address the organization records; recipients of pet files: email address.
  • Clients of clinics: appointments (time, reason, name and phone noted), the owner's agreement to reminders, reminders sent, and addresses that stopped reminders.
  • Fosters and other people named in records or documents (for example on pet passports).
  • Change history entries relating to these people.

No special categories of data are intended; the controller does not enter them.

4. Processor's obligations

  • Process the data only on the controller's documented instructions — the use of Petdocus' features is the instruction — unless the law requires otherwise.
  • Tell the controller immediately if an instruction appears to infringe data protection law.
  • Ensure that anyone authorised to process the data is bound to confidentiality.
  • Implement appropriate technical and organisational measures (Art. 32): encryption in transit, secure password hashing, two-step verification for admins, server-side permission checks on every request, private file storage with logged views, append-only hash-chained audit log, EU-jurisdiction storage, point-in-time recovery.
  • Engage sub-processors only as listed on the sub-processor page; inform controllers of intended changes so they can object; impose the same data protection obligations on them.
  • Assist the controller with data subject requests (self-service export and erasure in the app; further help on request) and with Articles 32–36.
  • Notify the controller without undue delay after becoming aware of a personal data breach, with the information available.
  • At the end of the service, delete or return the data at the controller's choice (the organization export in Settings gives a full copy), unless the law requires storage.
  • Make available the information needed to demonstrate compliance and allow for audits in a reasonable way.

5. Controller's obligations

  • Have a legal basis for the data it records and inform the people concerned (for example adopters).
  • Record only what is needed; keep notes free of unnecessary personal details.
  • Give members only the permissions they need; keep two-step verification on for admins.

6. International transfers

Data is stored with EU jurisdiction. Sub-processors in the US are covered by the EU–US Data Privacy Framework and/or standard contractual clauses. Transfers to the United Kingdom rely on the EU adequacy decision for the UK.

7. Liability and law

Liability follows Art. 82 GDPR. Romanian law applies. When this agreement changes materially, controllers are asked to accept the new version in the app.