# Schedule 2 — Technical and organisational measures > **Corrected review edition — 17 November 2026; proposed version 2.0.** This document is a review draft, not an executed agreement or country approval. It cannot take effect until the relevant parties validly execute it and the applicable publication, supplier, security and local-law conditions are satisfied. Target-market inclusion does not open enrollment. Brazil, Quebec, Europe, Africa, Asia, other Caribbean countries except the Dominican Republic, and unreviewed overseas territories are outside the new offer. See [current availability and review conditions](/legal/availability/) and [previous wording](/legal/archive/). Unresolved evidence/legal questions remain conditions, not verified facts. **Review edition: 17 November 2026. Proposed version 2.0; not in effect.** This Schedule distinguishes implemented product behaviour from evidence still required before the processing agreement can be activated. It is not a certification or a promise of features that are not available. ### A. Encryption and key custody 1. Browser/service traffic uses TLS. Google Cloud provides encryption at rest for hosted data. 2. DentalX uses AES-256-GCM field encryption for patient first/last name, birth date, telephone, address, emergency contact, medical history and insurance details. Patient email is not field-encrypted. Names and contact details copied to other operational records do not all have this additional encryption. 3. New consent forms and prescriptions use the clinical encryption path where enabled. Earlier records may remain unsealed; completion of a historical migration must not be assumed. Other clinical collections, images and messages do not all use field encryption. 4. The application keyring is held in Google Secret Manager. This is not externally controlled EKM/HSM custody and does not prevent legally compelled access by the hosting provider. Recovery arrangements, administrator access and migration evidence must be reviewed before activation; an off-platform key copy is not asserted here. ### B. Access and sessions 5. Database/storage rules isolate clinics and deny unauthorized access. Individual staff roles govern permitted actions; shared logins are prohibited. 6. The app requires every clinic user to enroll and sign in with a second factor. Administrative-console access also requires a second factor. These app requirements do not establish that every server-side enforcement switch has been enabled; deployment evidence remains a release condition. 7. The browser app signs users out after **30 minutes without interaction**, including elapsed time while closed. Browser inactivity logout is distinct from revoking connected Google grants or every credential already issued by a provider. 8. Patient links expire; consent-signing links are single-use. Staff must use authorized recipients and verify the identity/authority of patients and representatives. 9. A clinic Gmail mailbox is available to staff with Messages access. A clinician mailbox is limited to that clinician and clinic owners/managers. Its stored authorization grant is encrypted. Disconnect removes that stored grant without revoking every shared Google permission, so Calendar is not automatically disconnected. ### C. Audit, browser storage and recovery 10. The audit trail records chart openings, changes, exports and deletions. It does not capture every direct stored-file read and does not record IP addresses. Seven-year active-account retention and clinic-purge handling follow clause 14 and the Privacy Policy; older records without expiry need controlled handling. 11. Standard server-log retention is 30 days; application error/performance records use 90 days. Legacy entries may lack expiry. This is not a claim that every historical record has been remediated. 12. Database backups and point-in-time recovery use seven-day windows. Recovery copies remain protected. File-version removal and a complete clinic purge must be evidenced for the actual deletion operation. 13. The browser can keep a working copy and temporarily display readable records. Sign-out attempts to clear local copies; this is best effort when storage is blocked or another tab remains active. Use managed devices and operating-system locks. DentalX uses no advertising or session-replay tools. ### D. Operational duties and activation evidence 14. VstreamX must restrict production access to authorized personnel, bind them to confidentiality, train them for their duties and maintain an incident procedure capable of the notices required by the applicable agreement. Signed undertakings, training, administrator MFA, risk analysis and restore/deletion exercises require evidence; publication of this draft does not supply it. 15. The controlled release process includes dependency/security checks and restricted third-party browser origins. No independent DentalX security certification, universal HIPAA certification or absolute prevention of incidents is claimed. 16. Clinic/doctor Gmail processing, imported message retention and Google Limited Use follow Schedule 3 and the Privacy Policy. Patient-email restrictions for US clinics and other country restrictions continue to apply. No clinical AI can be activated by this Schedule. 17. Before activation, resolve the evidence conditions in the agreement registry, including server MFA, supplier coverage/locations, complete export/purge, appropriate access logs and applicable patient-storage consent. No date or future control is deemed verified merely because the document is available online.