faunium

Trust and security

Built to carry medical records between practices and insurers.

Every claim on the network holds a pet's medical history, an owner's consent and an insurer's decision. Here is how Faunium protects each one.

A calm claims office at dusk, a laptop with a hardware security key beside two blank monitors
Insurer firewalleach insurer sees only its own claims
Audit trail · append-only
Illustrative. Three practices send claims through the Interlock, which routes each claim to one insurer. A firewall keeps each insurer to its own claims, fraud matching compares fingerprints and never claim details, and every routing step is written to the audit trail.

At a glance

How the data is protected.

The main controls, in plain terms.

Controls
  • Encryption in transit (TLS) and at rest
  • Default-deny database: row-level security on every table
  • Insurer data firewall: each insurer sees only its own claims
  • Owner consent before any records release
  • Append-only audit trail on claims, consents and decisions
  • Roles and scope checked on the server, every request
  • Private document storage, 60-second links
  • Hashed keys and device tokens, immediate revocation
  • Signed update manifests for installed apps

The insurer data firewall

One insurer never sees another's claims.

  • An insurer sees a claim only when it is addressed to that insurer and submitted.
  • Rules, decisions and prices are keyed to the insurer that owns them, and to no one else.
  • Another insurer's claim answers exactly like one that does not exist.
  • One account can never belong to a practice and an insurer, or to two insurers.
  • Every insurer connects on the same published terms. No one is asked for exclusivity.

Faunium Signal

The cross-insurer fraud check compares keyed fingerprints that never leave the database. An alert names the fields that matched, never the other insurer or its claim.

Data protection and access control

Default deny, checked on the server.

Browsers never query the database. Every request goes through one server layer that checks who is asking and which practice or insurer they belong to.

Encryption

TLS in transit and encryption at rest on the hosting platform. Practice software credentials sit in an encrypted vault, never in a table column.

Default-deny data

Row-level security on every table with no client access at all. An automated check confirms it on every test run, and any new table is locked down on creation.

Private documents

Records live in private storage, reachable only through links that last 60 seconds and are issued after a scope check. Each one is logged.

Signed events

Every event sent to an insurer is signed so the insurer can confirm it came from Faunium, and goes only to secure addresses.

Quiet logs

Logs and audit rows carry ids, counts and states. Never document text, tokens or keys. Errors return a request id and nothing more.

Roles set by the server

A user's role comes from a server-controlled claim that users cannot edit. Unknown roles get nothing.

Keys shown once

API keys, device tokens and link tokens carry 256 random bits and are stored only as hashes. Test keys never touch live data.

Claim eventsappend-only
09:14:02Claim submitted
09:13:48Owner consent signed
09:12:10Document opened through a 60-second link
09:11:57Claim marked ready by staff
09:09:31Document received from the practice
Illustrative events. Sample data.

Audit trail

Written once. Never edited.

Claim events, insurer decisions, owner consents and the audit log refuse updates and deletes for every role, our own included. Every change to a claim is logged with who made it, and a claim's lines are frozen once it is submitted.

Insurer supervisors can export their own audit log, up to 90 days at a time. The export is itself logged.

A clinic back office computer beside a compact printer, a gray tabby cat asleep on a towel on the desk

Device security

The software on the practice's computers.

Print to Faunium, Faunium Sync and Faunium Sidebar run at the practice, so each one is locked to that practice and to its own install.

  • Print to Faunium stays on the computer

    The virtual printer listens on the machine's own loopback address only. It refuses other devices on the network and any request from a web page.

  • Pairing is single use

    A device joins a practice with an 8-character code that works once and expires in 15 minutes.

  • Tokens bound to one install

    Each device token is hashed at rest, tied to the install that first used it and revoked the moment a practice removes the device.

  • Automatic capture needs an owner

    Turning on automatic capture takes a one-time approval code from a practice owner or manager. Every change is logged.

  • Signed updates

    Print to Faunium and Faunium Sync check an Ed25519 signature on every update before installing it, with staged rollout and rollback.

AI policy

AI reads the paperwork. People decide.

Faunium uses a language model from Anthropic to read invoices and records and turn them into a claim. These are the rules it works under.

  1. 01

    It reads only what the claim needs.

    The model sees the document being read and the practice's patient names and policies needed to match it. Nothing else.

  2. 02

    It keeps nothing.

    The reader stores nothing and touches no database. Its answer is checked field by field. Document text is then dropped, except the visit note, which is kept with the visit like any other record.

  3. 03

    No training on your data.

    Faunium does not train models on customer data, and under Anthropic's commercial API terms, inputs and outputs are not used to train its models.

  4. 04

    People make the decisions.

    The reader drafts a claim. A person at the practice reviews it and submits. Every coverage decision belongs to the insurer's adjusters or the insurer's own written rules.

Retention and vendors

Where data lives, and for how long.

Retention

Records stay in the practice's own space on the network. Ask us for the retention schedule that applies to your data.

Your data, portable

Filing never depends on Faunium alone: a practice can always file with an insurer directly.

Subprocessorsupdated September 30, 2026
  • SupabaseDatabase, file storage, sign-in and server functions for the networkClaims, records, consents and account data
  • CloudflareHosting and network edge for the website and appsTraffic passing through, such as IP addresses and request logs
  • AnthropicReading invoices, records and policy forms to build a claim, and answering Help Center questionsThe document being read and the details needed to match it to a patient; Help questions with record details removed
  • ResendSending email (claim packets, owner links and notifications) and receiving email sent to a practice's Faunium addressEmail addresses and message content
  • StripeBilling for paid practice plans and insurer invoicesBilling contacts and plan details; card and bank details stay with Stripe

Practices and insurers can read the full terms in the data processing terms.

Compliance

Plain about where we stand.

  • Our position

    SOC 2 Type II

    Faunium does not hold a SOC 2 report.

  • Our position

    HIPAA

    HIPAA covers human health records, not animal ones, so we don't claim HIPAA compliance. We design how we handle veterinary records to a strict standard instead.

  • On request

    Vendor reviews

    Insurers review their service providers. We answer security questionnaires and walk your team through this page control by control.

Responsible disclosure

Found a vulnerability? Tell us first.

Email security@faunium.com with what you found and how to reproduce it. We aim to confirm receipt within two business days, and we will keep you updated until it is fixed.

  • Test only against accounts and data you own.
  • Don't access, change or keep anyone else's records.
  • Give us reasonable time to fix the issue before sharing it.
  • Don't disrupt the service, send spam, trick people or test physical security.

We treat research done in good faith under these rules as authorized and won't pursue legal action against it. We don't pay rewards for reports.

For insurers and groups

Reviewing us as a vendor?

Tell us what your security review needs. We will walk your team through each control and answer your questionnaire.