Home/Security

Your data stays in your systems.

We work inside some of the most sensitive systems a company has: its customer records, its books and its payments. These are the practices that govern every engagement.

Named access only

We sign in with named user accounts protected by multi-factor authentication. No shared logins, and no credentials sent by email or chat.

Least privilege

Access is scoped to what the work requires. Integration and agent users get their own permission sets, limited to the objects they need.

Sandbox first

Changes are built and tested in a sandbox. Nothing is deployed to production without a comparison against what is live and your approval.

No data leaves the platform

Client records stay in your Salesforce org and your accounting system. Test data in sandboxes is created for the purpose, and anything created in production for testing is removed the same day.

People approve money

Automations and AI agents that touch invoices, payments or accounting records require a named person's approval before acting in production.

Clean offboarding

At the end of an engagement our access is removed, integration credentials are rotated on request, and all code and documentation remain yours.

Have a security questionnaire?

Send it over. We are happy to complete vendor reviews as part of scoping.