Choose the processing perimeter
Private deployment keeps data in your environment. For cloud deployments, processing location and transferred data are agreed before launch.
Security
Processing boundaries are visible before work starts
Choose a deployment model, inherit existing permissions and keep a human confirmation for irreversible actions.
By design
Access, data and actions each have explicit limits.
Preserve source permissions
A person should not see through Primal what they cannot see in the source system.
Separate read from action
Write and send actions require their own minimum permission and human confirmation.
Keep the decision trail
Managed and private deployments retain the signal, evidence, approval and result in an audit trail.
Important boundary
Primal does not claim certainty where the source is incomplete.
It can show the missing record, assign the check and return the result. It should not invent an answer or silently pass an exception through.