Security & data handling
Concrete controls for a review-first documentation workflow.
This page describes the current NotoVet architecture and its limits. It is not a claim of compliance with a specific healthcare privacy framework.
Current flow
What happens to the information you provide.
Unsaved generator input
Processed for the request by Cloudflare Workers AI. It is not written to NotoVet’s application database unless you deliberately save the generated note.
Saved workspace notes
Stored in Cloudflare D1 under the authenticated user identifier supplied by Supabase. Server-side ownership checks apply to every saved-note operation.
Audio
Audio-to-SOAP is disabled for public and Solo users. The transcription endpoint remains unavailable unless a server-side beta flag and eligible authenticated plan are both present.
Billing
Paddle handles checkout and payment details. NotoVet stores subscription identifiers and status needed to grant plan access; it does not store full payment-card numbers.
Safeguards
Controls in the current product.
- HTTPS in transit through the hosting and service-provider layers.
- Supabase server-side session verification for every generated note and private workspace.
- Prepared D1 statements and user-scoped ownership checks for saved records.
- Private, no-store API responses for generated content and account data.
- Strict generator input sizes, provider timeouts, and account-level monthly allowances.
- Self-service saved-note deletion and account deletion, with a privacy inbox for manual help.
Report a concern
Tell us without sending more sensitive data.
Email privacy@vetsoapnotesai.com with the affected account email, approximate time, and a concise description. Do not attach full records unless we specifically request a secure transfer method.