Security

Built for your security review.What we store, and what is still on the roadmap.

Ogno is designed never to see more, or do more, than your people allow. This page covers what that means in practice, what we store, and what is still on the roadmap.

SOC 2 Type II: In progress
Training on your data: Never
Credentials: Server-side only
New sources: Off by default

See what Ogno can reach.

Switchboard is the page a team owner opens to answer “what can Ogno see here?” Every source and tool is listed with its switch, and the change applies on Ogno's next call.

Try turning on the tenant_ssn table. The organization has closed it, so a team can't open it.

Switchboard · #operations

2 pending

Waiting on a person

Send the renewal summary to 4 customers
gmail.send
Change Acme Freight's renewal date to Nov 14
salesforce.update
Waiting for the request above
drive.readRead the ops handbook in DriveAllowed

Sources · #operations

Drive · Ops handbook
Read live, cited in every answer
Database · leases
Approved queries only
Database · tenant_ssn
New table, arrived switched off

Actions

Gmail · draft
Write drafts in the thread
Gmail · send
Always asks a named person first

What Ogno can read

Switchboard lists every source, table and tool Ogno can reach in a team, each with its own switch.
The organization sets the ceiling. A team can switch off what the organization opened, never open what it closed.
New tables, folders and tools arrive switched off.
Ogno reads with the access its team was given, not by mirroring each person's permissions.

What Ogno can do

Every tool is set to on, ask first, or off.
Sending, spending, sharing and deleting can never be set to run without asking.
An approval names one person, shows the exact request, and only that request is sent. The decider is never Ogno.
Email ends as a draft unless someone added a send step on purpose. An unanswered request does nothing.

Isolation

Every read and write is scoped to your organization and permission-checked on the server, not left to the model's judgment.
Each person and team has its own Ogno, with its own connections, memory, knowledge and sandbox.
Content Ogno reads cannot grant it permissions: the model drafts, and only an allowed action or an approved request changes another system.

Identity and roles

One organization owner, organization admins, members, and team owners for each team.
A Slack account links to an Ogno account only through a verified email address.
Single sign-on is available for pilots. SCIM provisioning is on the roadmap.

Models

Model providers and subprocessors are listed in the security package, with their terms.
Ogno does not train models on your data.

Audit

Every run and every approval is recorded, with who decided and what changed.
Administrative actions are logged.
Log export to your SIEM is on the roadmap.

What Ogno stores

Retention periods and hosting region are set in your agreement and detailed in the security package.

What	What it holds	Kept within
Map of your company	Names, links between systems and owners. Not copies of your records.	Per person, team and organization
Memory	What people and teams told Ogno. Visible to them, and they can make it forget.	Personal memory never reaches a team
Run records	What ran, who approved it and the result, as redacted summaries rather than raw payloads.	Per organization
Sandbox files	Scripts and reports Ogno builds while working.	The scope's own isolated workspace
Approvals	Who decided what, on which exact request, and when.	Per organization
Your documents and records	Not stored. Read live from the source each time, and cited.

Security package

Our architecture overview, data inventory with retention and region, model providers and subprocessors, and SOC 2 status, sent to your security team.

Request the security package.For your security team.

Tell us where to send it.