Your data,handled properly.
Where your data lives, who can see it, how long we keep it, and the rules the assistant is built never to break. Written into the code, not left to the AI.
Your lock screen
stays quiet.
One quiet notice that your brief is ready. No names, no subjects and no previews, so nothing private shows on a desk or a train.
Nothing is sent without your tap
rule.send = HUMAN_TAPIt writes drafts in your own mailbox. Nothing is sent until you say send and tap Send. There is no send all, and nothing runs on a timer.
Every outside action needs your confirm
rule.action = CONFIRM_FIRSTBooking, cancelling, sharing, moving, saving a file or writing to a sheet or another system is shown to you first, with undo where possible.
It never pays, signs or submits
rule.money = NEVERIt never pays anyone or moves money, never signs anything, never submits forms and never overwrites your existing documents.
An email cannot give it orders
rule.inbound = DATA_NOT_COMMANDAnything from outside is treated as information, never as an instruction.
Sums and dates are worked out in code
rule.math = CODEThey are not guessed by the AI. It never invents prices, facts or quotes.
No advice
rule.advice = NONENo legal, financial, immigration or safe to sign judgements. It shows facts, dates and sources.
Private by design
rule.scope = OWN_DATAEach person sees only their own mail, diary, files and recordings. Manager views are counts only, with no rankings or scores of people.
Sensitive matters stay with people
rule.welfare = HUMANWelfare, medical and safeguarding content is never summarised away, drafted from or read aloud.
Notifications carry no content
rule.notify = NO_CONTENTNo subjects, names or previews on a lock screen.
It moves one way only.
Everything runs in your own accounts, on your own servers. We do not keep a copy of your data on our systems. Nothing is written back unless a person asks for it and confirms it on screen.
Email, calendar, Drive and tasks stay exactly where they are. We read them under each person's own login, and never copy your Drive.
A cloud project in your own account holds the working parts: an index of your documents, chat history, email summaries and the activity log. Your account, your keys, nothing kept by us.
Only the text one question needs. It has no access to your systems or to the database, and does not train on your content.
Limits enforced in code.
A rule in a prompt can be talked around, so the important limits are written into the code instead. These are the measures around every deployment.
Each person signs in with their own Google account. Only an allow list you control can get in, so your multi factor and device rules still apply.
Each person connects their own account. There is no domain wide access, so no single credential can read everybody's mail.
Read only for mail and Drive. Calendar and file changes only for the features you switch on, and every permission is explained when a person connects.
HTTPS in transit and encrypted at rest. Each person's Google sign in token is encrypted again with AES 256, with the key held in Secret Manager.
Each client runs in a cloud project in their own account, in the London region, with its own database, secrets, keys, logs and indexes. Nothing is shared and nothing sits with us.
Named people only, with the least access needed and multi factor sign in. You can remove it at any time. No shared logins, and no client data on our laptops.
It stays your data. We only process it.
- You decide what the assistant may read and which features are on
- You set the lawful basis and own the privacy notice and impact assessment
- Your source data never leaves your Google Workspace
- You can withdraw our access at any time, without notice
- We act only on your documented instructions, under an Article 28 agreement
- We hold no copy of your data on our own systems
- We never use your data for our own purposes, for another client or to train models
- We tell you of a breach without undue delay
- At the end we delete or return everything, with a signed note
Built for inboxes that hold children's data.
A leader's inbox in education holds children's, health and safeguarding details. We treat that as the normal case, not the exception.
What we keep, and for how long.
All of this lives in your own cloud account, not with us. Your email, calendar and documents follow your Workspace retention, which we never touch. Every limit is set with you in the agreement.
Mapped to UK GDPR.
| Topic | Reference | What we do |
|---|---|---|
| Principles | Art. 5 | We hold only what a feature needs, for a set time, and keep it secure. |
| Controller and processor | Art. 28 | A written agreement covering instructions, confidentiality, security, sub processors, help with rights requests, deletion at the end and audit information. |
| Sub processors | Art. 28(2), (4) | Listed in a register you receive, with prior notice of any change and a right to object. |
| Protection by design | Art. 25 | Key limits are written into the code, and higher risk features are off by default. |
| Records of processing | Art. 30(2) | We keep our processor record and share it with you. |
| Security | Art. 32 | The measures above, matched to the risk of the data involved, backed by cyber and data breach insurance. |
| Breaches | Art. 33 | We tell you without undue delay, so you can report to the ICO within 72 hours where required. |
| Impact assessment | Art. 35 | Yours to own. We write the technical half. |
| Transfers outside the UK | Chapter V | The AI model runs in the US. The transfer mechanism is recorded in our transfer register. |
A summary, not legal advice. The full statement, data processing agreement and registers are available on request, and our ICO registration number is ZC171099.
Questions from your data protection lead?
We answer in writing, with evidence, or tell you plainly that we cannot.