Braio

Agent controls

Czytaj po polsku

AI agent security - access, approvals and costs

Deploying an agent means deciding which data it accesses, which actions it performs and who makes decisions. Braio provides roles, approvals and usage accounting; their scope must fit the process.

This describes product mechanisms and deployment questions. It is not a certificate, a security audit report or an assurance that every deployment meets every requirement.

Content reviewed:
01

Private financial files and profile

Financial file and result access is checked against organization, owner and conversation. A private financial profile belongs to its owner within an organization; it is not automatically a company-wide policy. An agent proposal does not activate a profile: explicit human review and approval are required.

The public demonstration pack contains synthetic data only. Before using company data, confirm actual retention, deletion and subprocessors for your deployment. A tool description is not an additional certification, data-region or provider-training promise.

02

Who provides the service

Under the published terms, the Braio service is provided by Braio sp. z o.o., based in Warsaw, KRS 0000603234, tax ID NIP 5213723593. Braio is the product name. The terms and privacy policy linked in the footer describe service terms and data processing.

03

Identity and access scope

User roles, organization membership and integration permissions define the scope of work. Before connecting sources, review Braio configuration and permissions in the external system.

Start with the minimum required access. Also test what happens after access is revoked and who can see a task's result.

04

Approvals and responsibility

Risk policies and approvals apply to specific operations. Do not assume every action always needs approval or that all actions are autonomous. Agreeing on rules and decision owners is part of process setup.

For example, the QA fix loop requires a person to review and merge the PR. Other automation can have different settings and should be assessed separately.

05

Costs and work history

Model usage and task execution have costs. Accounting and cost consent mechanisms help control selected operations, but do not replace checking workspace plans, limits and configuration.

Confirm the availability, scope and retention of history during rollout. We do not promise a specific retention period or unlimited logging here.

06

Questions about data and providers

Before sharing data, agree on the processing model, providers, integrations and organization requirements. We do not make unverified promises about data residency, on-prem deployment, certifications or model training.

  • Which data is needed and where will it be processed?
  • Who can grant, revoke and review access?
  • Which agreements, retention rules and reporting procedures apply to this deployment?
  • How can work be stopped and who reviews sensitive results?

Questions and answers

Does this page establish ISO or SOC 2 certification?
No. We do not attribute a partner's or provider's certification to Braio. Agree on the required evidence during assessment of the specific deployment.
Can an agent make a mistake?
Yes. Scope, permissions and approvals reduce risk but do not guarantee a correct result. Important decisions and artifacts need appropriate review.