Schema-level tenant isolation
Each clinic's tenant-owned records live in a separate PostgreSQL schema. Tenant routing is selected from the clinic hostname before tenant data is queried.
Security architecture
Teliyadu OralOS protects clinic and patient data through layered technical and organizational controls. Security controls support responsible use; they do not make every clinic deployment automatically compliant with every country's law.
Each clinic's tenant-owned records live in a separate PostgreSQL schema. Tenant routing is selected from the clinic hostname before tenant data is queried.
Authenticated clinic users receive role-based access. The product separates Admin, Dentist, Receptionist, and Nurse responsibilities rather than treating every staff account alike.
Patient-record access and financial mutations are audit-logged so sensitive actions can be traced without logging raw medical record content or credentials.
The platform uses encrypted transport, encrypted AWS storage, and automated database backups as layers in its data-protection approach.
Production infrastructure is hosted in AWS eu-central-1 (Frankfurt). This is an infrastructure fact, not a promise of local data residency in another country.
Patient mobile identity is per clinic. A patient account is not a cross-clinic identity, balance, or shared medical record.
Country requirements
Healthcare, privacy, retention, cross-border transfer, patient-rights, and breach-notification requirements differ by country. Clinics remain responsible for their legal obligations and should obtain local advice. Contact Teliyadu to assess product configuration, contracting, and data-processing requirements for your market.
Responsible disclosure
Email support@teliyadu.com with the subject “Security Vulnerability.” Include the affected surface, reproducible steps, and potential impact. Do not include real patient data, passwords, tokens, or other secrets in the report.
Need a market-specific data-protection discussion?