Security

Written for
your security team

This page is written for your security and procurement teams. The short version: we read your data where it lives, with read access you grant yourself, plus drafts a person sends. A person approves wherever a mistake costs money, and every action the agent takes is logged. What is not yet built is stated below, not implied.

Sign in with Google

Panorithm wants access to your Google Account

Ss.mokoena@kestrelcinemas.example

This will allow Panorithm to:

Read your email messages and settingsIncluding attachments, and scans or photographs of paper
Create drafts in your mailboxA draft only. You press send
See and edit only the files it createsThe rest of your Drive stays invisible to it
Not on this screen, because it was never asked for: sending, deleting, altering anything, or changing a single setting. There is no permission to switch off later.
CancelContinue

This is the screen. Each person grants it in their own name, and can withdraw it on Google's own account page without asking us.

On your mailboxes it cannot send, delete or change anything

by design

The permission was never requested. Not withheld in a setting somebody could turn on later, and not enforced by our own code: it is absent from the consent screen your people approved, so the capability does not exist in the token. Drafts are written and left in your drafts folder. A person presses send. Elsewhere, agents do the work inside your systems, and anything that leaves the business, an email, a payment or a filing, waits for a person to approve it.

Each person connects their own mailbox

live

Through Google's own consent screen, in their own name, and they can withdraw it there without asking us. Nobody connects a colleague's mailbox on their behalf, and an administrator cannot connect the company's mail in one action.

GrantedRead mail and metadata, create drafts Never grantedSend, delete, modify, change settings, manage filters DriveOnly files Panorithm created itself, never the rest of the drive

Every answer shows the document it came from

live

Nothing is asserted without the email or the file beside it. When the answer is not in your mail, it says so rather than inventing one. That is a property of the product, not a habit we ask it to keep.

Sharing outside the company is a link, not an account

live

An auditor or an accountant opens a link that expires, and it only ever opens the documents somebody at your company approved in advance. They get no account, they cannot search anything, and the link stops working on its date whether or not they used it.

Default life14 days ScopeThe approved documents only ApprovalA person at your company, before it is sent

Stored in Johannesburg, and yours

live

Your data is never used to build anything for anyone else, and never used to train a model. POPIA aligned, and the detail is published rather than summarised.

Who has checked us

MetaVerified as a Tech Provider GoogleOAuth verification passed for the scopes above

What is not built yet

honest

Single sign-on, per-document retention rules, and an audit export a compliance officer can read without asking us. None of it exists today. It is on the changelog when it ships, and not before. Department-level scoping and deployment inside your own environment are in build. Say so on enquiry and we will tell you honestly where each stands.