Start with permitted information
Confirm rights, minimize inputs and use synthetic or approved sanitized examples first. Agree storage, processing locations, retention and deletion before client information is used.
Clear access. Human accountability.
Data and permissions are part of the workflow design, before anything is connected.
Use client-owned access
Prefer named, client-controlled accounts and the narrowest necessary scopes. Secrets belong in an approved secret store, never in documents, source code or prompts.
Control consequential actions
Define which tools may act, which outputs require review and who can approve. Instructions inside retrieved content do not grant authority to send, spend or change records.
Evaluate and prepare a fallback
Test missing inputs, unsupported claims, prompt injection, isolation and failure handling. Keep a manual route, incident owner and rollback plan.
Describe the actual assurance
No SOC 2, GDPR certification or other formal compliance status is claimed. Client-specific legal, security and procurement requirements require their own evidence and qualified review.
Plan for handover and exit
Document accounts, component licenses, export, retention/deletion and access removal. Ongoing support, reusable software and vendor dependencies must be explicit in the agreement.