How VetIOS handles clinical data, inference traces, and operator telemetry across the platform mesh.
VetIOS is designed with a privacy-first clinical mesh. We collect three primary categories of data to facilitate veterinary intelligence:
All data is encrypted in transit via TLS 1.3 and at rest using AES-256. We utilize Supabase for robust authentication and Row Level Security (RLS) to ensure that clinical signals are only accessible to authorized tenants.
VetIOS does not sell clinical data. We may use anonymized, aggregated signals to train and refine our veterinary models, but specific patient or clinic identities are never shared with external advertisers.
VetIOS uses Google OAuth through Supabase Auth for sign-in only. The integration requests standard OpenID Connect scopes and does not access Google Drive, Calendar, Gmail, Workspace APIs, or any other Google service. VetIOS requests minimum scopes only.
You can revoke VetIOS Google access from your Google Account permissions page at myaccount.google.com/permissions.
To request VetIOS account deletion, contact privacy@vetios.tech.
VetIOS does not use Google user data, including email, profile, or any Google-sourced information, to train, fine-tune, or improve any AI or machine learning model. Veterinary inference models are trained exclusively on structured clinical signals, including species, vitals, and symptoms, submitted directly by platform operators. Google-sourced identity data is fully isolated from the ML training pipeline.
As a platform operator or partner, you retain ownership of your clinical inputs. You may request data exports or deletion of your tenant space at any time via the Control Plane or by contacting our platform team.
For inquiries regarding GDPR, CCPA, or specific clinical data handling policies, please reach out to:
privacy@vetios.tech