Skip to main content
For the AMLOK web application, the published privacy policy describes collection, consent, rights, retention, and cross-border processing. Send privacy requests to privacy@amlok.io. Enterprise processing instructions and responsibilities are documented in your agreement.

​
Purpose and processing scope

AMLOK uses purpose-limited processing: the institution defines its underwriting or portfolio-monitoring purpose, and AMLOK processes agreed information under documented instructions. Actual activities and applicable law determine the legal allocation of responsibilities. The processing schedule should identify people and entities involved, data categories, permitted workflows, duration, customer instructions, approved providers, and secondary-use restrictions.

​
Source permissions and notices

Before collection, identify the authority to obtain information, relevant notices and consent where required, and permissions granted by each source. Access to a connected account does not automatically authorize every downstream use. For monitoring, distinguish permission for new collections from obligations to retain earlier records. Revocation should trigger a review of future collection, processing, and retention, with legal requirements considered separately. Authorization records include the source, permitted scope, purpose, subject or account reference, and grant, expiry, and revocation details.

​
Data minimization

Limit collection to the agreed workflow. Business records may contain personal information about owners, guarantors, employees, or customers. Treat sensitive identifiers and financial details accordingly. Avoid full borrower records, credentials, identification documents, or sensitive account information in general support tickets, logs, or demonstrations. Define an approved channel for necessary diagnostic material.

​
Model use and secondary purposes

AMLOK’s data-handling policy separates customer-requested inference from model training, service improvement, and other secondary purposes. Review AMLOK’s use and each model provider’s retention and training terms independently. The agreement must state permitted uses, any opt-in mechanism, and restrictions on customer data and derived information. An integration’s ability to transmit data does not establish permission to use it for training.

​
Retention and workspace deletion

Authorized users manage data-retention settings in the AMLOK platform. Retention follows your workspace configuration and the compliance frameworks applicable to your institution, data, and processing purpose. After the cancellation request month closes and necessary final information is generated, the workspace is deleted. When workspace deletion is completed, all data associated with that workspace is deleted. This includes its source data, normalized records, derived information, documents, and analysis outputs. Completion means the full workspace-deletion process is finished; it is not merely an acknowledgment of a request. Retention configuration and workspace deletion are platform controls. There is no separate customer deletion-request API. Disconnecting an integration stops future collection but does not itself delete previously collected workspace data. Deleting an AMLOK workspace does not delete the original records held independently by an external bank or business system. When cancellation is submitted in the portal or set by your account manager, all product processing, usage deductions, and new or scheduled top-ups stop immediately. Pending processing is cancelled without another charge. Request account cancellation in the client portal, or through your dedicated account manager for enterprise clients. Cancellation schedules workspace deletion and reconciliation of unused credits. You may cancel at any time without notice. Account closure is at the end of the request month, with an immediate refund of the entire unused balance to your saved bank account. Deletion follows month closure and generation of the necessary final information. Export needed records before requesting cancellation. See account management.

​
Access and correction requests

Determine who receives and answers requests, how identity and scope are verified, and how AMLOK assists the responsible organization. Search supplied information and relevant derived records. Correcting a source record may require reviewing affected analysis. Apply the legal response deadline for the jurisdiction and request. Service response targets are separate from legal deadlines. See Canadian requirements, Quebec privacy, and United States requirements. AMLOK retains only the necessary final billing, refund, and bank-return records separately from the deleted workspace to reconcile the refund and resolve delivery issues. These records do not retain borrower source data, documents, or analysis outputs and do not keep the workspace or its API access active.