| Item | Detail |
|---|
| Legal Entity | Paytex Solutions Ltd. |
|---|
| Trade Name | Monitiva |
|---|
| FINTRAC MSB | Registered — #C100000118 |
|---|
| Bank of Canada PSP | Registered under RPAA — REG-3961 (February 2, 2026) |
|---|
| Privacy Contact | Compliance Officer (delegated privacy function) — privacy@monitiva.com |
|---|
| Registered Office | 130 Spadina Avenue, Unit 807, Toronto, Ontario M5V 2L4, Canada |
|---|
| Website | https://monitiva.com |
|---|
1. Introduction and Commitment
Paytex Solutions Ltd., operating under the trade name Monitiva (“we,” “us,” “our,” or “Monitiva”), is committed to protecting the privacy and personal information of all individuals who interact with our services, whether through our waitlist, website, mobile applications, or financial platform. This Privacy Policy explains how we collect, use, disclose, and protect your personal information at every stage of your relationship with us.
1.1 About Monitiva
Paytex Solutions Ltd. (Monitiva) is a corporation incorporated in the Province of Ontario (Ontario Corporation Registration Number: 1000801222), registered as a Money Services Business (MSB) with FINTRAC (#C100000118) and as a Payment Service Provider (PSP) with the Bank of Canada under RPAA (REG-3961, registered February 2, 2026).
Monitiva is building cross-border domestic payment infrastructure through which, once payment services launch, users will maintain a safeguarded Local Balance — held in trust by Paytex, in Canadian dollars, in a trust account at a prudentially regulated Canadian financial institution or trust company — and execute domestic payments in Destination countries through a Just-in-Time (JIT) FX mechanism. When a confirmed payment instruction is executed, Paytex converts the required CAD amount and executes the domestic payment in the Destination country (at launch, Local Payment via SPEI in Mexico; Bill Pay and Cardless Withdrawal as they are offered; additional Destination rails as they become available), from the prefunded balance that Paytex will hold with its payment provider in the Destination. No foreign client balance is created at any point. Client funds never leave Canada; once a User-instructed payment is debited from the Local Balance, the amount debited is no longer client funds. Some processing occurs on infrastructure operated by affiliated entities and by service providers. The written data-processing and intercompany agreements governing that processing are being put in place and will be in force before payment services launch. In all cases Monitiva remains the controller of your personal information and determines the purposes and means of its processing.
Data Controller Declaration: Paytex Solutions Ltd. dba Monitiva acts as the data controller for all personal data collected through the Platform, waitlist, and associated services.
1.2 Two Operational Phases Covered by This Policy
CURRENT STATUS — PRE-LAUNCH: Monitiva is currently in a pre-launch phase. The only service available today is waitlist registration. Monitiva does not currently open accounts, accept or hold client funds, or process payments. Accordingly, the Phase 2 processing described below — identity verification, biometric verification, risk assessment, location data, and transaction monitoring — does not occur today. It describes the processing that will apply when payment services launch and you open a Monitiva Account. Only the Phase 1 processing described below applies to you at present.
Phase 1 — Waitlist and Pre-Launch: Collection of interest registration information (name, email, city, user profile, urgency indicator, payment frequency, and monthly spend estimate) through landing pages and waitlist forms, including campaign and marketing analytics.
Phase 2 — Full Platform: Processing of personal and financial information necessary to provide payment services, including identity verification (KYC), risk assessment, transaction processing, regulatory reporting, and AML/CTF compliance.
1.4 Acceptance
By accessing our website, submitting your information for our waitlist, or using our services, you acknowledge that you have read and understood this Privacy Policy and consent to the collection, use, and disclosure of your personal information as described herein, subject to the legal bases set out in Section 4.
2. Scope and Applicable Law
2.1 Jurisdictional Scope
| Jurisdiction | Applicable Law | Applies To |
|---|
| Canada (Federal) | PIPEDA | All users in Canada; all Monitiva data processing |
| Quebec, Canada | Act 25 — Act Respecting the Protection of Personal Information in the Private Sector | Quebec residents; stricter requirements apply |
| Canada (Federal) | CASL — Canada’s Anti-Spam Legislation | All commercial electronic messages and marketing |
| Canada (Federal) | PCMLTFA | Financial service users; regulatory compliance |
| Canada (Federal) | RPAA — Retail Payment Activities Act | Payment service users; operational compliance |
| European Union / EEA | GDPR — General Data Protection Regulation | Users in EU/EEA, including via CA→EU corridor (deferred) |
| Mexico | Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP), published 20 March 2025 and in force 21 March 2025 — repealing the 2010 law of the same name; supervised by the Secretaría Anticorrupción y Buen Gobierno | Processing on the Mexican payout leg of the CA→MX corridor |
3. Information We Collect
3.1 Waitlist and Pre-Launch Registration Data
| Category | Data Collected | Purpose |
|---|
| Identity | First name, last name | Personalizing communications; identifying waitlist participants |
| Contact | Email address | Sending waitlist confirmations, product updates, and launch notifications (CASL consent) |
| Location | City or region (self-selected) | Tailoring landing page content; prioritizing beta launch by geography |
| User Profile | Self-identified category (snowbird, property owner, digital nomad, new arrival, other) | Understanding user segments; prioritizing feature development |
| Urgency Indicator | Timeframe for needing the service | Prioritizing beta access; planning onboarding capacity |
| Payment Frequency | Estimated number of payments per month (self-reported) | Product demand analysis; feature prioritization; onboarding capacity planning |
| Monthly Spend Estimate | Estimated monthly payment volume in CAD (self-reported range) | Market sizing validation; onboarding capacity planning |
| Marketing Consent | Express opt-in consent to receive Monitiva’s newsletter and marketing communications (boolean — checkbox, not pre-selected) | Legal basis for sending commercial electronic messages under CASL; consent record retained for 3 years from last interaction or withdrawal of consent, to evidence consent (under CASL s.13 we bear the onus of proving consent) |
3.2 Technical and Analytics Data (Automatically Collected)
We automatically collect: IP address (anonymized where feasible); browser type, version, and operating system; device type and screen resolution; referring URL and landing page URL; UTM parameters for campaign attribution; pages visited, time spent, and navigation patterns; cookie identifiers; and A/B test variant exposure.
3.3 Personal Identification Information (Platform Users — KYC)
| Category | Specific Data |
|---|
| Identity | Full legal name, date of birth, country of residence (and nationality where shown on the identity document) |
| Identity Documents | Government-issued photo ID (passport, driver’s licence, or equivalent): type, issuing authority, number, expiry date |
| Address | Full residential address; recent proof of address (such as a utility bill or bank statement) |
| Contact | Email address; mobile phone number |
| PEP Declaration | Self-declaration of Politically Exposed Person status |
3.4 Financial and Transactional Information
We collect: details of the Canadian bank account you link to your Monitiva Account in order to fund your Local Balance by pre-authorized debit (account number, institution, and the name of the account holder of record); your pre-authorized debit authorization and the record of it; your Local Balance and transaction history; source of funds documentation; purpose of transactions; and Beneficiary name and domestic payment identifier (CLABE or equivalent).
Account ownership verification. When you link a Canadian bank account, we verify that the account belongs to you by comparing the name of the account holder of record against your verified legal name. We do this to prevent third-party funding, which we do not permit, and to meet our obligations under PCMLTFA and the requirements of our banking partner. If the names do not match, the account cannot be linked and you will not be able to fund your Local Balance from it. You may ask us to review this outcome (see Section 13).
3.5 Risk Assessment and Suitability Information (KYC)
To meet our risk-based obligations under PCMLTFA and to assign appropriate transaction limits, we collect the following at onboarding and, where applicable, at Enhanced Due Diligence (EDD):
| Category | Specific Data |
|---|
| Employment | Employment status and occupation; employer or business name (optional, contextual); industry category |
| Income | Annual income (range) |
| Intended Use | Declared intended use of the account |
| Expected Volume | Expected monthly payment volume (range) |
| Enhanced Due Diligence (higher-risk or higher-limit users) | Source of funds and supporting documentation; source of wealth declaration; detailed intended use; property ownership documentation where relevant |
How we use employer and business information. Where you provide the name of an employer or business, we use it to assess the risk profile associated with your declared occupation and industry, and it may be screened against adverse media sources as part of our AML/CTF due diligence. This screening is directed at the named organization in the context of your risk assessment.
Data minimization by design. Consistent with PIPEDA and Quebec Act 25 minimality requirements, we limit what we collect:
- We do not collect your Social Insurance Number (SIN) or your country of birth. These are not necessary for our MSB/PSP scope and are excluded by design.
- We do not receive or store your online banking credentials. When your bank account is verified, you authenticate with your bank inside an environment hosted by our verification provider; your banking credentials are never transmitted to or held by Monitiva.
3.6 Biometric Verification Information
We collect biometric information — facial images for liveness verification, and biometric data compared against your identity document — through our identity verification and compliance provider Sumsub. Biometric verification occurs at two points:
- At onboarding, as part of the identity verification process required before we can provide you with any financial service.
- On an ongoing basis, at each Cardless Withdrawal request. We re-verify your identity biometrically in the application each time you request a Cardless Withdrawal, before the voucher is issued, to confirm that the person making the request is you. This is a recurring verification for as long as you use Cardless Withdrawal, not a one-time check.
Before identity verification, and before each Cardless Withdrawal request, we ask for your express consent to collect and use your biometric information for identity verification only. You give it by an affirmative action within the verification flow; starting the verification or the request does not by itself constitute consent. If you do not consent, we cannot verify your identity or issue the Cardless Withdrawal voucher. We do not use biometric data for any other purpose, and we do not use it to identify you in any context other than verifying your own identity to your own account.
3.7 Location Information
When you use the payment services, we collect information about where you are located. This is distinct from the website analytics described in Section 3.2 and is used for compliance and fraud-prevention purposes.
| Category | Data Collected | Purpose |
|---|
| IP-based location | The IP address from which each transaction and session originates, and the country and region derived from it | Detecting account takeover and fraud; identifying activity from jurisdictions we do not serve or that are subject to sanctions; assessing your risk profile |
| Precise device location (GPS) | GPS coordinates reported by your device when you request a Cardless Withdrawal | Verifying that you are physically present in the Destination country, and fraud detection |
| Device time zone | The time zone reported by your device | Corroborating your reported location, together with IP and GPS signals |
| Location over time | Whether your sessions consistently originate from a given country over an extended period | Risk assessment. Sustained activity over an extended period from a country other than Canada or the Destination where you use the Services causes us to review your risk profile sooner. |
Cardless Withdrawal location gating. Cardless Withdrawal requires you to be physically present in the Destination country. We verify this using a combination of the signals above; if we cannot confirm your presence, the Cardless Withdrawal request is declined. You may ask us to review this outcome (see Section 13).
What we do not do with location data. We do not use location information for advertising, marketing, or profiling unrelated to compliance and fraud prevention. We do not sell or share it with marketing platforms. We do not use it to determine your tax residency or your immigration status, and we do not report it to tax or immigration authorities except where we are legally compelled to respond to a valid order or regulatory request. Our use of location data is for AML/CTF compliance, fraud prevention, and risk assessment only.
4. Legal Bases for Processing
4.1 Overview
| Legal Basis | Application | Applicable Law |
|---|
| Contractual Necessity | To provide services; to process transactions; to execute payment instructions | PIPEDA; GDPR Art. 6(1)(b) |
| Legal Obligation | To comply with PCMLTFA, RPAA, FINTRAC, sanctions screening, Travel Rule, and tax laws | PIPEDA; GDPR Art. 6(1)(c); PCMLTFA |
| Legitimate Interests | To prevent fraud and financial crime; to ensure security; to manage operational risk | PIPEDA; GDPR Art. 6(1)(f) |
| Express Consent | Marketing and commercial electronic messages (CASL); biometric data processing; non-essential cookies | PIPEDA; CASL; Quebec Act 25; GDPR Art. 6(1)(a) |
4.1.1 Legal Basis by Activity — Waitlist and Pre-Launch Phase
| Activity | Legal Basis | Notes |
|---|
| Waitlist signup (name, email, city, profile, urgency, payment frequency, monthly spend) | Consent | User submits form voluntarily; consent recorded with timestamp and policy version |
| Sending waitlist confirmation email | Contractual necessity / CASL s.6(6) (consent not required) | Transactional message; identification and unsubscribe requirements still apply (CASL s.6(2)) |
| Sending commercial electronic messages | CASL express consent | Separate opt-in checkbox required |
| Analytics — waitlist funnel | Consent (cookie banner) | Only fires after user grants analytics consent |
| Campaign attribution | Consent (cookie banner) | Only fires after user grants marketing consent |
| A/B variant and city variant tracking | Consent (functional cookies) | Required under Quebec Act 25 |
| Security and fraud detection | Legitimate interests | Necessary to protect Platform integrity |
4.2 CASL Compliance
Monitiva fully complies with CASL. We will only send you commercial electronic messages if you have provided express consent through our waitlist form or platform registration. Every commercial message identifies Monitiva as the sender, provides our complete contact information, and includes a clear, functioning unsubscribe mechanism honored within 10 business days. We maintain records of how and when consent was obtained. Withdrawal of consent does not affect transactional or service messages.
4.3 Quebec Act 25 — Specific Requirements
Although the payment Services are not offered to residents of Quebec at this time (see the Terms of Use), a Quebec resident’s personal information may still be processed — for example, through waitlist registration or an application that is declined. Where we process the personal information of a Quebec resident, the protections of Quebec Act 25 apply. For Quebec residents, we apply: the principle of minimality (we collect only the minimum personal information necessary); clear, specific information about each purpose before collection; express consent before using information for purposes not identified at collection; Privacy Impact Assessments (PIAs) before implementing new technologies; data portability in structured, machine-readable format; and the ability to request de-indexation of information. The privacy assessment that Quebec law requires before the personal information of a Quebec resident is communicated outside Quebec — including to the hosting described in Section 7 — is pending. Either that assessment will be completed before any such information is communicated outside Quebec, or that information will not be collected.
5. How We Use Your Information
5.1 Waitlist and Pre-Launch Activities
- Sending waitlist confirmation, position updates, and launch notifications
- Communicating product developments, beta access invitations, and early adopter offers (with CASL-compliant consent)
- Analyzing demand by geography and user profile
- Running A/B tests on messaging to optimize the product before launch
- Prioritizing beta access based on urgency, profile, and geographic alignment
- Sending newsletter content and marketing communications of potential interest to the User — including cross-border payment tips, product updates, and corridor-specific information — exclusively to Users who have provided separate express opt-in consent in accordance with CASL at the time of waitlist registration. Each communication will identify Monitiva as the sender, include complete contact information, and provide a clear unsubscribe mechanism honored within 10 business days.
5.2 Platform Service Delivery
- Verifying ownership of the Canadian bank account you link, and processing Local Balance funding by pre-authorized debit (PAD) against that account
- Executing JIT FX conversions and domestic payment instructions in the Destination country
- Maintaining RPAA-compliant Trust Account sub-ledgers for each client
- Providing customer support and resolving service issues
5.3 Regulatory Compliance
- Complying with PCMLTFA, including filing Suspicious Transaction Reports (STRs), Electronic Funds Transfer Reports (EFTRs), and Listed Person or Entity Property Reports (LPEPRs) with FINTRAC
- Complying with RPAA operational and incident reporting requirements to the Bank of Canada
- Conducting sanctions screening against applicable Canadian, US, UN, and EU lists
- Implementing and maintaining our AML/CTF program, including transaction monitoring and risk classification
5.4 Travel Rule Compliance
Where required by law, we include information identifying you and the beneficiary with the payment instruction and share it with the institutions involved in executing the transfer. This is a mandatory legal requirement under PCMLTFA and does not require additional consent.
5.5 Fraud Prevention, Security, and Business Improvement
We use your information to detect and prevent fraudulent activity and account takeover; maintain audit trails for security and compliance; analyze service usage to improve our product; and personalize the user experience based on your profile and preferences.
6. Information Sharing and Disclosure
6.1 Service Providers
We share personal information with service providers strictly as necessary to deliver and safeguard the service. With the exception of Sumsub (named below given its role in identity verification and compliance), providers are described by function rather than by name; where they relate to cookies and analytics, the specific vendors are listed in our Cookie Policy.
| Provider | Purpose | Data Shared |
|---|
| Sumsub (identity verification and compliance provider) | KYC identity verification, biometric liveness check, document-authenticity and tamper detection on identity, banking, and enhanced-due-diligence documents, and sanctions/PEP/adverse-media screening. Transaction monitoring will be performed by a transaction-monitoring provider that will be contracted and in operation before any user can make a payment | Identity documents, banking and EDD documents, biometric data, KYC and risk-assessment data, and screening results |
| Cloud infrastructure provider | Cloud infrastructure and data storage for the Platform, including the core banking system: Amazon Web Services, eu-west-1 (Ireland) region, with the hosting operated for Paytex by Variant Technologies Holdings, S.L. (Spain), a company under common control with Paytex (Section 7); the written agreements governing this processing are being put in place and will be in force before payment services launch (Section 1.1) | All customer data, including identity-verification (KYC) data; designed to be encrypted at rest and in transit (Section 9.1) |
| Bank account verification provider | Verifying ownership of the Canadian bank account you link, through an environment hosted by the provider in which you authenticate with your bank; your banking credentials are never received by Monitiva | Account ownership and account details returned by the verification; processed in Canada with no additional sub-processors, according to the provider; contractual confirmation is pending |
| Prudentially regulated Canadian banking partner / trust company | Holding all client funds in trust in the Trust Account; execution of pre-authorized debits and withdrawals; verification of the account holder of record when you link a bank account; management of Paytex’s corporate operating accounts, once opened (the trust-account agreement is not yet executed; no account is open) | Client sub-ledger identifiers; account holder name for verification; transaction data; RPAA-required records |
| Regulated money-services provider in the Destination (Mexico) | Execution of the domestic payment in Mexico, as the provider engaged by Paytex to execute payments in that country, under a contract with Paytex for SPEI payments; arrangements for the other Services are being put in place. No client funds are held in Mexico. | Beneficiary and transaction data necessary to execute the payment in Mexico. Transferred under the data-protection terms being put in place with the provider (Section 1.1). No client funds deposited in Mexico. |
| Domestic payment infrastructure partner — Destination Corridor (CA→EU) | SEPA payment processing for CA→EU corridor (deferred launch); operative account management in Europe (corporate capital only) (planned; not yet engaged) | Transaction data for EU corridor participants only. No foreign client funds deposited. |
| International settlement / FX rebalancing partner | Bilateral net settlement of Corridor Prefunding Pools between jurisdictions (corporate capital operations only) (planned; not yet engaged) | Aggregate corporate settlement data only — no individual client personal data |
| Core banking and sub-ledger system | Internal sub-ledger management; Local Balance tracking; enforcement of limits and the retained balance cap; transaction audit trail | All transaction and balance data. The core banking system is to be operated by Paytex under a licence from Variant Technologies Holdings, S.L.; that licence is being put in place and will be in force before payment services launch. The core banking system is hosted as described in the cloud infrastructure row; processing by affiliated entities and service providers occurs under the written agreements that are being put in place and will be in force before payment services launch (Section 1.1), subject to Section 7. Monitiva remains the controller of this data and determines the purposes and means of its processing. |
| Communications provider | Delivering service and transactional messages (waitlist confirmations, notifications, security and account alerts) and, where you have given consent, marketing communications on Monitiva’s behalf. The provider processes your personal information only to deliver these messages on Monitiva’s behalf; the written data-processing agreement governing this processing is being put in place (Section 1.1); Monitiva remains the controller and determines the purposes and means. | Contact details (name, email, and, where applicable, phone number), message content and delivery status, and consent and unsubscribe status. No financial account or transaction data is shared for this purpose. Processing may occur outside Canada (see Section 7). |
| Analytics providers | Campaign performance measurement; waitlist conversion tracking. See our Cookie Policy for the complete list of analytics providers and opt-out mechanisms. | Anonymized or pseudonymized behavioral data; UTM parameters; conversion events. No financial data shared. |
6.2 Regulatory Authorities
| Authority | Report Type | Legal Framework |
|---|
| FINTRAC | STR, EFTR, LPEPR | PCMLTFA |
| Bank of Canada | RPAA compliance reports, incident reports (within 48 hours for material incidents) | RPAA |
| RCMP / CSIS | Disclosure of property of listed or designated persons and related transactions, without delay | Criminal Code and Canadian sanctions legislation |
| Law enforcement agencies | Upon valid court orders or legal requests | Applicable Canadian laws |
| Office of the Privacy Commissioner (OPC) | Material privacy breach notifications | PIPEDA |
| Commission d’accès à l’information (CAI) | Confidentiality incident notifications presenting risk of serious harm | Quebec Act 25 |
6.3 What We Do NOT Do
Monitiva does not, and will not: sell, rent, or trade your personal information to third parties for marketing purposes; share your information with advertisers or ad networks for behavioral targeting on other platforms; or use your financial transaction data or Local Balance information for purposes other than providing and improving our services and complying with legal obligations.
7. International Data Transfers
As a cross-corridor domestic payment service provider, your personal information may be transferred to and processed in countries outside of Canada, including Mexico and, in future phases, other Destination jurisdictions. These transfers are necessary to process cross-border payments, comply with Travel Rule requirements, and work with our international partners. Your personal information may also be processed outside Canada by service providers that act on our behalf — for example, the communications provider described in Section 6.1; the written data-processing agreements that require protection consistent with this Policy are being put in place and will be in force before payment services launch (Section 1.1). Monitiva’s production systems and data — including customer and identity-verification (KYC) data and the core banking system — will be hosted on Amazon Web Services in the eu-west-1 (Ireland) region, with the hosting operated for Paytex by Variant Technologies Holdings, S.L. (Spain), a company under common control with Paytex. Your personal information may also be accessed from Mexico by personnel of GTI Ads Latam, S.A.P.I. de C.V., a company under common control with Paytex that is to provide operational support to Paytex, once Paytex has authorised that access. In each case Paytex remains accountable for your personal information and will require, by written agreement, protection comparable to that required in Canada; those agreements are being put in place and will be in force before payment services launch (Section 1.1). For transfers to the EU/EEA, we will use Standard Contractual Clauses (SCCs). For transfers to Mexico, we comply with the requirements of Mexico’s Federal Law on the Protection of Personal Data Held by Private Parties (2025). By using our services, you expressly consent to the transfer of your personal information to the Destination countries necessary to complete your transactions.
8. Data Retention
| Record Type | Retention Period | Legal Basis |
|---|
| Waitlist registration data | Until 12 months after platform launch, unless earlier withdrawal of consent | CASL; PIPEDA; legitimate interests |
| Transaction records | Minimum 5 years from the date the transaction was conducted (PCMLTFA; Document Retention Policy) | PCMLTFA / FINTRAC |
| Customer identification and risk-assessment records (KYC) | Minimum 5 years after the end of the business relationship (PCMLTFA; Document Retention Policy) | PCMLTFA / FINTRAC |
| FINTRAC reports (STR, EFTR, LPEPR) and related investigation records | Minimum 5 years from filing or investigation-file closure; longer where required (PCMLTFA; Document Retention Policy) | PCMLTFA; Document Retention Policy |
| Local Balance sub-ledger records | Minimum 5 years, retained as part of RPAA safeguarding records | RPAA; PCMLTFA |
| Location data associated with transactions | Retained as part of the transaction record: minimum 5 years | PCMLTFA / FINTRAC |
| Biometric verification data | Each biometric check (at onboarding and at each Cardless Withdrawal request) is not retained by Monitiva once that verification is complete; our identity-verification provider retains it only for the period set out in its contractual retention terms, after which it is deleted. The record that a verification occurred, and its outcome, is retained as part of your KYC and transaction records. | PIPEDA; express consent |
| Bank account verification records | Retained by Monitiva as part of the funding-source and KYC record for the periods stated above, independently of the verification provider’s own retention. Where the provider anonymizes or deletes on its own schedule, Monitiva’s own records remain the system of record. | PCMLTFA; RPAA |
| CASL consent records | 3 years from last interaction or withdrawal of consent, to evidence consent (under CASL s.13 we bear the onus of proving consent) | CASL s.13 (onus of proving consent) |
| Security incident and investigation files | Minimum 5 years after closure; longer where required for ongoing regulatory, legal, or investigative purposes | RPAA; PIPEDA; Document Retention Policy |
9. Data Security
9.1 Safeguards
Monitiva is implementing safeguards appropriate to the sensitivity of personal information, designed to include encryption of data in transit and at rest, role-based access control with multi-factor authentication for privileged access, network and application security controls, monitoring and audit logging, and backup and recovery arrangements. These safeguards will be in operation before payment services launch. Today we hold only waitlist and website data (Section 1.2). Access to personal information is to be granted on a least-privilege basis and reviewed periodically.
9.2 Fund Segregation Security
Once payment services launch, client funds (Local Balances) will be held in trust in the Trust Account and segregated from Paytex’s own corporate funds. Client funds are not Paytex’s property, are not used to fund Paytex’s operations, and are not available to Paytex’s creditors. This segregation protects client funds and is a non-negotiable operational requirement under RPAA safeguarding obligations.
10. Security Breach Notification
In the event of a breach affecting your personal information that poses a real risk of significant harm, we will notify you as soon as feasible, as required by law. As an internal service standard — not a legal requirement — Monitiva applies a self-imposed maximum of 72 hours after determining that the breach poses a real risk of significant harm (or, for Quebec residents, a risk of serious injury); where the law requires faster notification, that requirement governs. Where the breach is also a material incident under the RPAA that affects you, we will notify you without delay. We will also notify: the Bank of Canada, without delay and no later than 48 hours after a materiality determination for a material incident, under the RPAA; FINTRAC as required by PCMLTFA; the Office of the Privacy Commissioner of Canada (OPC) for breaches posing a real risk of significant harm; and the Commission d’accès à l’information du Québec (CAI) for incidents presenting a risk of serious injury to Quebec residents whose personal information we have processed.
11. Your Privacy Rights
11.1 Rights Under PIPEDA (All Canadian Residents)
You have the right to: access the personal information we hold about you; request correction of inaccurate or incomplete information; withdraw consent for processing activities based on consent (subject to mandatory legal retention obligations); and file a complaint with the Office of the Privacy Commissioner of Canada (OPC).
11.2 Additional Rights Under Quebec Act 25
Quebec residents have additional rights including: data portability in structured, machine-readable format; de-indexation requests; information about automated decisions significantly affecting you; and human review of automated decisions.
11.3 Additional Rights Under GDPR (EU/EEA Residents)
EU/EEA residents have additional rights including: data portability; restriction of processing; right to object; erasure (“right to be forgotten”, subject to mandatory PCMLTFA retention obligations); and the right not to be subject to solely automated decisions with legal effects.
11.4 CASL Unsubscribe Rights
You may withdraw consent to receive commercial electronic messages at any time by clicking the unsubscribe link in any commercial email, emailing privacy@monitiva.com, or updating your communication preferences in your account settings. We will honor unsubscribe requests within 10 business days.
12. How to Exercise Your Rights
To exercise any of your privacy rights, contact us at: privacy@monitiva.com | Subject: “Privacy Rights Request — [Type of Request]” | or by post: Paytex Solutions Ltd. (Monitiva), Attention: Compliance Officer (delegated privacy function), 130 Spadina Avenue, Unit 807, Toronto, Ontario M5V 2L4, Canada. We will verify your identity before processing your request. Standard response timelines: PIPEDA — 30 days (extendable by 30 days with notice); Quebec Act 25 — 30 days (no extension); GDPR — 30 days (extendable by 60 days for complex requests).
13. Automated Decision-Making
Once payment services launch, Monitiva will use automated systems to support onboarding, risk classification, and monitoring. Identity verification and sanctions and adverse-media screening are performed by our identity-verification and screening provider; transaction monitoring will be performed by a transaction-monitoring provider that will be contracted and in operation before any user can make a payment; the enforcement of limits and of the retained balance cap is performed in the core banking system, which Paytex is to operate under a licence from Variant Technologies Holdings, S.L.; that licence is being put in place and will be in force before payment services launch. You are never shown the underlying risk score, weights, or thresholds; you see only the outcome (for example, an assigned limit, a request for additional documentation, or a decision on your application).
| Area | Purpose | Potential Impact |
|---|
| KYC Verification | AI-powered identity document validation and liveness check | Account opening approval or rejection |
| Transaction Monitoring | Detection of suspicious activities and unusual patterns | Transaction hold or block; compliance alerts; FINTRAC reporting |
| Risk Assessment | Customer risk classification for AML/CTF due diligence | Assigned transaction limits; Enhanced Due Diligence requirements; account approval or denial |
| Fraud Detection | Identification of fraudulent patterns in real time | Temporary account suspension; hold on transactions |
| Account Ownership Verification | Comparison of the account holder of record on the bank account you link against your verified legal name | Refusal to link the account; inability to fund your Local Balance from that account |
| Cardless Withdrawal Location Gating | Verification, from IP, GPS, and device time zone signals, that you are physically present in the Destination country, together with biometric re-verification | Real-time refusal of a Cardless Withdrawal request |
| Payment Hold and Review | Automated flagging of a payment instruction against our transaction monitoring rules | The payment is paused pending review before it is executed |
You have the right to request human review of any automated decision that significantly affects you, including a refusal to link a bank account, a declined Cardless Withdrawal request, an assigned limit, a paused payment, or a decision on your application. A manual review path will exist for these decisions, and a member of our compliance team — not an automated system — makes the final determination on review. Contact compliance@monitiva.com with the subject “Automated Decision Review”.
Where we are legally prohibited from disclosing the reason for a decision — for example, where disclosure would constitute prohibited tipping-off under PCMLTFA — we will tell you that a review has been conducted, without disclosing the underlying reason.
14. Cookies and Tracking Technologies
We use cookies and similar tracking technologies on our website and platform. For a complete description of the cookies we use, your consent options, and how to manage your preferences, please read our Cookie Policy at https://monitiva.com/cookies.
15. Marketing Communications
Service-related messages (waitlist confirmation, account security alerts, transaction receipts (delivered in-app; email or push notices carry no transaction data), regulatory notifications, material policy changes) are sent without additional consent. Commercial electronic messages are sent only with CASL express consent obtained through a clear, separate opt-in mechanism. You may withdraw consent at any time.
16. Changes to This Policy
We may update this Privacy Policy to reflect changes in our services, legal requirements, or data practices. We will notify you of material changes by updating the “Last Updated” date, posting a notice on our website, sending an email notification to registered users, and requesting renewed consent where required by law.
| Version | Date | Summary |
|---|
| 2.6 | 22 October 2026 | Supersedes v2.5. Monitiva described as building the service, with users maintaining a Local Balance once payment services launch; Local Payment via SPEI at launch and Bill Pay and Cardless Withdrawal as they are offered; payments from the prefunded balance that Paytex will hold (§1.1). Transaction monitoring attributed to a provider to be contracted and in operation before any user can make a payment; Sumsub’s role limited to identity verification, biometrics, document authenticity and screening (§6.1, §13). Banking-partner row: corporate operating accounts once opened; trust-account agreement not yet executed and no account open. Destination provider engaged under a contract for SPEI payments, with arrangements for the other Services being put in place; EU and settlement/FX partners marked as planned and not yet engaged (§6.1). Production hosting stated in the future tense (§7). Holding and segregation of client funds stated as from launch (§9.2). Automated decision-making and the manual review path stated as from launch (§13). No other change. |
| 2.5 | 21 October 2026 | Supersedes v2.4; core banking licence described as being put in place; draft markers removed. The licence from Variant Technologies Holdings, S.L. under which Paytex is to operate the core banking system is described as being put in place and in force before payment services launch (§6.1, §13); the three draft markers in §6.1 and §7 replaced by a reference to Section 1.1; hosting on Amazon Web Services described as operated for Paytex by Variant (§1.1, §6.1, §7); the requirement of comparable protection by written agreement stated as future, consistent with those agreements being put in place (§7). No other change. |
| 2.4 | 8 October 2026 | Supersedes version 2.3; effective on publication (header). Privacy contact stated as the Compliance Officer exercising the delegated privacy function; no separate Privacy Officer (header, §1.3, §12, §17.1). Paytex Solutions Ltd. identified as the corporation and the point at which debited amounts stop being client funds stated (§1.1). CASL consent-record retention stated in the same terms in §3.1 and §8 and tied to the onus of proving consent and the waitlist confirmation message described correctly (§4.1.1). Biometric consent stated as express, given by an affirmative action (§3.6). GPS collected only for Cardless Withdrawal; location-over-time review limited to countries other than Canada and the Destination (§3.7). Quebec: the assessment required before communication outside Quebec stated as pending — either it is completed before any such communication, or that information is not collected (§4.3); 30-day response period without extension (§12). Hosting on Amazon Web Services in Ireland through Variant Technologies Holdings, S.L., possible access from Mexico by GTI Ads Latam once authorised, and the bank-account verification provider’s sub-processors described (§6.1, §7; provisional, to be aligned with the data-processing agreement). RCMP/CSIS disclosures described under the Criminal Code and sanctions legislation (§6.2). Security safeguards described as being implemented, to be in operation before launch (§9.1). Breach notice: 72-hour self-imposed maximum measured from the real-risk-of-significant-harm determination, and notice without delay for a material RPAA incident (§10). Core banking system described as operated by Paytex under licence from Variant (§13). Summary of version 2.3 restored as originally issued, with a replacement note (§16). |
| 2.3 | 29 September 2026 | Pre-signature reconciliation pass. Updated the Mexican data-protection reference to the Federal Law on the Protection of Personal Data Held by Private Parties (published 20 March 2025, in force 21 March 2025; supervised by the Secretaría Anticorrupción y Buen Gobierno), replacing the 2010 framework, and scoped it to processing on the Mexican payout leg (§2.1, §7). Confirmed the FINTRAC report set as STR/EFTR/LPEPR with no LCTR (cashless model). Removed the residual reference to the Compliance Officer’s name from the version history, consistent with the functional-drafting principle (role only). Made country of residence the primary residency identifier in the Identity data category, with nationality collected only where shown on the identity document, matching the identity-verification practice and data-minimization principle (§3.3). Minor reference corrections; no change to the effective date. Stated execution as occurring when a confirmed instruction is executed, not at the instant of confirmation, and Paytex as trustee of the Local Balance (§1.1). Described the Mexican provider as engaged by Paytex to execute payments rather than as a correspondent, and the core banking infrastructure as operated by Paytex (§6.1, §13). Stated that transaction receipts are delivered in-app and that email or push notices carry no transaction data (§15). Described execution from Paytex’s prefunded balance with the Destination provider (§1.1) and corrected the supervisory-authorities table (§17.2). Registered office address stated in one form. Stated that the written data-processing and intercompany agreements are being put in place and will be in force before launch (§1.1, §6.1, §7). Biometric retention stated by reference to the provider’s contractual terms (§8). Bank-account-verification sub-processor confirmation stated as pending (§6.1). |
| 2.2 | 29 September 2026 | Consolidated amendment aligning to the compliance suite. Lowered the granularity of the security-safeguards description to appropriate-to-sensitivity terms, removing named control specifications that cannot be independently evidenced and removing internal-only commitments (§9.1). Renamed Cash Pickup to Cardless Withdrawal throughout (§3.6, §3.7, §13). Described the core banking system and hosting in functional terms (processing on infrastructure operated by Monitiva and affiliated entities/providers; Monitiva remains controller) (§1.1, §6.1). Split automated processing between the identity/screening provider and Monitiva’s core banking system (§13). Described the three products (§1.1). Renamed the designated-property report to LPEPR (§5.3, §6.2, §8). Added document-authenticity/tamper detection to the provider’s role (§6.1). Described the Mexican executor and the international transfer functionally (§6.1). Added a bank-account-verification minimization statement — no banking credentials received (§3.5) — and its data-residency and retention treatment (§6.1, §8). Noted that Quebec residents are excluded from the service while retaining Act 25 protections for any processing that occurs (§4.3). Aligned all retention periods to the minimum five-year base rule of the Document Retention Policy, removing the unsupported seven-year figures (§8). Reframed the breach-notification section so the 72-hour figure is stated as a self-imposed maximum rather than a legal requirement, and the 48-hour Bank of Canada notice runs from the materiality determination (§10). §6.2 aligned to §5.3 and to the AML/CTF Policy: LCTR does not apply (cashless model); FINTRAC report set = STR/EFTR/LPEPR. Added disclosure of the communications provider that delivers service and marketing messages as a processor of personal information under a written agreement, with Monitiva as controller (§6.1), and covered its possible processing outside Canada in the international-transfers section (§7). |
| 2.1 | July 2026 | Added a pre-launch status disclosure (§1.2). Added a location information section (§3.7) disclosing IP, GPS, device time zone, and location-over-time processing and their purposes. Disclosed that biometric verification recurs at each Cardless Withdrawal request, not only at onboarding, and updated the corresponding retention entry. Described funding as a pre-authorized debit against a linked account, and disclosed account ownership verification at linking (§3.4). Disclosed the use of employer and business name for adverse-media screening (§3.5). Added account ownership verification, Cardless Withdrawal location gating, and payment hold-and-review to the automated decision-making table (§13). Replaced the “FBO Account” label with the Trust Account structure and aligned the fund segregation description (§1.1, §5.2, §6.1, §9.3). |
| 2.0 | June 2026 | Aligned to the per-transaction pricing model (removed subscription “plan preference” and plan-based purposes). Migrated to the Local/Destination lexicon (“Local Balance”). Recorded the Compliance Officer as the contact for privacy and compliance matters (by role). Named Sumsub as the identity-verification and compliance provider; other providers described by function. Added risk-assessment KYC data (§3.5) and an explicit data-minimization statement (no SIN, no country of birth). Set funding to EFT only. Updated retention to the minimum five-year base rule. Clarified automated decision-making. |
| 1.0 | April 2026 | Initial version |
17. Contact and Supervisory Authorities
17.1 Contact Monitiva
| Channel | Details |
|---|
| Privacy Contact | Compliance Officer (delegated privacy function) — privacy@monitiva.com |
| Compliance Officer | compliance@monitiva.com |
| General Inquiries | hello@monitiva.com |
| Website | https://monitiva.com |
| FINTRAC MSB | C100000118 |
| BoC PSP | REG-3961 |
| Postal Address | 130 Spadina Avenue, Unit 807, Toronto, Ontario M5V 2L4, Canada |
17.2 Supervisory Authorities
| Jurisdiction | Authority |
|---|
| Canada (Federal) | Office of the Privacy Commissioner of Canada — www.priv.gc.ca — 1-800-282-1376 |
| Quebec | Commission d’accès à l’information du Québec (CAI) — www.cai.gouv.qc.ca — 1-888-528-7741 |
| EU/EEA | Data protection authority in your country of residence. See: https://edpb.europa.eu |