Amlok / POLICIES

Privacy Policy

How information is handled when you browse this website, contact Amlok, or engage with our services.

Website & business relationships
AT A GLANCE
  • Website enquiries and institutional processing have different purposes.
  • Share only the information needed for your request.
  • Contact privacy@amlok.io to ask about your information or exercise applicable rights.

This overview is a reading aid. The sections below provide the detail.

01Who this policy covers

This policy describes information handling for the Amlok marketing website, business enquiries, and meeting requests. It also explains how those activities relate to Amlok’s institutional services. “Personal information” means information about an identified or identifiable individual.

For website enquiries and business communications, Amlok determines how to respond and administer the relationship. For financial information processed for an institution, the institution’s notices, the applicable service and processing agreements, and the actual activities determine the parties’ responsibilities. This website policy does not expand the purposes for which customer data may be used.

The authenticated Amlok application has its own published privacy policy. If your bank, lender, insurer, or other institution uses Amlok, consult that institution’s notice for information about your assessment and its decisions.

02Information we receive

The information involved depends on how you interact with us. Ordinary browsing does not require you to upload financial records or create an Amlok account.

  • Business contact information: your name, work email, organization, role, and other details you choose to provide.
  • Enquiry and correspondence information: your message, product interests, requested follow-up, and records of our response.
  • Scheduling information: booking details and answers you provide when arranging a meeting through Cal.com.
  • Technical request information: IP address, browser and device details, requested URL, referring information where available, timestamps, and error or security information handled by website delivery services.
  • Browser preferences: the selected language stored in this browser, as described in the Cookies Policy.

03How website features handle information

The contact form prepares a message in your email application. Preparing the draft does not submit it to an Amlok website form database; Amlok receives the message when you send it. The journal signup feature similarly prepares an email request. Your email provider handles drafts and messages under its own terms.

The website loads Cal.com’s booking script after the page becomes interactive. Requests to that service can occur before you open a booking dialog. When you book, the details you submit are handled through Cal.com and made available for arranging the meeting. The current embed configuration also forwards page query parameters into the booking experience. Do not place confidential information in website URLs or booking notes.

External links, including social and AI-summary links, take you to services with their own privacy practices. Those services receive the information associated with the request you choose to open.

04Why information is used

We use business contact and correspondence information to answer questions, arrange meetings, explain the product, support a requested commercial relationship, and keep a record of those communications. Technical information supports website delivery, troubleshooting, and security.

Where you request updates, we use the information needed to respond to that request and manage your communication preferences. You can ask us to stop optional marketing communications; operational messages about an existing service may still be necessary.

Applicable authority depends on the activity and jurisdiction, including consent where required, steps to establish or perform a business relationship, and legal or security obligations. Browsing the website is not blanket permission to process your financial accounts or use customer records for unrelated purposes.

05Institutional and connected financial information

An authorized customer deployment may involve identity attributes, account and transaction records, business and ownership information, documents, contractual obligations, verification results, and derived findings. Business records can also include information about owners, guarantors, employees, and other individuals. The actual categories and permitted workflows are defined for that deployment.

Collection and analysis must remain within the agreed purpose, source permissions, and applicable authorization. Connecting an account does not automatically permit every downstream use. Institutions establish the required notices, permissions, and review processes, and Amlok processes information under the applicable documented instructions.

The data-handling policy separates customer-requested analysis from training, service improvement, and other secondary uses. The agreement must identify permitted uses and restrictions for Amlok and relevant providers. An integration’s technical ability to transmit data is not permission to use it for model training.

06Service providers and other disclosures

Website delivery and business communications involve providers that receive the information needed for their role. This site is deployed using Cloudflare infrastructure and integrates Cal.com scheduling. Email communications also involve the sender’s and recipient’s email services.

Institutional deployments may involve approved infrastructure, financial-data connectivity, identity verification, communications, billing, and model-processing providers. A provider listed in an integration catalog is not necessarily used for every customer. Deployment-specific entities, locations, and safeguards are documented in the relevant subprocessor register and agreements.

Information may also be disclosed where required by law or where lawfully necessary to investigate abuse, protect systems or people, resolve disputes, or carry out a business transaction subject to applicable safeguards. Disclosures remain subject to the purpose, agreement, and legal requirements that apply.

07Processing locations

Information may be handled in Canada or other countries where the relevant service providers or authorized personnel operate. Laws and lawful-access requirements can differ by location. This marketing website does not make a Canada-only hosting or processing commitment.

For institutional services, processing locations and transfer requirements must be assessed for the whole deployment, including storage, backups, inference, operational access, and exports. Any geographic restriction must be documented in the agreement; a primary database region alone does not describe every processing location.

08Retention and deletion

Website correspondence and business records are retained for the purposes for which they were collected, taking account of the relationship, follow-up needs, legal requirements, and dispute or security obligations. Contact us for information about the retention relevant to your request. Language preferences remain in browser storage until changed or removed.

For institutional workspaces, authorized users manage retention settings under the applicable configuration and requirements. Disconnecting a source stops future collection but does not itself delete earlier records or records held independently by the original source.

Under the published cancellation process, workspace deletion follows the close of the cancellation request month and generation of necessary final information. Completed workspace deletion removes its source data, normalized records, derived information, documents, and analysis outputs. Necessary final billing, refund, and bank-return records are retained separately; they do not preserve borrower records or active workspace access.

09Safeguards and sensitive submissions

Amlok’s security approach includes access restrictions, tenant separation, encryption, and defined operational responsibilities appropriate to the service. Specific controls and assurance materials must be reviewed for the relevant deployment. No transmission or storage method eliminates all risk.

Do not send full borrower records, credentials, identification documents, or sensitive account information through general website enquiries, booking notes, or ordinary support messages. Ask for an approved secure channel when such information is necessary.

10Your choices, requests, and complaints

Depending on your location, the information, and the applicable law, you may have rights to request access or correction, obtain information about processing, request deletion or portability, object to or restrict certain processing, or withdraw consent where processing depends on it. These rights have conditions and exceptions; withdrawal does not automatically erase earlier lawful processing or records that must be retained.

Send a request to privacy@amlok.io with enough context to identify the relationship and what you are asking for. We may need to verify identity or authority using proportionate information. Do not include passwords, bank credentials, or identity-document scans in the initial email. We will explain any secure verification step needed.

If your request concerns information provided through an institution, that institution may need to handle the request or authorize Amlok’s assistance. Correcting a source record may also require a review of affected findings. Applicable legal response deadlines govern rights requests.

You may raise a concern with Amlok and, where applicable, the privacy regulator in your jurisdiction, including the Office of the Privacy Commissioner of Canada or the relevant provincial or state authority.

11Children and the marketing website

This website is intended for professional and institutional audiences and is not designed to collect information from children. Do not submit a child’s personal information through website enquiries or booking fields. Contact privacy@amlok.io if you believe such information has been provided so we can assess and address it.

12Updates and contact

We may update this policy when practices or requirements change. The updated date identifies the current version. Where a change requires additional notice or consent, that step must be provided; posting a revised notice does not itself authorize an unrelated use of information.

For questions about this policy, processing arrangements, or your information, contact privacy@amlok.io. For general business support, contact support@amlok.io.