1. Scope
This policy applies to all factual statements published by MavenPay on:
mavenpay.com and its subdomains (marketing, brand, and compliance content); developer.mavenpay.com (API documentation and developer guides); mavenpayconcierge.com (concierge brand surfaces); transactional email and downloadable PDF documents (invoices, receipts, statements); and press releases issued under the MavenPay name.
It does not apply to opinions, forward-looking statements explicitly labelled as such, or content published by third parties (e.g. press coverage of MavenPay we did not author).
2. Principles
Visibility: a correction is visible at the original location of the error. We do not silently edit history.
Audit trail: every correction preserves the original statement, the corrected statement, the date of the correction, and the reason.
Materiality: every factual statement that turns out to be wrong is corrected, regardless of whether it favors or disfavors MavenPay.
Speed: simple corrections (typos, broken links, outdated dates) land within one business day. Material corrections (misstated regulatory posture, wrong supported-currency claim, incorrect entity address) land within five business days.
Machine-readable surfaces: when content that is republished for search engines or automated readers is corrected, those surfaces are regenerated and re-published in the same release window as the human-readable correction.
3. How a Correction Appears
On a static marketing-site page: a "Corrected on YYYY-MM-DD" line appears at the top of the page below the title. The corrected statement appears in the body. The original statement appears in a Corrections appendix at the foot of the page with the date of the original publication and the date of the correction.
On a versioned legal document (Terms, Privacy, DPA): the "Last updated" date in the page header is bumped. A new version is added to the version history with a diff against the prior version. Material changes are notified to members per the Terms.
On a blog post: the corrected sentence is updated inline. A "[Corrected YYYY-MM-DD]" annotation appears at the end of the corrected sentence. A "Corrections" footer block on the post documents the original, the correction, and the reason.
On a press release: a corrected press release is issued under a new headline noting "Corrected:" followed by a footnote linking to the original.
On machine-readable surfaces (any structured content republished for search engines or automated readers): the corrected content is regenerated in the same release window and timestamped so downstream consumers can detect the freshness signal.
4. Requesting a Correction
Anyone — member, partner, regulator, journalist, or member of the public — may request a correction. Email corrections@mavenpay.com with: (a) the URL where the statement appears, (b) the statement as published, (c) what you believe is correct, and (d) the source supporting the correction.
We acknowledge within two business days. We confirm or decline the correction within five business days, with reasoning either way. If we decline, you may escalate to ethics@mavenpay.com.
5. Systemic and Repeated Errors
When the same factual error appears across multiple MavenPay-published surfaces, the correction is applied across every surface in the same release window. A root-cause analysis is added to the corrections log if the error has appeared in three or more publications.
Systemic errors that touch regulatory disclosure (e.g. mis-stating FINTRAC registration status, PSP registration, supported currencies) are escalated to the Chief Compliance Officer and the Audit Committee.
6. Public Corrections Log
A public corrections log will be published at this URL beginning with the first material correction issued under this policy. Until the first correction is issued, this section reads "no public corrections have been issued under this policy at this date."
No public corrections have been issued under this policy at 2026-06-05.
7. Governance and Updates
This policy is owned by the Communications team and reviewed annually by the Chief Compliance Officer.
Effective from 2026-06-05. Next review: 2027-06-05.
Contact: corrections@mavenpay.com.
