Trust center

Oya runs browsers that sign in to the systems your business depends on. Here is how we protect what they see.

Available

HIPAA, self-hosted

Run the control plane and browsers in your own cloud. Pages, recordings and audit records stay in your infrastructure.

BAA on request

HIPAA, Oya Cloud

A per-project HIPAA mode, with business associate agreements across our subprocessors. 14 of 15 Security Rule controls are verified. Request the BAA at enterprise.oyabrowser.com/trust.

Every release

Evidence pack

Each HIPAA Security Rule control is mapped to the code that implements it and a check that runs against it. Gaps are listed, not hidden.

Security practices

Encryption

TLS in transit. Credentials, MFA seeds, cookies, proxy credentials and recordings are sealed with AES-256-GCM, bound to their tenant, with key rotation.

Tamper-evident audit trail

Every privileged action is written to a hash-chained log. The database refuses edits and deletes, and the chain head is anchored outside it.

Access control

TOTP multi-factor sign-in, owner, operator and viewer roles per project, API keys stored only as hashes, and every staff sign-in as a customer audited.

Network containment

A project can limit the hosts its browsers may reach. Anything off the list is refused before it leaves.

Retention and deletion

Recordings expire after 7 days by default. Audit records keep a retention floor. Deleting a project or an account erases its data.

Minimal telemetry

Error reports drop request bodies, headers and cookies and scrub emails. Product analytics never carries URLs or page content.

HIPAA Security Rule controls

Generated from the code on 2026-10-07. Read the full evidence pack, with the check behind each verdict.

ControlRequirementStatus
Audit controls§164.312(b)Record and examine activity in systems that contain or use ePHI.Met
Integrity§164.312(c)(1)Protect ePHI from improper alteration or destruction.Met
Mechanism to authenticate ePHI§164.312(c)(2)Corroborate that ePHI has not been altered or destroyed.Met
Person or entity authentication§164.312(d)Verify that a person seeking access is the one claimed.Met
Transmission security§164.312(e)(1)Guard against unauthorised access to ePHI in transit.Met
Information access management§164.308(a)(4)Authorise access to ePHI only as appropriate, minimum necessary.Met
Encryption and decryption§164.312(a)(2)(iv)Encrypt and decrypt ePHI, including credentials at rest.Met
Minimum necessary, recordings and logs§164.502(b)Limit PHI in what is stored to the minimum necessary.Gap
Business associate contracts§164.308(b)(1)A BAA with every subprocessor that handles ePHI.Gap
Documentation retention§164.316(b)(2)Retain required documentation for six years.Gap

Subprocessors

Third parties that process customer data for Oya Cloud. Self-hosted deployments use none of them.

CompanyPurposeData
Google CloudHosting of the control planeAll service traffic
SupabaseDatabase, sign-in and recording storageAccount data, settings, recordings
DaytonaCloud browser sandboxesPages visited by cloud browsers
OpenAI, Anthropic, GoogleAgent models, when Oya’s key is usedPage content the agent reads
StripeBillingBilling contact and payment details
SentryError reportingScrubbed error reports
PostHogProduct analyticsAccount identifier and email
CloudflareBot check at sign-upVisitor IP and browser signals
SlackInternal sign-up and billing alertsAccount email

Contact

For a business associate agreement, a security questionnaire or our policies, write to sales@getoya.ai. To run Oya in your own cloud, read the self-hosting guide. To report a vulnerability, open a private security advisory.