
Create Account
Free registration for Canadian sweepstakes players 19+
Create Account
Signup Funnel Conversion
Verification Method Split
Signup Sources by Channel
Registration Requirements
| Field | Required | Used For |
|---|---|---|
| Email address | Yes | Login & notifications |
| Date of birth | Yes | 19+ verification |
| Postal code | Yes | Provincial eligibility |
| Password | Yes | Account access |
| Marketing opt-in | No | Bonus offers |
Age & Region Verification
| Province | Age Threshold | Verification |
|---|---|---|
| Ontario | 19+ | Government ID upload |
| Quebec | 18+ | Government ID upload |
| British Columbia | 19+ | Government ID upload |
| Alberta | 18+ | Government ID upload |
| Manitoba | 18+ | Government ID upload |
| Other | 19+ default | Government ID upload |
Post-Signup Welcome Package
| Item | Quantity | Currency Mode |
|---|---|---|
| Welcome Gold Coins | 5,000 | Gold |
| Welcome Sweeps Coins | 2.3 | Sweeps |
| Daily login streak start | Day 1 | Both |
| Onboarding tutorial | 1 walkthrough | N/A |
Onboarding Flow and Data Minimisation
Account creation on Pulsz Canada is engineered to collect only the minimum information required by regulation and by legitimate service operation. The registration form asks for an email address, a password, a date of birth for age verification, a postal code for provincial eligibility and an optional marketing opt-in. Every field is documented in the registration requirements table with the specific purpose it serves. No data collected during registration is used for any purpose beyond those disclosed, and members can revise or withdraw non-essential elements from the account panel at any time after signup. Identity verification steps that require government ID are handled through a separate flow triggered at a defined activity threshold, not as a precondition of registration itself.
The signup funnel visualised above reflects real conversion rates across the last measurement window. Drop-off between landing and form-start is the largest single loss and is primarily attributed to visitors who are not eligible under provincial age or residence requirements. Drop-off between email entry and age verification is smaller and typically indicates members who realise mid-flow that they wish to proceed with additional consideration. Members who exit the funnel mid-registration can resume from the same email address without losing entered data for a defined recovery window, after which any unfinished registration data is purged in line with the minimum retention posture.
Age verification is the single most consequential compliance step in the registration flow and is handled with commensurate care. The primary path uses a government identity document upload verified through an independent identity-service provider certified for the Canadian regulatory environment. Verification typically completes within minutes for supported document types and within a business day for edge cases requiring human review. Members whose primary verification path is unsuccessful can escalate through the manual-review triage bench for alternate document acceptance. Age verification data captured for this purpose is treated as sensitive throughout its retention window and is not repurposed for any secondary use whatsoever.
Welcome Package and Early Journey
New members receive a documented welcome package immediately upon successful account creation as listed in the welcome-package table above. The initial Gold Coin and Sweeps Coin allocations are intended to allow immediate exploration of the platform without any purchase pressure. The daily login streak begins from day one and members can accumulate compounding streak bonuses simply by returning daily during the first two weeks. The onboarding tutorial is optional but recommended and covers currency mechanics, responsible-play controls and navigation of the primary interfaces. Progress through the tutorial is not gated and members can skip and return at any time from the account panel.
Early journey guidance points new members toward the durable-play scaffolding as a first-week priority so that limits are configured before habits form. Members are also encouraged to review the virtual-currency dual-model explainer to understand the meaningful distinction between Gold and Sweeps Coins before making any purchase decision. First-week engagement patterns are a strong predictor of long-term satisfaction, and members who configure at least one self-limit during their first two weeks report significantly higher session enjoyment across all subsequent measurement windows. The early-journey optimisation programme continues to iterate on this signal to improve outcomes for the next cohort of newly registered members.
Referral Programme and Friend-of-Member Signups
Members who complete registration and clear the initial activity threshold become eligible to invite friends through the referral programme. Each successful referral generates a modest Sweeps Coin allocation to both the referring member and the newly joined member, subject to the friend completing their own initial activity threshold. The referral link is unique per member and the credit only applies to signups completed through that link, which prevents post-hoc attribution disputes. Members can review pending and completed referrals in the account panel and can see cumulative referral earnings across the account lifetime. Referral fraud detection uses standard graph-analysis techniques to identify coordinated abuse patterns; legitimate individual referrals are not affected by these controls.
Cross-registration between related family members is permitted where each account represents a distinct natural person aged 19+ residing in an eligible jurisdiction. Shared residence is not by itself a barrier to multiple accounts within the household, but each account must independently pass identity verification and must be operated by its own account holder rather than shared. Historical account activity from any single household member is not treated as a proxy for account activity by any other member. Members who inadvertently create duplicate accounts for themselves can request consolidation through the account-hygiene review queue, which will merge activity histories where possible and clarify going-forward account status.
Post-registration verification cadence follows a documented model that scales verification depth to account activity. Small-envelope accounts operate with light-touch verification consisting of email confirmation and basic age attestation. Accounts crossing defined activity thresholds trigger enhanced verification requiring government identity document upload, and the highest-envelope accounts undergo periodic re-verification to maintain compliance with financial-intelligence obligations. Members are notified in advance of any impending verification requirement and can complete verification proactively from the account panel before their activity would otherwise trigger it. This proactive path avoids any interruption to ongoing activity and is documented in the initial welcome package materials.
Complementary reading across sibling resources helps members orient the specific topic against the broader platform context, so cross-navigation between adjacent pages is encouraged whenever the topical adjacency is genuinely useful and never merely for the sake of interlink volume alone. This short bridging paragraph closes the current explainer while directing curious members onward.
Create Account 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.