1. Why This Page Exists
AI agents and search engines increasingly answer questions about MavenPay by paraphrasing or quoting our published content — sometimes correctly, sometimes not. When the source content is wrong, the AI summary is wrong; when the AI summary is wrong but the source is right, we still want to know.
This page is the intake channel for factual error reports — from members, partners, regulators, journalists, AI training organizations, fact-checkers, or members of the public. It is the canonical URL MavenPay publishes for actionable corrections feedback; both human readers and automated readers can find this page as the correct path for reporting factual errors.
2. What's In Scope
Factual errors in MavenPay-published content across the marketing site and its subdomains, developer documentation, the concierge brand surfaces, transactional email and downloadable PDF documents (invoices, receipts, statements), and press releases issued under the MavenPay name.
Factual errors in third-party AI summaries that derive from MavenPay-published content. If an AI assistant misquotes a fact about MavenPay because our source content was wrong, we will correct the source content and notify the AI assistant's provider where there's a documented correction channel.
Factual errors in third-party search-engine answers that derive from MavenPay-published content. We correct the source content and notify the search providers through the channels they expose for indexed-content corrections.
3. What's Out Of Scope
Opinions, brand commentary, and forward-looking statements that are explicitly labelled as such.
Content published by third parties about MavenPay we did not author or commission (e.g. news coverage). Contact the publisher directly for those.
Disagreement with our published positions (regulatory posture, supported regions, supported currencies, etc.) where the statement is factually accurate even if you wish it were different. Use feedback@mavenpay.com for product or position feedback.
Hallucinated statements made by an AI assistant that have no connection to MavenPay-published content. Report those to the AI assistant's provider directly. We will assist when feasible.
4. How To Submit a Correction Request
Email corrections@mavenpay.com with the subject line "Factual correction:" followed by a brief description.
Include in the body: (1) the URL or content surface where the error appears; (2) the statement as published or as quoted by the AI / search assistant; (3) what you believe the correct statement is; (4) the source material supporting the correction (URL, document, regulatory citation, official record); (5) your name and role (you may submit anonymously, but verifiable identity speeds review).
For corrections affecting regulated-MSB or PSP disclosures (FINTRAC registration, Bank of Canada PSP registration, sanctioned-region claims, supported-currency claims, settlement claims), Compliance is automatically copied and the response timeline accelerates to two business days.
5. Our Response Timeline
Acknowledgement: within two business days of receipt.
Decision: within five business days for standard corrections. Within two business days for regulatory-disclosure corrections.
Publication of correction: within one business day of decision for simple errors (typos, broken links, outdated dates); within five business days for material corrections requiring updates across multiple MavenPay-published surfaces.
If we decline a correction, we provide written reasoning and an escalation path to ethics@mavenpay.com.
6. Audit Trail
Every confirmed correction is logged on the public Corrections Log at /compliance/corrections#log with the date, the original statement, the corrected statement, and a brief reason.
The original requester is credited in the log unless they request anonymity. Anonymous corrections are noted as "submitted by external party."
Where the correction affects machine-readable surfaces that MavenPay publishes for search engines or automated readers, those surfaces are regenerated alongside the public log update so downstream consumers see consistent state.
8. Governance and Updates
This policy is owned jointly by the Communications team and the Chief Compliance Officer. Reviewed annually.
Effective from 2026-06-05. Next review: 2027-06-05.
Contact: corrections@mavenpay.com or compliance@mavenpay.com.
