Legal
Data processing terms
Last updated September 30, 2026
1. Roles
| Data | Whose it is | Faunium's role |
|---|---|---|
| Records, invoices and patient and owner details sent by a practice | The practice | Service provider, acting on the practice's instructions |
| A submitted claim, once it reaches the insurer | The practice and the receiving insurer | Service provider to each |
| Insurer rules, decisions, prices and messages | That insurer | Service provider, acting on that insurer's instructions |
| Owner consents | The practice, as evidence of consent | Records and enforces them |
The customer (the practice or insurer) is responsible for having the right to send us its data and for the notices and consents the law requires, other than the owner consent we collect on Faunium Pass for the practice.
2. Purposes
We process claim data only on the customer's instructions, which are these terms and the customer's use of the service, to:
- build, deliver and track claims and answer records requests;
- provide Faunium, Faunium Pass, Faunium Process and the API to the customer that owns the data;
- secure, support and fix the service, and meet our legal duties; and
- improve how invoices and records map to claims, using de-identified data that cannot reasonably be linked to a person, practice or insurer, without exposing one customer's data to another.
We do not sell customer data, share it for advertising, or train AI models on it. We do not keep, use or disclose it for any other purpose, or combine it with data from other sources except as these purposes and the law allow. We will tell the customer if we can no longer meet these terms. The customer may take reasonable steps to stop unauthorized use.
We also measure and improve how the service is used, from usage records about the customer's staff: the screens and buttons they use, the time each step takes and the errors they see. Usage records contain no claim content and are not claim data. We handle them under our privacy policy, keep them first party, never show them to another customer, and stop recording them for a customer's team on request.
3. Owner consent
Records go to an insurer only after the owner consents on Faunium Pass, for that pet and that insurer. Our systems refuse to answer a records request without a release on file for the requesting insurer. Consent records are append-only.
4. The insurer data firewall
- An insurer sees a claim only when it is addressed to that insurer and submitted.
- Each insurer's rules, decisions and prices are visible to that insurer alone.
- No insurer receives another insurer's claims, volumes or terms, in raw or aggregate form.
- Usage records about an insurer's staff are seen by Faunium staff only, never by another insurer.
- Faunium Signal, when it launches, compares keyed fingerprints only and tells an insurer which fields matched, never who the other insurer is.
5. Security measures
The measures in place today are listed control by control on our trust and security page. They include encryption in transit and at rest, default-deny database access with row-level security, server-side role and scope checks, private document storage with 60-second links, hashed keys and device tokens, and an append-only audit trail. Faunium is not SOC 2 certified.
6. Subprocessors
| Company | Purpose | Data |
|---|---|---|
| Supabase | Database, file storage, sign-in and server functions for the network | Claims, records, consents and account data |
| Cloudflare | Hosting and network edge for the website and apps | Traffic passing through, such as IP addresses and request logs |
| Anthropic | Reading invoices, records and policy forms to build a claim, and answering Help Center questions | The document being read and the details needed to match it to a patient; Help questions with record details removed |
| Resend | Sending email (claim packets, owner links and notifications) and receiving email sent to a practice's Faunium address | Email addresses and message content |
| Stripe | Billing for paid practice plans and insurer invoices | Billing contacts and plan details; card and bank details stay with Stripe |
Each subprocessor is bound by written terms at least as protective of customer data as these. We will give customers notice before adding or replacing a subprocessor that handles their data, by updating this list and, for insurers, as their agreement sets out. A customer that objects on reasonable data protection grounds may stop using the affected part of the service or close its account. We remain responsible for our subprocessors' work.
7. People with access
Our staff reach customer data only for support and operations, are bound to keep it confidential, and work through an admin console that is read-only for support views, never acts as a customer and logs every view with the staff member's id.
8. Help with requests
We help customers answer requests from individuals to see, correct or delete their information, and pass on any request we receive directly about a customer's data.
9. Incidents
If we confirm a security incident affecting a customer's data, we will notify that customer without undue delay, share what we know, take reasonable steps to contain it and help the customer meet its own notice duties.
10. Retention, return and deletion
Customers can export their data from their account at any time. When an agreement ends, we return or delete the customer's data on request, except where the law or our retention schedule requires us to keep it, and anything we keep stays under these terms. Claim records are kept for 7 years after the claim's last activity; the full schedule is in our privacy policy and, for insurers, in the security review package.
11. Location
Faunium serves U.S. practices and insurers and stores customer data in the United States. Our providers may carry traffic through their networks outside the United States in transit, under their own security terms.
12. Audits and reviews
Insurers can review our controls, send security questionnaires and, under their agreement, request evidence. Insurer supervisors can export their own audit log at any time.
13. Contact
Data protection questions: privacy@faunium.com. Security: security@faunium.com.
Related