Security & code handling
How we handle customer code, data, and access across every engagement.
1. Read-only by default
We start every engagement read-only. We don’t need write access to your production systems to look at a workflow, propose a modernization plan, or even to build a parity-tested replacement. Write access is requested only when the engagement specifically requires it, and only to the minimum scope needed.
2. Sanitized samples preferred
Where we need data to reproduce a workflow, sanitized or synthetic samples are strongly preferred over real customer records. Real data is only handled under explicit written permission, with the smallest reasonable sample.
3. Customer code remains customer property
Any code we receive from a customer remains the customer’s intellectual property. We do not relicense it, redistribute it, or claim ownership of derivatives. The deliverable is yours.
4. Customer code is not used to train models
We don’t use customer source code, customer data, or customer documents to train AI models — ours or anyone else’s. Any AI tooling we use during an engagement runs with vendors whose data-handling terms forbid training on submitted content.
5. Isolated engagement workspace
Each engagement runs in its own encrypted, isolated workspace. Customer code and data from one engagement are not visible to another engagement, and are not aggregated into any shared repository.
6. Deletion certificate on close
On engagement close, we delete customer code, customer data, and engagement artifacts unless we’ve agreed otherwise in writing. A short deletion certificate is delivered alongside the final engagement report.
7. No production changes by Agentum
We don’t merge, deploy, or otherwise change your production systems. The deliverable is reviewable code or documentation; the cutover is owned by your team. This protects you from accidental breakage and protects us from operational risk we’re not staffed to carry.
Things we will not do, ever
- Use customer code or data to train AI models.
- Share customer code, customer data, or customer engagement details across other engagements.
- Make any change to production systems without written authorization for that specific change.
- Operate on real production credentials when sanitized or read-only access would do the same job.
- Sell, syndicate, or co-market customer data.
Verify a specific control
Have a security or compliance requirement we should know about before talking? Send it our way and we’ll tell you directly whether we can meet it or not.