Privacy Policy

Data Governance and Regulatory Alignment

Personal data handling at Pulsz Canada is governed by a documented framework aligned with the Personal Information Protection and Electronic Documents Act as well as applicable provincial privacy legislation across each participating jurisdiction. The framework specifies clear roles for data controllers and processors, documented lawful bases for every category of processing, and formal review cadences for every retention window. Aggregate data flows are diagrammed in an internal data-map that is refreshed whenever a new integration is onboarded, and independent third-party services accessing personal data are covered by service-level data-processing agreements that mirror the platform’s own commitments. Members exercising their access, correction or deletion rights should reference the rights table above for the applicable service-level windows.

Data-minimisation is treated as an operational principle rather than an aspirational statement. Every field in every data model on the platform must be justified with reference to a specific use case, and fields that fall out of use are removed from schemas during standard maintenance cycles. Backup snapshots are subject to the same retention discipline as primary storage; a member exercising deletion rights sees their data removed from both primary and backup surfaces within the applicable window. This end-to-end lifecycle discipline is what makes retention commitments meaningful in practice rather than merely nominal. Members concerned about historical data retention from before an account was created can query specifically through the privacy-ticket lane.

Third-party data disclosure is intentionally rare and always documented. Legitimate disclosure categories include regulatory reporting where mandated, payment processing where operationally necessary, identity verification during specific compliance flows, and law-enforcement responses following formal legal process. Beyond these documented categories, personal data is not shared with any external party. Marketing and analytics partners work only with anonymised aggregate data unless the member has provided specific granular consent through the preferences panel. Members can review current consent status at any time via the account panel and can withdraw any granular consent with immediate effect on future data flows. Historical processing that occurred while consent was active remains lawful under the standard controller framework.

Cookies, Trackers and Client-Side Storage

Cookie usage on the platform is limited to categories necessary for functional operation, performance measurement, and where enabled by the member, personalised experience. The functional category includes session identifiers and CSRF-mitigation tokens that cannot be disabled without breaking the sign-in flow. The performance category collects anonymised aggregate usage metrics with no personally identifying content. The personalisation category is enabled only when the member has explicitly opted in through the cookie preferences banner. Third-party cookies are not set by first-party pages, and any embedded content that would set third-party cookies is loaded only after explicit consent for the affected category.

Client-side storage beyond cookies includes local-storage entries for interface preferences and IndexedDB entries for cached game data. Both storage mechanisms are subject to the same retention framework as server-side data and can be cleared entirely from the account panel or the browser’s standard clear-site-data controls. Members who suspect an unusually large storage footprint from Pulsz can inspect it directly through browser developer tools. The member conduct compendium outlines the reciprocal obligations that members accept in relation to platform integrity, and the interaction between those obligations and the privacy framework is described in the dedicated data-and-conduct explainer available on request through the standard support channels.

International Data Transfers and Sub-Processor Controls

Personal data processed on behalf of Canadian members is stored primarily within Canadian data centres operated by certified infrastructure partners. Certain sub-processors necessary to platform operation such as anti-fraud vendors and identity-verification providers may process specific data classes outside Canada, and every such transfer occurs under a documented transfer mechanism that ensures equivalent protection to Canadian frameworks. The full list of sub-processors is maintained in an internal register that can be shared with members on request through the privacy enquiry channel. Where a sub-processor arrangement changes materially, members are notified in advance through the standard notification channels and can exercise their rights before the change takes effect.

Breach notification obligations follow the timelines specified in PIPEDA and applicable provincial legislation. In the event of a breach of security safeguards involving personal information under the platform’s custody, notification to the Privacy Commissioner of Canada and to affected members would occur within the required windows. The platform maintains a formal incident response playbook that includes documented decision authority, forensic protocols and communication templates specifically to ensure that breach obligations can be met even under time pressure. Members can review the general shape of the incident response framework in the transparency section of the privacy documentation available on request through privacy documentation dispatch.

Data subject access requests are handled through a dedicated privacy team rather than through general customer support. This routing ensures that requests receive the specialised handling required to meet regulatory requirements including complete data compilation, sensitive data redaction where appropriate and delivery in a portable format. First-time access requests typically complete within the fifteen-business-day window; complex requests may extend to the full thirty-day window with interim status communication. Members exercising these rights should reference the rights table documented earlier on this page for the applicable procedural details.

Privacy Policy Documentation

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.

Within the rigorous framework of digital platform governance, comprehensive documentation serves as the foundational architecture for user trust and regulatory compliance. Every operational parameter, from session authentication protocols to data retention policies, must be transparently articulated in compliance with provincial regulatory mandates across Canadian jurisdictions. The cryptographic infrastructure underlying user credential management employs industry-standard hashing algorithms with salted iterations exceeding current NIST recommendations. Administrative access controls implement role-based permission matrices with mandatory multi-factor authentication for any operation affecting user data persistence layers. Continuous integration pipelines automatically validate documentation accuracy against active system configurations, ensuring that published policies reflect current operational reality without temporal drift across the entire deployed platform infrastructure.