Ausculto

Privacy Notice

Effective date: May 6, 2026

Last updated: May 6, 2026

This notice explains how Ausculto is designed to handle clinical audio, synced clinical drafts, account data, and billing data. It also explains the privacy responsibilities that remain with the clinic using the product.

Who This Notice Applies To

This notice applies to the Ausculto product, website, and related services used by veterinarians, clinic staff, and veterinary practices.

Ausculto is documentation support software. It should be read together with the privacy notice or client-facing privacy materials provided by the clinic using the product.

How Ausculto Handles Clinical Audio

Ausculto is designed so clinical audio remains transient and local on supported web browsers and on the native iPhone app during transcription and draft generation.

Ausculto is not designed to store clinical audio in its hosted backend as part of the normal product workflow.

If a device does not support the required local workflow, Ausculto does not provide a cloud clinical-audio fallback for transcription or draft generation.

What Clinical Data May Sync

While clinical audio is intended to stay local, generated clinical content may sync to the signed-in workspace. This can include transcripts, SOAP drafts, discharge instructions, referral summaries, patient names, species, review notes, approval state, and export state.

The shared workspace sync boundary is the generated clinical draft, not raw clinical audio or on-device setup files.

Clinics should assume that synced drafts are cloud-hosted workspace data and handle them accordingly within their privacy, retention, and access-control programs.

Account, Billing, And Operational Data

Ausculto may process account information, user sign-in data, license state, subscription status, payment identifiers, service logs, and operational health-check data needed to run the service.

Clinical content should not be placed in billing metadata, support requests, authentication profile fields, or other non-clinical administrative fields.

Access And Security

Synced drafts are intended to be scoped to the relevant clinic workspace and signed-in account context.

Ausculto relies on account authentication, workspace boundaries, and service-side access controls to limit access to synced drafts. Clinics remain responsible for staff access management, device security, and offboarding.

Consent, Review, And Export Controls

Ausculto is designed to support an in-app consent workflow before recording.

Drafts are intended to remain in a review state until a veterinarian approves them. Copy and export actions are designed to occur only after review and approval in the normal product workflow.

Clinic Responsibilities

Each clinic remains responsible for its own privacy program, client consent practices, system-of-record retention, access requests, incident response, staff offboarding, and professional compliance obligations.

Ausculto is not a substitute for the clinic's own privacy policy, record-retention rules, or legal obligations to clients, regulators, or veterinary colleges.

Retention And Deletion

Clinical audio is intended to be transient and local rather than stored in Ausculto's hosted backend during normal use.

Synced drafts and related workspace data may remain in the workspace until they are deleted, overwritten, exported into the clinic's system of record, or otherwise handled under the clinic's retention practices and service configuration.

Deleting a user account removes the sign-in and saved profile for that user. Shared or paid workspaces require billing cancellation or ownership transfer before deletion so clinic records and staff access are not removed accidentally.

If a user explicitly confirms deletion of a solo owned workspace, synced drafts in that workspace may be deleted with the workspace. Clinics should export or otherwise handle any records that must be retained before using that option.

Service Providers

Ausculto uses third-party service providers for hosting and deployment, authentication and database infrastructure, and subscription billing.

At the time of this notice, those categories include services such as Vercel for deployment, Supabase for account and workspace infrastructure, and Stripe for billing.

Questions About Privacy

If you are a client or patient representative with a question about a veterinary record, consent, or a clinic's use of Ausculto, you should first contact the clinic that collected or reviewed the record.

If you are a clinic user with a product privacy question about Ausculto itself, use the support or onboarding contact associated with your Ausculto account or subscription.

This notice describes the current product privacy posture reflected in the application workflow. Clinics should review it together with their own client-facing privacy materials and legal advice.