What is a HIPAA-compliant browser?
A HIPAA-compliant browser lets people and AI agents work on pages that show protected health information (PHI) under the controls HIPAA expects: a signed business associate agreement (BAA), access control, and a record of who did what. Oya Browser is a HIPAA-compliant browser on Oya Cloud and the enterprise edition, where we sign BAAs. It is also an AI browser and an agentic browser for healthcare teams.
What a HIPAA-compliant browser needs
When a browser, or an agent driving one, opens a payer portal, an EHR or a registry, it sees PHI. HIPAA then asks for these things.
- A business associate agreement with the company that runs the browsers.
- Access control: only the people and agents you allow, and only the systems you allow them to reach.
- An audit trail of every action, that nobody can quietly change.
- Control over where the data lives: your own network, if you need it.
- A person who can watch and take over.
How Oya Browser does each
Oya runs browser agents on payer portals, EHRs and registries, and keeps the controls in the browser itself.
- We sign BAAs. Our SOC 2 Type II audit is in progress.
- Every action, by an agent or a person, is a hash-chained audit row the database refuses to edit or delete, kept for 365 days at least.
- Oya Cloud, or the enterprise edition in your own infrastructure (Docker, ECS, GCP or Kubernetes), so PHI can stay in your network.
- A person can watch any session live, take over and hand it back.
- Browsers reach only the hosts you allow.
An AI browser and an agentic browser
The Oya desktop app for macOS and Windows is an AI browser: you browse, and an agent can take a tab while you can take it back. Oya Cloud and self-hosted Oya are an agentic browser for teams: agents run many browsers at once, each one on the audit trail.
Questions
Is there a HIPAA-compliant AI browser?
Yes. On Oya Cloud and the enterprise edition, Oya Browser is an agentic browser built for healthcare: HIPAA compliant, we sign BAAs, and every agent and person action lands on a tamper-evident audit trail.
Can AI agents access PHI in a browser?
Under a BAA and with the right controls, yes. Oya records every action on a hash-chained audit trail, lets browsers reach only the hosts you allow, and lets a person take over any session. Self-hosted, pages, recordings and audit records stay in your network. Recordings are not yet redacted for PHI in the community edition; turn recording off for sessions that show PHI.
Does Oya sign a BAA?
Yes. We sign BAAs. Write to [email protected].
Is Oya SOC 2 certified?
Our SOC 2 Type II audit is in progress.
Can I self-host a HIPAA-compliant agentic browser?
Yes, with the enterprise edition: it runs on Docker, ECS, GCP or Kubernetes, comes with a BAA, and keeps HIPAA workloads in your own infrastructure. Write to [email protected]. The source-available community edition self-hosts too, without the HIPAA offering. Every playbook exports as Playwright code you keep.