Skip to content

See what enters your business record and who can act on it.

Connect business sources, set access by role and review how information is retained. Follow a governed action from its request through its check, approval and recorded outcome.

Your business
AgreementsConversationsWork records
Access follows the person and the purpose.

Relevant business context, within granted permissions.

Your peopleYour AI agents
Private conversations and personal toolsSeparate from shared business knowledge

Set access around the work each person owns.

Source connections, company administration and business knowledge have separate permissions. Each person sees and does what their role allows, including when they ask a question or start an action.

People & access
RW

Set company roles, agent grants and knowledge access separately.

Ryan Walker

Company role

Administrator

Manages company settings and membership.

Agent grant

No access

Has no access to the Agents portal.

Knowledge access

Detail with evidence

Can inspect permitted knowledge and its supporting evidence for the selected kinds of records.

A role sets the boundary.

Roles define what a person can read and do. Questions and actions use the same permission checks as the rest of the service. Asking does not grant more access.

Private stays personal.

Your private conversations and personal notes are not visible to company administrators. An explicit contribution is required before private information enters the company record.

A company has its own record.

Business records are scoped to your organization in the application. Additional database boundaries depend on the deployment. Your security review can examine how these controls protect both source access and retained knowledge.

Keep useful business knowledge with a clear lifecycle.

Raw documents and messages are temporary by default. Extracted facts, summaries and source references form the business record and follow their own retention and deletion processes.

Information and retention
Information used

Connected sources

Authorized documents, messages and business records from the tools you connect.

What is retained

Extracted facts, summaries and source references. Raw documents and messages are temporary by default; authorized evidence can be fetched again.

Disconnecting a source stops new collection. Retained facts and required history follow their own retention and deletion processes.

Your business memory grows from your work, not model training.

As people work, new records, decisions and outcomes update the company’s own business memory. We never use your business data to train our models. External AI providers process request content under their own applicable data-use and retention terms, which your security team can review.

Security
RW

Protect the way people sign in.

PasskeysPasswordless sign-in
Multi-factor authenticationAn additional identity check
Active sessionsReview and revoke access

Secure sign-in and connected credentials.

Members can sign in with Google, passwords or passkeys, and add multi-factor authentication. Review active sessions and revoke access when it is no longer needed.

Information is encrypted in transit and at rest. Credentials for connected tools are encrypted separately for each organization. Review key custody and deployment arrangements with our team.

Follow the action, the check and the outcome.

Each recorded action can show who requested it, which rule version applied, who reviewed it and what outcome followed. Your team can examine the full chain when an action needs explanation.

On connected execution paths, rules can hold an action before it happens. Imported logs record activity after the fact. The evidence shows which path took place.

Audit record

Follow the decision through.

1
The request

Who or what proposed the action

2
The rule

The exact version checked at the time

3
The review

The responsible person and their decision

4
The outcome

What the connected tool confirmed

A fixed account for a defined scope and period

Review the environment before you connect.

Examine data flows, hosting arrangements and available evidence with your security team. The service runs on Orcinta-operated Google Cloud infrastructure in US regions.

Your data

Sources, permissions, retention and deletion requirements.

Your environment

Hosting region, encryption, key custody and connectivity.

Your providers

Subprocessors, AI data flows, processing terms and training restrictions.

Agree the hosting your business needs.

Dedicated hosting and customer-owned storage are scoped engagements. Customer storage changes where data rests; it does not move processing. Accounts, sessions, billing and the web interface remain centrally hosted in US regions.

Review the evidence behind the assurances.

Discuss AI provider terms, subprocessors and current assessment evidence. No SOC 2 attestation or ISO 27001 certification is currently claimed. Full customer-hosted and air-gapped installations are not currently offered.

Questions for your security review.

Which sign-in and access controls are supported?

Members can use Google sign-in, passwords or passkeys, and add multi-factor authentication. Active sessions can be reviewed and revoked. Company roles determine what each member can read and do.

How is information encrypted?

In transit, always. At rest, with the cloud provider’s encryption, and credentials for connected tools are encrypted separately for each company. Ask about key custody and customer-managed keys during your review.

Do you use our data to train your models?

No. We never use your business data to train our models. Orcinta’s understanding grows through your connected records, decisions and outcomes. That business memory is separate from model training. External AI providers process request content under their applicable data-use and retention terms, which you can review with our team.

Can we review your subprocessors?

Yes. Request the current subprocessor register during your security review. Confirm which providers receive which information and the processing terms that apply to your deployment.

Does disconnecting a source delete everything learned from it?

No. Disabling a connection stops new collection, but does not automatically erase extracted facts or required history. Retention, privacy and deletion processes govern those records separately.
Read the privacy policy

Can the entire service run in our own cloud?

Full customer-hosted and air-gapped installations are not currently offered. Dedicated hosting and customer-owned storage are scoped engagements. Customer-owned storage changes where data rests; processing stays in the service’s environment, and accounts, sessions, billing and the web interface remain centrally hosted in US regions.

Are you SOC 2 attested or ISO 27001 certified?

No SOC 2 attestation or ISO 27001 certification is currently claimed. Framework mappings and verifiable records can support a review, but do not replace independent assurance. Ask for the current assessment status and available evidence.
Explore compliance frameworks

What does a verified receipt establish?

Verification checks the integrity of a recorded event or shared packet. It does not establish that the underlying action was correct, that every event was captured or that the company is compliant.
Decisions & evidence

What happens if we leave?

You can export your company’s record and then request deletion. The export, the deletion process and its timing are set out in the agreement and the privacy policy, and private member data is deleted with the member.
Read the privacy policy

Report a security concern.

Send the affected feature and steps to reproduce the issue. Keep credentials and private customer content out of your report. Reports are acknowledged; good-faith research that follows this guidance will not be met with legal action.

Essential

Always on

Remembers your cookie choice for 180 days so it can be respected on your next visit.

No analytics or advertising cookies are currently used on this website. Closing this window leaves your saved choice unchanged.