Security and trust center
What we do to protect the records you keep in Kaivo Health EHR, stated plainly and kept up to date.
Status as of
Kaivo Health EHR is built to HIPAA requirements, with security controls designed to align with the SOC 2 Trust Services Criteria and ISO/IEC 27001. No SOC 2 examination or ISO/IEC 27001 certification has been completed yet.
We will update this page when an independent SOC 2 report or an ISO/IEC 27001 certificate exists.
Business associate agreement
We sign a BAA with every customer.
Our BAA includes every provision HIPAA requires in a business associate agreement, including breach reporting, subcontractor agreements and the return or destruction of records when service ends. It includes 42 CFR Part 2 qualified service organization terms for substance use disorder programs.
Kaivo Health EHR is owned by Priestly Consulting LLC, a Utah limited liability company, which signs the BAA with each customer. Gpenda Technologies builds and runs the platform as its subcontractor, and is bound by a subcontractor BAA with the same Part 2 terms before any customer's patient data enters Kaivo Health EHR.
Where patient data lives
Patient data is stored and processed only in US data centers, on Google Cloud in Iowa, with backups in South Carolina. Google's HIPAA Business Associate Addendum was accepted for the Kaivo Health Google Cloud account on November 11, 2026. Emails to patients are sent through Amazon SES in Northern Virginia, under the AWS Business Associate Addendum accepted on November 13, 2026.
Our engineering team at Gpenda Technologies works mainly from Canada, through a platform console that shows no patient data. Server access is possible only through Google's Identity-Aware Proxy, and every session is logged. A customer whose contract requires US-only administration gets a US-based admin.
Kaivo Health EHR has not launched yet. The controls below are the ones the platform is being built with.
Security controls
| Area | What we do |
|---|---|
| Sign-in | Multi-factor authentication for every user, session timeouts and quarterly access reviews. Personal PIN switching on shared tablets is coming soon, and single sign-on for Network plans is planned. |
| Access | Role-based and site-based access with least privilege by default. Emergency "break-the-glass" access requires a reason and is reviewed. |
| Separation between customers | Each customer's records are walled off in the database with row-level security that is enabled and forced on every table. Automated tests try to cross that wall on every code change. |
| Encryption | TLS 1.2 or higher in transit. Encryption at rest on every disk, snapshot and storage bucket, with separate keys for backups and for each customer's documents and most sensitive fields. |
| Audit trail | Every view and change is recorded in an append-only audit log. Customers can search their own log. Audit records are kept for at least 6 years. |
| Secure development | Code review on every change, automated scanning of code, dependencies and secrets, and only tested, signed builds reach production. Development uses synthetic data only. |
| Vulnerability management | Critical security patches within 7 days. An independent penetration test before launch, then every year. |
| Monitoring and response | Security monitoring and alerting, a written incident response and breach notification plan, and tabletop exercises twice a year. |
| Backups and recovery | Daily server snapshots and continuous database backup in a second US region, with quarterly restore drills. Targets: no more than about 15 minutes of data lost, and service restored within 4 hours. |
| People | Background checks, and security and HIPAA training at hire and every year. |
| Vendors | A business associate agreement with every service that handles patient data, and a yearly vendor review. |
Availability: 99.5% monthly uptime is promised in customer contracts, with service credits if we miss it. A public status page hosted outside our servers is coming soon; until then we email customers about outages and maintenance. Support targets: a first reply within 2 business hours, and within 30 minutes at any hour for an urgent (P1) problem.
AI and your data
Every Kaivo Health EHR feature works without AI, and there are no AI features at launch. The Kaivo AI add-on is planned for a later phase and is not sold until it exists. It will be optional and off by default. When a customer turns it on, it will use Google's Gemini models through a Google Cloud service covered by Google's BAA. It will be staff-facing only, produce drafts that a named person reviews and signs, and never write to the medication record, submit a claim or assign a diagnosis.
Subprocessors
As of . Only services under a signed business associate agreement may receive patient data. We give customers at least 30 days' notice before adding a subprocessor that will handle customer data.
| Company | What it does for us | Location | Patient data |
|---|---|---|---|
| Google Cloud | Hosting: servers, database, file storage, backups, logs, encryption keys and sign-in | United States (Iowa, with backups in South Carolina) | Yes, under Google's HIPAA Business Associate Addendum, accepted November 11, 2026 |
| Amazon Web Services (Amazon SES) | Sends emails to patients and clients for practices, such as portal invitations and sign-in links | United States (Northern Virginia, us-east-1) | Yes, under the AWS Business Associate Addendum, accepted November 13, 2026 |
| Resend | Email to practice staff and business contacts only, such as staff invitations and billing notices | Resend's email service; Resend, Inc. is a United States company | No. Resend never carries patient information or patient email addresses |
| Cloudflare | Domain name system (DNS) for kaivohealth.com, delivery of this public website (including what you send through its contact form, on its way to our servers), and forwarding of email sent to our kaivohealth.com addresses to the inboxes our team reads | Cloudflare's worldwide network, at the data center nearest each visitor or sender; Cloudflare, Inc. is a United States company | No. We never send it patient information, and app, portal and API traffic does not pass through Cloudflare. Please do not put patient information in our contact form or in email to our addresses |
| Stripe | Subscription billing for practices only | Stripe's payment network; Stripe, Inc. is a United States company | No. Stripe receives the practice's billing details, never patient information |
Gpenda Technologies' team works mainly from Canada, through a platform console that shows no patient data. Gpenda Technologies is bound by a subcontractor BAA before any customer's patient data enters Kaivo Health EHR. Email to our kaivohealth.com addresses is forwarded through Cloudflare and is not a channel for patient information.
Cookies on this website
This website uses no advertising, analytics or cross-site tracking cookies, and loads no scripts, fonts or images from other companies.
It stores one item in your browser's local storage, kaivo-cookie-notice, to remember that you closed
the cookie notice. You can clear it at any time in your browser settings.
The Kaivo Health EHR app and patient portal use only essential cookies to keep you signed in and secure.
Report a security concern
Email security@kaivohealth.com, or use our contact form and choose "Security report". Please do not include patient information. We can share our security documents with customers and serious prospects under a non-disclosure agreement.
Start your 30-day free trial
Solo and Practice start free for 30 days, with no card. Or look around the demo clinic first: it uses fictional data only. The first 25 practices to subscribe get 20% off for 24 months. We apply it when you subscribe.