Security & compliance

Put browser automation for regulated industries on the record.

When an agent signs in to a system that holds regulated data, your reviewers ask what they would ask of any staff member: what it did, where it could go, and who could stop it. Start with those answers, then choose where the work runs.

Healthcare is the regulated work Oya covers by contract. For protected health information (PHI), Oya Cloud and the enterprise edition come under a Business Associate Agreement (BAA).

Book a demo
Oya
BAA
Access
Audit

On Oya Cloud and the enterprise edition.

Conceptual illustration

Start with what a reviewer will ask.

Take one browser task that touches regulated data and list the questions your security or compliance reviewer will ask about it: who acted, on which pages, with which credentials, and what was kept. The sections below answer them in that order.

Keep a record of every action.

Every action by an agent or a person is a row on a hash-chained audit trail, and the database refuses edits and deletes.

  • Audit records are kept for 365 days at least.
  • Recordings expire after 7 days by default.
  • Every staff sign-in as a customer is audited.

Limit who and what can reach the work.

Access is set per project. Each project has owner, operator and viewer roles, sign-in uses TOTP multi-factor authentication, and API keys are stored only as hashes.

  • A project can limit the hosts its browsers may reach. Anything off the list is refused before it leaves.
  • Stored passwords and TOTP seeds are sealed and never shown to the model.
  • Each project can allow only the model providers you choose.
  • Credentials, cookies and recordings are sealed with AES-256-GCM, bound to their tenant, with key rotation.

Keep a person able to step in.

A person can watch any session live, take over and hand it back. When a sign-in needs a person, such as a text-message code, staff take over the session and return it to the agent.

Run it in your own network when data may not leave.

Oya runs as Oya Cloud, or self-hosted on Docker, ECS, GCP or Kubernetes. Self-hosted, pages, recordings and audit records stay in your infrastructure.

  • Oya Cloud: browsers we run for you.
  • Enterprise edition: self-hosted, with the HIPAA offering and a BAA for healthcare work.
  • Community edition: source-available and self-hosted, free up to 5 cloud browsers at once, without the HIPAA offering.
  • Every playbook exports as Playwright code you keep.

Know where the SOC 2 work stands.

Oya holds a SOC 2 Type I report, and its Type II audit is in progress. Send security questionnaires to sales@getoya.ai.

Check which regulations Oya has an offering for.

Oya’s contractual compliance offering today is for healthcare: Oya Cloud and the enterprise edition are HIPAA compliant, and we sign Business Associate Agreements (BAAs). For other regulated industries, the controls above are what Oya provides. This page makes no claim under any other regulation, so map the controls to your own requirements.

Bring your SOP or screen recording. Scope your first workflow with the founders.

Book a demo

Questions

What is browser automation for regulated industries?

Software, often an AI agent, that works web portals under controls a reviewer can check: an audit trail of every action, access roles, limits on the hosts a browser can reach, and a person able to take over. Oya Browser provides these on Oya Cloud and self-hosted.

Is Oya SOC 2 compliant?

Oya holds a SOC 2 Type I report, and its Type II audit is in progress.

Can we run it in our own network?

Yes. Oya self-hosts on Docker, ECS, GCP or Kubernetes, and self-hosted, pages, recordings and audit records stay in your infrastructure. The source-available community edition is free up to 5 cloud browsers at once. The enterprise edition adds the HIPAA offering and a BAA. Write to sales@getoya.ai.

What does the audit trail record?

Every action by an agent or a person, as a row on a hash-chained log that the database refuses to edit or delete. Audit records are kept for 365 days at least.

Is Oya compliant with regulations other than HIPAA?

Oya’s compliance offering is for healthcare: Oya Cloud and the enterprise edition are HIPAA compliant, and we sign Business Associate Agreements (BAAs). Oya also holds a SOC 2 Type I report. It makes no claim under other industry regulations; review the controls against your own requirements.

Does the agent see our passwords?

No. Stored passwords and TOTP seeds are sealed and never shown to the model.