Trust & security
Built to be trusted with your records.
Owl's whole promise is that it never invents a clinical finding. Handling your data with the same honesty is the other half of that promise. Here, in plain language, is exactly how your records are processed, stored, and protected — and how to get them out or delete them whenever you want.
Who touches your data
Our subprocessors
A visit passes through a small, deliberate set of vendors — each doing one job, under a commercial agreement. We don't sell your data, and we don't share it beyond what these services need to do their work.
Anthropic
Transcript textGenerates your structured SOAP note from the visit transcript (Claude models).
AssemblyAI
Visit audioTranscribes the visit audio into text (speech-to-text).
Supabase
Records, audio, imagesDatabase, authentication, and encrypted storage of your records, audio, and images. Access is scoped per account with row-level security.
Vercel
App trafficHosts and serves the Owl application.
Cloudflare
DNS onlyDNS — routes owlpov.com to our servers.
Resend
Recipient email + reportDelivers transactional email, such as a Pet Parent Report you choose to send.
Your data is not training data
We don't train AI on your visits.
Owl does not train any AI model on your records, and we never sell your data. Your visit content goes to our subprocessors for one purpose — to transcribe your audio and draft your note — and is not used to train their models.
Concretely: note generation runs on Anthropic's API, which under its commercial terms doesn't train on your content; and for transcription, we've opted out of AssemblyAI's model-improvement program, so your audio isn't used to train their models either.
How your data is handled
Encrypted, isolated, and yours
- Encrypted in transit and at rest. Traffic to and from Owl is protected with TLS, and your records, audio, and images are encrypted at rest by our infrastructure providers.
- Isolated per account. Every record is scoped to the account that owns it using database row-level security. One practice cannot see another's data — the isolation is enforced at the database, not just the UI.
- Your records are yours. You can export your notes at any time, and you can request deletion of your records or recordings whenever you want (see below).
Recordings
Your recordings, your call.
When you record or upload a visit, Owl uses the audio to write your note. You decide what happens to that audio afterward:
- Keep it (the default). The recording stays in Owl so you can play it back and check the note against its source — the proof behind Owl's promise never to invent clinical detail. You can download it (as a file named for the patient and date) or delete it at any time.
- Don't keep it. If you turn keeping off — globally in Settings, or for a single visit — Owl automatically deletes the recording from storage once your note is generated. Nothing about the note changes; it stands on its own.
A few specifics, stated honestly:
- The default is keep, but you set it. Change the account default in Settings, or override it per visit before you submit.
- Changing the default only affects new visits. Owl never reaches back and deletes recordings you already chose to keep.
- Deleting a recording is permanent and never touches your note. Deleting audio removes only the audio file; your SOAP note and its underlying record are untouched.
- Only you can reach your recordings. Downloads and deletes are scoped to your account; recordings are stored privately and served through short-lived, signed links — no public URLs.
- Retained recordings are kept until you delete them. There is no automatic time-based expiry in this version.
Deletion
How to delete your data
You can delete any visit's recording yourself from the visit view in the app, at any time. To request deletion of records or your account, or to ask any data-handling question, email hello@owlpov.com and we'll take care of it.
The honest part
What we are — and aren't
Veterinary records are not covered by HIPAA, which governs human health data. We don't claim otherwise, and we don't display compliance badges we haven't earned. We hold ourselves to a high security bar regardless — because it's the right way to handle your records, not because a regulation forces it.
We do not currently hold a SOC 2 certification. We'll pursue formal certification when our customers need it for their own procurement — and when we do, you'll read about it here, not before.
Have a security or data question we didn't answer? Email hello@owlpov.com. A real person reads it.