Security & Privacy
Health data is among the most sensitive information a person can share. We've built RemissionRoute with privacy and security at the foundation — not bolted on as an afterthought.
Our security principles
Six commitments that guide every architecture and product decision we make.
Encryption at Rest & in Transit
All data is encrypted using AES-256 at rest. All connections are secured via TLS 1.2 or higher. No health data travels unencrypted.
Canadian Data Residency
Patient data is designed to reside within Canada, in line with provincial health privacy requirements including BC PIPA and Ontario PHIPA.
Consent-First Architecture
Every data collection event is tied to an explicit, time-stamped consent record. Patients can review what they've consented to at any time.
Minimal Data Collection
We collect only what is necessary for the care journey. We do not sell patient data. We do not use health data for advertising.
Right to Deletion
Patients can request full deletion of their account and all associated data. Deletion requests are processed within 30 days.
Role-Based Access Controls
Access to patient data is strictly role-gated. Care team members see only what is relevant to their clinical relationship with the patient.
Encryption & Infrastructure Security
RemissionRoute is designed from the ground up with enterprise-grade data protection. Patient health information is encrypted at every layer — whether stored in the database or transmitted between the app and server.
Our infrastructure is built on cloud providers with SOC 2 Type II and ISO 27001 certifications, giving us a secure foundation from day one.
- AES-256 encryption for all data at rest
- TLS 1.2+ for all data in transit
- Hosted on SOC 2 Type II-certified cloud infrastructure
- Database-level row-security policies restrict data access by user identity
- Regular dependency audits and security patch cadence
Consent Logging
Every time a patient consents to data collection or accepts our Terms of Use, we create an immutable, time-stamped log entry. This gives both the patient and the platform an auditable record of what was agreed to and when.
Consent can be withdrawn at any time — withdrawal is logged with equal fidelity.
- Immutable consent records with full timestamp and version reference
- Separate consent logs for different data types
- Plain-language consent language — never dense legalese presented as a checkbox
- Patients can view their consent history in the app at any time
- Withdrawal of consent triggers a data review and deletion workflow
Canadian Data Residency
Provincial health privacy legislation in Canada — including British Columbia's PIPA, Ontario's PHIPA, and Quebec's Law 25 — places significant requirements on where and how health data can be stored. RemissionRoute is designed with these requirements in mind.
We are a Canadian company, co-founded by a Canadian physician. Our commitment to keeping patient data within Canada is both a legal position and a founding principle.
- Patient data designed to reside within Canadian data centre regions
- Architecture aligned with BC PIPA, Ontario PHIPA, and Quebec Law 25 principles
- PIPEDA-aware data handling practices throughout the platform
- Cross-border data transfer controls
- Data governance documentation available for institutional review
A word on certification language
We describe RemissionRoute as being designed with HIPAA, PIPEDA, and provincial health privacy frameworks in mind. As a pre-launch startup, we have not yet completed formal third-party HIPAA certification or PHIPA attestation audits. We are committed to pursuing these certifications as the platform scales and work proactively with legal and compliance advisors. We will never claim certifications we have not earned.
Security questions from your institution?
We work directly with hospital IT security teams and privacy officers. Reach out and we'll walk you through our architecture in detail.
Contact Our Team