KYC/AML & Privacy Policy
Last updated: November 11, 2026
1. BSA/AML Program Overview
Glide, operated by Montauk Analytics Inc., maintains a comprehensive Anti-Money Laundering (AML) program in compliance with the Bank Secrecy Act (BSA), USA PATRIOT Act, and FinCEN regulations. Our program is designed to detect, prevent, and report money laundering, terrorist financing, and other financial crimes conducted through or facilitated by our Service.
The program is built on five core pillars that form the foundation of our compliance framework:
- Internal Policies, Procedures, and Controls - Written policies governing all aspects of BSA/AML compliance, including customer onboarding, transaction monitoring, suspicious activity reporting, and record retention. These policies are reviewed and updated annually.
- Designated BSA Compliance Officer - A qualified individual responsible for the day-to-day administration of the AML program, with authority to implement policies and escalate issues to senior management.
- Ongoing Training Program - Annual training for all employees covering BSA/AML requirements, red flag indicators, reporting obligations, and updates to regulations and enforcement trends.
- Independent Testing - Annual independent review of the AML program by a qualified third party to assess effectiveness, identify gaps, and recommend improvements.
- Customer Due Diligence (CDD) - Risk-based procedures for verifying customer identity, understanding the nature and purpose of customer relationships, and conducting ongoing monitoring for suspicious activity.
Together, these pillars ensure that Glide operates in full compliance with federal anti-money laundering requirements while maintaining the security and integrity of our financial services.
2. BSA Compliance Officer
Montauk Analytics Inc. has designated a BSA Compliance Officer (the Head of Compliance named in Glide's compliance policies) who is responsible for the overall administration and implementation of the AML program. The Compliance Officer reports directly to senior management and has the authority to make decisions regarding account suspension, SAR filing, and escalation to law enforcement.
Key responsibilities of the BSA Compliance Officer include: ensuring the AML program is current and effective, managing the alert investigation and SAR filing process, coordinating with regulatory examiners and law enforcement agencies, overseeing employee training, and reporting to senior management on the state of the compliance program.
The Compliance Officer maintains current knowledge of BSA/AML regulations, FinCEN guidance, and industry best practices through ongoing professional development, attendance at compliance conferences, and participation in industry working groups.
In the absence of the primary Compliance Officer, a designated deputy is authorized to perform all compliance functions to ensure continuity of the AML program.
3. Customer Identification Program (CIP)
In accordance with Section 326 of the USA PATRIOT Act and FinCEN regulations, Glide implements a Customer Identification Program (CIP) that verifies the identity of every individual who opens an Account. Fiat services (bank account details and deposits, bank transfers from a fiat balance, conversion between fiat balances, payroll and batch payments) are available only after identity verification is successfully completed. Bank payouts are available only to customers whose KYC has been approved: they are carried out by Noah, our regulated payments partner, which only pays out from KYC-approved accounts. Before verification, a customer can hold, send, receive and swap crypto in their own self-custody wallet, except where a feature says otherwise; crypto transfers made through Glide are subject to wallet sanctions screening.
Identity verification is conducted by our licensed verification partner, Noah, through its hosted onboarding, which uses Sumsub for document and biometric checks. The process requires the user to submit a photograph of a valid, unexpired government-issued photo identification document (passport, driver's license, or national ID card) and a live selfie photograph for facial comparison.
The partner's automated verification system performs document authentication checks (including tamper detection, expiration validation, and format verification) and biometric facial matching between the submitted selfie and the ID photograph. If the automated checks are inconclusive, the application is escalated for manual review by trained verification specialists.
We retain records of the identification information collected during the CIP process for 7 years after account closure under our Data Retention Policy, longer than the five-year minimum the Bank Secrecy Act requires.
4. Customer Due Diligence (CDD)
Customer Due Diligence is performed during onboarding and on an ongoing basis throughout the customer relationship. CDD enables us to understand each customer's risk profile, the expected nature and purpose of the account relationship, and to identify transactions that deviate from expected patterns.
During onboarding, the following information is collected through the partner's verification process: full legal name, date of birth, residential address, Social Security Number (for US persons) or national identification number (for non-US persons), and source of funds declaration.
Based on the information collected, each individual customer is assigned a risk score in one of four bands (low, medium, high, or critical) that compliance staff take into account when reviewing the account. Risk scores are recalculated nightly and when new information becomes available, such as changes in transaction patterns or screening results.
CDD information is stored securely and encrypted at rest. Access is restricted to authorized compliance personnel on a need-to-know basis.
5. Enhanced Due Diligence (EDD)
Enhanced Due Diligence is applied to customers and transactions that present higher levels of risk. EDD goes beyond standard CDD procedures and requires additional information gathering, documentation, and senior-level review.
EDD is triggered by any of the following conditions: the customer's risk score is in the high or critical band; the customer, a beneficial owner or a signatory is a potential match against sanctions or Politically Exposed Person (PEP) lists; our verification partner asks for high-risk or source-of-wealth information; the customer is resident in, a national of, or doing business in a high-risk country, or the business operates in a high-risk industry; or transaction monitoring suggests activity inconsistent with the customer's profile.
When EDD is triggered, additional documentation may be required, including but not limited to: proof of source of funds (bank statements, employment records, or investment documentation), proof of source of wealth, detailed explanation of the business relationship or purpose of transactions, and references from other financial institutions.
EDD reviews are conducted by senior compliance staff and documented thoroughly. The decision to onboard, continue, or terminate a high-risk customer relationship requires approval from the BSA Compliance Officer (the Head of Compliance).
6. Beneficial Ownership
For business accounts, Glide is required under FinCEN's Customer Due Diligence Rule to identify and verify the identity of all beneficial owners who own 25% or more of the legal entity, as well as at least one individual who has significant managerial control over the entity.
Beneficial ownership information is collected through our Know Your Business (KYB) process and verified by our verification partner. Each identified beneficial owner must provide the same identification information required for individual accounts: full legal name, date of birth, residential address, and Social Security Number or national ID.
The entity itself must provide: legal entity name, formation documents, Employer Identification Number (EIN) or equivalent, and a list of all individuals with ownership interests of 25% or greater. We may also request organizational charts, operating agreements, or articles of incorporation.
Beneficial ownership information is verified, recorded, and retained for 7 years after the business relationship ends (account closure) under our Data Retention Policy, longer than the five-year minimum the Bank Secrecy Act requires.
7. OFAC/SDN Screening
Customers and the crypto transfers made through Glide are screened against the Office of Foreign Assets Control (OFAC) Specially Designated Nationals and Blocked Persons (SDN) list and other relevant sanctions lists, at several points in the customer lifecycle.
Fiat transfers are screened by the licensed partner that executes them, under its own sanctions screening programme, against OFAC lists and other applicable sanctions lists.
Cryptocurrency addresses are screened with Chainalysis's sanctions screening service. The recipient of outgoing crypto transfers made through Glide is screened before the transfer is allowed, and the sending address of deposits Glide detects is screened. A match on an outgoing transfer blocks it; a match on a deposit flags it. Either raises a critical alert for the compliance team. If the screening service is unavailable, outgoing transfers are blocked.
Customers who complete verification, and verified businesses with their directors and owners, are screened against sanctions and PEP lists by our verification partner as part of verification. Any potential matches are escalated to the BSA Compliance Officer for investigation and resolution.
8. Ongoing Monitoring
Glide monitors customer activity to detect patterns that may indicate money laundering, terrorist financing, sanctions evasion, or fraud. Controls before a transaction (sanctions screening, account status, verification requirements and limits) can stop it. After a transaction, automated sanctions screening and the monitoring rules that Compliance has enabled raise alerts for review.
Glide's rules engine supports rules for large transactions, aggregate activity, possible structuring, new accounts, payments to new beneficiaries, rapid movement of funds and crypto transfers that may need Travel Rule information. By procedure, Compliance decides which rules are enabled and sets their thresholds on a risk basis; thresholds are not published. Alerts are reviewed manually by our compliance team, and the outcome is recorded on the alert or on a compliance case.
Alerts are prioritized by severity, with critical alerts (such as sanctions matches) triaged first.
For more on monitoring and investigation procedures, see our Transaction Monitoring Policy.
9. SAR Filing
Where our compliance team concludes that activity is suspicious, it prepares a suspicious activity report and files it with the competent authority, and notifies the relevant partner where the partner's own obligations require it. Reports are filed through the authority's own filing channel.
The SAR filing clock begins when suspicious activity is first detected by our monitoring systems or otherwise brought to the attention of the compliance team. Where a report is filed with the Financial Crimes Enforcement Network (FinCEN), our target is to file within 30 calendar days of initial detection, or 60 days where no suspect has been identified.
The admin console pre-fills a draft narrative from the compliance case record. A qualified compliance officer reviews, completes and approves every SAR before filing. The narrative includes a description of the suspicious activity, the parties involved, the transactions at issue, and the reason why the activity is deemed suspicious.
We are prohibited by federal law (31 U.S.C. § 5318(g)(2)) from notifying any person involved in a SAR filing that a report has been or will be filed. All SAR-related information is maintained with strict confidentiality and access controls.
10. CTR Filing
Currency Transaction Reports (CTRs) are required for cash transactions exceeding $10,000 in a single business day, as mandated by the Bank Secrecy Act. Glide handles electronic transactions, and where a CTR is required it is filed by the institution that holds the obligation for that transaction.
Attempted structuring - the deliberate breaking up of transactions to avoid reporting thresholds - is a federal crime and is monitored as part of our transaction monitoring program. Detected structuring patterns are treated as suspicious activity and may result in SAR filing, account suspension, and law enforcement referral.
11. Record Keeping
Glide maintains comprehensive records in accordance with BSA record-keeping requirements. The Bank Secrecy Act requires these records to be kept for a minimum of five years; our Data Retention Policy keeps all BSA-related records for 7 years after account closure, longer than the statutory minimum.
The following record categories are subject to the 7-year compliance retention: all transaction records (deposits, withdrawals, and transfers), Suspicious Activity Reports (SARs) and supporting documentation, KYC/CIP identification documents and verification results, alert investigation case files and disposition records, and sanctions screening outcomes on transactions and alerts.
Sensitive records are encrypted at rest with AES-256, and full identity data is accessible only to authorized compliance personnel. Viewing and revealing customer records in the admin console is logged for audit purposes.
For complete details on our data retention schedule, encryption standards, and destruction procedures, see our Data Retention Policy.
12. Data Collection & Use
We collect and process personal data in connection with the provision of the Service. The types of data we collect, the purposes for which we use it, and the legal bases for processing are described below.
Identity Data
Full legal name, date of birth, nationality, government-issued ID images, and selfie photographs. Collected for KYC/CIP verification as required by BSA regulations and to fulfill our contractual obligation to provide the Service.
Contact Data
Email address, phone number, and residential address. Collected for account management, communications, and regulatory compliance (CDD requirements).
Financial Data
Transaction history, account balances, bank account details for linked accounts. Collected to provide the Service, monitor for suspicious activity, and comply with BSA reporting requirements.
Technical Data
IP address, device information, browser type, login timestamps, and session data. Collected for security purposes (fraud detection, unauthorized access prevention) and legitimate business interest in maintaining service integrity.
We use product analytics linked to your Glide user ID and company workspace to improve the service, including country, verification status and rounded transaction activity. Session replay masks text and inputs and blocks sensitive KYC, bank and money screens. Analytics properties exclude names, email addresses, phone numbers, addresses, identity documents, wallet addresses and raw IP addresses.
Our legal bases for processing personal data include: compliance with legal obligations (BSA/AML requirements), performance of a contract (providing the Service), and legitimate interests (fraud prevention, service improvement, and security).
13. Data Sharing
We share personal data with third-party service providers only as necessary for service delivery and regulatory compliance. We do not sell personal data to third parties, and we do not share data for marketing purposes without your explicit consent.
Data is shared with the following vendors in the course of providing the Service:
- Privy - Receives email address and authentication data for user login and wallet provisioning.
- Noah - Our licensed verification and account partner. Receives identity data (name, DOB, address, ID images, selfie) for KYC and KYB verification through its hosted onboarding, which uses Sumsub for document and biometric checks, and financial data for the accounts and payments it provides.
- IDRX - Our Indonesian partner. Receives identity data and documents for Indonesian rupiah accounts, and financial data for the payments it provides.
- Bridge - Receives financial data for crypto conversion where it performs it, and holds identity data for verifications completed with Bridge before Noah became our verification partner.
- Column N.A. - Receives identity and financial data where it provides a bank account or processes a transfer for a customer, and for regulatory compliance on those records.
- Chainalysis - Receives cryptocurrency wallet addresses for OFAC/SDN sanctions screening. No personal identity data is shared with Chainalysis.
- AI model providers - Anthropic and OpenRouter, which power Glide's in-app and Telegram assistants and staff drafting tools. They receive the messages and account information needed to answer a request or prepare a draft.
- Infrastructure and operations providers - Hosting and key management (Google Cloud), customer-support messaging, email delivery, error monitoring, logging and product analytics. These receive only the operational data they need, filtered as described in this policy.
We may also share data with law enforcement agencies, regulatory authorities, or courts in response to valid legal process, including subpoenas, court orders, or regulatory examination requests.
14. Data Rights
Depending on your jurisdiction, you may have the following rights with respect to your personal data:
- Right of Access - You may request a copy of the personal data we hold about you.
- Right of Correction - You may request correction of inaccurate or incomplete personal data.
- Right of Deletion - You may request deletion of your personal data, subject to the 7-year compliance retention for BSA records described in our Data Retention Policy. Data required for BSA compliance cannot be deleted until the retention period has expired.
- Right of Portability - You may request that your personal data be provided in a structured, commonly used, machine-readable format for transfer to another service provider.
To exercise any of these rights, email privacy@glide.co. We will respond to your request within 30 calendar days. In certain circumstances, we may request additional information to verify your identity before processing a data rights request.
Please note that the 7-year compliance retention for BSA records supersedes deletion rights under CCPA, GDPR, and other data protection regulations for those records. We will inform you if any portion of your deletion request cannot be fulfilled due to regulatory retention obligations.
15. Training
All Montauk Analytics Inc. employees complete AML training within 30 days of joining, and before they are given access to customer data, and annual refresher training thereafter. Training is tailored to each employee's role and responsibilities, with more intensive training provided to compliance staff and personnel who interact directly with customers or handle financial transactions.
Training covers the following topics: overview of BSA/AML regulations and FinCEN requirements, recognizing red flags and indicators of suspicious activity, SAR and CTR filing procedures and responsibilities, OFAC sanctions compliance and screening procedures, customer identification and due diligence requirements, and data privacy and security best practices.
Training records, including attendance, content covered, and assessment results, are maintained for a minimum of seven years. The training program is reviewed and updated annually to incorporate changes in regulations, new enforcement actions, emerging typologies, and lessons learned from internal audits and examinations.
The BSA Compliance Officer is responsible for overseeing the training program and ensuring that all staff remain current on their compliance obligations.
16. Independent Testing
Montauk Analytics Inc. engages a qualified independent third party to conduct an annual review of the AML program. The independent testing evaluates the effectiveness of our policies, procedures, and controls, and identifies areas for improvement. This requirement is mandated by BSA regulations and is a critical component of a sound AML compliance framework.
The scope of independent testing includes: review of the CIP/CDD program for completeness and accuracy, assessment of transaction monitoring system effectiveness and calibration, evaluation of SAR and CTR filing processes and timeliness, review of OFAC screening procedures and match resolution, assessment of training program adequacy, and review of record-keeping practices and data security.
Findings and recommendations from the independent testing are documented in a formal report that is presented to the BSA Compliance Officer and senior management. An action plan is developed to address any identified deficiencies, with specific timelines and responsible parties assigned.
Progress on remediation actions is tracked and reported to senior management on a quarterly basis until all findings are resolved. The independent testing report and all related documentation are retained for a minimum of seven years.
17. MCP connections
When you connect an assistant to Glide through MCP, Glide receives the tool name, its parameters, and the access token for your connection. The directory endpoint provides personal account balances, requested transaction details, payment status, and identity verification status within your granted access. It does not return identity documents, business accounts, or vault member identities. Tool schemas do not request your conversation history.
We use this information to authenticate the connection, check account access, answer your requests, and maintain security and audit records. The assistant provider you connect receives tool responses so it can answer you. Its use and retention of that data are governed by its own terms and privacy policy. Glide uses hosting, authentication, database, and audit infrastructure to process requests.
Audit records include account and grant identifiers, tool names, outcomes, request times, IP addresses, client information, and a hash of tool inputs. Retention depends on the record category in our data retention policy, including applicable financial compliance records. Disconnect the connector in your assistant to stop using it. Revoke its personal grant in Connect with your agent, and contact support for data access, correction, or deletion requests. Legal retention requirements can limit deletion.