Privacy Protocol

What Fortune Wheelz Canada Actually Collects

Fortune Wheelz Canada — the operator of the Fortune Wheelz Canada sweepstakes portal — collects the minimum personal data required to run a compliant Canadian sweepstakes casino product. That minimum is: an email address for account communication, a legal name and date of birth for age and identity verification, a country and province of residence for jurisdictional processing, and the payment metadata that the applicable payment rail requires for a given deposit or redemption. Everything beyond that minimum is either derived operational data (session logs, device fingerprints for security) or explicit opt-in data (marketing preferences, trusted-contact nomination) that the player controls from the account drawer.

We do not collect a photograph, a voice recording, a home address beyond province level, or any social-network identifier. We do not enrich the account with data purchased from third-party data brokers, and we do not sell any account data under any circumstance. These are policy commitments rather than technical accidents; the systems are built to make an enrichment purchase or a data sale operationally difficult on top of being contractually prohibited, because a policy that a small mistake can bypass is a policy that will eventually be bypassed.

Legal Basis and Jurisdictional Framework

Fortune Wheelz Canada processes personal data under the Personal Information Protection and Electronic Documents Act (PIPEDA) at the federal level, and the applicable provincial private-sector privacy laws where they apply (PIPA in British Columbia and Alberta, and Quebec's Law 25). Cross-border data processing is limited to service providers under contractual data-processing agreements with equivalent-protection commitments. Every service provider is listed in the sub-processor register inside the account drawer, and any change to the register triggers an in-app notification thirty days before the change takes effect.

The legal basis for processing varies by data category. Account-identifying data is processed under contract necessity — you cannot open an account without providing it. Payment metadata is processed under legal obligation (anti-money-laundering and consumer-protection statutes require it). Session logs are processed under legitimate interest, with a clear right to object that pauses non-security logging. Marketing preferences are processed under explicit consent, and consent can be withdrawn at any point without any effect on account access or prize eligibility.

Retention — How Long Data Actually Stays

Retention windows are set to the shortest period consistent with the applicable statute. Account-identifying data is retained for the life of the account and for seven years after account closure, which is the standard AML retention window in Canada. Payment metadata carries the same retention window because payment records are required to be preserved for the AML audit. Session logs are retained for ninety days by default and truncated automatically at the window edge; extended-retention exemptions apply only when a specific incident investigation is open, and any exemption is time-limited to the investigation's duration.

Marketing preference data is retained only while the consent is active. When a player withdraws marketing consent, the preference record itself is retained for six months as evidence that the withdrawal was actioned, and it is deleted at the six-month mark. Trusted-contact nominations are retained while the nomination is active; a revoked nomination is deleted from the record within seven days, and the revocation itself is logged for one year as a security-audit trail.

Cookies and Local Storage — the Complete List

Fortune Wheelz Canada uses two cookie categories: strictly necessary and analytics. Strictly necessary cookies handle session authentication, cross-request state, and the responsible-play modal state; they cannot be disabled because doing so would break authentication itself. Analytics cookies are opt-in from the first-visit banner and they feed a first-party analytics pipeline that runs on infrastructure the platform controls. There are no third-party marketing cookies on this site; every cookie the site sets is either set by Fortune Wheelz Canada directly or by a strictly-necessary service provider named in the sub-processor register.

Local storage is used for the same categories the cookie policy covers, subject to the same opt-in gate for analytics. Local storage is per-device rather than per-account, which means clearing the browser's local storage removes the analytics state for that device without affecting the account. Every analytics data point flows into a pipeline that aggregates before it retains; individual-round-level analytics data is discarded inside 24 hours, and only aggregated cohort data survives to the ninety-day retention window.

Player Rights and How to Exercise Them

Every Canadian resident has statutory rights under PIPEDA to access, correct, and (in most circumstances) delete the personal data Fortune Wheelz Canada holds about them. Access and correction requests are actioned inside thirty days for straightforward cases and inside sixty days for cases that require a documentary verification step. Deletion requests are actioned inside thirty days unless a legal-obligation retention period applies, in which case the response explains the specific retention period and the statute that requires it. Every response is written and every response includes the appeal pathway.

Requests go through the privacy request escalation channel that the support page publishes. The channel routes to a small team with the authority to action a request end-to-end without additional approvals; that flat routing structure is why the thirty-day response window is realistic rather than theoretical. Requests never require the player to pay a fee, provide additional identity documentation beyond the account's existing verification, or agree to any waiver as a condition of the response. Every one of those anti-patterns is common in the sector; none of them applies here.

Security, Breach Notification and Third-Party Sharing

All data at rest is encrypted with AES-256, all data in transit is transported under TLS 1.3, and access to identity-linked data is logged at the record level. Access to identity data is limited to a small set of roles — account operations, compliance, and the fact-checker who verifies published-page claims that involve individual-level data — and every access event is auditable. Bulk exports require dual approval and are logged with a mandatory business justification. The audit log is immutable and it is one of the datasets we hand to independent security assessors during the annual pen-test.

Breach notification follows the PIPEDA "real risk of significant harm" standard. Any breach that meets that threshold triggers a notification to the Office of the Privacy Commissioner of Canada, a notification to every affected account holder, and a public disclosure inside the security section of this site inside seventy-two hours of the breach being confirmed. Notifications include a plain-English description of what happened, what data was involved, what steps the platform has taken, and what steps affected account holders should take. There is no dark-pattern minimisation and no legal-boilerplate hiding of material facts; the standard is the same standard we would want as consumers on the receiving end of the notice.

International Transfers, Sub-Processors and What Leaves Canada

Some categories of processing require data to leave Canada. Payment processing depends on rail-specific processors that operate cross-border by design; email delivery routes through a US-based transactional email provider; anti-fraud enrichment for payment metadata uses a provider located in the European Union. Every sub-processor is contracted under a data-processing agreement that binds the provider to equivalent-protection commitments and to the specific processing purpose the contract names, mirroring the safeguards written into the companion terms of operation document. The full list is published in the sub-processor register inside the account drawer, and every material change to the list generates a thirty-day advance notification to the account holder.

Data that leaves Canada is minimised at the point of transfer. Payment metadata that ships to a US processor is stripped of any information the processor does not need to complete the specific transaction; email content that ships to the transactional email provider does not include account balance information or session detail; anti-fraud metadata is submitted as a hashed fingerprint rather than a full identity record wherever the anti-fraud check permits. This minimisation is not a nice-to-have — it is the operational implementation of the "purpose limitation" principle that PIPEDA and its provincial equivalents require.

Children, Under-18 Users and Family Blocker Interoperability

Fortune Wheelz Canada is an 18+ service and it does not knowingly collect any personal data from a person under the age of majority in their province of residence. Every account confirmation requires documentary age verification against a government-issued identity document, and any account that fails age verification is closed immediately with the associated data purged inside seven days rather than the standard retention window. If a parent or guardian believes a person under 18 has created an account, the fastest resolution route is the confidential privacy request channel; every such report is triaged the same day and verified accounts are suspended immediately.

The platform integrates with the two major family-blocker filter categories — Net Nanny and Cyber Patrol — through the standard content-classification signals those tools consume. Parents managing a shared device can block the domain at the filter layer, and both major desktop operating systems (Windows Family Safety and macOS Screen Time) will respect a domain block set at the OS level without any additional integration from us. The multi-layer approach — OS filter, network filter, and platform-level age verification — is deliberate; a single-layer block that a technically-inclined teenager can defeat is not a real safeguard.