Claims you can check, not just trust.
Automate with confidence. Before a digital worker goes live, you can read its blueprint (a plain plan of every step it takes) and watch it work on practice data. An optional test also attacks it the way a hacker would. This page shows how we back up each promise, and what we don’t claim yet.
EU data protection law
California privacy law
Encrypted when sent and when stored
People sign off on key steps
Independent security audit
Top of the roadmap — target date: being finalized.
Information security management
Managing AI responsibly
Accessible to people with disabilities
“In place” means it is true today. “Roadmap” means a certification from an independent auditor that we are working toward but do not hold yet. We never claim a certification before we have it. For the latest status and documents, write to security@nexgile.com.
Some labels say Roadmap on purpose. We mark what is true today and what is still to come, and we use the same labels across this whole site.
SOC 2 Type II — target date: being finalized.
In the meantime, you can rely on this:
- The software runs on your systems, under the security rules you already follow.
- You can read our audit-trail specification, which lists everything that gets recorded.
- Your security team can ask for sample files from a download, with sensitive details taken out.
Security built into every delivery.
Every download includes a threat model: a map of its security risks and how each one is handled. Our own platform is run to enterprise standards.
- Encryption whenever data is sent or stored
- Each person sees only what their role allows
- A map of risks and data flows in every download
- Continuous monitoring, activity logs and an incident plan
- A clear, responsible way to report security issues to us
Your data stays with you.
Workers can be tested entirely on practice data, so you can try them without sharing real records. After delivery, the software runs on your own systems, not in a Nexgile cloud.
- Design and test a worker without real data
- Runs on your own servers or cloud
- Data residency (where data is kept) across our Herndon, VA and Hyderabad, India operations
- Aligned with the GDPR and CCPA privacy laws, with data kept or deleted on request
- On request: the list of outside firms that handle data for us
Decisions you can explain.
Keeping AI in check is part of the product, not the small print. Every worker is built so each decision can be explained and checked.
- A plan you can read, not “the AI decided”
- Your rules built in wherever possible: same case, same answer
- At every approval step, the worker waits for a person
- Every approval recorded, plus an optional log that shows later changes. See the audit-trail specification
- Personal details can be hidden when the worker uses its tools. Optional, off by default
Four promises, each one checkable.
Every promise on this site rests on these four. You can check each one in a live session, in a document your auditors request, or by re-running a past test.
Rehearsal before reality
Each worker does its job on realistic practice data before it touches anything real. You can run it step by step, watch it pause for approvals, test several workers together and even speed up time. An optional test also attacks it the way a hacker would. Because no real data is involved, your security team can approve an evaluation that starts from a written description, with no data-sharing agreement.
See it in Nx·StudioRules you can rely on
The rules you state are built into the worker wherever possible, and you are told about any that can’t be. A built-in rule never uses AI, so the same case always gets the same answer. For routine decisions nobody has written down, our separate Cognitive Engine learns from past examples and acts only after passing an exam on cases it has never seen.
Meet the Cognitive EngineBlueprints you can read
Every worker comes with a blueprint in plain terms: what it does, who approves what, and when a case goes to a person. Every version is saved, so you can compare changes or go back. Business teams can view it as a simple chart of who does what. Like everything the platform makes, it is yours.
See how oversight worksProof in every download
Every download includes a signed list of everything inside it (a bill of materials) and a tool your IT team can use to check it offline. It also holds the threat model and a guide that maps it to the documents the EU AI Act asks for. The Studio adds a full list of what you received. The worker runs without us: no Nexgile software, no license check, no usage meter, and nothing sent back to us. So you can check “no lock-in” for yourself.
Check it yourselfYou don’t need to take our word for it.
Every download comes with proof you can check yourself: a signed list of every part of the software and its AI (a bill of materials). Your IT team checks it on your own computers, offline, without contacting us. The Studio adds a full list of what you received. You can ask for a sample with sensitive details removed, and judge it yourself.
Each worker is built to run without us: no Nexgile software, no license check, no usage meter and nothing sent back to us.
Rules work the same way. In any live session, ask us to run one case twice and watch your rules give the same answer both times.
- Signed bill of materials A signed list of every part of the software and its AI, with a tool to check it offlinein the download
- Threat model Its security risks, how each one is handled and where data flowsin the download
- EU AI Act cross-reference Maps the Act's documentation items to the bill of materials. It is not an official compliance assessmentin the download
- Ownership report A full list of everything delivered, with a PDF summaryfrom the Studio
Checked on your own computers. The verdict is yours.
Know what a worker will do before it acts.
No black boxes. You get plain documents to read, compare across versions and keep.
One plan for everyone
Every worker comes with a readable blueprint, and every version is saved. It shows the worker’s AI agents and their jobs, its connections, its approval steps, where each case goes and its rules. Nothing is buried in AI instructions or a supplier’s software. Developers compare its versions, your compliance team reviews it before launch, and auditors check against it later.
Every approval on record
Every approval is recorded on an audit trail: who approved what, and when. Two extras are optional and off by default: a log that reveals any later change, and a record of where each piece of data came from (data lineage). Built-in rules always give the same answer to the same case.
Approvals run in your software
Approvals happen in a review inbox built into the worker itself, and requests can also go to Slack, Microsoft Teams or email. You decide who approves each step, such as a role or a team. Because it is all code you own, your approval rules are enforced in your software, not in a setting on our servers.
What happens to the data you share.
Each worker gets practice data shaped like its own work, so practice runs, test runs and attack tests need none of your real data. If you upload your own sample data instead, it stays in your workspace, visible only to its members.
Anything you share during design is handled separately. You might share documents, process records or sample data so your workers fit your real workload. You decide what to share, it is used only to design your workers, and a data-processing agreement (a contract on how your data is handled) is signed first.
Start from a written description, and that description is all you share.
What never changes, what can vary, and who decides.
AI answers can differ from one run to the next.
That is why your rules don’t depend on AI. Wherever possible, they are built into the worker and give the same answer every time. You can replay a past test run step by step to see it. Routine decisions nobody has written down can be handled by our separate Cognitive Engine. It learns from past examples and acts only after passing an exam on cases it has never seen.
Where AI judgment is needed, a quality check can score each answer. You set the minimum score and choose what happens below it: flag it, stop the run, or route the case elsewhere, such as to a person. By default, it only raises a flag. At an approval step, the worker waits for a person to decide.
You decide when a person takes over.
Documents your auditors can request.
Each one is shared on request, with sensitive details removed. To ask for any of them, write to security@nexgile.com.
A sample worker plan
The who-does-what chart and download summary for a sample worker, so your team can see what a worker will do before it acts.
A sample test report
Produced from a test run on practice data. It is the report purchasing teams usually ask for.
A small sample download
Its folder layout, a page of its operating guide and a test report, to show what “ready for real work” looks like.
An outline of the threat model
What the threat model in each download covers, without the set-up details.
The audit-trail specification
Every event the audit trail records, and how the optional log reveals any later change.
A sample ownership report
The full list, the signed bill of materials and the checking tool’s results for a sample download. You judge the result.
Your auditors see what the worker will do before it acts.
Small promises, all provable.
Each is one sentence, limited to what the platform can prove. A small promise you can check beats a big one you can’t.
You can design and test a worker without any of your real data.
Your workers run without Nexgile software, with no fee to us per decision and nothing sent back to us.
If you stop paying us, nothing stops working.
Every number on this site says how it was measured. If we can’t measure something honestly, we leave it out.
Other people’s numbers follow the same rule: we quote them only with their source and date. Our delivery counts say how we counted, and we re-check them each time we publish. If we can no longer confirm a figure, we remove it from the whole site.
Reliability
The software we deliver runs on your own servers or cloud, so you control when it is available. Our own platform is monitored continuously, with a plan for handling incidents. A public status page for Nexgile services is planned.
Talk to the right team
- Security questions, or to report an issue security@nexgile.com
- Privacy & data rights privacy@nexgile.com
- Accessibility accessibility@nexgile.com