Nobar/sys · Assistant for leaders
Data & security — UK GDPR

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.

We hold no copyEverything stays in your own accounts and your own cloud
ICO registeredRegistration ZC171099
InsuredCyber and data breach insurance
Notifications — rule.notify = NO_CONTENT

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.

No senderNo subjectNo preview
02 — The rules it always keeps
01

Nothing is sent without your tap

rule.send = HUMAN_TAP

It 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.

02

Every outside action needs your confirm

rule.action = CONFIRM_FIRST

Booking, cancelling, sharing, moving, saving a file or writing to a sheet or another system is shown to you first, with undo where possible.

03

It never pays, signs or submits

rule.money = NEVER

It never pays anyone or moves money, never signs anything, never submits forms and never overwrites your existing documents.

04

An email cannot give it orders

rule.inbound = DATA_NOT_COMMAND

Anything from outside is treated as information, never as an instruction.

05

Sums and dates are worked out in code

rule.math = CODE

They are not guessed by the AI. It never invents prices, facts or quotes.

06

No advice

rule.advice = NONE

No legal, financial, immigration or safe to sign judgements. It shows facts, dates and sources.

07

Private by design

rule.scope = OWN_DATA

Each person sees only their own mail, diary, files and recordings. Manager views are counts only, with no rankings or scores of people.

08

Sensitive matters stay with people

rule.welfare = HUMAN

Welfare, medical and safeguarding content is never summarised away, drafted from or read aloud.

09

Notifications carry no content

rule.notify = NO_CONTENT

No subjects, names or previews on a lock screen.

03 — Where your data lives

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.

01Your Google Workspace

Email, calendar, Drive and tasks stay exactly where they are. We read them under each person's own login, and never copy your Drive.

02Your own cloud, in London

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.

03The AI model

Only the text one question needs. It has no access to your systems or to the database, and does not train on your content.

Answers link back to the original file, so your own Drive permissions still decide what opens.The only place text leaves your accounts is the AI model, for one question at a time. Anthropic provides the text AI and ElevenLabs the voice; Anthropic deletes inputs within 30 days and does not train on them.
04 — Security, UK GDPR Article 32

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.

Your own sign in

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.

No master key

Each person connects their own account. There is no domain wide access, so no single credential can read everybody's mail.

Least access

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.

Encrypted throughout

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.

In your account, walled off

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.

Our access, named and logged

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.

Outside content is data, not ordersText arriving in email and calendar is labelled as information, so a message cannot instruct the assistant.
Permissions checked outside the AICode filters to what the signed in person can open before anything is shown.
Built and tested on made up dataWe never use real client data to build, test or demonstrate.
05 — Under UK GDPR and the Data Protection Act 2018

It stays your data. We only process it.

You are the controller
  • 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 are your processor
  • 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
06 — Children's data and safeguarding

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.

Children are never usersOnly named adults on an allow list you control can sign in.
Kept separateYour data, settings and keys sit apart from every other client.
Never real data in testingWe build, test and demonstrate on made up data only.
Your duties stay yoursThe assistant does not replace your safeguarding procedures or Keeping Children Safe in Education. Where health or safeguarding details count as special category data, you set the condition and we help you record it.
07 — Storage limitation, UK GDPR Article 5(1)(e)

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.

90 daysEmail summaries and priority scores
90 daysChat history with the assistant
30 daysTeam chat, if you connect Slack
90 daysMeeting transcripts, only if recording is on
DeletedMeeting audio, once it is written up
Follows DriveDocument index, removed when a file changes, goes or access is revoked
12 monthsActivity log of every action, redacted by default
On exitYou remove our access and the working data is deleted, with a signed note. It was always in your account.
08 — The law, and how we meet it

Mapped to UK GDPR.

TopicReferenceWhat we do
PrinciplesArt. 5We hold only what a feature needs, for a set time, and keep it secure.
Controller and processorArt. 28A written agreement covering instructions, confidentiality, security, sub processors, help with rights requests, deletion at the end and audit information.
Sub processorsArt. 28(2), (4)Listed in a register you receive, with prior notice of any change and a right to object.
Protection by designArt. 25Key limits are written into the code, and higher risk features are off by default.
Records of processingArt. 30(2)We keep our processor record and share it with you.
SecurityArt. 32The measures above, matched to the risk of the data involved, backed by cyber and data breach insurance.
BreachesArt. 33We tell you without undue delay, so you can report to the ICO within 72 hours where required.
Impact assessmentArt. 35Yours to own. We write the technical half.
Transfers outside the UKChapter VThe 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.

Next step

Questions from your data protection lead?

We answer in writing, with evidence, or tell you plainly that we cannot.

Book a call ↗