Implemented controls
Controls available in the application and supporting operational modules.
Trust Center
Define purpose, access, retention and deletion before data enters a workflow.
Understand the platform data zones, project membership, encrypted company-formation intake, research and healthcare records, payment metadata and administrative logs.
Public trust information
Core capabilities
Designed as part of the platform—not as an isolated feature.
Configuration duties
Controls that require hosting, account, policy or integration setup.
Customer responsibility
Organization-specific data, access, legal and operating decisions.
Independent assurance
External testing or certification remains separately evidenced.
How it works
A controlled workflow from setup to review.
- 01
Identify the relevant system and data scope.
- 02
Review implemented and required controls.
- 03
Assign customer and Amexwrite responsibilities.
- 04
Collect and review evidence.
- 05
Resolve gaps before production reliance.
Frequently asked questions
Clear answers before activation.
Can detailed evidence be requested?
Evidence may be shared under appropriate authorization and confidentiality controls, depending on the record and customer relationship.
Next step
Review a specific requirement.
Send the framework, data type and intended deployment scope.