This list covers only a third party that processes Organization data on Telvo LLC's instructions to provide vetman. It is versioned separately.
Current subprocessors
| Provider | Service | Data | Location | Use |
|---|---|---|---|---|
DigitalOcean, LLC — infrastructure, Frankfurt region (fra1) | Application server, database and uploaded-file infrastructure | Data placed in vetman by the Organization and technical logs | Frankfurt, Germany; support and ancillary processing may occur at other locations under the provider's terms | Continuously for core hosting |
| Cloudflare, Inc. | DNS, TLS termination, traffic routing and protection against attacks (CDN/WAF) | All requests and responses passing through vetman, including data an Organization enters, while in transit; IP address, browser data and technical logs | Cloudflare's global network (each request is handled by the data center nearest the user); company based in the USA | On every request; Cloudflare does not store content permanently, apart from technical logs under its terms |
| Cloudflare, Inc. — R2 | Off-server backup storage (Cloudflare R2) | Backup copies of the database and files, encrypted on our server before upload; only Telvo LLC holds the decryption key and Cloudflare cannot read their content | European Union (R2 EU jurisdiction: the copies are stored only within the EU); company based in the USA | Nightly; the copies are used only for restoration and kept for the backup cycle |
| uBill | Sending SMS messages | Recipient phone number, SMS text and sender name | Georgia | Only when the Organization turns on the SMS feature itself |
vetman system email is sent through our msg.vetman.app infrastructure and no separate external email subprocessor is identified in this edition.
The SMS function sends data to uBill only when the Organization turns that feature on itself.
Other external services not listed here as Organization-data subprocessors
- Google Analytics is used only for public-website statistics and does not receive Organization clinical records from vetman;
- Google Sign-In is used only when chosen for account authentication and is processed in the context of our role as controller.
See the Privacy Policy and Cookie Notice for details.
Changes
How subprocessors are added or replaced, including consent for an optional feature's provider, is set out in section 5.3 of the DPA.
For questions, use the contact page.