Trust Center
Security & Trust
Building toward HIPAA compliance, in the open.
Ambé Wellness handles health information, and we hold ourselves to the standard that comes with it. We are partway through a formal HIPAA readiness program. Rather than claim a finish line we have not crossed, this page shows exactly what is in place today, what is being built, and what is still ahead.
Last reviewed September 2, 2026
A note on where we are
HIPAA has no government certification — no agency issues a badge that says a company is “HIPAA certified.” What it requires is a documented, continuously maintained program of safeguards. We are building that program now, and we are not finished. Until every item below reads Live, we will not describe Ambé Wellness as HIPAA compliant, and neither should anyone on our behalf.
Safeguards
Encryption
How your information is protected in motion and at rest.
- Live
TLS 1.2+ in transit
All traffic between our apps and our servers travels over encrypted connections. Certificates are managed by our cloud provider and rotated automatically.
- Live
AES-256 at rest
Databases, file storage, and backups are encrypted at rest with AES-256 by our cloud provider, with keys managed in Google Cloud KMS.
- In Progress
Customer-managed encryption keys (CMEK)
Moving encryption keys under our own control so key rotation and revocation are independent of the platform default.
- In Progress
Field-level encryption for clinical notes
Additional encryption applied to the most sensitive clinical fields so that they remain unreadable even to platform-level operators.
Safeguards
Access Control
Who can reach health information, and under what conditions.
- Live
Individual accounts, no shared logins
Every patient, practitioner, and staff member authenticates as themselves. Credentials are never shared between people.
- Live
Role-based access control (RBAC)
Practitioner, patient, support, and administrator roles are strictly separated so each role reaches only the records it needs.
- Live
Database-enforced record isolation
Authorization rules are enforced in the database tier so a patient record is reachable only by that patient and their assigned care team — enforced cryptographically on the server.
- In Progress
Multi-factor authentication (MFA)
MFA will be required for every practitioner and administrator account, and offered to patients.
- Live
Automatic session timeout
Idle sessions end automatically (15 minutes for staff, 30 minutes for patients) requiring re-authentication, as required by HIPAA §164.312(a)(2)(iii).
- In Progress
Quarterly access reviews
A recurring review confirming that every account still needs the access it holds, with removals documented.
Safeguards
Infrastructure & Network
Where the platform runs and how it is isolated.
- Live
Managed cloud hosting (Google Cloud / Firebase)
The platform runs on Google Cloud Platform, which maintains its own SOC 2, ISO 27001, and HITRUST certifications for the underlying infrastructure.
- In Progress
United States data residency
Confirming and pinning every data store to United States regions, and documenting the result.
- In Progress
Private networking / VPC Service Controls
A service perimeter around production data so it cannot be reached from the public internet, only from authorized services.
- In Progress
Web Application Firewall & DDoS protection
Edge filtering for common web attacks and volumetric traffic floods.
Safeguards
Logging & Monitoring
How access to health information is recorded and reviewed.
- Live
Infrastructure and application logging
Server activity and errors are captured in Google Cloud Logging.
- Live
PHI access audit trail
An immutable, six-year audit log recording access to consultation tokens, patient charts, and record modifications — satisfying HIPAA §164.312(b).
- In Progress
Automated alerting on anomalous access
Alerts on unusual access patterns, such as bulk record reads or logins from unexpected locations.
- In Progress
Log integrity protection
Write-once retention so audit logs cannot be altered or deleted, including by administrators.
Safeguards
Backup & Disaster Recovery
What happens if data is lost or a system fails.
- In Progress
Automated daily backups
Scheduled, encrypted backups of all patient data with a defined retention window.
- In Progress
Tested restore procedure
A documented contingency plan with a restore drill performed and recorded at least annually, as HIPAA requires.
- In Progress
Published RTO / RPO targets
Formal recovery time and recovery point objectives, published here once tested and met.
Safeguards
People & Process
The administrative safeguards behind the technology.
- In Progress
Designated Security Officer and Privacy Officer
Two named individuals formally accountable for the security and privacy programs, as HIPAA requires.
- In Progress
Annual workforce HIPAA training
Required annual training for everyone who touches code, infrastructure, or patient support, with completion records kept.
- In Progress
Annual Security Risk Analysis
A documented, repeated assessment of risks to health information and the plan to remediate them.
- In Progress
Incident Response & Breach Notification Plan
A written plan covering detection, containment, and notification within the timelines set by the HIPAA Breach Notification Rule.
- In Progress
Written policies and procedures
The full HIPAA policy set — sanction policy, workstation use, media disposal, contingency planning, and more.
- In Progress
Background checks for workforce with PHI access
Pre-engagement screening for anyone who can reach patient data.
Vendors
Subprocessors
Every third party that can touch personal or health information, what they do, and whether a Business Associate Agreement governs that relationship.
| Vendor | Purpose | Data touched | BAA status |
|---|---|---|---|
| Google Cloud / Firebase | Application hosting, database, authentication, file storage | Account and health information | Coming Soon BAA execution in progress with Google Cloud. |
| Agora | Live video consultations | Real-time audio and video of consultations | Coming Soon HIPAA-eligible plan and BAA being arranged. |
| Vercel | Website and web portal hosting | Account information in transit | Coming Soon Requires an Enterprise agreement to obtain a BAA. |
| Stripe | Payment processing | Billing information only — no clinical data | No PHI shared Stripe does not act as a Business Associate. We deliberately keep all clinical information out of payment records. |
| PayPal | Alternative payment processing | Billing information only — no clinical data | No PHI shared Same segregation as Stripe: billing data only. |
| Apple / Google push notification services | Mobile push notifications | Neutral notification alerts only (no clinical data) | No PHI shared Notifications are content-free prompts — all clinical content is fetched inside the app after cryptographic authentication. |
Compliance
Our roadmap
Where we are headed, in the order we are getting there. Timelines are targets, not guarantees, and we will update this page as each phase completes.
- In Progress
Phase 1 · Now → 90 days
HIPAA Security Rule remediation
- Close all critical access-control gaps
- Execute Business Associate Agreements with every vendor touching PHI
- Stand up the PHI access audit trail
- Appoint Security and Privacy Officers
- Complete the first documented Security Risk Analysis
- In Progress
Phase 2 · 3 → 6 months
Policy, training, and independent testing
- Publish the full written policy set
- Complete annual workforce HIPAA training
- Third-party penetration test with remediation
- Tested backup and disaster recovery drill
- In Progress
Phase 3 · 6 → 12 months
SOC 2 Type I
- Independent CPA firm attests that controls are designed correctly
- Report available to enterprise partners under NDA
- In Progress
Phase 4 · Year 2
SOC 2 Type II
- Controls proven to operate effectively over a 6–12 month window
- Continuous control monitoring in place
- In Progress
Phase 5 · Year 2+
HITRUST or ISO 27001
- Pursued when required by hospital systems or enterprise health partners
Under NDA
Documentation for partners
Enterprise partners, employers, and provider groups can request the following under a mutual non-disclosure agreement. Items marked Coming Soon do not exist yet — we will not send a document we have not produced.
Sample Business Associate Agreement
In ProgressOur standard BAA template for enterprise and provider partners.
Penetration test summary
In ProgressExecutive summary of our most recent third-party security test.
SOC 2 Type I report
In ProgressAvailable to prospective partners under NDA once issued.
Security Risk Analysis summary
In ProgressHigh-level findings and remediation status from our annual analysis.
Architecture and data-flow diagram
In ProgressHow health information moves through our systems, end to end.
To start a review, write to info@ambewellness.com.
Patients
Your rights
If we hold health information about you, HIPAA gives you specific rights over it.
Access your records
Request a copy of the health information we hold about you.
Request a correction
Ask us to amend information you believe is inaccurate.
An accounting of disclosures
Ask who your information has been shared with, and why.
Request restrictions
Ask us to limit how your information is used or disclosed.
File a complaint
Raise a concern with us directly, or with the U.S. Department of Health and Human Services Office for Civil Rights. We will never retaliate.
To exercise any of these rights, contact info@ambewellness.com. See also our Privacy Policy.
Disclosure
Report a vulnerability
If you believe you have found a security issue, we want to hear from you before anyone else does.
Email info@ambewellness.com with enough detail to reproduce the issue. We aim to acknowledge every report within two business days.
We ask that you give us a reasonable window to fix the issue before disclosing it publicly, and that you avoid accessing, changing, or deleting any real patient data while testing. We will not pursue legal action against researchers who follow this.
A formal bug bounty program is In Progress.
This page describes our security program as of September 2, 2026 and is updated as controls change. It is provided for transparency and is not a warranty, a certification, or a contract. Ambé Wellness is operated by Lakshmi Devi Namaha LLC.