Privacy framework
Effective on 29 June 2026
Coverage of this notice
This notice explains how Income AI Path Inc. manages personal information in connection with incomeaipath.pro, programme registration, learner support, and related operational services. Our approach aligns with PIPEDA principles and practical safeguards suitable for vocational education delivery in Canada.
Governance and accountability
A designated privacy contact oversees policy adherence, incident handling, and response workflows. Internal roles and responsibilities are documented so staff and facilitators understand expectations. Governance reviews help ensure controls remain effective as services, tools, and legal interpretations evolve.
Purpose transparency
We communicate collection purposes in plain language at or before collection. Typical purposes include enquiry response, enrolment management, billing, scheduling, communication, and quality improvement. We avoid unrelated secondary use unless new notice and consent requirements are satisfied.
Consent handling
Consent is obtained through understandable notices and user-controlled choices. Optional fields are identified, and required fields are limited to operational necessity. The PIPEDA consent checkbox in contact forms is not preselected. Cookie preferences are managed separately and can be revisited through browser tools.
Collection minimisation
We collect only data reasonably necessary for the stated purpose. Information may include name, contact details, registration choices, and payment references. We discourage submission of unnecessary sensitive details and provide guidance for safer sharing during practical AI exercises.
Learner records
Programme administration may involve attendance logs, assignment submissions, facilitator notes, and checkpoint progress records. These files support educational continuity and completion verification. Access is limited to authorised personnel with legitimate operational need, and retention windows are reviewed for proportionality.
Payments and accounting
Transactions are processed through service providers with contractual safeguards. We retain billing records required for accounting and legal compliance while avoiding storage of full payment card data on local systems. Access to financial records is role-restricted and monitored.
Support correspondence
Communication records from email and support channels may be retained to resolve issues, document commitments, and improve service quality. Where operational and legal requirements permit, older correspondence is anonymised or deleted after relevance declines.
Technical logs
Security and performance logs may include IP details, browser characteristics, timestamps, and error traces. These records support reliability, abuse detection, and troubleshooting. Retention periods are calibrated to operational requirements rather than indefinite storage.
Cookie and storage categories
Essential storage supports security and user preference continuity. Optional analytics storage is activated only with consent. Promotional tracking remains off by default. Detailed category information and controls are provided in the Cookie policy for transparent decision-making.
Disclosure limits
Data may be shared with processors supporting hosting, payments, or communications under confidentiality and contractual controls. We do not sell personal information. Any mandated legal disclosure is handled carefully and documented within our compliance process.
Cross-border processing context
Primary operations are based in Canada, yet some vendors may process data in other jurisdictions. We assess provider safeguards and contractual terms where transfer occurs. Users should understand that legal environments can differ outside Canada.
Access and correction rights
Individuals can request access to personal information and seek correction where records are inaccurate or outdated. Verification steps may be needed before release. We respond within practical timelines and explain limits where legal exceptions apply.
Retention and deletion
Retention durations vary by category and purpose. Enquiry data, learner artefacts, and accounting files follow different schedules. After obligations end, records are deleted, de-identified, or anonymised using methods suitable to platform architecture and backup constraints.
Safeguard controls
We apply administrative, technical, and physical safeguards including encryption, access governance, credential controls, and staff training. Safeguards are reviewed periodically to address changing risk conditions. Absolute security cannot be guaranteed, but we pursue reasonable, proportionate protection.
Incident procedures
Potential incidents are escalated for assessment, containment, and remediation. If an incident meets legal reporting thresholds, notification procedures are followed as required by Canadian privacy law. Lessons from incident reviews inform future control improvements and staff guidance.
Minor data
Services are intended for adult learners. We do not intentionally solicit personal information from minors through standard channels. If minor data is identified unintentionally, processing is restricted and records are handled according to legal and operational requirements.
External resources
The site may link to external platforms or references for convenience. Third-party sites manage information under their own policies. Users should review those policies before sharing personal information because external handling is outside our direct governance.
Escalation path
We encourage users to contact our privacy team first for practical resolution. If unresolved, concerns may be directed to the national privacy regulator and commissioner channels in Canada. We cooperate with lawful requests and transparency obligations.
Notice updates
When practices change materially, this notice is revised with updated date references and content. Additional communication may be issued when appropriate. Continued service use after notice indicates acceptance, subject to rights available under applicable law.
Operational awareness
Team members receive recurring guidance on privacy obligations, secure communication habits, and minimisation principles. Training reinforces consistent behaviour across enrolment support, instruction, and technical operations.
AI-specific caution
Learners are taught to limit personal identifiers in AI prompts, apply redaction techniques, and validate output before sharing. This helps maintain confidentiality and supports responsible use of third-party AI systems within professional service contexts.
Privacy communications
Send requests to [email protected] with identifying details needed to verify and process your inquiry securely.
Checkpoint Log 1 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 1 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 2 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 2 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 3 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 3 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 4 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 4 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 5 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 5 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 6 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 6 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 7 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 7 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 8 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 8 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.
Checkpoint Log 9 for privacy.php: 102 Street coaching emphasises practical orchestration across prompts, reviews, and delivery packaging so Edmonton participants can maintain quality under pressure, justify fees with evidence, and operate with measured confidence across changing client requirements. Pathway field note 9 adds implementation detail on scope boundaries, timeline signalling, and correction loops, enabling professionals to defend standards, prevent avoidable churn, and build stable income-supporting services through accountable AI-assisted execution.