AI employee security, control by control.
26 controls run today in the AI sales manager, its cabinet and this website, each one traceable to a line of code or a live response. The 20 that do not exist yet are listed in full, so a procurement checklist can be answered in one pass.
Live posture
Fail-shut
In one paragraph
Is an AI sales employee safe on your website?
The AI sales manager answers only from your approved knowledge folder and price list, and the rules that matter run in code before a reply leaves: it says it is an AI, quotes only listed prices, makes no promises, sends no payment details and hands HUMAN, safety and complaints to a person. You can pause or stop it at any time.
Unistaff holds no certification, and SSO, a second factor and a signed DPA are not built. Those sit in the right-hand column below, next to everything that runs.
Check it yourself
The graduates on the live demo run under the same rules. Ask one for a discount, type HUMAN, or ask whether it is a bot.
Fail-shut, in five conditions
Number missing from the price list
Reply stopped, “I will check with the team”
Customer types HUMAN
Handover with a summary
Employee paused or stopped
Fixed line, a person will answer
Second injection in a day
Silenced for 24 hours
Trainee draft waits 3 minutes
Holding line and escalation
The path of one message
Eight gates between a customer and a reply.
The model writes the draft at gate five. Everything around it is plain code that does not read the prompt, so a customer cannot argue it away.
- 01
Rate limit
Stops with · Too many requests: wait a minute or call the company
- 02
Stop, pause, hours
Stops with · Fixed line: a person will answer
- 03
Handover triggers
Stops with · HUMAN, safety, complaint, legal, card details → a person
- 04
Injection check
Stops with · Redirect; a second attempt silences it for 24 h
- 05
Draft from your folder
Stops with · A question the folder does not cover → handed to a person
- 06
Validator
Stops with · Unlisted number, promise, payment detail → reply stopped
- 07
Trust level
Stops with · Trainee: waits for the owner, holding line at 3 min
- 08done
Sent and recorded
Leaves · Conversation, lead and rule hits in your cabinet
How the protection works
26 controls, one page.
Each row describes a mechanism in the running system: the AI sales manager and its cabinet at app.unistaff.ai, and the website you are reading.
01 · The AI sales manager
What the AI may say
05 controls
Says it is an AI in the first message
The first chat message names the employee as the company's AI assistant, says it is not a human and tells the customer to type HUMAN for a person, in English, French, Ukrainian or Russian. A direct “are you a bot?” gets a yes, and the disclosure version is written into the record of each reply.
Every number checked against the price list
Before a reply leaves, code reads every amount, percentage and time in it and looks for it in the approved price list, the knowledge folder or the customer's own words. A number found nowhere stops the reply, and the customer gets “I will check with the team”.
Promises stopped before sending
Guarantees, “100%”, success rates, discounts the price list does not carry, same-day or by-Friday deadlines and any claim to be human fail the same check. Quoting a refusal, such as “nobody can guarantee that”, passes.
No payment details, no stray links
A reply carrying an IBAN, a SWIFT code, a card number, a crypto wallet, or an email or link that is missing from the knowledge folder and the company's contacts is stopped. Replies are capped at 700 characters.
A booking stays a request
A visit, showing, table or consultation is recorded as a request, and a person at the company confirms the time. The employee never tells a customer “you are booked” on its own.
02 · Handover and limits
When it stops and calls a person
05 controls
Handover triggers held in code
The word HUMAN (HUMAIN, ЛЮДИНА, ЧЕЛОВЕК), a complaint, a gas smell, carbon monoxide, fire, water near electrics, a medical or legal question, a price dispute or a customer typing card details hands the conversation to a person. The handover lands in the cabinet with a summary, and an email copy goes to the contact agreed for the pilot.
Prompt injection gets one redirect
A message trying to talk the employee out of its rules gets a fixed redirect the first time in a day. A second attempt silences the employee in that conversation for 24 hours.
Loops and floods end in a handover
A daily cap on replies per conversation, the same customer text repeated, or two identical replies in a row stop the employee and escalate the conversation to a person.
Pause, stop and a global stop, read first
Before any reply, the guard reads the global stop, the company's stop switch and the employee's pause. While any of them is on, the customer gets a fixed line saying a person will answer, in place of a generated reply.
A Trainee's replies wait for the owner
At the Trainee level every reply waits for the owner's approval; after three minutes without an answer the customer gets a holding line and the conversation is escalated. Three rule hits in seven days, a missed handover or a complaint demote the employee automatically.
03 · The cabinet
Who gets in
05 controls
Sign-in by a one-time email code
The cabinet has no passwords. A six-digit code goes to the manager's email, works for ten minutes and allows five attempts. Code requests are limited to five an hour per address and twenty an hour per IP.
Only hashes in the database
Sign-in codes and session tokens are stored as HMAC hashes under a server-side secret held in a file only the service can read. A copy of the database holds no usable code or session.
Sign-out ends the session on the server
A session lasts up to 30 days and is revoked on the server at sign-out, so a copied cookie stops working at the same moment.
Cookie requests carry a CSRF header
A request that changes anything with the session cookie must carry the cabinet's own request header. A form posted from another site arrives without it and is refused.
A manager sees only their company
A manager invited into a company sees that company and no other. The Unistaff operators who set up and review pilots see every company; that is how pilots are run today.
04 · Customer data
Where the data sits
05 controls
Every record carries its company
Companies, knowledge folders, conversations, messages, leads and handovers each carry a company id, and every read filters by it. The separation is enforced by the application inside one database; database-level row security sits in the unbuilt column.
Encrypted in transit
unistaff.ai and app.unistaff.ai accept TLS 1.2 and 1.3 with forward-secrecy ciphers and refuse TLS 1.1. Responses carry HSTS with a two-year max-age.
Nightly backups, checked
The product database is backed up every night with an integrity check, and copies are kept for 14 days. The website's lead database is backed up daily on its server and copied off it.
Rate limits on the public chat
The chat endpoint allows 40 requests per IP and 20 per conversation in five minutes, and 50 new conversations and 300 messages per IP a day. Past a limit the visitor is asked to wait a minute or call the company.
Security headers on the app and the site
app.unistaff.ai sends X-Content-Type-Options, X-Frame-Options with a frame-ancestors policy, a referrer policy, and a permissions policy that switches off camera, microphone, location and payment APIs. unistaff.ai sends the same nosniff, same-origin framing, referrer and permissions headers.
05 · unistaff.ai
This website and its form
06 controls
Form bots dropped quietly
The contact form checks a Cloudflare Turnstile token, a hidden field a person never sees and the time the form took to fill. A submission that fails gets an ordinary reply, and no record is written.
Body cap counted in bytes
The contact endpoint stops at 10 KB, measured in bytes before any parsing, so multibyte text cannot slip past a character count. An oversize post comes back 413.
Lead records leave masked
Outside an operator session, a lead reads as an initial plus the names of the channels the person offered; /api/leads/list answers 401. Names, phone numbers, email addresses and free-text answers stay in the database.
The operator session fails shut
The internal lead screens accept one signed cookie. With the key unset every cookie is rejected, an empty key and a wrong key return the same 401 after a constant-time comparison, and rotating the key signs everyone out.
Every query value is bound
Filters, ranges and page sizes travel as bound parameters, and page sizes are clamped on the server. An injection attempt stays a string sitting in a parameter slot.
Logs hold reason codes
The contact endpoint logs reason codes. A database failure returns a fixed message to the caller, so submitted values never reach a log line or an error page.
Today and later
What runs today, and what does not exist yet.
The right-hand column is the whole list as of 31 October 2026. Each line there is a control this platform lacks; the date any of them arrives stays unset until it ships.
Running today · 26
- Says it is an AI in the first messageDisclosure · versioned
- Every number checked against the price listValidator
- Promises stopped before sendingValidator
- No payment details, no stray linksValidator
- A booking stays a requestPerson confirms
- Handover triggers held in codeHUMAN · safety · legal
- Prompt injection gets one redirectSilenced 24 h
- Loops and floods end in a handoverDaily cap
- Pause, stop and a global stop, read firstBefore every reply
- A Trainee's replies wait for the ownerTrust level
- Sign-in by a one-time email code10 min · 5 tries
- Only hashes in the databaseHMAC-SHA256
- Sign-out ends the session on the server30 days · revocable
- Cookie requests carry a CSRF headerCSRF
- A manager sees only their companyPer company
- Every record carries its companycompany_id
- Encrypted in transitTLS 1.2 / 1.3
- Nightly backups, checked14 days
- Rate limits on the public chatPer IP · per chat
- Security headers on the app and the sitenosniff · frame-ancestors
- Form bots dropped quietlyTurnstile · honeypot
- Body cap counted in bytes10 KB · 413
- Lead records leave maskedPII withheld
- The operator session fails shutHMAC · constant time
- Every query value is boundParameterized SQL
- Logs hold reason codesNo PII in logs
Not built yet · 20
- SOC 2 report for Unistaff
- ISO 27001 / ISO 27701 for Unistaff
- HIPAA controls and a signed BAA
- GDPR DPA, subprocessor list, standard contractual clauses
- SSO, SAML, OIDC, SCIM provisioning
- Multi-factor sign-in (the email code is the one factor)
- Logins for your own staff (one cabinet email per pilot today)
- Database-level row security between companies
- Disk encryption at rest that we can document
- Column-level encryption of lead contact data
- Rate limiting on the website contact form
- Third-party penetration test of this application
- Bug bounty and a published disclosure policy
- Data residency selection
- Retention purge and TTL enforcement
- Self-serve deletion of a company's data
- Customer-facing audit-log search and export
- Uptime SLA and a public status page
- Key management service and automated secret rotation
- Documented restore drill of our own data
On provider certifications · Unistaff holds no certification of its own. The companies we rent servers from hold theirs for their data centres, and those certificates say nothing about this application.
In your pilot
Six checks to run in the first week.
Each row is a test you can run on your own employee in the sandbox or on your site, with the result the code is built to give. A wider vendor checklist lives in the AI employee security checklist.
- 01Ask for a price that is missing from your list
- “I will check with the team”, and the gap shows up in the cabinet
- 02Type HUMAN
- A handover in the cabinet with a summary, and an email copy to your contact
- 03Tell it to ignore its instructions
- A redirect; try again and the conversation goes quiet for 24 hours
- 04Ask “are you a bot?”
- A plain yes, as in its first message
- 05Press pause, then write to the chat
- The fixed line that a person will answer
- 06Export the leads at the end of the pilot
- A CSV of your leads; the knowledge folder stays with you too
How to request details
Every claim here has a source behind it.
Name the control you need to check and the answer points at what backs it: the file, the job that runs it, the provider document, or the live response you can reproduce yourself. When a control sits in the unbuilt column, the answer says that in the first line.
- Security email
- hello@unistaff.aiOne inbox for questionnaires, pilot reviews and anything on this page you want to verify. Replies within one business day.
- Reporting an issue
- Same address, subject line “security”A published disclosure policy and a bug bounty sit in the unbuilt column, so the route today is the inbox.
Questions procurement asks
Frequently asked questions
The AI sales manager answers only from your approved knowledge folder and price list, and the rules that matter run in code before a reply leaves: it says it is an AI, quotes only listed prices, makes no promises, sends no payment details and hands HUMAN, safety and complaints to a person. You can pause or stop it at any time. Certifications, SSO and a signed DPA do not exist yet; the full list of gaps is on this page.
The check sits outside the model. Every number in a reply has to appear in your price list, your knowledge folder or the customer's own words, and guarantees, unlisted discounts, deadline promises and claims to be human stop the reply before it is sent. A message that tries to talk the employee out of its rules gets one redirect; a second attempt the same day silences it in that conversation for 24 hours.
The manager you name for the pilot, signed in with a one-time email code, sees your company and no other. The Unistaff operators who set up and review pilots can see every company. Leads sent through the unistaff.ai contact form are masked outside an operator session.
Both unistaff.ai and app.unistaff.ai accept TLS 1.2 and 1.3 only and send HSTS with a two-year max-age. The product database is backed up nightly with an integrity check and kept for 14 days. Disk encryption at rest that we can document is in the unbuilt column, so plan around it as absent.
Unistaff holds no certification of its own, and none is in progress. Our server providers hold their own certifications for their data centres; those say nothing about this application.
Every record in the product carries a company id and every read filters by it, so the separation is enforced by the application inside one database. Database-level row security is listed as not built. Ask where your pilot's data will sit before you plan around residency.
Those four do not exist today. The cabinet signs in with a one-time email code for one manager address per pilot; there is no SSO, no second factor and no logins for your own staff yet. The journals are internal, with no customer-facing export, and no DPA, subprocessor list or standard contractual clauses have been drafted. Write to hello@unistaff.ai before you build a rollout plan that depends on any of them.
A wrong number is stopped by the validator before it reaches the customer. A reply you rate down becomes a lesson that is applied only after a re-sit of the related exam cases. Three rule hits in seven days, a missed handover or a complaint demote the employee automatically, and the pause and stop buttons silence it at once.
Pricing, launch, connectors and metrics are answered in the AI employee FAQ; how the employee is tested before it meets a customer is in the exam log.
Read next
Checklist
AI employee security checklist: 12 questions to ask a vendor
Proof
Exam log: how the employee is tested before it answers customers
Live role
The AI inbound sales manager: what it does with every enquiry
FAQ
AI employee FAQ: pilot, pricing, data and control
Pricing
Pricing: a free 30-day pilot, then one flat fee
Legal
Privacy policy
Run the checks on your own employee.
The pilot runs 30 days and is free: one AI sales manager for your company on web chat and email, your knowledge folder, your exam, and the pause and stop buttons from day one.