This policy reflects the controls implemented in the current platform and must be reviewed against the final legal entity, vendors, data flows, and province-specific obligations before production publication.
Accountability and scope
MapleFind designates a privacy lead responsible for personal information under our control. This policy covers information collected through MapleFind.ca, listing submissions, claims, corrections, advertising enquiries, and direct communications.
Public facts about a business can still involve personal information when they identify a sole proprietor or individual. We apply purpose, accuracy, access, and safeguard controls accordingly.
What we collect
We may collect the information you submit, including name, business role, response email, message, consent records, and evidence needed to assess a listing request. Routine server logs may include IP address, user agent, requested URL, time, and security events.
Public listings use reviewed business facts such as business name, public contact methods, service area, official website, public social profiles, and source freshness. Private research captures, outreach records, credentials, and model traces are not published as listing metadata.
Purposes and consent
We use information to operate and secure the directory, answer requests, verify authority to claim a record, correct or remove inaccurate information, assess advertising enquiries, prevent abuse, and meet legal obligations. We identify the purpose at or before collection and do not require consent for unrelated optional uses.
Optional analytics and advertising storage remain disabled unless you choose them. You may withdraw that choice from “Privacy choices” in the footer; withdrawal applies going forward.
Public sources and directory research
Candidate business facts may be observed on official business websites, government or registry sources, and official public profiles. Every public fact in the ingestion model can reference a source record and observation date. Unknown facts remain unknown, conflicts go to review, and another directory is not treated as automatically authoritative.
Retention and deletion
We keep information only as long as needed for the identified purpose, legal obligations, dispute handling, security, or defensible audit records. Directory provenance may be retained while a public fact remains active and for a limited period afterward. Rejected or abandoned requests are scheduled for deletion or de-identification under an approved retention schedule.
Safeguards and breaches
Safeguards are proportionate to sensitivity and include least-privilege access, restricted provenance, authenticated publishing, no public integration credentials, input validation, logging minimization, backups, and incident response. If a breach creates a real risk of significant harm, MapleFind’s response process includes required regulator reporting and affected-person notification. Records are kept for all security safeguard breaches as required.
Access, accuracy, and challenges
You may ask whether we hold personal information about you, request access, challenge its accuracy, or ask how it has been used or disclosed, subject to lawful exceptions and identity verification. Listing-specific corrections, disputes, claims, and removals use dedicated workflows so they reach editorial review.
Questions or challenges can be sent to privacy@maplefind.ca. Please do not send identity documents or sensitive information until we explain a secure verification method.
Canadian privacy laws
PIPEDA applies to many private-sector commercial activities across Canada. Substantially similar provincial private-sector laws may apply in Alberta, British Columbia, or Quebec, and other sector-specific rules may also apply. This implementation is a technical and editorial baseline, not a substitute for advice about MapleFind’s final corporate structure, vendors, or processing operations.
Official guidance used
This baseline follows the Office of the Privacy Commissioner of Canada’s PIPEDA fair information principles, meaningful consent guidance, and breach reporting guidance. The governing statute should be checked in its current consolidated form.
Changes to this policy
Material changes will be dated and explained. If a change creates a new use requiring consent, we will seek an appropriate choice before that use begins. Last implementation review: July 26, 2026.