Clear answers on access and data.
What can it access?
Only the accounts, records, and actions the job needs. You authorize each connection, and where a tool supports narrower permissions, we use them.
Credentials, revocation, and sensitive records
Setup establishes how credentials are handled, how you revoke access, and what happens to access when the service ends. Personnel, customer, and financial records get explicit treatment, and we look at whether the job can use less data. Passwords don’t belong in the contact form.
Where does information go?
Your systems stay the main record where the design supports it. Before any real data is sent, we show you which providers process it and what is stored. Use “Show what leaves your systems” above to see the path.
AI providers, retention, and encryption
Data use, model-training treatment, and retention depend on the provider and account terms, so they are confirmed for your workflow rather than assumed. Encryption, data separation, retention, and deletion are confirmed for each service component. Raise your own requirements during discovery.
Who controls actions, and can stop it?
You do. The scope sets what the workflow may do and which actions need your approval. You can pause it, and revoking access stops further actions. Approvals and control →
Interruptions and recovery
Before launch we agree how work is paused, who is notified, and how safe recovery is checked. Some actions can’t be reversed; those limits are agreed before the workflow acts. A security concern is contained, investigated, and verified before work resumes.
Have a security requirement or concern?
Send a general description and we’ll arrange a suitable way to exchange sensitive details. Please don’t include passwords or records in the form.