
Security
Security and compliance checklist for AI employees: 12 questions to ask
Aug 3, 2026 · 9 min read
Updated Oct 31, 2026
A security and compliance checklist for an AI employee covers five areas: where your data lives and how it is encrypted, who can read it, what is recorded, how the AI is kept from saying or doing the wrong thing, and what the contract commits to. Put the twelve questions below to every vendor and get the answers in writing before a pilot starts.
Unistaff answers all twelve below, gaps included. The full list — 26 controls that run and 20 that do not exist yet — is on the security page.
The 12 questions, with what a good answer includes
| Question | A good answer includes | Unistaff today |
|---|---|---|
| 1. Where is our data stored, and is it encrypted? | The hosting provider, encryption in transit and at rest, backup retention | TLS 1.2/1.3 with two-year HSTS; nightly backups with an integrity check, kept 14 days; disk encryption at rest that we can document is on the not-built list |
| 2. Is our data separated from other customers? | How separation works, in plain words | Every record in the product carries a company id and every read filters by it; database-level row security between companies is on the not-built list |
| 3. Who can read a full customer record? | Named roles, masking for everyone else | The manager named for the pilot sees your company and no other; the Unistaff operators who set up and review pilots see every company |
| 4. What material does the AI need? | The minimum to start, and who approves it | Your public website, read into a draft knowledge folder, plus the prices, hours, contacts and never rules you add and approve |
| 5. How do our people sign in? | SSO, MFA, per-user roles, offboarding | Pilot cabinet access for one email address; logins for your own staff are planned; SSO and MFA do not exist today |
| 6. What can the AI do without a person? | Levels of autonomy, approval as the default | Trainee: every reply waits for you. Junior: sends from the price list. Independent: adds ready-to-pay handovers and follow-ups if switched on |
| 7. Can we stop it at once? | Pause, takeover, a stop for everything | Pause, conversation takeover and a company-wide stop button in the cabinet |
| 8. What is recorded, and can we export it? | Conversations, actions, approvals; an export path | Every conversation is readable in the cabinet and leads export as CSV; customer-facing audit-log search and export do not exist yet |
| 9. How does it avoid inventing prices or promises? | Checks that run in code before a reply leaves | Prices only from the approved list; a number outside it is stopped and replaced with “I will check with the team”; customer messages are treated as data, never as instructions |
| 10. Does it say it is an AI, and when does it hand over? | Disclosure, explicit handover triggers | Says so in its first message and keeps an AI badge; hands over on HUMAN, a complaint, an emergency, legal, tax or medical questions, or a customer ready to pay |
| 11. How is it tested before customers see it? | A repeatable test with mandatory safety cases | Twelve trade cases, each run three times; every safety, “give me a human” and complaint case must pass; the exam log is public |
| 12. What will you sign, and which certifications do you hold? | DPA, subprocessor list, SOC 2 or ISO 27001 reports | Unistaff holds no certification of its own and none is in progress; no DPA, subprocessor list or standard contractual clauses are drafted yet; no external penetration test |
Data: where it lives and who reads it
Ask for the hosting provider by name, how traffic is encrypted, how storage is encrypted and how long backups are kept. Then ask who can read a full customer record, because encryption at rest protects a stolen disk and does nothing about a colleague with too much access. A good vendor masks records for everyone outside a named role and can tell you how separation between customers works without reaching for a diagram.
Keep the material small at the start. A pilot that begins from your public website and a price list puts less of your data in the vendor’s hands than one that begins with a CRM export, and it still shows whether the AI answers well.
Access: your people and the AI
Two kinds of access need answers. Your people: how they sign in, whether there is single sign-on and multi-factor authentication, and what happens when someone leaves. The AI: what it may do without a person. The safest default is approval for everything, with autonomy granted step by step and taken back automatically when something goes wrong. At Unistaff the employee starts as a Trainee and is demoted on its own after three rule hits in seven days, a thumbs-down share of 30% or more once five replies are rated, a missed handover or a complaint.
Records: what you can read back
When an AI makes a mistake you need to see the conversation, what it was answering from and who approved what. Ask whether conversations are kept and readable, whether approvals are recorded with a time, and whether you can export the record for an audit. If the logs are internal and have no export, ask the vendor for a date in writing.
Behaviour: the rules every reply must pass
Next to data security, an AI employee carries a second risk: what it says. Ask which rules are enforced in code on every reply, as opposed to being written into a prompt the model may ignore: price checks, AI disclosure, handover triggers, topics it must refuse. Ask how a customer message that tries to give the AI instructions is handled. Ask to see the test the AI passed before release, with the failed runs left in.
The exam log shows Unistaff’s own sittings with every run, including a correct refusal the grader misread and a graduate that never asked about the house.
Contract and certifications: what to get in writing
A data processing agreement, a list of subprocessors and the vendor’s certifications belong in the contract file. Read certifications carefully: a hosting provider’s SOC 2 or ISO 27001 report covers the provider’s platform and says nothing about the application running on it. If a vendor is missing any of these, decide before the pilot whether your rollout depends on it.
How to run the checklist in a pilot
- Send the twelve questions before the pilot and keep the written answers with your contract file.
- Start from public material: your website and price list, no customer exports.
- Keep the AI at the approval-first level for the first weeks and read what it drafts.
- Try the handover yourself: type HUMAN, complain, ask a tax question, and check who is told.
- Read the exam results, including the cases that failed.
- Decide at the pilot review which of the missing controls your next stage needs, and ask for dates in writing.
Questions about AI employee security and compliance
Twelve questions across five areas: where data is stored and how it is encrypted, separation and who can read full records, sign-in and what the AI may do without a person, what is recorded and exported, the rules every reply must pass, and the contract and certifications.
Data handling: hosting, encryption, backup retention, masking and who reads full records. Human oversight: approval as the default, explicit handover triggers, a stop button, readable conversations and automatic demotion when the AI breaks a rule.
Unistaff holds no certification of its own and none is in progress. Hosting providers publish their own certifications, which cover their platforms and say nothing about this application.
Both are absent today, along with MFA and per-user accounts for your staff. Write to hello@unistaff.ai before you build a rollout plan that depends on them.
Traffic runs over HTTPS on TLS 1.2 or 1.3 with two-year HSTS. The product database is backed up every night with an integrity check, and the copies are kept for 14 days. Disk encryption at rest that we can document is on the not-built list, so plan around it as absent.
Prices come only from the approved list; a number outside it is stopped before sending and replaced with “I will check with the team”. Bookings are recorded as requests and a person confirms the time.
- Security at Unistaff: 26 controls that run, 20 that do not yetSecurity
- Exam log: every run of 17 sittingsExams
- The rules the Live role keeps on every replyLive role
- AI employee FAQ: data, control, pilot and pricingFAQ
- How to train an AI employee on your company knowledgeGuide
- Pricing: a free 30-day pilot, then one flat feePricing