Security
Clear rules for data, access and responsibility.
CAS describes its actual operating practices plainly. Some controls are always in place; hosting, access and retention details depend on the deployment agreed with each customer.
Available today
Standing rules for every CAS system.
These are the boundaries CAS follows regardless of the project size or workflow.
- API keys stay server-side
- Credentials for AI providers and connected services are kept out of the browser and are not exposed to visitors or customer users.
- Human approval is required
- A person reviews quotations, schedule changes, issued documents and other consequential actions before they are used.
- AI does not write unsupervised
- AI can help prepare information, but it does not independently write to a customer's systems or make consequential changes.
- Demos use sample data
- The public demos are not connected to customer systems and should not be used with real customer or production data.
Interactive demo
How human approvals are tracked.
Every consequential action — whether AI-prepared or manually entered — is logged with the actor, approver and outcome. Try filtering and expanding entries below to see the audit trail.
| Timestamp | Actor | Action | Approval | Approver | |
|---|---|---|---|---|---|
| 2026-11-14 09:42:11 | ai.quotegen AI Assistant | Prepared quotation #Q-2041 Quote: Steel plate 12mm, 50 units | Approved | Adejuwon Victor | |
| 2026-11-14 08:15:33 | sara.m@client.com Estimator | Updated job schedule for Job #J-883 Job: Laser cutting batch — delivery moved to Nov 18 | Approved | Sara Mansour | |
| 2026-11-13 16:30:07 | ai.docdraft AI Assistant | Drafted delivery note #DN-552 Document: Delivery note for Job #J-879 | Pending review | — | |
| 2026-11-13 14:05:52 | ai.quotegen AI Assistant | Prepared quotation #Q-2040 Quote: Aluminium sheet 3mm, 200 units | Rejected | Adejuwon Victor | |
| 2026-11-13 11:20:44 | omar.k@client.com Floor Supervisor | Approved inspection report #IR-301 Quality: Dimensional check — press brake parts | Approved | Omar Khalid | |
| 2026-11-12 17:45:19 | ai.kpigen AI Assistant | Generated weekly KPI summary Report: Output, scrap and cycle-time — Week 46 | Approved | Adejuwon Victor |
This is a sample viewer with demonstration data. In a live deployment, every consequential action — whether AI-prepared or manually entered — is recorded with the actor, timestamp, approver and outcome, so the chain of human accountability is always traceable.
Depends on deployment
The details are agreed before go-live.
CAS does not make one blanket claim about hosting, access or data handling. Those choices are documented for the specific system being built.
- Hosting location
- The hosting provider, region and environment are selected and documented for each deployment. The location is not the same for every possible deployment.
- Who can access data
- Access is limited to the customer roles and CAS operators agreed for that deployment. Roles, permissions and any administrator access are defined before go-live.
- AI providers
- The AI provider or providers that may process customer data are agreed before deployment. No provider should be assumed to receive data unless it is listed in the project scope.
- Retention and deletion
- How long operational data, backups and logs are kept — and how deletion requests are handled — is agreed and documented for each deployment.
Customer responsibility
Security is shared.
A secure system also depends on how it is configured and used by the customer team.
- Choose which staff and third parties should have access, and keep those permissions current.
- Provide accurate information about the data, systems and integrations included in the project.
- Protect user accounts, devices and any credentials that CAS does not manage.
- Review and approve consequential outputs before they are sent, acted on or written into another system.
- Tell CAS promptly about suspected unauthorised access, incorrect data or a change in the agreed use of the system.
CAS does not currently claim a security or compliance certification. Any deployment-specific commitments should be confirmed in the project scope and operating agreement.
Frequently asked questions
Straight answers to common security questions.
Will CAS use our data to train an AI model?+−
That is not an automatic part of a CAS deployment. The AI providers that may process customer data, and the permitted use of that data, are agreed and documented before go-live.
Which AI provider will receive our data?+−
There is no single provider for every deployment. CAS identifies the provider or providers used for the agreed workflow before customer data is connected.
Can AI change our production or customer records?+−
No. AI may prepare information or suggest an action, but a responsible person must review consequential work. AI does not write to customer systems unsupervised.
Where will our data be hosted?+−
The hosting provider, region and environment depend on the deployment. They are selected with the customer and recorded in the project scope rather than assumed in advance.
Can we control who sees our data?+−
Yes. Customer roles, CAS operator access and administrator permissions are agreed for the specific deployment. The customer is responsible for keeping its own user access current.
How long is our data kept, and can it be deleted?+−
Retention for operational data, backups and logs is agreed per deployment. Deletion handling is also documented so the customer knows what is removed and what may remain in backups until their retention period ends.