
Rules
How Canadian privacy law shapes social media contests under PIPEDA
PIPEDA social media contests need clear consent, limited collection, set retention limits and prompt breach reporting for entrant data in Canada.
What to take away
- PIPEDA social media contests require consent for every collection, use and disclosure of entrant data.
- Ten fair information principles govern how you collect, keep and destroy lead form and retargeting data.
- Retention limits mean you must set a destruction date before the contest opens, not after.
- The Office of the Privacy Commissioner of Canada (OPC) can investigate complaints and expects breach reports when there is real risk of harm.
- Contest rules and privacy policies must match what you actually do with entrant data.
What PIPEDA covers when a contest collects entrant data
PIPEDA is the federal private-sector privacy statute. It covers organizations that gather, use, or share personal information as part of commercial activities. A contest is commercial activity when it promotes a product, builds a list or feeds a sales funnel. That makes most brand contests in Canada subject to PIPEDA.
Which law governs the contest
PIPEDA
- Quebec, BC, Alberta
- Cross-border only
- Ontario, Atlantic
- Applies
- Federal businesses
- Applies
- Hospital, university
- Not applicable
Provincial law
- Quebec, BC, Alberta
- Regulator handles
- Ontario, Atlantic
- Not applicable
- Federal businesses
- Not applicable
- Hospital, university
- Public-sector law
Personal information is broad. It includes a name, email address, phone number, province and birth date. It also covers a social handle, an IP address and any user-generated content you ask entrants to submit. Inferred data counts too, such as a retargeting audience built from contest engagement.
The law does not care whether the data sits in a spreadsheet, a CRM or an ad platform. If you can identify a person from it, or link it to a device, PIPEDA applies.
Three provinces have substantially similar private-sector laws: Quebec, British Columbia and Alberta. In those provinces, provincial regulators handle most private-sector complaints. PIPEDA still applies to federally regulated businesses and to cross-border data flows. Ontario and Atlantic Canada rely on PIPEDA for private-sector privacy.
Public sector and health data sit under different statutes. A contest run by a hospital foundation, a university or a municipal tourism body may fall under provincial public-sector law instead. Check which regulator governs the organization before you draft rules.
PIPEDA permits collection only for purposes a reasonable person would consider appropriate. Running a contest to gather emails is appropriate if you say so. Running a contest to gather health details for an insurance lead list is not.
The OPC sets out PIPEDA consent and collection rules in a short overview for businesses. Read it before you write your entry form.
Worked example: an Ontario skincare brand runs an Instagram contest
The brand asks for name, email and Instagram handle. Purpose: award the prize and send a one-time offer. Consent is a single unchecked box for contest administration plus marketing. Retention is 18 months for marketing, 6 months for contest records.
No retargeting audience is built from entrants. A French version of the rules runs for Quebec entrants. The agency holds the data under a written privacy schedule. At close, the brand deletes the ad account audience and confirms the CRM deletion.
That structure meets the fair information principles without needing a lawyer for every field. It also keeps the promotion simple enough to explain in one screen of rules.
Consent, collection and use: the fair information principles applied to lead forms
PIPEDA rests on ten fair information principles. They set rules for accountability, identifying purposes, consent and limiting collection. They also cover accuracy, safeguards, openness, individual access and challenging compliance.
Fair information principles for lead forms
- Name a privacy owner in the rules
- State each field's purpose at collection
- Use unchecked, plain-language consent
- Collect only what the purpose needs
- Limit use and disclosure of data
Accountability means someone in your organization owns privacy. Name that person in the contest rules. A generic privacy@ inbox with no owner fails the test when a complaint arrives.
Identifying purposes means you state why you collect each field before or at the time of collection. "To administer the contest and send marketing emails" is a purpose. "For internal business purposes" is not.
Consent must be meaningful. A pre-checked box is not consent. Neither is burying the marketing opt-in inside a wall of contest terms. The Commissioner expects consent that a normal person can understand without legal training.
Limiting collection means asking only for what the stated purpose needs, the same principle found in social media accessibility requirements us state checklists. If the prize is a gift card, you do not need a postal code, a job title and a household income bracket.
Limiting use and disclosure means you cannot later repurpose entrant data for a new purpose without fresh consent. Selling or renting the list to a partner is a disclosure. It needs its own consent line, not a footnote.
Openness means your privacy policy is easy to find. Individual access means an entrant can ask what you hold and get a real answer. Challenging compliance means there is a named route for complaints.
Safeguards apply from the first click. If your entry form posts over an unsecured connection, you have failed before you have collected anything.
Consent can be express or implied, depending on sensitivity. Email addresses for a contest newsletter are low sensitivity, so implied consent may work if the purpose is obvious. Health data, financial data or data about minors needs express consent.
Minors need special care. Quebec and federal guidance treat under-13 data as highly sensitive. If your contest is open to all ages, add an age gate and a parental consent path, or restrict entry to adults.
Retention limits and destruction duties for contest and retargeting data
PIPEDA requires you to destroy, erase or anonymize personal information once it is no longer needed for the stated purpose. There is no fixed number of years in the statute. The limit is purpose-driven.
Retention and deletion schedule
- Before launchSet retention period in rules
- Contest close6 months for contest records
- Ongoing12-24 months for marketing consent
- On withdrawalSuppress within reasonable time
- Deletion datePurge CRM, ad account, backups
Set a retention period before the contest opens. Write it into the rules. A common pattern is 12 to 24 months for marketing consent, with a shorter window for contest administration records. Whatever you choose, you must be able to justify it.
Retargeting audiences create a second retention problem. A custom audience built from contest entrants may keep matching people for as long as the platform holds the hashed list. You need a deletion schedule for the ad account, not just the CRM.
Destruction must be effective. Deleting a row from a spreadsheet while the same data sits in a backup, a mailing list and a Meta audience is not destruction. Map every copy before you promise a deletion date.
Keeping entrant data forever is a retention failure that also distorts social media metrics canadian ecommerce. Access requests still apply after the contest ends, so you must be able to find whatever you hold. That is hard if contest data was copied into three tools with no owner.
Accuracy matters for retargeting. If an entrant later withdraws consent, your audience list must reflect that within a reasonable time. Quarterly suppression syncs are a defensible practice.
Safeguards must match sensitivity. A lead list with names and emails needs access controls, encryption at rest and a rule about who can export it. Contractors and agencies need written privacy obligations.
The OPC summarises those duties in PIPEDA requirements in brief, covering consent, collection, use and disclosure on one page.
Where OPC guidance bites on retargeting audiences
The PIPEDA interpretation bulletins explain how the Commissioner reads consent and disclosure in digital marketing. They are not statutes, but they signal enforcement priorities.
Is this retargeting audience allowed?
Did entrants consent to cross-site tracking?
Disclose in policy and rules
Do not enrol contest entrants
The Commissioner has been clear that tracking across sites for advertising requires meaningful consent.
Online behavioural advertising guidance treats inferred interests as personal information. That means a lookalike audience built from contest entrants is a use of personal information, even if no names are visible to you.
Lookalike audiences are the highest-risk retargeting use. Start from your own customer list, not from contest entrants who never expected it.
Disclosure to ad platforms is a disclosure under PIPEDA. You are handing personal information to a third party for its own purposes, including measurement and optimisation. Say so in the privacy policy and in the contest rules.
The Commissioner expects privacy policies to be readable. Long, legalistic text that hides the retargeting clause does not meet the openness principle. A short summary with a link to detail works better.
Cross-border transfers need disclosure too. If entrant data is stored or processed outside Canada, entrants should know that foreign law may apply to it. This matters for US-based ad platforms and CRMs.
Consent to retargeting can be withdrawn. If someone asks out, you must remove them from the audience and stop using their data for that purpose. Keep a suppression list you actually check.
Complaints can lead to a formal report and, in serious cases, to a compliance agreement or court application. The reputational cost lands before the legal one. A contest that trends for the wrong reason is a marketing loss.
Contest rules, privacy policies and the wording entrants actually read
Contest rules and the privacy policy are two documents with different jobs. The rules govern the promotion: eligibility, prize, odds, closing date and how winners are chosen. The privacy policy explains data handling.
Contest rules vs privacy policy
Contest rules
- Purpose
- Govern promotion
- Covers
- Eligibility, prize, odds
- Quebec
- French version needed
- Consent
- Must match policy
- Placement
- Next to submit button
Privacy policy
- Purpose
- Explain data handling
- Covers
- Collection, use, disclosure
- Quebec
- French notice needed
- Consent
- Must match rules
- Placement
- Linked summary
Both must be consistent. If the rules say data is used only to award the prize, but the privacy policy allows marketing, you have a consent problem. Align the wording before launch.
Quebec adds a language requirement. Bill 96 and the Charter of the French Language require French-language contest materials in many cases. A French version of the rules and privacy notice is safer for any promotion open to Quebec residents.
The Competition Bureau Canada also has a stake. It expects contest terms to be clear and not misleading, including the chances of winning and any material conditions. A privacy clause that hides a marketing consent can shade into a misleading representation.
For teams running promotions in both countries, compare contest rules what the FTC and state laws require. Canadian and US rules differ on consent, disclosure and breach timing.
Place the consent language where entrants actually read it. That means on the entry form, next to the submit button, not only in a linked document. A short sentence with a checkbox beats a paragraph in 8-point type.
If you use a lead form ad on a platform, the platform's own terms apply on top of PIPEDA. Meta and TikTok both require a privacy policy link. Neither replaces your PIPEDA obligations.
Winners' names create a separate question. Many brands publish a winner list or ask for a photo. Get express consent for that use, ideally on the entry form, and let entrants decline publicity without losing the prize.
For a broader walkthrough of mechanics and platform rules, see how to run a social media giveaway legally. It covers the operational steps that sit alongside the privacy analysis here.
Breach reporting duties when lead data is exposed
PIPEDA has a mandatory breach reporting regime. You must report to the OPC any breach of security safeguards involving personal information under your control if it creates a real risk of significant harm.
Breach reporting duties under PIPEDA
- Assess real risk of significant harm
- Report to OPC as soon as determined
- Notify affected individuals in most cases
- Log every breach for at least 24 months
- Confirm agency contract reporting path
You must also notify affected individuals in most cases. And you must keep a record of every breach, even ones you decide not to report, for at least 24 months.
File the report through the OPC's online breach report form. The form asks for the nature of the breach, the number of people affected and the steps you took.
Notify individuals with a clear description of the breach, the personal information involved, what you are doing to reduce harm and a contact for questions. Keep the 24-month log in a place you can retrieve quickly if the OPC asks.
Real risk of significant harm depends on sensitivity and the probability of misuse. A leaked list of contest emails is lower risk than a leak that includes birth dates, addresses and prize claim details. But email lists enable phishing, so they are not automatically low risk.
The clock matters. Report as soon as you determine a breach occurred. Delays without justification can be treated as a separate compliance failure.
The OPC has a breach video series for businesses that walks through assessment, reporting and notification duties. It is a useful training tool for agencies handling lead data.
A breach log is not optional paperwork. The Commissioner can ask for it, and it is your evidence that you assessed incidents consistently.
Your agency contracts should say who reports. If the agency holds the lead data and the breach happens there, the brand still has accountability. Write the reporting path and timelines into the contract.
PIPEDA social media contests checklist for Canadian marketers
Use this before launch, then again at contest close.
PIPEDA contest launch checklist
- Confirm regulatorOPC or provincial
- Name privacy owner in rules
- List fields and purposes
- Unchecked consent next to submit
- Separate marketing and retargeting opt-ins
- Set retention and ad deletion dates
- Map every data copy
- Check Quebec French requirements
If you are choosing where to run the promotion, defining a qualified lead before picking a channel changes the whole funnel. A contest that gathers low-intent emails on a platform your buyers do not use will fail on both privacy and performance.
Pre-launch checklist
- Name an internal privacy owner and put the role in the contest rules.
- State the purpose for each field on the entry form, before or at collection.
- Use an unchecked consent box for marketing; never pre-check it.
- Limit fields to what the prize and stated purpose require.
- Set a destruction date for contest records and marketing data, and write it into the rules.
- Map every copy of entrant data, including CRM, ad accounts and backups.
- If you operate in Alberta, British Columbia or Quebec, confirm which regulator handles private-sector complaints under the substantially similar provincial regimes.
- Draft a French version of the rules and privacy notice for Quebec entrants.
- Put breach reporting duties and deletion deadlines in agency contracts.
Post-contest checklist
- Delete or anonymize contest administration records on the date set in the rules.
- Remove custom and lookalike audiences built from entrant data.
- Check suppression lists and remove anyone who withdrew consent.
- Keep the 24-month breach log current and easy to retrieve.
- Respond to access requests within the time the law allows.
Quick reference
| Item | PIPEDA requirement | Practical step |
|---|---|---|
| Consent | Meaningful, purpose-specific | Unchecked opt-in boxes |
| Collection | Limited to stated purpose | Cut unnecessary fields |
| Retention | Destroy when purpose ends | Set dates in rules |
| Disclosure | Inform before sharing | Name ad platforms and partners |
| Breach | Report real risk of harm | Keep a breach log |
| Access | Respond to requests | Test the process |







