Access control
Roles instead of shared passwords, two-factor sign-in, reviewed on a schedule.
roles.ymlService / Data protection
Who can access what, encrypted backups and logs, then a full restore you watch. Staff use of AI is covered too.
01 / What you get
Roles instead of shared passwords, two-factor sign-in, reviewed on a schedule.
roles.ymlCopies kept off-site, separate from the systems they protect.
backup-plan.mdA full restore to an isolated copy, timed, with you watching.
GDPR Art. 32(1)(c)Who signed in and what changed, kept for an agreed period.
audit.logWho does what in the first hours, including the 72-hour notice.
GDPR Art. 33Client data kept out of personal chatbots.
AI data leakage →02 / How it runs
Review
data, people, systems
Plan
controls, in writing
Set up
access, backups, logs
Test
a restore, with you
Repeat
on an agreed schedule
03 / Example
Illustrative. Accounts and times are invented.
Example · invented data
04 / What to send us
06 / FAQ
No supplier can promise that. We set up and document technical measures of the kind GDPR Article 32 asks for. Policies and the legal assessment stay with you.
GDPR asks for regular testing of security measures (Article 32(1)(d)) without fixing a period. We agree a schedule with you and log each test.
Yes. Our AI data-leakage page sets out the risks and the setup we recommend: a local model, or business versions of the tools under contract, with logs.
No. We set up and check the controls. A formal penetration test is a separate job for a specialist.
Where your data is, who can reach it, how you back it up.