Meeting transcripts are the most sensitive text your company owns.
So the boundary is enforced in the database, the credentials are encrypted, the scopes are read-only, and every privileged action is written to an audit log your owners can read.
How isolation is enforced
Row-level security
Each query runs inside a transaction bound to one organisation. A bug in application code cannot read another tenant's rows, because the database refuses them.
Search is scoped too
Keyword and vector retrieval both filter by organisation before ranking, and the isolation is covered by tests that deliberately aim a query at another tenant's data.
Encrypted credentials
Microsoft refresh tokens are encrypted at rest, held server-side only, and revocable from your connections page or from Entra ID.
Audited support access
Staff access is a separate, explicitly flagged path. Where it happens it is recorded with the actor and the reason, and shown in your audit view.
Where your data goes
Turning AI search off keeps every transcript inside your workspace: capture, notes and keyword search run entirely on our own infrastructure.
Reviewing us?
We’ll send the security questionnaire, the data processing agreement, the list of subprocessors, and the Graph permissions we request with the reason for each.
Request the security packReporting a vulnerability
Mail security@notesai.com. We acknowledge within one working day and will keep you updated until it’s closed. We don’t pursue researchers acting in good faith.