Agree the processing boundary
Specify where information is stored, processed, backed up, and accessed. Database location alone does not describe the full flow. Include inference, telemetry, search indexes, support access, exports, and disaster recovery.
Record Canada-only requirements explicitly and check the whole boundary. Do not infer exclusive Canadian processing from a Canadian primary hosting region.
Suppliers and subprocessors
The deployment’s register should identify each legal entity, function, data received, locations, onward providers, retention, and safeguards. It should explain how material changes are communicated and reviewed. Providers may process information on behalf of an institution, act under their own obligations, or supply data under separate terms. An integration catalog entry is not a declaration that the provider receives data in every deployment.Subprocessor categories
This public overview describes service categories and their potential data access. The confidential subprocessor register identifies the legal entities, services, processing locations, and safeguards applicable to your deployment. Request it through your AMLOK contact under a signed nondisclosure agreement (NDA).
The applicable processing agreement and confidential register establish which services are used, where processing occurs, and the notice and review process for changes. Model-processing terms address permitted use, retention, and training restrictions for the relevant service.
Contact privacy@amlok.io for the register, applicable provider assurance materials, and processing details. See security materials under NDA for the review process.