In short
- Application servers, encrypted databases, and AI processing for Silenoa run in Montréal (northamerica-northeast1), Québec, Canada.
- Zero audio is ever written to disk (0 h): voice is transcribed transiently in volatile memory and discarded immediately, in both Ephemeral Scribe Mode and Longitudinal Clinical Mode.
- Clinical notes and transcripts are never used to train any AI model and are governed by strict contractual Zero Data Retention commitments with the model infrastructure provider.
- Health insurance numbers (RAMQ) and Social Insurance Numbers (SIN) are stripped automatically before note synthesis, and strict clinical prompt rules forbid fabricating vital signs or unstated clinical facts.
- Every clinical workspace is logically isolated at the data access layer; a dedicated isolated database or Bring Your Own Cloud (BYOC) deployment is available for multidisciplinary clinics and private FMGs.
- Every view, creation, signature, addendum, and PDF export is recorded in an immutable audit log built to support Québec Law 5 traceability obligations.
1. Where your data is hosted
In Montréal, Québec. All core clinical workloads—application servers, encrypted databases, real-time transcription, and AI note synthesis—execute inside the Montréal (northamerica-northeast1) cloud region in Canada. No patient or client health information is transferred outside Canada during standard platform operations.
Two purpose-built architectures depending on your practice. Silenoa separates its two clinical modes strictly so that it never stores more than your charting obligations require:
| Data category | Ephemeral Scribe Mode (Physicians & NPs with an EMR) | Longitudinal Clinical Mode (Psychologists, Allied Health & Clinics) |
|---|---|---|
| Encounter audio stream | 0 h on disk (volatile RAM in Montréal, discarded immediately) | 0 h on disk (volatile RAM in Montréal, discarded immediately) |
| Pending draft note | Encrypted in Montréal; purged on EMR transfer or after 48 h by default (30-day cap) | Encrypted in Montréal until reviewed and signed by the practitioner |
| Signed longitudinal chart | No patient chart module inside Silenoa; your EMR remains the sole chart | Stored and locked in Montréal (later clarifications via dated, signed Addendums only) |
| Real-time Whisper assistant | Reads the active EMR tab strictly in volatile session RAM (0 database writes) | Mathematically locked to the single open client chart in Montréal (ContextLock) |
| Access & action logging | Consent timestamp and draft purge confirmation | Immutable Law 5 audit log recording every view, creation, signature, and export |
End-to-end encryption in transit and at rest. All traffic between your browser, the Chrome extension, the built-in telehealth video room, and our Montréal servers is encrypted in transit over TLS 1.3. All data stored in the database—including transient drafts, signed longitudinal records, and audit trails—is encrypted at rest using AES-256.
Practitioner sign-in credentials. Only the clinician's own account identity (name, professional email address, and encrypted authentication token) passes through Google's global identity service to authenticate sign-in. Zero clinical notes, zero patient or client names, and zero health records ever pass through that authentication layer.
2. What the AI sees, and what it does not keep
Strictly scoped to the active encounter. During a visit or therapy session, the AI synthesis pipeline receives only the volatile text transcript produced in memory and the structure of the clinical template selected by the practitioner (such as a four-part SOAP note or a specialty progress note aligned with your professional college).
Zero Data Retention and zero model training. All transcription and language model calls execute under enterprise Zero Data Retention commitments in Canada:
- No clinical transcript, transient draft, or signed progress note is logged or retained by the model provider once the structured response is returned.
- Zero data from your clinic is ever used to train, fine-tune, or evaluate any public or proprietary AI model.
Automatic stripping of RAMQ and SIN numbers. Before the volatile transcript is synthesised into a clinical draft, a deterministic redaction filter detects and removes Québec Health Insurance Numbers (RAMQ) and Canadian Social Insurance Numbers (SIN) spoken aloud during the visit.
Anti-hallucination clinical guardrails. System instructions strictly forbid inventing unstated symptoms, fabricating vital signs (blood pressure, heart rate, temperature, oxygen saturation), or inserting default normal physical exam findings that were not verbalised. If a measurement was not stated during the encounter, that detail is omitted rather than guessed, leaving full clinical control to the reviewing practitioner.
3. Audio is never written to disk
Zero voice recordings to store, secure, or disclose. Retaining raw audio recordings of medical visits or psychotherapy sessions creates significant privacy exposure: raw audio captures vocal biometrics, hesitations, and off-topic personal remarks, and becomes an archivable record subject to disclosure requests. Silenoa eliminates this risk by writing zero seconds of audio to disk (0 h).
How volatile in-memory transcription works
- Pre-consent lock: until the practitioner ticks the informed verbal consent box, the microphone remains locked in the workspace interface.
- Encrypted streaming buffers: once unlocked, voice travels in short TLS 1.3 encrypted chunks directly into volatile memory (RAM) on Montréal servers.
- Immediate buffer destruction: each audio buffer is converted into text within milliseconds and immediately overwritten in RAM. No WAV or MP3 file is ever written to a disk volume, object bucket, or backup snapshot.
- One-click pause: during a physical examination or whenever the person asks to share something off the record, one click pauses audio capture immediately.
This rule applies equally in both clinical modes: even when you follow a client across months of care in Longitudinal Clinical Mode (psychology, physiotherapy, chiropractic, osteopathy, occupational therapy, speech-language pathology, or dietetics), only your reviewed, signed written notes are preserved in the chart—never raw audio.
4. Isolation between clinics
Logical workspace isolation enforced at the repository layer. Every clinic workspace carries a unique tenant identifier. In Silenoa's backend architecture, this identifier is automatically injected at the data access layer on every read, write, search, and export query. A clinician signed in to Clinic A is structurally prevented from querying any record belonging to Clinic B.
Single-chart ContextLock inside clinics. Even within the same clinic in Longitudinal Clinical Mode, the real-time Whisper assistant never queries across your broader caseload. When you launch a session from a fictional client's chart—for instance Ms. Camille Bergeron's rehabilitation record—, Whisper is mathematically scoped to that single chart identifier. Zero details from another client's file can cross into the active session.
Deployment tiers for multidisciplinary clinics and FMGs
For group practices and institutions with heightened governance requirements, three deployment tiers are available in Montréal:
| Isolation tier | Database architecture | Governance & key control | Typical organisation |
|---|---|---|---|
| Isolated Clinic Workspace (Standard) | Strict logical tenant isolation per clinic in Montréal | Per-clinician retention settings; managed encryption | Solo practitioners and small private clinics |
| Dedicated Database (Group 5+ clinicians) | Physically separate encrypted database instance in Montréal | Shared team templates and admin-enforced retention caps | Multidisciplinary clinics and private FMGs |
| Dedicated Instance or Bring Your Own Cloud (BYOC) | Dedicated isolated stack or deployed inside your own Montréal Google Cloud account | Your own encryption keys, VPC network boundaries, and IAM policies | Large FMGs, clinic networks, and professional bodies |
5. Access and the audit log
Role-based access controls. Workspace access requires individual practitioner authentication (professional email with strong password or federated Google workspace sign-in). Administrative governance is cleanly separated from clinical charting:
- Practitioner: starts encounters or sessions, accesses authorised client charts, reviews and signs notes, and appends signed addenda.
- Clinic Administrator: invites and removes team members, manages billing, curates shared clinical templates, and enforces clinic-wide draft retention ceilings.
- No silent impersonation: Silenoa contains no hidden super-administrator backdoor allowing vendor staff to sign in as a clinician or browse clinical notes.
Immutable Law 5 audit trail. Québec's Act respecting health and social services information (Law 5) requires health sector bodies to maintain tamper-evident logs of access to health information. In Longitudinal Clinical Mode, every action on a client chart is recorded in an append-only, unalterable audit trail:
- Chart views (reads) of any client file or signed progress note, stamped with the exact date, second-level timestamp, and practitioner identity.
- Session creation and cryptographic signature, permanently locking the original clinical entry.
- Dated, signed Addendums appended beneath a locked session note.
- Complete PDF chart exports, ready for client access requests or professional college inspections (See the guide to exporting charts and reading the audit log).
6. Our subprocessors
We intentionally keep Silenoa's subprocessor footprint minimal. Below is the complete list of third-party infrastructure providers and their exact scope:
| Subprocessor | Role for Silenoa | Data processed | Processing region |
|---|---|---|---|
| Google Cloud Platform | Application hosting, in-RAM speech transcription, and AI inference under Zero Data Retention terms | Volatile RAM audio buffers, encrypted drafts and signed notes | Montréal (northamerica-northeast1), Québec, Canada |
| MongoDB Atlas (on Google Cloud) | Managed database encrypted at rest (AES-256) for clinical workspaces and Law 5 audit logs | Encrypted workspace data and append-only access logs | Montréal (northamerica-northeast1), Québec, Canada |
| Google Identity / Firebase Auth | Practitioner sign-in authentication | Practitioner name, professional email, and hashed sign-in credentials only (0 patient data) | Global authentication service |
| Stripe | Subscription billing and invoice processing | Clinic billing contact details; payment card numbers stay on Stripe (0 patient data) | North America |
Your EMR or clinic software remains under your own contract. When you use our Chrome extension to auto-fill an encounter inside your certified EMR (MYLE, Omnimed, OSCAR, Cristal-Net) or clinic management platform (Jane App, Gorendezvous, Cliniko, Medexa), field injection occurs locally inside your open authenticated browser tab. Those platforms remain your direct vendors under your existing agreements.
Breach notification and PIA documentation. In accordance with Québec Law 25 and Law 5, our team notifies your privacy officer (RPRP) without delay in the event of any confidentiality incident affecting your workspace. To request our complete PIA / ÉFVP documentation package, consult our Privacy Policy, our white paper on the transient draft, or our white paper on consent and AI scribes.







