The province now wants credit for modernizing government through artificial intelligence. Anthropic says the Government of Alberta has used Claude Code since 2025 to review government systems, find vulnerabilities, and fix them. According to Anthropic, a team inside Alberta’s Ministry of Technology and Innovation scanned 466 million lines of code in 20 hours, remediated security gaps, and built tools to make those systems safer. Anthropic also says the ministry maintains systems across all 27 provincial ministries, including applications that hold sensitive information such as tax records, procurement data, and social-services case files. (Anthropic)

We can argue about whether that is good or bad governance.

Supporters will point to speed. They will say old government code needs to be reviewed, legacy systems need to be modernized, and AI can help find vulnerabilities faster than conventional processes.

Critics will point to a different set of risks: whether AI-assisted code verification creates false confidence, whether secure-code benchmarks remain uneven, whether AI-generated or AI-reviewed code still requires rigorous human validation, and whether reliance on a U.S.-based AI company raises data-sovereignty concerns under foreign legal regimes such as the CLOUD Act and related U.S. access laws.

Those are real arguments. They matter.

But they also risk missing the larger point.

It is not only the technology that needs to be modernized. The processes need to be modernized too.

A government can use AI to scan old code while still running public-facing democratic systems through habits designed for another century. It can talk about cybersecurity while failing at civic security. It can modernize software while leaving citizens exposed to the vulnerabilities created by its own administrative processes.

That is what the electoral-list issue should have made impossible to ignore.

Elections Alberta described the List of Electors as “extremely sensitive” after the alleged inappropriate use or distribution of the list by a legitimate recipient. It stressed that there was no breach of Elections Alberta’s own databases or systems, but that framing is exactly the point: a privacy failure does not have to be a hack. It can happen because legally distributed data leaves the institution and the downstream controls are not strong enough to protect the people on the list.

The Office of the Information and Privacy Commissioner said the incident involved the public exposure of personal information from the List of Electors for more than 2.9 million Albertans, including names, addresses, and in some cases phone numbers. The commissioner warned there was likely a real risk of significant harm for some people, including law-enforcement workers, public officials, people fleeing intimate partner violence, and other vulnerable individuals.

That should have been the alarm bell.

Not a minor procedural concern. Not a communications problem. Not a “no database was hacked” reassurance. A warning that the old model of public data distribution no longer fits the risk environment citizens actually live in.

After a major electoral-data exposure, no one should be expected to answer an unsolicited call, text, or email without suspicion.

That would be foolish.

People were told sensitive voter information had been improperly exposed or distributed. Then they were expected to trust unexpected contact asking them to verify petition information?

Suspicion is not the problem. Suspicion is the rational response.

If Elections Alberta cannot understand why people would distrust unsolicited verification calls after a failure involving electoral data, then the verification process is not just outdated. It is disconnected from the risk environment it helped create.

And that same risk environment now surrounds petition verification.

The Water Not Coal petition shows why verification design matters to democracy itself. That petition did not fail because nobody signed it. Elections Alberta reported 207,435 initial signatures and 196,088 valid signatures counted, but after its statistical verification process, the verified estimate dropped to 172,088 — below the 177,732 required. Among the reasons Elections Alberta gave were electors being unable or unwilling to verify the information on the petition sheet, or not providing valid contact information to reach them for verification.

That should stop us cold.

Because if verification depends on reaching people through channels they have every reason to distrust, then the verification process itself becomes a democratic vulnerability.

People are now trained to distrust unsolicited calls. They are trained to distrust texts. They are trained to distrust emails asking them to verify personal information. They are trained to be suspicious of callback numbers left in voicemails. Government agencies themselves have spent years telling people to be careful, not to click, not to call back blindly, not to trust official-sounding messages, and not to provide personal information through uncertain channels.

The CRTC warns that caller ID can be spoofed, meaning callers can hide or misrepresent their identity by displaying fictitious or altered phone numbers. The CRTC also advises people to be cautious when asked for personal information and, when in doubt, to hang up and call the number on the organization’s website.

So when an election authority relies on phone calls, texts, emails, caller ID, voicemail, and callback instructions to verify politically sensitive information, it is not operating in a neutral administrative space. It is operating inside the same channels fraudsters use.

No caller ID is a problem. But caller ID itself is no longer enough.

Even if the proper name appears on a phone, that does not fully solve the issue. People know numbers can be spoofed. People know names can be faked. People know government branding can be imitated. A callback number does not solve that trust problem either. Scammers leave callback numbers too. They build official-sounding scripts, route people through fraud centres, and rely on victims trusting the pathway provided by the first suspicious contact.

The safe process today is not “trust the call.”

It is not even “call back the number we left.”

The safe process is: independently find the official public channel, then verify through that.

This is the reality Elections Alberta — and the province — need to face: petition-signature verification is going to become more difficult, more expensive, more time-consuming, and more resource-heavy. The old methods are no longer safe or effective enough for the world we now live in.

It has to assume phone numbers can be spoofed, callback numbers can be fake, emails can be phishing attempts, texts can be weaponized, and people may be right to refuse unsolicited requests for personal information.

That means government cannot treat public suspicion as the obstacle. Public suspicion is the evidence that the old process has failed.

The same contradiction appeared in the Alberta Energy Rebate process.

The province’s own rebate page says applicants must log into a verified Alberta.ca account, verify information, provide a Social Insurance Number, provide spousal or common-law partner tax-identification information where applicable, and set up payment through Interac’s Verification Service. The province also acknowledged that some Albertans experienced delays applying, that an Alberta.ca account sign-in performance issue had to be resolved, and that not all banks participate in Interac verification, requiring some people to use document verification instead.

Again, the issue is not only whether the technology eventually works.

The issue is whether the process was designed around the people who actually have to use it.

Who gets excluded when verification depends on participating banks? Who gets frustrated into giving up when the site fails? Who becomes vulnerable when a public benefit creates a predictable wave of scam attempts? Who is blamed for failing to navigate the system when the system itself was built around assumptions that do not match people’s lives?

And there is another layer: in-app browsers.

If a government process asks people to enter SINs, identity information, and payment-verification details, it should not allow that process to unfold casually inside app-controlled browser environments without warning.

In-app browsers are not always neutral windows. They can place an app-controlled browsing layer between the user and the site they believe they are visiting. Security researcher Felix Krause documented that some apps using in-app browsers can inject JavaScript into third-party websites, and that TikTok’s in-app browser could observe taps and keyboard inputs, including potentially sensitive fields, though he cautioned that the analysis did not prove malicious data collection.

That matters.

A privacy-first government should not assume the citizen understands every hidden layer between them and the official site. It should remove the hidden layer before asking for sensitive data. It should force sensitive government processes to open in a trusted external browser, or at minimum warn users clearly: do not complete this application inside Facebook, Instagram, TikTok, Messenger, an email-app browser, or any in-app browser. Open the official government website directly.

That is what privacy-first design looks like.

It does not assume the user knows what a WebView is. It does not assume the user can identify when a trusted government portal is being rendered inside an app-controlled capture layer. It does not assume the person applying for a rebate has the technical confidence, time, device, eyesight, accessibility setup, banking access, or digital literacy to navigate hidden security risks the government should have designed out of the process in the first place.

This is the difference between a data-first government and a privacy-first government.

A data-first government asks: how do we collect, match, verify, process, and approve?

A privacy-first government asks: what is the safest way to do this without exposing people to unnecessary risk?

A data-first government sees the citizen as an entry in a system.

A privacy-first government sees the citizen as a person who may be vulnerable, targeted, cautious, digitally excluded, fleeing harm, using a credit union, avoiding scam calls, navigating disability, living with limited technology, or simply trying to survive a government process without becoming someone else’s fraud target.

That is the modernization Alberta actually needs.

Not just AI-assisted code review. Not just faster scans. Not just new portals. Not just automated verification. Not just a press release about innovation.

Modern government requires process design that understands the world citizens are forced to live in: spoofed numbers, phishing texts, fake portals, breached data, political manipulation, social engineering, inaccessible systems, in-app browsers, and collapsing public trust.

It is possible for the Alberta government to be technologically ambitious and still procedurally reckless. It is possible to scan 466 million lines of code and still fail to understand that an unidentified phone call asking about petition verification is itself a risk. It is possible to modernize the machinery while leaving the human being exposed.

That is the point.

Alberta’s failure is not that it uses advanced technology. Alberta’s failure is that it appears to understand technology as something government uses, not as an environment citizens are forced to survive.

That environment includes AI tools, foreign-law data-sovereignty risks, old voter-list distribution systems, petition-verification calls, failed signature processes, in-app browsers, spoofed numbers, fake portals, and public-benefit sites asking for sensitive information through pathways people have been warned not to trust.

Modernization cannot mean scanning old code while leaving old processes untouched.

The process is part of the system.

And right now, the process is where the public is being asked to carry the risk.

The future of government will not be secured by AI alone. It will be secured when governments stop treating people as data sources to be contacted, verified, copied, matched, and processed, and start treating privacy as the first condition of public trust.

Because if Alberta can understand vulnerabilities in code, it should also understand vulnerabilities in process.

And it is time Elections Alberta, and every government department, started taking a privacy-first approach instead of a data-first one.

Was it stored securely?

Was it breached?

Was it shared without consent?

Was the privacy policy clear enough?

Those questions matter. But they are not the first question we should be asking.

The first question should be much simpler:

Why was anyone allowed to collect this data in the first place?

Personal data has become one of the central engines of modern power. It is used to profile us, price us, track us, sort us, target us, manipulate us, deny us, sell to us, scam us, and increasingly, to train systems that will make decisions about us long after we have forgotten we ever handed the information over.

That is the part too many laws still fail to address.

We are living under a data-first model. Businesses, platforms, employers, governments, landlords, insurers, schools, apps, devices, and service providers collect first, justify later, and protect only after the fact. Privacy becomes a setting, a policy link, a consent box, or a damage-control exercise after something goes wrong.

But once personal data exists, control has already been lost.

It can be copied, scraped, purchased, sold, inferred from, combined with other datasets, transferred across borders, accessed by governments, breached by criminals, or repurposed for technologies and uses that did not exist when it was collected.

And the people collecting it often understand its future value long before the rest of us understand the future risk.

That is why we need to reverse the model.

Not better consent boxes.

Not longer privacy policies.

Not another promise that our data will be kept safe after it has already been taken.

We need a Privacy First approach.

A model that begins with restraint.

A model that treats personal data not as a corporate asset, government convenience, or inevitable byproduct of modern life, but as something powerful enough to damage freedom, dignity, fairness, safety, democracy, and personal autonomy.

The question should no longer be:

How do we protect the data once it has been collected?

The question should be:

Why was collection allowed at all?

What follows is a draft policy proposal for a Privacy First Act — a framework built around one simple principle:

The right is not only to protect personal data after it is taken. The right is not to be unnecessarily collected in the first place.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

A Public Policy Framework for the Data Extraction Age

1. Purpose

The purpose of this policy is to reverse the current data-first approach to personal information and establish privacy as the default condition of participation in modern society.

Personal data is no longer a passive record of a person’s interaction with a service. It has become a source of power. It can be used to profile, manipulate, scam, defraud, exclude, surveil, price-discriminate, train artificial intelligence systems, influence political behaviour, evaluate risk, limit access to services, and create permanent records that follow people across institutions, borders, platforms, employers, governments, and markets.

For decades, data collection carried natural limits. Storage was expensive. Processing was limited. Access was restricted. Most organizations collected what they needed because collecting everything was impractical.

That world no longer exists.

Today, personal data can be collected constantly, invisibly, cheaply, and at scale. It can be scraped, copied, purchased, inferred, combined with other datasets, transferred across borders, breached, subpoenaed, monetized, or repurposed for uses that did not exist when the data was first gathered.

The central failure of modern data law is that it often treats privacy as something to be protected after data has already been taken. This policy begins from the opposite position.

The question should not be:

How do we protect the data once it has been collected?

The first question should be:

Why was anyone allowed to collect it in the first place?

2. Core Principle

Privacy shall be the default.

No person, business, platform, employer, contractor, service provider, public body, government agency, institution, landlord, insurer, financial entity, educational body, health-related service provider, or data processor shall collect, retain, generate, infer, purchase, sell, share, transfer, or use personal data unless the collection or use is demonstrably necessary for a specific lawful purpose, proportionate to that purpose, limited to the minimum data required, and incapable of being reasonably achieved through less intrusive means.

Personal data shall not be collected merely because it is useful, profitable, convenient, customary, technologically possible, or potentially valuable in the future.

3. The Right Not To Be Collected

Every person shall have a right not to be unnecessarily collected, tracked, profiled, identified, recorded, inferred, analyzed, monetized, or subjected to data extraction as a condition of ordinary life.

Access to employment, housing, health care, education, public services, transportation, financial services, commerce, communication, legal services, social support, public spaces, or digital platforms shall not be made conditional on unnecessary personal data collection.

Privacy is not a luxury feature, a subscription option, a buried setting, or a right that exists only after a person has surrendered their information.

Privacy is a condition of freedom.

4. Definitions

For the purpose of this policy:

Personal data means any information, record, identifier, signal, image, sound, biometric marker, behavioural pattern, device marker, location trace, transaction record, communication record, health-related information, employment information, financial information, demographic information, or inferred information that identifies, relates to, describes, predicts, profiles, or can reasonably be associated with a person.

Inferred data means information created, predicted, derived, assumed, classified, scored, or generated about a person based on other data, including behavioural predictions, risk scores, eligibility scores, productivity scores, health assumptions, political assumptions, financial assumptions, purchasing likelihood, vulnerability indicators, or emotional state analysis.

Sensitive personal data includes, but is not limited to, health information, biometric data, precise location data, government identification, financial data, children’s data, immigration or citizenship information, employment status, disability-related information, education records, legal records, sexual or intimate information, religious or political information, and data that may expose a person to discrimination, targeting, coercion, fraud, harassment, or exclusion.

Data collection includes direct collection, passive collection, purchase, scraping, recording, observation, tracking, device capture, form submission, account creation, background monitoring, third-party transfer, data matching, behavioural analysis, automated inference, or any other method by which personal data is acquired or generated.

Secondary use means any use of personal data beyond the specific purpose for which it was lawfully and expressly collected.

Data processor means any person, corporation, contractor, platform, public body, artificial intelligence system operator, vendor, broker, analytics provider, cloud provider, software provider, or other entity that collects, stores, accesses, analyzes, transfers, processes, infers from, or uses personal data on behalf of itself or another party.

5. Data Minimization as a Legal Requirement

All personal data collection shall be governed by the principle of strict minimization.

A collecting entity must prove that:

1. The data is necessary for a specific lawful purpose.

2. The same purpose cannot reasonably be achieved without collecting the data.

3. Less intrusive data would not be sufficient.

4. The amount of data collected is the minimum required.

5. The data will be retained only for the minimum period required.

6. The data will not be used for unrelated secondary purposes.

7. The person affected can understand what is being collected and why.

8. The collection does not create disproportionate future-use risk.

Where an entity cannot meet this standard, collection shall be prohibited.

6. Prohibited Data Practices

The following practices shall be prohibited unless expressly authorized by law and subject to independent oversight:

1. Collecting personal data for speculative, undefined, future, or “service improvement” purposes that are not clearly necessary.

2. Requiring personal data unrelated to the service being provided.

3. Bundling unnecessary data collection into terms of service or employment conditions.

4. Denying essential services because a person refuses unnecessary data collection.

5. Using consent to justify collection where there is a clear power imbalance.

6. Selling, licensing, renting, trading, or transferring personal data to third parties without a specific legal basis.

7. Combining datasets to create profiles beyond the original purpose of collection.

8. Using personal data for price discrimination without explicit disclosure and regulatory approval.

9. Using behavioural data to manipulate vulnerability, addiction, fear, urgency, political belief, financial insecurity, or emotional state.

10. Creating inferred profiles for eligibility, access, employment, insurance, credit, housing, health care, education, or public services without meaningful review and appeal.

11. Scraping personal data from public or semi-public sources for profiling, resale, artificial intelligence training, or behavioural analysis.

12. Collecting children’s data for advertising, profiling, prediction, monetization, or future behavioural analysis.

13. Using personal data collected for one purpose to train artificial intelligence systems without separate lawful authority.

14. Retaining personal data after the original lawful purpose has ended.

15. Transferring personal data into foreign jurisdictions where legal protections are weaker, unclear, or incompatible with the rights established under this policy.

7. Sensitive Data Protection

Sensitive personal data shall receive the highest level of protection.

Sensitive personal data may only be collected where it is strictly necessary, directly connected to the service or legal purpose, proportionate, time-limited, and subject to enhanced safeguards.

Entities collecting sensitive personal data must provide a clear explanation of:

1. Why the data is required.

2. What law or specific operational need authorizes collection.

3. Who will access it.

4. Where it will be stored.

5. Whether it will leave the jurisdiction.

6. How long it will be retained.

7. Whether it will be shared, processed, inferred from, or used by automated systems.

8. How the person can challenge collection or request deletion.

9. What harm may result from breach, misuse, transfer, or future repurposing.

No sensitive personal data shall be used for advertising, behavioural manipulation, unrelated profiling, commercial resale, or artificial intelligence training unless expressly permitted by law and subject to independent public-interest review.

8. Future-Use Risk Assessment

Every collection of personal data shall be assessed not only according to its stated present purpose, but according to reasonably foreseeable future-use risks.

This assessment must consider:

1. Whether the data could be combined with other datasets.

2. Whether the data could be used to identify, track, or profile a person.

3. Whether the data could expose a person to fraud, manipulation, discrimination, coercion, harassment, or exclusion.

4. Whether the data could be transferred to another jurisdiction.

5. Whether the data could be accessed by governments, law enforcement, foreign entities, data brokers, contractors, or unauthorized parties.

6. Whether the data could be used to train artificial intelligence or automated decision systems.

7. Whether future technologies could make the data more revealing than it appears at the time of collection.

8. Whether retention of the data creates more risk than benefit.

Where future-use risk is high, collection shall be prohibited unless a compelling public interest can be demonstrated.

9. Consent Is Not Enough

Consent shall not be treated as valid where a person has no meaningful ability to refuse.

Consent shall not be sufficient where access to employment, housing, health care, education, public services, financial services, essential commerce, government services, transportation, or communication depends on accepting unnecessary data collection.

Consent shall not legalize collection that is unnecessary, disproportionate, deceptive, coercive, overly broad, bundled, or unrelated to the service being provided.

A person cannot meaningfully consent to unknown future uses, undisclosed data transfers, artificial intelligence training, behavioural profiling, or risks that are not clearly explained.

10. No Privacy Penalty

A person shall not be punished, charged more, denied access, placed in a slower service stream, refused employment, refused housing, or treated less favourably because they exercise their privacy rights.

Where a service can reasonably be provided with less data, a privacy-protective option must be available without additional cost, reduced quality, unreasonable delay, or exclusion.

Privacy shall not become a premium product available only to those who can afford it.

11. Ban on Unnecessary Identity Collection

Government-issued identification, health numbers, social insurance numbers, citizenship information, driver’s licence information, biometric data, and similar identifiers shall not be collected unless specifically required by law or strictly necessary for the service being provided.

Where age, eligibility, residency, status, or identity must be confirmed, the least intrusive method shall be used.

For example:

1. If age confirmation is sufficient, a birthdate shall not be collected.

2. If residency confirmation is sufficient, full identity documents shall not be copied.

3. If eligibility can be verified without retaining documents, documents shall not be retained.

4. If a person can prove identity in person, no additional digital profile shall be created unless necessary.

5. If a one-time verification is sufficient, permanent storage shall be prohibited.

Share

12. Limits on Data Retention

Personal data shall not be retained indefinitely.

Every collecting entity must establish a fixed deletion schedule before collection occurs.

Personal data shall be deleted when:

1. The original purpose has been fulfilled.

2. The legal retention period has expired.

3. The person withdraws consent where consent is the legal basis.

4. The data is no longer necessary.

5. The data was collected unlawfully.

6. The future-use risk outweighs the need for retention.

Data retained “just in case,” “for analytics,” “for future development,” “for service improvement,” or “because it may become useful” shall be considered unlawfully retained unless a specific lawful purpose is proven.

13. Limits on Inferred Data

Inferred data shall be treated as personal data.

A person shall have the right to know when significant decisions or profiles are created using inferred data.

No person shall be denied employment, housing, credit, insurance, health care, education, public services, social support, financial services, or other significant opportunities based on inferred data without:

1. Clear notice.

2. Access to the basis of the inference.

3. A meaningful explanation.

4. The right to correct inaccurate information.

5. The right to challenge the decision.

6. Human review.

7. Independent auditability.

Secret scoring systems shall not be used to determine access to essential services.

14. Artificial Intelligence and Automated Systems

Personal data shall not be used to train, tune, test, improve, or operate artificial intelligence systems unless the use is specifically authorized, necessary, proportionate, disclosed, and subject to meaningful oversight.

Publicly accessible data shall not be presumed to be freely available for artificial intelligence training.

The fact that information can be scraped, copied, or accessed does not mean it may lawfully be used.

Artificial intelligence systems that rely on personal data must be subject to:

1. Data minimization requirements.

2. Source documentation.

3. Bias and harm assessment.

4. Future-use risk assessment.

5. Independent audit.

6. Public reporting where public services are affected.

7. Clear appeal rights where people are impacted.

8. Deletion and correction mechanisms where feasible.

No artificial intelligence system shall be deployed in a way that requires broad, unnecessary, or involuntary personal data extraction from the public.

15. Children and Vulnerable Persons

Children’s data shall not be collected for profiling, advertising, behavioural prediction, commercial manipulation, or future monetization.

Institutions serving children, seniors, patients, disabled persons, unhoused persons, people accessing social supports, workers in precarious employment, or other vulnerable groups shall be subject to heightened obligations.

A power imbalance shall be presumed where the person affected depends on the collecting entity for care, income, housing, education, safety, benefits, legal status, or essential services.

In these cases, consent alone shall not be sufficient.

16. Public Bodies and Government Data

Government bodies shall be held to the highest standard under this policy.

The state shall not collect, centralize, link, or repurpose personal data across programs unless expressly authorized by law, necessary for a defined public purpose, proportionate, publicly disclosed, independently reviewed, and subject to strict limits.

Government convenience shall not be treated as sufficient justification for mass data collection.

Public bodies shall not create centralized identity systems, cross-program databases, automated eligibility systems, or surveillance-linked service platforms without public notice, legislative authority, privacy impact assessment, and independent oversight.

Data collected for one public service shall not be used for unrelated enforcement, surveillance, eligibility reduction, immigration action, policing, debt collection, or benefit denial unless clearly authorized by law and subject to judicial or independent review.

17. Employers and Workplace Data

Employers shall not collect more personal data than is necessary to administer employment, safety, payroll, benefits, legal compliance, or legitimate workplace operations.

The following shall be prohibited unless strictly necessary and independently justified:

1. Continuous worker surveillance.

2. Keystroke logging.

3. Productivity scoring unrelated to actual job requirements.

4. Biometric monitoring.

5. Location tracking beyond working necessity.

6. Audio or video monitoring in non-public work areas.

7. Emotional analysis or attention tracking.

8. Health-related inferences unrelated to accommodation or safety.

9. Automated discipline based on opaque scoring systems.

10. Use of personal devices to collect workplace data without clear limits.

Workers shall have the right to know what data is collected, how it is used, who has access, and how long it is retained.

18. Data Brokers and Secondary Markets

The sale, resale, licensing, transfer, aggregation, or commercial exchange of personal data shall be prohibited unless specifically authorized by law and subject to strict oversight.

Data brokers shall not collect, purchase, scrape, infer, package, sell, or distribute personal data without a specific legal basis and clear rights for the person affected.

Every person shall have the right to know whether a data broker holds information about them, what information is held, where it came from, who it was sold to, and how to require deletion.

A public registry of data brokers shall be established.

Failure to register shall be an offence.

19. Transparency and Public Accountability

Entities collecting personal data must provide plain-language notice before collection.

This notice must state:

1. What data is being collected.

2. Why it is necessary.

3. What less intrusive alternatives were considered.

4. Whether collection is required by law or optional.

5. Who will access the data.

6. Whether it will be shared.

7. Whether it will be transferred outside the jurisdiction.

8. Whether it will be used for automated decision-making.

9. Whether it will be used for artificial intelligence training.

10. How long it will be retained.

11. How the person can access, correct, challenge, or delete it.

12. What consequences, if any, result from refusal.

Privacy notices shall not be buried in long terms of service, bundled consent forms, vague policies, or unreadable legal language.

20. Independent Privacy Impact Assessments

Before launching any program, system, device, platform, database, artificial intelligence tool, surveillance tool, public service integration, or large-scale data collection practice involving personal data, the collecting entity must complete a Privacy First Impact Assessment.

The assessment must determine:

1. Whether the data is necessary.

2. Whether the purpose can be achieved without collecting personal data.

3. Whether less sensitive data can be used.

4. Whether the data creates future-use risk.

5. Whether the data will be linked to other datasets.

6. Whether automated systems will use the data.

7. Whether the data could be used against the person in future.

8. Whether vulnerable people are affected.

9. Whether a power imbalance exists.

10. Whether deletion is possible and enforceable.

11. Whether public reporting is required.

12. Whether collection should be prohibited.

For public bodies and high-risk private systems, the assessment shall be filed with the privacy regulator and made public, with limited redactions only where strictly necessary for security or lawful confidentiality.

21. Right of Access, Correction, Deletion, and Explanation

Every person shall have the right to:

1. Know what personal data is held about them.

2. Know the source of that data.

3. Know who has accessed it.

4. Know who it has been shared with.

5. Correct inaccurate data.

6. Delete data that is unnecessary, expired, unlawfully collected, or no longer justified.

7. Challenge inferred data.

8. Receive a meaningful explanation of automated decisions.

9. Object to secondary use.

10. Withdraw consent where consent is the legal basis.

11. Seek compensation for misuse, overcollection, breach, or unlawful retention.

These rights shall be easy to exercise and shall not require legal assistance, excessive fees, unnecessary identification, or unreasonable delay.

22. Enforcement

A Privacy First Commissioner shall be established or empowered to enforce this policy.

The Commissioner shall have authority to:

1. Investigate complaints.

2. Conduct audits.

3. Order deletion of unlawfully collected data.

4. Suspend data collection practices.

5. Prohibit high-risk systems.

6. Issue binding orders.

7. Require public reporting.

8. Impose administrative penalties.

9. Refer serious violations for prosecution.

10. Require compensation or remediation for affected persons.

11. Audit artificial intelligence and automated decision systems.

12. Inspect data broker activity.

13. Require proof that collection is necessary.

The burden of proof shall rest on the collecting entity.

A person shall not be required to prove harm before unlawful collection can be stopped.

23. Penalties

Penalties shall be proportionate to the seriousness of the violation, the sensitivity of the data, the number of people affected, the financial benefit obtained, the degree of negligence or intent, and whether vulnerable persons were affected.

Penalties may include:

1. Fines.

2. Deletion orders.

3. Suspension of data processing.

4. Public notice requirements.

5. Compensation to affected persons.

6. Loss of public contracts.

7. Loss of licences or regulatory approvals.

8. Director and officer liability in cases of reckless or intentional misuse.

9. Criminal penalties for knowing misuse, concealment, trafficking, or unlawful sale of sensitive personal data.

Repeated unlawful collection shall be treated as a serious offence.

24. Public Procurement Conditions

No public money shall be used to purchase, license, operate, subsidize, or support systems that violate Privacy First principles.

Any vendor seeking public contracts involving personal data must demonstrate:

1. Data minimization.

2. No unnecessary secondary use.

3. No unauthorized artificial intelligence training.

4. No undisclosed subcontracting.

5. No foreign transfer without approval.

6. No sale or commercial reuse of public data.

7. Deletion at the end of the contract.

8. Audit rights for the public body and privacy regulator.

9. Compliance with this policy.

Public data shall not become a private asset.

25. Exceptions

This policy shall not prohibit necessary data collection for legitimate purposes, including health care, emergency response, legal compliance, public safety, fraud prevention, payroll, taxation, benefits administration, contractual performance, education administration, or other lawful and necessary purposes.

However, all exceptions must remain subject to necessity, proportionality, minimization, purpose limitation, retention limits, security safeguards, oversight, and future-use risk assessment.

An exception shall not become a loophole for broad data extraction.

26. Implementation

This policy should be implemented in stages.

Stage One: Public Sector Compliance

All government departments, agencies, Crown corporations, public schools, public health bodies, municipalities, and publicly funded programs shall complete data collection inventories and identify unnecessary collection, retention, sharing, and cross-program linkage.

Stage Two: High-Risk Private Sector Compliance

High-risk sectors, including finance, insurance, employment platforms, housing platforms, health-related services, education technology, data brokers, artificial intelligence firms, surveillance vendors, telecommunications, and large digital platforms shall be subject to mandatory Privacy First Impact Assessments.

Stage Three: General Data Minimization

All organizations collecting personal data shall be required to justify collection, reduce retention, eliminate unnecessary data fields, and provide privacy-protective alternatives.

Stage Four: Enforcement and Public Reporting

The Privacy First Commissioner shall publish annual reports identifying systemic risks, enforcement actions, high-risk sectors, data broker activity, artificial intelligence concerns, and recommendations for legislative updates.

27. Guiding Standard

The guiding standard of this policy is simple:

If a person cannot reasonably participate in society without surrendering unnecessary personal data, then privacy has already failed.

A free society cannot be built on constant extraction.

A fair market cannot exist when people are profiled, scored, manipulated, and priced according to hidden data systems.

A democratic government cannot justify collecting more information than it needs merely because technology makes it possible.

A person should not have to become a dataset in order to work, learn, travel, shop, communicate, receive care, access benefits, rent a home, enter a building, use a service, or live an ordinary life.

Privacy First means collection is the exception.

The person is the starting point.

The burden belongs to the collector.

The right is not only to protect data after it is taken.

The right is not to be unnecessarily collected at all.

Related Civic Sketches

This proposal is part of a broader set of privacy-focused policy frameworks I have been developing around the same core principle: people should not be forced to surrender personal data, sensitive information, biometric information, creative work, identity documents, employment history, or private behaviour simply to participate in ordinary life.

Related proposals include:

Camera-Capable Wearable Technology and Sensitive Information Protection Act
A policy framework addressing the use of smart glasses, body cameras, wearable cameras, and other camera-capable devices by businesses, employers, contractors, institutions, and public bodies in settings where sensitive information may be exposed.

Public Use of Camera-Capable Wearable Technology and Personal Data Protection Act
A companion framework addressing the broader public use of camera-capable wearable technology by individuals in places such as waiting rooms, clinics, schools, government offices, lineups, banks, airports, workplaces, bars, and other public or semi-public settings.

Truth in Job Advertising and Applicant Data Protection Framework
A proposal aimed at ghost jobs, misleading job postings, unnecessary applicant data collection, resume harvesting, identity-document requests, and the growing use of job applications as data-extraction tools.

The AI Upload Consent and Data Authority Act
A framework focused on consent, authority, ownership, and control when documents, creative work, images, recordings, personal information, organizational records, or third-party data are uploaded into artificial intelligence systems.

Together, these proposals begin from the same place:

Privacy should not be an afterthought.

It should not depend on whether a person finds the right setting, reads the right policy, objects in the right way, or discovers misuse after the harm has already happened.

The burden should be on the collector, the platform, the employer, the institution, the government body, or the system operator to prove why the data is needed at all.

The right is not only to protect data after it is taken.

The right is not to be unnecessarily collected in the first place.

At times, I have treated the issue of drop-in or parachute candidates as its own separate proposal. At other times, I have focused more narrowly on travel costs, housing allowances, official residences, or the growing disconnect between elected officials and the communities they are supposed to represent. But the more I return to it, the more I think these are not separate problems. They are connected symptoms of the same outdated political structure.

We live in a world where international organizations, multinational corporations, major institutions, courts, boards, and government agencies routinely use secure online meeting systems to save time, reduce travel, lower costs, and keep operations moving. These systems are not experimental anymore. They are part of how modern organizations function.

Yet elected officials are still often expected to spend large amounts of time away from their ridings, near the capital, inside a political ecosystem that can become more connected to party strategy, media access, and institutional routine than to the people who actually elected them.

That absence matters.

When representatives are physically removed from their ridings for long stretches of time, a disconnect forms. Constituents become scheduled appointments instead of daily surroundings. Local concerns become briefing notes instead of lived realities. The capital becomes the centre of political gravity, while the riding becomes a place to visit, campaign in, and occasionally report back to.

This policy concept asks a simple question: if modern technology is good enough for corporations, courts, public agencies, and international institutions, why is it not good enough to keep elected officials closer to the people they represent?

The goal is not to weaken Parliament, legislatures, committees, or councils. The goal is to make them harder to avoid, easier to audit, less expensive to operate, and more directly connected to the communities they serve.

Remote attendance should not become an excuse for absentee politicians. It should do the opposite. It should require elected officials to remain rooted in their ridings, attend official proceedings through secure verified systems, and be more available to their constituents, not less.

The same logic applies to publicly funded travel, second residences, and official housing. Public money should follow required public duty, not political tradition, personal convenience, media access, or party preference.

And if a person wants to represent a riding, they should have a real connection to that riding. Not a campaign address. Not a temporary rental. Not a party placement. A meaningful residential or community connection to the people they are asking to represent.

This proposal brings those pieces together: remote attendance, attendance accountability, public cost reduction, riding-based representation, limits on capital housing, and anti-parachute candidate rules.

At its core, the principle is simple:

Elected office should be structured around the people being represented, not around the convenience of the capital.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Direct Representation, Remote Attendance, and Public Cost Accountability Act

A Federal and Provincial Policy Proposal

1. Purpose

The purpose of this policy is to modernize elected representation by using secure digital attendance systems to increase direct citizen access to elected officials, improve attendance accountability, reduce publicly funded housing and travel costs, and ensure representatives remain rooted in the communities they were elected to serve.

Governments increasingly promote internet expansion, digital service delivery, remote work, online access, and modern communications across the public and private sectors. Elected institutions should be required to apply those same standards to themselves where doing so strengthens democratic access, reduces unnecessary public expense, and improves accountability.

This policy recognizes that elected officials should not be treated as temporary visitors to their ridings. Their first democratic duty is to the people and communities that elected them. Remote participation in Parliament, legislatures, committees, councils, and other public bodies should allow representatives to remain physically present in or near their communities more often while still fulfilling their formal duties.

The central principle is simple:

Public money should follow required public duty, not political tradition, party convenience, media access, or personal preference.

2. Core Objectives

This policy is intended to:

1. Increase direct citizen access to elected representatives.

2. Require elected officials to remain more present in the communities they represent.

3. Reduce unnecessary publicly funded housing, travel, and accommodation costs.

4. Improve attendance and participation in Parliament, legislatures, committees, councils, and other elected bodies.

5. Prevent avoidable absences from being excused by distance, travel burden, or capital-based scheduling.

6. Ensure official participation is recorded, verifiable, auditable, and accountable.

7. Require candidates to have a meaningful residential connection to the riding or district they seek to represent.

8. Reduce the use of “drop-in,” “paper,” or parachute candidates with little connection to the communities they claim to represent.

9. Distinguish official public duties from party work, fundraising, campaign activity, and political convenience.

10. Strengthen democratic continuity during pandemics, disasters, security threats, travel disruptions, and other emergencies.

11. Ensure rural, northern, Indigenous, remote, and underserved communities are not disadvantaged by digital participation rules.

12. Modernize elected office in line with secure systems already used by governments, courts, corporations, international organizations, and public institutions.

3. Presumption of Local Service

The default expectation of elected office shall be that representatives remain primarily based in the communities they were elected to serve.

Travel to the capital, capital-region housing, extended physical absence from the riding, and public reimbursement for capital-based living arrangements must be justified by required public duties, not tradition, party preference, media strategy, convenience, or personal choice.

Remote attendance should not weaken Parliament, legislatures, councils, or committees. It should make attendance harder to avoid, easier to audit, and more directly connected to the citizens elected officials are supposed to serve.

4. Constitutional and Legislative Authority

This policy shall be implemented in a manner consistent with constitutional requirements, parliamentary privilege, legislative independence, local government authority, and the standing orders or procedural rules of each elected body.

Where necessary, Parliament, provincial legislatures, territorial legislatures, municipal councils, school boards, public boards, or other elected bodies shall amend their rules to permit secure remote attendance, remote voting, verified digital participation, and public attendance reporting.

Nothing in this policy shall be interpreted as unlawfully limiting the authority of a legislative body to control its own proceedings, protect privilege, maintain order, or require in-person attendance where constitutionally or procedurally necessary.

5. Application

This policy may be adapted for:

• The House of Commons.

• The Senate, where applicable.

• Provincial and territorial legislatures.

• Legislative committees.

• Municipal councils.

• Regional districts.

• School boards.

• Public boards.

• Crown corporation boards with elected representation.

• Other elected public bodies.

Each jurisdiction may adapt the policy to its own constitutional framework, procedural rules, geography, security needs, and public office structures.

6. Indigenous Governance and Treaty Respect

Nothing in this policy shall limit the authority of Indigenous governments, treaty bodies, self-governing First Nations, Inuit governments, Métis governments, or Indigenous-led institutions to determine their own governance procedures.

This policy shall not be imposed on Indigenous governments without consent, consultation, or legal authority consistent with treaty rights, constitutional rights, self-government agreements, and the principle of Indigenous self-determination.

Where Indigenous communities choose to adopt similar remote attendance, residency, or public accountability rules, governments shall support that choice through funding, infrastructure, and technical assistance.

7. Remote Legislative and Committee Attendance

Elected representatives may attend eligible parliamentary, legislative, committee, council, board, caucus-related public, and public governance meetings through an approved secure online attendance system.

Remote attendance shall be treated as formal attendance where the member:

• Logs in through the approved government platform.

• Verifies identity through multi-factor authentication.

• Participates from an approved physical location.

• Remains visible and audible when required.

• Is actively present, responsive, and available to the presiding officer.

• Is subject to the same rules of order, decorum, voting, conflict-of-interest rules, privilege standards, and ethics requirements as in-person attendees.

• Has attendance, statements, votes, interruptions, conduct, and participation recorded as part of the official record.

Remote attendance shall not reduce the authority of the Speaker, Chair, Clerk, Ethics Commissioner, Conflict of Interest Commissioner, or other responsible officer to discipline, mute, remove, suspend, report, or censure a member for misconduct.

8. Presumption in Favour of Remote Attendance

Remote attendance shall be presumed valid for eligible proceedings unless there is a clear legal, constitutional, security, procedural, confidentiality, or operational reason requiring physical presence.

Where physical attendance is required, the reason must be recorded and, where possible, publicly disclosed.

This policy does not require that every proceeding be remote-capable in every circumstance. It requires that government justify why physical presence is necessary when secure remote participation is available.

9. Approved Remote Attendance Locations

An elected official may only attend remotely from:

1. Their own riding, electoral district, ward, or represented region.

2. A directly adjacent riding, district, ward, or region where housing, geography, weather, disability, caregiving, safety, or connectivity makes this necessary.

3. A federal, provincial, territorial, municipal, or Indigenous government building.

4. A designated constituency office.

5. A public library, courthouse, public service centre, community office, band office, municipal office, school, or other approved public institution.

6. Another secure public location approved by the relevant Speaker, Chair, Clerk, or designated officer.

Remote attendance from private vacation properties, political party offices outside the riding, corporate offices, donor-owned premises, foreign jurisdictions, hotels not linked to official travel, or unverified private locations shall not qualify unless specifically approved under an exemption.

The purpose of this rule is to ensure remote attendance strengthens local representation rather than becoming a tool for absentee representation.

10. Rural, Northern, Remote, and Connectivity Fairness

No elected official shall be penalized for living in a rural, northern, Indigenous, remote, or underserved region where broadband, cellular service, power reliability, or secure digital infrastructure is inadequate.

If government requires or permits digital legislative attendance, government must ensure reliable access points exist.

Each riding, district, ward, or represented region shall have access to at least one approved secure participation site, which may include:

• A constituency office.

• Municipal office.

• Public library.

• Courthouse.

• Provincial or federal service centre.

• Band office or Indigenous government facility, where consent is given.

• Community hall.

• School or public institution.

• Other secure public facility.

Where geography requires it, multiple approved access points shall be established.

The cost of creating secure access points shall be treated as democratic infrastructure, not as a personal expense of the elected official.

11. Accessibility and Accommodation

The remote attendance system must be fully accessible.

It shall include, where required:

• Closed captioning.

• Sign-language interpretation.

• Screen-reader compatibility.

• Accessible voting tools.

• Keyboard navigation.

• Audio-only backup options where video is temporarily inaccessible.

• Plain-language platform instructions.

• Assistive technology compatibility.

• Medical exemptions.

• Disability accommodations.

• Caregiver accommodations.

• Safety accommodations for elected officials facing threats, stalking, harassment, domestic violence, or targeted intimidation.

Remote attendance shall not be used to exclude, disadvantage, or penalize elected officials with disabilities, caregiving responsibilities, safety concerns, or health limitations.

12. Active Attendance Requirement

A member shall not be counted as present solely by logging into the system.

Attendance requires active, responsive, and verifiable participation unless the member has been formally excused by the Speaker, Chair, Clerk, or presiding officer.

A member may be marked as non-participating if they:

• Log in but do not respond when called upon.

• Leave the camera or microphone unattended without permission.

• Are not visibly present when visibility is required.

• Fail to vote during a vote without being excused.

• Are unreachable during proceedings.

• Appear to have left the proceeding while still logged in.

• Use the system to create a false impression of attendance.

Logged-in presence is not the same as democratic participation.

13. Attendance Accountability

All eligible meetings shall maintain a public attendance record showing whether each elected official attended:

• In person.

• Remotely from within their riding, district, ward, or represented region.

• Remotely from an approved government or public location.

• Remotely by exemption.

• Absent with notice.

• Absent without acceptable reason.

• Logged in but marked non-participating.

• Disconnected due to verified technical failure.

Attendance records shall be published in a searchable public format.

Repeated absence from Parliament, a legislature, council, board, or assigned committee shall trigger escalating public reporting and possible penalties, including:

• Public notice of attendance failure.

• Loss of committee compensation, where applicable.

• Reduction or suspension of travel, housing, or discretionary allowances.

• Referral to an ethics or accountability officer.

• Referral to a legislative management body.

• Formal censure by the elected body in severe or repeated cases.

Where secure remote attendance is available, distance from the capital shall not be treated as a routine justification for absence.

14. Voting and Participation

Remote participation shall include the ability to:

• Speak in debate.

• Ask questions.

• Present petitions or constituency concerns.

• Vote.

• Participate in committee hearings.

• Question witnesses.

• Move or second motions where permitted.

• Attend emergency sessions.

• Participate in recorded division votes.

• Raise points of order or privilege where permitted.

• Table documents electronically where permitted.

Remote votes must be authenticated, time-stamped, location-verified, and recorded in the same manner as in-person votes.

A remote vote shall not be valid unless the member’s identity, location, and active participation are verified.

15. Security Classification Levels

Not all proceedings require the same level of digital security.

Remote attendance rules shall classify proceedings into tiers, including:

Tier 1: Public Proceedings

Examples include ordinary public sittings, public committee meetings, public council meetings, and public board meetings.

Requirements may include standard identity verification, public recording, secure login, and location verification.

Tier 2: Closed Proceedings

Examples include in-camera committee sessions, caucus-adjacent official meetings, personnel discussions, or confidential administrative matters.

Requirements may include enhanced identity verification, approved devices, secure rooms, restricted recording, and confirmation that unauthorized persons are not present.

Tier 3: Confidential or Legally Sensitive Proceedings

Examples include ethics matters, legal advice, procurement confidentiality, child-protection issues, private personnel matters, or commercially sensitive public business.

Requirements may include government-issued devices, secure networks, private approved rooms, no unauthorized recording, and audit trails.

Tier 4: Classified, Security, or Emergency Proceedings

Examples include national security briefings, emergency management, cabinet-level security matters, intelligence briefings, or serious public safety events.

Requirements may include physical attendance, secure government facilities, classified communication systems, or other restrictions determined by law, security officials, the Speaker, Chair, Clerk, or executive authority.

Remote attendance shall not be permitted for proceedings where the security risks cannot be reasonably managed.

16. Public Record and Conduct

All official remote attendance shall form part of the public record where the meeting itself is public.

The approved attendance platform shall record:

• Login time.

• Logout time.

• Location category.

• Voting actions.

• Speaking time.

• Official interventions.

• Points of order.

• Interruptions.

• Misconduct.

• Technical failures.

• Chair, Speaker, or presiding officer warnings.

• Any removal, muting, suspension, or loss of participation rights.

Private, confidential, national security, cabinet, personnel, child-protection, or legally privileged proceedings may be subject to separate security rules, but attendance must still be internally recorded and auditable.

17. Lobbying, Coaching, and Third-Party Influence Protections

Remote participation shall not be used to conceal lobbying, coaching, intimidation, party control, donor influence, or third-party direction during official proceedings.

During votes, confidential proceedings, committee questioning, witness examination, and other official decision-making moments, a member may be required to confirm that they are not receiving undisclosed assistance, coaching, instruction, or pressure from:

• Lobbyists.

• Donors.

• Party officials.

• Campaign staff.

• Corporate representatives.

• Union representatives.

• Advocacy groups.

• Foreign actors.

• Constituency staff not formally authorized for that proceeding.

• Any other unauthorized third party.

This does not prevent elected officials from receiving legitimate staff support, legal advice, accessibility assistance, translation assistance, or technical support where permitted.

However, any assistance that could affect the independence, confidentiality, or integrity of the proceeding must be disclosed according to the rules of the elected body.

18. Technical Failure Rules

A member shall not be penalized for a verified technical failure outside their control.

Technical failure rules must distinguish between:

• Verified platform failure.

• Regional internet outage.

• Power outage.

• Emergency service disruption.

• Member equipment failure.

• Failure to appear.

• Failure to remain present.

• Failure to use an approved location.

• Misuse of technical failure claims to avoid accountability.

Repeated technical failures from an unapproved, inadequate, or unreliable location may result in the member being required to attend from an approved government building, constituency office, public institution, or other secure site.

The elected body shall maintain backup procedures for urgent votes, emergency sessions, and critical proceedings.

19. False Attendance, False Location, and System Misuse

It shall be a serious breach of public trust for an elected official or candidate to knowingly misrepresent attendance, location, identity, participation, technical failure, or residency status.

Penalties may apply where a person:

• Logs in from an unapproved location.

• Spoofs or conceals location.

• Allows another person to access the system on their behalf.

• Claims attendance while absent.

• Claims active participation while not participating.

• Makes a false technical failure claim.

• Misrepresents their identity.

• Falsifies voting participation.

• Conceals unauthorized coaching or third-party influence.

• Makes a false residency declaration.

• Uses a temporary or artificial address to evade residency rules.

Penalties may include public reporting, loss of allowances, loss of committee compensation, ethics referral, administrative fines, censure, removal from committee roles, referral to election authorities, or other sanctions authorized by law.

20. Exceptions Requiring In-Person Attendance

Certain proceedings may still require physical attendance, including:

• Swearing-in ceremonies.

• Confidence votes, where required by law or legislative rule.

• Budget votes, where required.

• Constitutional votes.

• Emergency national security sessions.

• Classified briefings.

• Ceremonial duties.

• Proceedings involving sensitive legal privilege.

• Proceedings involving secure documents that cannot be accessed remotely.

• Situations where the Speaker, Chair, Clerk, or presiding officer determines physical attendance is essential to the integrity of the proceeding.

These exceptions must be limited, justified, recorded, and, where possible, publicly disclosed.

The presumption should remain that remote attendance is valid unless a clear reason exists to require physical presence.

21. Housing and Capital Residence Costs

Public funds should not automatically pay for elected officials to maintain a second residence near the capital where secure remote participation allows them to fulfill their duties from within their own riding.

An elected official who chooses to maintain a residence in the capital region for personal, political, party, media, or convenience reasons shall not be entitled to full public reimbursement unless the position requires regular physical presence.

Publicly funded capital housing or accommodation may be available only where:

• The official holds a position requiring frequent in-person attendance, such as Prime Minister, Premier, Cabinet Minister, Speaker, House Leader, Whip, Opposition Leader where justified, or other designated office.

• The role includes security, emergency, national interest, executive, ceremonial, or constitutional obligations requiring physical proximity.

• The legislature or Parliament is in a period requiring extended in-person attendance.

• A verified disability, health, safety, family, or accessibility need makes the arrangement necessary.

• Remote attendance is temporarily unavailable due to technical, legal, constitutional, emergency, or security reasons.

Where an elected official does not qualify for public housing support but chooses to live near the capital, those costs should be paid personally or through riding-generated political funds, subject to strict transparency rules, donation limits, conflict-of-interest rules, and public disclosure.

Public housing support shall not be justified by party strategy, media convenience, fundraising, campaign operations, or personal preference.

22. Opposition Leader Residence

This policy shall eliminate any automatic entitlement of the Leader of the Opposition to a government-funded official residence in the capital region.

The Leader of the Opposition may receive publicly funded accommodation only when physical presence in the capital is required for parliamentary, security, ceremonial, emergency, constitutional, or other official public duties.

Routine political work, party strategy, media availability, caucus management, fundraising, campaign planning, and ordinary parliamentary participation shall not, by themselves, justify a permanent taxpayer-funded residence where secure remote attendance and communication systems are available.

Where the Leader of the Opposition chooses to maintain a residence in the capital for convenience, party operations, media access, or political strategy, those costs shall not be borne by general public funds.

Any public support must be limited, disclosed, justified, and tied to required official duties rather than political preference or tradition.

The same principle shall apply provincially and territorially to opposition leaders where government-funded capital housing, official residences, or equivalent housing allowances exist.

23. Party Work Versus Public Work

Public reimbursement shall distinguish between official public duties and party-political work.

Public funds may support:

• Parliamentary or legislative duties.

• Committee duties.

• Constituency duties.

• Cabinet or executive duties.

• Required official travel.

• Required public hearings.

• Emergency governance responsibilities.

• Official public representation.

Public funds shall not be used to subsidize:

• Party fundraising.

• Campaign planning.

• Candidate recruitment.

• Party strategy.

• Internal party media preparation.

• Donor meetings.

• Election operations.

• Partisan events unrelated to official duties.

• Travel or housing primarily for party convenience.

Where an expense has mixed public and party purposes, the public portion must be clearly identified, justified, and disclosed.

24. Travel Cost Reduction

Travel reimbursement shall prioritize necessary travel, not routine political convenience.

Public reimbursement may be provided for:

• Required in-person sittings.

• Emergency sessions.

• Security briefings.

• Cabinet or executive duties.

• Constituency service travel within the riding.

• Committee work requiring physical inspection, witness attendance, or site visits.

• Accessibility or family-care needs where justified.

• Official intergovernmental meetings.

• Required travel to Indigenous, rural, remote, or northern communities.

• Official disaster, emergency, or public safety duties.

Public reimbursement should not be used for repeated travel to the capital where the member could reasonably attend remotely from an approved location.

Annual travel and accommodation costs for each elected official shall be publicly disclosed in a searchable format, separated by:

• Constituency travel.

• Capital travel.

• Committee travel.

• International travel.

• Party-related travel.

• Accommodation.

• Meals.

• Incidentals.

• Security-related travel.

• Accessibility-related travel.

• Family-care or medical accommodation where disclosure can be made without violating privacy.

25. Public-Facing Constituency Availability Standard

Each elected official shall be required to maintain regular, published public availability within their riding, district, ward, or represented region.

This shall include:

• Published constituency office hours.

• Public contact information.

• A minimum number of public constituency days.

• A minimum number of open town halls or public meetings each year.

• Virtual town halls where geography requires them.

• Appointment availability.

• Community office days.

• Regular meetings with local organizations, municipalities, Indigenous governments, public institutions, or community groups.

• Public reporting on issues raised by constituents.

• An annual riding accessibility report.

The purpose is to ensure remote attendance in Parliament or a legislature increases local availability rather than reducing official duties.

An elected official should not be permitted to remain in the riding physically while still being inaccessible to the public.

26. Candidate Residency Requirement

A person seeking election in a riding, district, ward, or represented region must have a primary residence in that riding or, where geography or housing availability makes that unreasonable, in a directly adjacent riding or district.

The residency requirement must be satisfied for a minimum period before nomination or election, unless an exemption applies.

Possible exemption categories may include:

• Newly created or redistributed ridings.

• Northern, rural, remote, or Indigenous communities with limited housing availability.

• Safety concerns.

• Military service.

• Diplomatic service.

• Caregiving obligations.

• Medical treatment.

• Education.

• Temporary public-service obligations.

• Candidates displaced by disaster, fire, flood, domestic violence, or other verified emergency.

• Temporary absence where the person has a long-standing and demonstrable connection to the riding.

A candidate shall not be permitted to rely only on party appointment, temporary rental arrangements, mailing addresses, campaign offices, short-term occupancy, or symbolic addresses to satisfy the residency requirement.

27. Definition of Primary Residence

For the purposes of this policy, “primary residence” means the place where the candidate or elected official ordinarily lives and maintains a genuine personal, civic, and community connection.

Factors may include:

• Where the person sleeps most nights.

• Where immediate family resides, where applicable.

• Where the person receives personal mail.

• Where the person is registered for tax, health, school, vehicle, or other civic purposes.

• Where the person maintains long-term housing.

• Where the person participates in ordinary community life.

• Whether the residence is more than a nominal or campaign-related address.

• Whether the person has a long-standing connection to the community.

• Whether the person has recently moved only for electoral eligibility.

No single factor should be determinative, but the standard must prevent artificial, temporary, or misleading residency claims.

28. Anti-Parachute Candidate Rule

Political parties shall not nominate candidates who lack a meaningful residential or community connection to the riding unless a public exemption is granted.

Where a party seeks an exemption, it must disclose:

• Why a local candidate was not selected.

• The candidate’s connection to the riding.

• Whether the candidate intends to relocate.

• Whether the candidate has previously lived, worked, studied, served, or held community responsibilities in the riding.

• Why the exemption is in the public interest.

• Whether the candidate’s residence is permanent, temporary, campaign-related, or symbolic.

• Whether the candidate has been placed in the riding by the party.

This disclosure must be made before the candidate is confirmed on the ballot.

Voters have the right to know whether a candidate actually lives in the community they seek to represent.

29. Election-Period Residency Rules

Candidate residency status shall be disclosed publicly at the time of nomination.

Election authorities shall be empowered to review candidate residency claims and require supporting documentation where necessary.

False residency claims may result in:

• Public correction.

• Administrative penalties.

• Party fines where the party knowingly supported a false claim.

• Referral to the relevant election authority.

• Disqualification where permitted by law.

• Post-election review where the false claim may have affected voter trust.

Residency rules shall not be used to exclude legitimate candidates with real community ties who are temporarily absent for health, safety, family, employment, education, military, diplomatic, disaster, or public-service reasons.

The purpose is not to punish mobility. The purpose is to prevent artificial representation.

30. Security, Privacy, and Integrity Requirements

The remote attendance system must meet strict standards for:

• Identity verification.

• Location verification.

• Cybersecurity.

• Encryption.

• Public record preservation.

• Accessibility.

• Interpretation and translation services.

• Protection of confidential proceedings.

• Protection against impersonation.

• Protection against location spoofing.

• Protection against undisclosed third-party coaching.

• Protection against unauthorized recording.

• Protection against cyberattack.

• Technical redundancy.

• Secure voting.

• Audit logs.

• Independent review.

The system must be publicly audited at regular intervals by an independent officer, agency, or auditor.

Audit reports shall be public unless disclosure would compromise security.

31. Democratic Continuity and Emergency Governance

This policy shall also serve as a democratic continuity framework.

Remote attendance systems shall be maintained so elected bodies can continue to function during:

• Pandemics.

• Wildfires.

• Floods.

• Severe weather.

• Public health emergencies.

• Terrorist threats.

• Security lockdowns.

• Travel shutdowns.

• Infrastructure failures.

• Occupation or blockade of public buildings.

• Attacks on democratic institutions.

• Regional disasters.

• Other emergencies that prevent safe or practical physical attendance.

A democracy should not become non-functional because representatives cannot travel to one building.

32. Independent Oversight and Enforcement

Oversight responsibilities shall be assigned to existing independent officers wherever possible.

These may include:

• The Speaker or presiding officer for attendance and order.

• The Clerk for procedural compliance and official records.

• The Ethics Commissioner or Conflict of Interest Commissioner for conduct and misuse.

• The Chief Electoral Officer for candidate residency rules.

• The Auditor General for cost reporting and public savings.

• The Parliamentary Budget Officer or equivalent for financial analysis.

• Privacy commissioners for data protection.

• Cybersecurity authorities for system integrity.

• Legislative management committees for internal rules.

A new agency is not required unless existing institutions cannot provide effective oversight.

The policy must clearly assign responsibility so enforcement does not disappear between offices.

33. Cost Comparison and Public Savings Reporting

Each elected body shall publish annual cost reporting showing:

• Previous housing, travel, and accommodation costs.

• Current housing, travel, and accommodation costs.

• Cost of operating the secure digital attendance system.

• Cost of secure public access points.

• Estimated savings.

• Expenses avoided.

• Net public benefit.

• Per-member travel and accommodation costs.

• Capital-residence reimbursement.

• Exemptions granted.

• Public explanation for major cost increases.

The purpose is to ensure the policy actually reduces unnecessary public spending rather than simply shifting costs into new categories.

34. Annual Public Reporting

Each Parliament, legislature, council, board, or elected body subject to this policy shall publish an annual report showing:

• In-person attendance.

• Remote attendance.

• Absences.

• Non-participating logins.

• Committee participation.

• Voting participation.

• Travel costs.

• Housing and accommodation costs.

• Publicly funded capital residence use.

• Exemptions granted.

• Technical failures.

• Constituency office accessibility.

• Public availability within the riding.

• Town halls or public meetings held.

• Residency exemptions granted to candidates.

• Complaints related to absence or lack of local availability.

• Penalties or corrective actions imposed.

• Net public savings or costs.

The report shall be available in a searchable public database.

35. Transition and Implementation

This policy shall be implemented through a staged transition.

Year 1: Preparation and Baseline

• Amend standing orders or procedural rules where required.

• Build or procure secure digital attendance systems.

• Identify approved remote attendance locations.

• Establish cybersecurity and accessibility standards.

• Publish baseline travel, housing, and accommodation costs.

• Pilot remote attendance in selected committees or public proceedings.

Year 2: Legislative and Committee Implementation

• Expand remote attendance to eligible proceedings.

• Begin public attendance reporting.

• Require active attendance verification.

• Introduce cost reporting.

• Establish technical failure rules.

• Create secure access points in underserved regions.

Year 3: Housing and Travel Reform

• Reform capital housing reimbursement.

• Restrict public funding for second residences.

• Apply party-work versus public-work expense rules.

• Publish first full cost comparison report.

• Apply penalties for false location, false attendance, and misuse.

Next Election Cycle: Candidate Residency Reform

• Apply candidate residency disclosure requirements.

• Enforce anti-parachute candidate rules.

• Require public exemption applications.

• Allow election authorities to review false or artificial residency claims.

This transition period allows governments to modernize without disrupting democratic operations.

36. Review Clause

This policy shall be reviewed after the first full election cycle following implementation, and every five years afterward.

The review shall assess:

• Attendance rates.

• Public access to elected officials.

• Cost savings.

• Impact on rural and remote representation.

• Impact on disabled elected officials and constituents.

• Security performance.

• Public trust.

• Abuse or misuse of remote attendance.

• Whether exemptions are being overused.

• Whether candidate residency rules are effective.

• Whether capital housing and travel expenses have actually declined.

The review shall include public consultation.

37. Plain-Language Summary

This policy would allow elected officials to attend Parliament, legislatures, committees, councils, and other public meetings through a secure online system, but only from within their riding or from approved government or public buildings.

It would reduce unnecessary taxpayer-funded housing and travel costs, make attendance easier to track, and remove distance from the capital as a routine excuse for missing meetings.

It would also require candidates to actually live in, or very near, the riding they want to represent, with limited exemptions for special circumstances.

The policy would eliminate automatic taxpayer-funded capital housing where the position does not truly require it, including any automatic official residence entitlement for an opposition leader.

The goal is simple: elected officials should be more available to the people who elected them, more accountable for showing up, and less dependent on public money to live near the capital when secure technology already allows them to do much of the work from home.

38. Core Principle

Elected office should not be structured around the convenience of the capital.

It should be structured around the people, communities, and ridings that elected officials are supposed to represent.

If governments expect citizens, workers, courts, schools, businesses, and public services to adapt to modern digital systems, elected officials should not be exempt from the same modernization when it improves accountability, reduces costs, and brings representatives closer to the people they serve.

Every new subdivision, warehouse, school, hospital, condo tower, data centre, and commercial development increases demand on an energy system we already know is under strain. At the same time, governments keep talking about affordability, electricity reliability, emissions, housing costs, AI infrastructure, and future energy supply as though they are separate issues.

They are not.

If we are going to keep building, then new buildings should not simply consume from the public grid. They should help support it.

This proposal does not require every new structure to power itself completely. That would be unrealistic in many cases. What it does require is that every new building include some form of renewable energy supply or demand-reduction system — solar, wind, geothermal, solar thermal, or an approved equivalent — so that new construction provides at least some relief to the grid it depends on.

It also addresses two fairness issues that are often ignored.

First, if renewable energy lowers a household’s monthly energy costs, mortgage applications should be required to count that savings when assessing affordability. A home that costs less to operate should not be treated the same as one that leaves the buyer fully exposed to rising utility bills.

Second, when a home or building sends surplus power back to the grid, that returned power should not be hit with delivery and transmission charges. You should not be charged as though you are consuming electricity when you are helping supply it.

This is not just a climate policy.

It is housing policy, grid policy, affordability policy, and infrastructure policy.

If a new building adds demand, it should also provide some relief.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Renewable-Ready Construction and Grid Relief Policy

Purpose

Every new building adds demand to the electrical grid. As homes, businesses, warehouses, schools, public buildings, and industrial facilities are constructed, governments should require that new development contribute to grid resilience rather than simply increasing grid pressure.

This policy would require all new building construction to include an on-site renewable energy component, such as solar, wind, geothermal, or another approved low-emission energy system.

The purpose is not to require every building to fully power itself. The purpose is to ensure that every new building helps reduce long-term demand on the public grid, lowers energy costs where possible, and contributes to a more resilient energy system.

Core Requirement

All new building construction would be required to include a renewable energy supply or renewable energy offset system.

Eligible systems may include, but are not limited to:

• Rooftop or building-integrated solar.

• Small-scale wind generation, where appropriate.

• Geothermal heating and cooling.

• Solar thermal systems.

• Community-based renewable connections where on-site generation is impractical.

• Other approved renewable or low-emission systems that reduce demand on the public grid.

The renewable system would not be required to supply the full energy needs of the structure. However, it must provide a measurable contribution toward reducing the building’s net demand.

Minimum Contribution Standard

The policy should establish a minimum renewable contribution requirement based on building type, size, use, and location.

For example, the requirement could be based on one or more of the following:

• A minimum percentage of projected annual electricity use.

• A minimum installed generation capacity per square metre.

• A minimum reduction in projected grid demand.

• A minimum contribution to heating, cooling, or hot water demand.

• A site-specific renewable feasibility assessment.

The standard should recognize that not every technology is suitable for every location. A solar requirement may make sense for one site, while geothermal may be more appropriate for another.

Residential Mortgage Recognition

For residential housing, mortgage qualification rules should recognize the real monthly cost savings created by renewable energy systems.

Where a new home includes a renewable energy supply that reduces monthly utility costs, lenders and mortgage insurers should be required to account for the verified energy-cost offset when assessing housing affordability.

Currently, a household may be treated as though it carries the full energy cost of a conventional home, even when the home’s renewable system will reduce those costs. This can make renewable-equipped homes appear less affordable on paper, even when they are less expensive to operate month to month.

Mortgage applications for qualifying homes should therefore include:

• Estimated monthly energy savings.

• Expected reduction in utility costs.

• Any renewable energy credit or grid-return benefit.

• Maintenance costs, where applicable.

• Net monthly housing cost after energy savings.

This would allow affordability assessments to reflect the actual cost of living in the home, rather than only the purchase price and conventional utility assumptions.

No Delivery and Transmission Charges on Power Returned to the Grid

Where a renewable-equipped building is connected to the electrical grid, power returned to the grid should not be subject to delivery and transmission charges.

A household, business, school, farm, or public facility that generates surplus electricity and sends it back to the grid is supplying energy to the system. It should not be charged delivery and transmission fees on electricity it contributes.

This rule should operate alongside a fair market buyback requirement. Returned power should be compensated at current market value, and the person or entity supplying that power should not be charged delivery and transmission fees on the energy they are providing to the grid.

Utilities may still apply reasonable administrative, metering, interconnection, and safety standards, but those standards must not be used to discourage small-scale renewable generation, reduce the value of returned power, or create hidden penalties against distributed energy producers.

Fair Market Buyback for Power Returned to the Grid

Where a renewable-equipped building returns surplus electricity to the grid, the grid operator or utility must purchase that electricity at current market value.

Returned power should not be treated as a favour to the property owner, nor should it be discounted simply because it comes from a household, farm, school, small business, public building, or community-scale renewable system.

If the grid needs electricity, and a building supplies electricity, that power has value.

The buyback rate should reflect the current market value of electricity at the time it is supplied to the grid, subject only to transparent and publicly regulated rules. Utilities should not be permitted to create artificial pricing structures that substantially reduce the value of small-scale or distributed renewable generation.

The only exception should apply when both of the following conditions are met:

• The grid is already being supplied by 100% renewable energy at that time; and

• All available grid-connected energy storage is already at capacity.

In that limited circumstance, the grid may temporarily decline or reduce compensation for additional returned power, because accepting the power would provide no practical system benefit.

This exception must be narrow, time-limited, publicly auditable, and based on real grid conditions. It must not be used as a general excuse to avoid compensating property owners for renewable electricity returned to the system.

Where power is accepted by the grid, it must be paid for.

Where power is needed by the grid, it must be valued fairly.

A renewable-ready construction policy only works if the public is not asked to invest in generation systems while utilities are allowed to undervalue the electricity those systems produce.

Grid Resilience and Public Benefit

This policy recognizes that distributed renewable generation provides public benefits.

On-site and local renewable systems can:

• Reduce peak demand.

• Lower long-term pressure on transmission infrastructure.

• Improve resilience during grid stress.

• Reduce household and business operating costs.

• Support local energy independence.

• Reduce the need for expensive new centralized generation.

• Lower emissions from new development.

• Make new buildings less vulnerable to future energy price shocks.

A building that contributes even a small share of its own energy needs is less burdensome to the public system than one that contributes nothing.

Share

Public Buildings

All new publicly funded buildings should meet a higher renewable contribution standard.

This would include:

• Schools.

• Hospitals.

• Libraries.

• Recreation centres.

• Government offices.

• Public housing.

• Transit facilities.

• Municipally owned buildings.

Where public dollars are used to construct a building, the long-term operating savings should benefit the public as well. Renewable systems should be considered part of responsible public infrastructure, not optional upgrades.

Large Commercial and Industrial Buildings

Large commercial, warehouse, institutional, and industrial buildings should be required to complete a renewable feasibility and grid-impact assessment before approval.

This assessment should identify:

• Projected grid demand.

• Available roof, land, or structural capacity for renewable generation.

• Heating and cooling alternatives.

• Potential for geothermal or waste-heat systems.

• Battery storage opportunities.

• Expected peak-demand contribution.

• Measures to reduce demand on local grid infrastructure.

Large buildings with significant roof area or land area should not be permitted to add major new electrical demand without also contributing meaningful generation or demand reduction.

Exemptions and Alternatives

Exemptions should be limited and justified.

A building may qualify for an exemption or alternative compliance pathway where:

• Renewable installation is technically impractical.

• The site has insufficient access to renewable resources.

• Structural or safety limitations prevent installation.

• Heritage or environmental protections restrict installation.

• A better community-scale renewable option is available.

Where an exemption is granted, the builder or owner should be required to contribute to an approved community renewable energy project, local grid-resilience fund, or equivalent demand-reduction program.

Exemptions should not become a loophole that allows ordinary projects to avoid compliance.

Anti-Affordability Abuse Clause

The cost of renewable installation must not be used as a justification for excessive housing price increases.

Governments should support standardized installation practices, bulk procurement, low-interest financing, and predictable permitting to reduce costs.

For residential construction, the goal is to lower long-term housing costs, not create another price premium that benefits developers while burdening buyers.

Builders should be required to disclose:

• The installed cost of the renewable system.

• Expected monthly energy savings.

• Expected maintenance costs.

• Warranty terms.

• Expected lifespan of the system.

• Any rebates, grants, or tax incentives received.

Any public subsidy or incentive for renewable installation should be passed through transparently to the purchaser, tenant, or public owner.

Rental Housing

Where renewable systems are installed on rental housing, the financial benefit should not flow only to the building owner while tenants continue paying full utility costs.

For rental properties, the policy should require transparent allocation of benefits.

This may include:

• Reduced utility charges for tenants.

• Lower common-area energy costs.

• Rent-control recognition where public subsidies were used.

• Disclosure of who receives the energy savings.

• Protection against using publicly supported renewable upgrades as a pretext for excessive rent increases.

If tenants are helping pay for the system through rent, fees, or public subsidy, tenants should share in the benefit.

Building Code Integration

The renewable requirement should be integrated into building codes, development approvals, and occupancy permitting.

A new building should not be approved unless it includes:

• A renewable energy plan.

• A projected energy contribution estimate.

• Grid-connection details, if applicable.

• Maintenance and ownership responsibility.

• Disclosure of expected savings.

• Confirmation that returned power will not be charged delivery and transmission fees.

This requirement should be treated as a standard part of modern construction, similar to insulation, ventilation, fire safety, accessibility, and energy-efficiency requirements.

Implementation Timeline

The policy should be phased in to allow industry adaptation.

A possible timeline could include:

• Year 1: Mandatory renewable feasibility disclosure for all new buildings.

• Year 2: Renewable requirement for public buildings and large commercial buildings.

• Year 3: Renewable requirement for new residential construction.

• Year 4: Full integration into building codes and mortgage affordability rules.

Remote, northern, rural, and low-income housing contexts should receive specific implementation support so the policy does not worsen affordability or regional inequality.

Enforcement

Enforcement should occur through the building approval and occupancy process.

Compliance should be required before final occupancy approval unless an approved alternative compliance pathway has been granted.

Penalties may apply where developers:

• Misrepresent projected energy savings.

• Fail to install required systems.

• Remove or disable systems after approval.

• Claim renewable compliance through systems that are not functional.

• Receive public incentives but fail to pass through the disclosed benefit.

• Charge delivery or transmission fees on power returned to the grid contrary to the policy.

Policy Principle

New buildings should not only consume from the public grid. They should help support it.

A renewable energy requirement for new construction recognizes that energy infrastructure is no longer separate from housing policy, affordability policy, climate policy, and public infrastructure planning.

If a building is going to add new demand, it should also provide some relief.

Subscribe now

This proposal, the Homes First Residential Ownership Act, is built around a simple distinction: purpose-built apartment buildings can and should remain part of the rental housing system, but single-family homes, duplexes, townhouses, and other family-scale housing should not be quietly converted into corporate portfolios.

When corporations, funds, holding companies, or large investor networks buy up family homes, they do more than compete with individual buyers. They remove attainable homes from the ownership market, push prices upward, increase rental pressure, and turn neighbourhoods into revenue streams. The result is a housing market where ordinary people are asked to compete not just with other families, but with capital itself.

This policy also ties directly into two earlier proposals: the Property Tax Stability Model and the Farm Valuation Model.

The Property Tax Stability Model is based on the idea that people should not be taxed out of their homes simply because surrounding land values have been inflated by speculation. The Farm Valuation Model applies a similar principle to agricultural land, protecting working farms from being priced as future development assets rather than food-producing land.

This proposal extends that same logic to residential ownership.

Homes should be valued and regulated according to their social purpose, not merely their maximum speculative value. A house is not just an asset class. A farm is not just undeveloped real estate. A neighbourhood is not just a portfolio waiting to be optimized.

Together, these policies form a broader land-stability framework: protect people in their homes, protect farmland as farmland, and protect family-scale housing from being absorbed into corporate investment structures.

The goal is not to eliminate rental housing. It is to draw a clear line between rental housing that adds needed supply and investment behaviour that removes homes from the people and communities they were built to serve.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Homes First Residential Ownership Act

Purpose

The purpose of this Act is to protect residential housing as shelter first, not primarily as a speculative investment asset.

The Act recognizes that purpose-built rental housing has a legitimate role in the housing system, especially apartment buildings, seniors’ residences, student housing, co-operative housing, non-profit housing, and supportive housing.

However, widespread corporate ownership, investor aggregation, and multi-property speculation in single-family homes, duplexes, triplexes, row houses, and townhouses can remove attainable homes from the ownership market, increase rents, concentrate housing power, and destabilize communities.

This Act is intended to preserve family-scale housing for households, local residents, non-profits, co-operatives, and community housing providers while still allowing professionally managed apartment rental housing.

1. Definitions

Residential property

“Residential property” means land or buildings intended primarily for human habitation.

Family-scale residential property

“Family-scale residential property” means:

• a detached single-family home;

• a semi-detached home;

• a duplex;

• a triplex or fourplex, where each unit could reasonably function as a family dwelling;

• a townhouse;

• a row house;

• a condominium unit not located in a purpose-built rental apartment building;

• any substantially similar dwelling prescribed by regulation.

Purpose-built rental apartment building

“Purpose-built rental apartment building” means a residential building originally constructed, approved, or legally converted for long-term rental occupancy, generally containing multiple rental units under common management, and not designed primarily for individual resale as separate family homes.

Corporate owner

“Corporate owner” means a corporation, trust, partnership, real estate investment trust, private equity fund, numbered company, holding company, or any entity other than a natural person, public housing provider, non-profit housing provider, Indigenous government, co-operative housing provider, or approved community land trust.

Beneficial owner

“Beneficial owner” means any person or entity that directly or indirectly owns, controls, profits from, or exercises decision-making authority over a residential property.

2. Core Principle

Family-scale residential property should not be treated as a bulk investment class.

Corporations may own and operate apartment complexes, purpose-built rental housing, seniors’ residences, student housing, supportive housing, and other approved multi-unit rental facilities.

Corporations should not be permitted to accumulate single-family homes, duplexes, townhouses, or similar family-scale housing in ways that reduce ownership supply, inflate prices, or extract excessive rents from communities.

3. Corporate Ownership Restrictions

Prohibited acquisition

A corporate owner may not purchase, acquire, or obtain beneficial control over a family-scale residential property unless an exemption applies.

This includes acquisition through:

• direct purchase;

• subsidiary ownership;

• numbered companies;

• trusts;

• nominee ownership;

• shareholder agreements;

• lease-to-own control structures;

• long-term beneficial control agreements;

• bundled portfolio purchases;

• foreclosure acquisition, except under strict temporary rules.

Exemptions

A corporate owner may acquire family-scale residential property only where the property is used for one of the following approved purposes:

• non-profit housing;

• co-operative housing;

• transitional housing;

• emergency shelter;

• supportive housing;

• Indigenous housing;

• public housing;

• staff housing in remote or essential-service communities;

• redevelopment into higher-density purpose-built rental housing, subject to strict timelines;

• temporary ownership by a lender after foreclosure;

• temporary estate, insolvency, or court-supervised administration;

• other public-interest housing purposes approved by the regulator.

4. Multiple Property Ownership by Individuals

This policy should not only address corporations. Large-scale individual accumulation can create the same problem.

Ownership threshold

A natural person may own:

• one principal residence;

• one recreational or seasonal property;

• up to two additional family-scale residential rental properties.

Ownership beyond this threshold would trigger enhanced regulation, taxation, disclosure, or restriction.

Aggregated ownership

Ownership limits apply across spouses, dependent corporations, trusts, holding companies, partnerships, and beneficial ownership arrangements.

A person may not avoid the ownership threshold by placing properties in the names of relatives, corporations, trusts, or nominees while retaining beneficial control.

5. Progressive Housing Concentration Tax

Where an individual or related group owns multiple family-scale residential properties, a progressive annual tax applies.

Example structure:

• 1 principal residence: no surcharge.

• 1 to 2 additional rental homes: standard property tax.

• 3rd additional rental home: moderate surcharge.

• 4th and 5th: significant surcharge.

• 6th and beyond: prohibitive surcharge unless exempted.

The purpose is not to punish small landlords, but to prevent housing hoarding and speculative accumulation.

Revenue from this tax must be dedicated to:

• non-market housing;

• co-operative housing;

• public housing acquisition;

• rent supplements;

• first-time buyer assistance;

• community land trusts;

• accessibility upgrades;

• affordable housing construction.

6. Corporate Divestment Requirement

Corporations that already own family-scale residential properties must register those properties and file a divestment plan.

Transition period

A reasonable transition period should be provided, for example:

• 3 years for owners of fewer than 25 properties;

• 5 years for larger portfolios;

• longer only where immediate sale would seriously harm tenants or local housing stability.

Right of first refusal

Before selling, corporate owners must offer the property first to:

1. existing tenants;

2. non-profit housing providers;

3. co-operatives;

4. community land trusts;

5. municipal or provincial housing agencies;

6. first-time local homebuyers.

This prevents divestment from simply transferring housing from one speculative owner to another.

Share

7. Tenant Protection During Divestment

No tenant may be evicted solely because a corporate owner is required to divest.

During the transition period:

• existing leases remain valid;

• rent increases remain subject to provincial limits;

• renovictions are prohibited unless genuinely necessary for safety;

• tenants receive extended notice of sale;

• tenants receive first opportunity to purchase where feasible;

• public or non-profit buyers may assume tenancy agreements.

The policy must not solve one housing problem by creating another.

8. Rental Rate Stabilization for Former Corporate Properties

Where a family-scale residential property is sold by a corporate owner, rent increases should be restricted for a defined period if the property remains a rental.

For example:

• rent may not increase beyond inflation for 5 years after transfer;

• no vacancy rent reset for 5 years;

• no conversion to short-term rental during that period;

• no eviction for purchaser’s use where the buyer is another investor.

This prevents corporations from selling inflated rental assets into the market and allowing the next owner to immediately raise rents.

9. Ban on Bulk Purchases of Family Housing

No person, corporation, fund, or related group may purchase multiple family-scale residential properties as a bundled transaction unless approved by the regulator.

This prevents investors from buying entire subdivisions, foreclosure packages, builder inventories, or distressed housing portfolios before ordinary buyers can compete.

Builders and developers may sell newly constructed family-scale homes only through transparent public sale processes, with priority access for owner-occupiers.

10. New Construction Rules

The policy should distinguish between creating new rental supply and capturing existing ownership supply.

Allowed

Corporations may build and own:

• purpose-built rental apartment buildings;

• mixed-use rental buildings;

• student housing;

• seniors’ housing;

• supportive housing;

• non-market housing partnerships.

Restricted

Corporations may not build or purchase subdivisions of detached homes, duplexes, or townhouses for long-term rental portfolios unless approved as a specific public-interest housing project.

Build-to-rent exception

A limited build-to-rent exception may be allowed only where:

• the project increases net housing supply;

• the homes are not replacing attainable ownership housing;

• long-term affordability requirements apply;

• rent controls apply;

• tenants receive security of tenure;

• the ownership structure is fully disclosed;

• the project is approved by the housing regulator.

Without these limits, “build-to-rent” can become a loophole for corporate control of entire neighbourhoods.

11. Short-Term Rentals

Family-scale residential properties subject to this Act may not be converted into short-term rentals unless:

• the property is the owner’s principal residence;

• the rental is limited to part of the home or a temporary absence;

• the municipality has issued a licence;

• the property is not needed for long-term housing supply.

Corporate ownership of short-term rental houses, duplexes, condos, or townhouses should be prohibited.

12. Beneficial Ownership Registry

Every residential property must disclose its beneficial owner.

The registry must identify:

• legal owner;

• beneficial owner;

• parent corporation;

• controlling shareholders;

• trusts or nominee arrangements;

• number of residential properties under common control;

• whether the property is owner-occupied, long-term rental, vacant, short-term rental, or exempt housing.

This registry should be searchable by regulators, municipalities, tax authorities, and housing enforcement bodies.

Public access may be limited for privacy reasons, but ownership concentration data should be publicly reported.

13. Anti-Avoidance Rules

A person or corporation may not avoid this Act through:

• numbered companies;

• layered corporations;

• trusts;

• relatives or nominees;

• staggered purchases;

• fractional ownership;

• foreign holding structures;

• management contracts that transfer practical control;

• artificial separation between related companies;

• rent-to-own structures designed to preserve investor control.

Where avoidance is found, the regulator may treat all related properties as commonly controlled.

14. Enforcement

The housing regulator may:

• refuse registration of prohibited purchases;

• unwind unlawful transactions;

• impose administrative penalties;

• order divestment;

• suspend rental licences;

• restrict rent increases;

• impose vacancy penalties;

• deny access to public subsidies, grants, tax credits, or development incentives.

Penalties

Penalties should be large enough that violation is not simply a cost of doing business.

Possible penalties:

• annual fines per property;

• percentage-based fines tied to property value;

• disgorgement of rental profit from unlawful ownership;

• loss of tax benefits;

• forced sale;

• prohibition from future residential acquisitions.

15. Public Subsidy Restriction

No corporation may receive public housing subsidies, infrastructure support, tax abatements, grants, discounted land, or development incentives if it owns prohibited family-scale residential properties.

Public money should not support entities that are simultaneously reducing access to family housing.

16. Local Housing Priority

Municipalities may designate high-pressure housing zones where stronger rules apply.

In those zones:

• corporate acquisition of family-scale housing is prohibited;

• multi-property ownership surcharges are higher;

• vacant home taxes are higher;

• short-term rental rules are stricter;

• tenant purchase rights are expanded;

• non-profit acquisition rights are prioritized.

This allows the policy to respond differently in Vancouver, Calgary, Toronto, Halifax, rural towns, resort communities, and northern regions.

17. Reporting Requirements

The government must publish an annual Residential Ownership Concentration Report showing:

• number of homes owned by corporations;

• number owned by large individual landlords;

• number of family-scale homes removed from owner-occupier inventory;

• average rents by ownership type;

• vacancy rates;

• divestment progress;

• enforcement actions;

• housing purchased by tenants, non-profits, co-ops, or public agencies;

• neighbourhood-level ownership concentration.

Subscribe now

This companion proposal looks at the other side of the same problem: ordinary individuals.

Smart glasses, body-worn cameras, wearable AI, and similar devices do not only create risks when they are used by staff behind a counter. They also create risks when they are worn by the person behind you in line, beside you in a waiting room, near you at a service desk, standing beside you at a payment terminal, or sitting across from you while your documents, screen, card, or ID are visible.

A person’s private information does not become public simply because it is briefly exposed in a public or semi-public place.

This proposal starts from a simple principle: just because someone can wear a camera does not mean they should be allowed to record your life.

Your ID, bank card, health card, passport, phone screen, medical documents, legal papers, government forms, employment records, and private information should not become someone else’s image file, AI input, searchable record, or social media post.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Public Use of Camera-Capable Wearable Technology and Personal Data Protection Act

Working Policy Proposal

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

1. Purpose

The purpose of this policy is to protect individuals from the unauthorized capture, storage, sharing, analysis, upload, or misuse of sensitive personal information by private individuals using camera-capable wearable technology.

This policy is intended to apply where a person who is not acting on behalf of a business, employer, government body, public institution, contractor, or organization uses smart glasses, wearable cameras, body-worn devices, wearable AI systems, or similar technologies to capture another person’s identity documents, payment cards, screens, records, forms, images, biometric information, or other sensitive information.

This policy recognizes that modern camera-capable wearable technology allows ordinary individuals to capture information that was previously difficult or impossible to record without being noticed.

The public should not be required to accept silent recording, background capture, concealed recording, or AI analysis of their sensitive information simply because camera technology has become small, wearable, and socially normalized.

2. Relationship to Companion Legislation

This policy is intended to operate alongside the Camera-Capable Wearable Technology and Sensitive Information Protection Act.

That companion policy focuses primarily on organizations, businesses, public bodies, employers, contractors, institutions, and controlled settings where people are required or expected to expose sensitive information.

This policy focuses on the conduct of private individuals, bystanders, patrons, visitors, customers, attendees, passengers, students, patients, applicants, observers, and members of the public who may use camera-capable wearable technology to capture another person’s sensitive information.

Together, the two policies recognize that sensitive information can now be captured both by institutions and by ordinary individuals using increasingly powerful wearable technology.

Privacy protection must apply both to the organizations that require people to expose sensitive information and to the individuals who may exploit that exposure.

3. Core Principle

No person has the right to use wearable camera technology to capture another person’s ID, bank card, credit card, health card, passport, document, phone screen, form, signature, face, biometric information, or other sensitive information without lawful authority or clear consent.

The fact that a person is in a public or semi-public place does not give others permission to capture, store, upload, analyze, or share their sensitive information.

A person’s sensitive information does not become public simply because it is briefly visible.

4. Definition: Camera-Capable Wearable Technology

For the purposes of this policy, camera-capable wearable technology means any device worn on the body, face, head, clothing, uniform, helmet, eyewear, badge, lanyard, jewellery, or accessories that is capable of capturing, recording, storing, transmitting, analyzing, scanning, processing, or interpreting images, video, audio, biometric information, text, documents, screens, cards, or identifying information.

This includes, but is not limited to:

• Smart glasses.

• Camera-enabled eyewear.

• Body cameras.

• Wearable AI devices.

• Button cameras.

• Badge cameras.

• Head-mounted cameras.

• Augmented reality devices.

• Hidden wearable cameras.

• Camera-enabled accessories.

• Devices capable of facial recognition.

• Devices capable of text recognition.

• Devices capable of document capture.

• Devices capable of payment card capture.

• Devices capable of background image, video, or audio capture.

• Any similar device capable of recording, scanning, storing, transmitting, or analyzing information while worn by a person.

A device does not need to be actively recording to fall under this policy if it is technically capable of capturing, buffering, scanning, analyzing, storing, or transmitting information in the relevant setting.

5. Definition: Sensitive Personal Information

For the purposes of this policy, sensitive personal information means any information that could reasonably be used to identify, locate, track, impersonate, profile, discriminate against, financially harm, expose, exploit, intimidate, or target a person.

This includes, but is not limited to:

• Driver’s licences.

• Health cards.

• Passports.

• Birth certificates.

• Citizenship or immigration documents.

• Social insurance numbers.

• Banking information.

• Credit cards.

• Debit cards.

• Security codes.

• Expiry dates.

• Signatures.

• Home addresses.

• Phone numbers.

• Email addresses.

• Medical documents.

• Legal documents.

• Employment documents.

• Student records.

• Government benefit documents.

• Tax documents.

• Insurance documents.

• Rental applications.

• Employment applications.

• Phone screens.

• Computer screens.

• Payment terminals.

• Login credentials.

• QR codes or barcodes connected to identity, payment, health, employment, education, government services, or access systems.

• Facial images connected to identity, health, employment, education, housing, income support, immigration, policing, or public services.

• Biometric information.

• Any document, card, screen, form, record, or image containing information that could reasonably be used for identity theft, fraud, stalking, discrimination, harassment, doxxing, surveillance, profiling, or exploitation.

6. Definition: Public and Semi-Public Spaces

For the purposes of this policy, public and semi-public spaces include places where members of the public, customers, clients, patients, students, tenants, passengers, voters, applicants, or service users may reasonably be present.

This includes, but is not limited to:

• Lineups.

• Waiting rooms.

• Bars.

• Restaurants.

• Clinics.

• Hospitals.

• Pharmacies.

• Schools.

• Colleges and universities.

• Government offices.

• Voting places.

• Banks.

• Airports.

• Transit stations.

• Buses, trains, taxis, rideshare vehicles, and other transportation settings.

• Courthouses.

• Libraries.

• Social service offices.

• Shelters.

• Employment centres.

• Landlord and tenant offices.

• Retail stores.

• Hotels.

• Service counters.

• Payment areas.

• Security checkpoints.

• Public events.

• Private businesses open to the public.

• Any place where people may be required or expected to present sensitive personal information.

7. Prohibited Capture of Sensitive Personal Information

No person may knowingly, recklessly, or negligently use camera-capable wearable technology to capture, record, scan, store, transmit, analyze, or share another person’s sensitive personal information without lawful authority or clear consent.

This prohibition applies to:

• Recording another person’s ID.

• Recording another person’s bank card.

• Recording another person’s credit card or debit card.

• Recording another person’s health card.

• Recording another person’s passport.

• Recording another person’s documents.

• Recording another person’s phone screen.

• Recording another person’s computer screen.

• Recording another person’s payment terminal.

• Recording another person’s signature.

• Recording another person’s medical, legal, employment, education, housing, immigration, or government documents.

• Recording another person’s forms while they are being completed, reviewed, signed, submitted, or presented.

• Recording information that is briefly visible during a transaction, application, appointment, service interaction, or public process.

A person may violate this policy even if the sensitive information is only partially captured.

A person may also violate this policy if the information is captured incidentally but then stored, shared, reviewed, uploaded, analyzed, or used.

8. No Consent by Public Presence

A person does not consent to the capture of sensitive personal information simply by being present in a public or semi-public space.

A person does not consent to the capture of sensitive personal information by:

• Standing in a lineup.

• Sitting in a waiting room.

• Entering a business.

• Attending school.

• Visiting a clinic.

• Voting.

• Paying for goods or services.

• Showing ID to staff.

• Filling out a form.

• Using a payment terminal.

• Holding a document.

• Looking at a phone screen.

• Accessing social supports.

• Applying for employment.

• Seeking housing.

• Seeking medical care.

• Participating in a government process.

Sensitive information remains private even when it is briefly visible to others.

Share

9. High-Risk Public and Semi-Public Settings

The use of camera-capable wearable technology by private individuals should be restricted or prohibited in high-risk settings where sensitive information is commonly exposed.

These settings include, but are not limited to:

• Lineups where IDs are checked.

• Waiting rooms where medical, legal, financial, or government documents are handled.

• Bars and clubs where IDs are presented.

• Clinics and hospitals.

• Pharmacies.

• Schools and child care settings.

• Government offices.

• Voting places.

• Banks and financial institutions.

• Airports and security checkpoints.

• Social service offices.

• Shelters and income support offices.

• Employment centres.

• Landlord and tenant offices.

• Payment counters.

• Any location where children, vulnerable people, victims, patients, or people accessing social supports may be present.

Restrictions may include requiring camera-capable wearable technology to be removed, turned off, covered, placed away, or kept out of sensitive information areas.

10. Protection of Children and Vulnerable Persons

Enhanced protections shall apply where camera-capable wearable technology is used to capture, record, scan, analyze, store, or share images or information involving:

• Children.

• Youth.

• Elderly people.

• Patients.

• Victims of crime.

• Survivors of abuse.

• People experiencing homelessness.

• People accessing social supports.

• People accessing food banks or shelters.

• People accessing disability supports.

• People receiving medical care.

• People receiving mental health care.

• People involved in legal, immigration, family, custody, or protection proceedings.

• People whose identity, location, health, status, or circumstances could expose them to harm.

Capturing sensitive personal information involving these individuals shall be treated as an aggravated violation unless clearly authorized by law or necessary to prevent immediate harm.

A person must not use camera-capable wearable technology to record a child’s documents, face, location, school information, medical information, or identity information for posting, sharing, AI processing, surveillance, mockery, harassment, or personal use.

11. Recording Documents Held by Another Person

No person may use camera-capable wearable technology to record, photograph, scan, magnify, zoom in on, or otherwise capture documents, cards, screens, forms, or records being held, completed, reviewed, carried, displayed, or presented by another person without lawful authority or clear consent.

This includes documents held:

• In a person’s hand.

• On a counter.

• At a service desk.

• At a payment terminal.

• In a waiting room.

• In a lineup.

• At a voting place.

• At a clinic.

• At a school.

• At a bank.

• At a government office.

• In a workplace.

• On public transportation.

• In any public or semi-public setting.

The fact that a document is momentarily visible does not make it available for capture.

12. Screens and Digital Displays

No person may use camera-capable wearable technology to capture, record, scan, store, transmit, or analyze another person’s phone screen, laptop screen, tablet screen, payment screen, work screen, school screen, medical screen, government service screen, or other digital display where sensitive personal information may be visible.

This includes:

• Banking apps.

• Payment apps.

• Health apps.

• Government service portals.

• Employment applications.

• Housing applications.

• School portals.

• Medical records.

• Legal documents.

• Email or messaging apps.

• Login credentials.

• QR codes.

• Authentication codes.

• Two-factor authentication screens.

• Personal photos or documents.

• Any screen displaying sensitive personal information.

A person may violate this policy even if they claim the screen was visible in a public place.

13. Uploading to AI Tools, Cloud Services, or Third-Party Platforms

No person may upload, submit, process, analyze, store, or share another person’s sensitive personal information through:

• Artificial intelligence tools.

• Chatbots.

• Image recognition tools.

• Facial recognition tools.

• Optical character recognition tools.

• Translation tools.

• Document conversion tools.

• Cloud storage services.

• Social media platforms.

• Data broker services.

• Background search tools.

• People-search services.

• Public databases.

• Private group chats.

• Messaging apps.

• Any third-party system that can retain, analyze, train on, share, or repurpose the information.

This prohibition applies whether the image, document, card, screen, or information was captured intentionally, incidentally, secretly, or in the background.

A person must not upload images of strangers’ documents, cards, faces, screens, or personal information to AI tools for identification, translation, enhancement, amusement, analysis, profiling, or any other purpose without lawful authority or clear consent.

14. Bystander Liability

A person may be liable under this policy if they capture, store, share, upload, analyze, or distribute another person’s sensitive personal information while acting as a bystander.

A bystander does not avoid responsibility by claiming they were not part of the business, organization, service, event, or transaction where the information was exposed.

Bystander liability may apply where a person:

• Records another person’s ID in a lineup.

• Records another person’s payment card at a counter.

• Records another person’s documents in a waiting room.

• Records another person’s phone screen on public transportation.

• Records a person accessing social supports.

• Records a person at a clinic, shelter, voting place, school, bank, government office, or legal proceeding.

• Shares or uploads another person’s sensitive information after capturing it.

• Uses wearable technology to zoom in on documents, screens, cards, or forms held by another person.

The absence of a direct relationship between the person recording and the person recorded shall not be a defence.

15. Concealed Recording

Concealed recording of sensitive personal information by camera-capable wearable technology shall be treated as an aggravated violation.

Concealed recording includes:

• Wearing hidden cameras.

• Disabling recording indicators.

• Covering recording indicators.

• Using camera-capable devices designed to appear inactive.

• Using camera-capable devices designed to resemble ordinary eyewear, accessories, clothing, jewellery, or badges.

• Recording while claiming the device is not active.

• Using software that captures information in the background while the device appears inactive.

• Using zoom, enhancement, AI analysis, or OCR to extract information not clearly visible to the human eye.

Where concealed recording occurs, the capture shall be presumed intentional unless the person responsible can prove otherwise.

16. Recording Indicators and Device Transparency

No person may disable, conceal, bypass, suppress, alter, or interfere with a recording indicator on camera-capable wearable technology when used in public or semi-public spaces.

A recording indicator includes any light, sound, icon, screen notice, haptic alert, software notification, system message, or other signal intended to show that image, video, audio, biometric, document, or data capture is occurring.

It shall be a serious violation to:

• Disable a recording light.

• Cover a recording light.

• Modify software to suppress a recording notice.

• Use third-party tools to hide recording.

• Use hardware modifications to conceal recording.

• Use a device known to provide misleading recording indicators.

• Use a device that captures information in the background without clear notice.

Disabling or concealing recording indicators shall trigger enhanced penalties.

17. Passive, Background, or Undisclosed Capture

No person may use camera-capable wearable technology in a way that allows passive, background, or undisclosed capture of sensitive personal information in public or semi-public settings.

This includes devices or software that:

• Temporarily buffer images, video, or audio.

• Store pre-recording footage.

• Scan text, cards, faces, documents, or screens in the background.

• Upload images, video, audio, or metadata to cloud services.

• Create OCR outputs.

• Create facial templates.

• Create object recognition data.

• Create searchable records.

• Use “always-on,” “context awareness,” “memory,” “assistant,” “scene understanding,” or similar functions.

• Retain information after the user believes the device is inactive.

• Make sensitive information available to a device manufacturer, software provider, AI system, advertiser, analytics vendor, or third party.

A person may be liable if they knowingly use a device in a setting where such background capture is reasonably foreseeable.

18. Sharing, Publishing, or Redistributing Captured Information

No person may share, publish, post, sell, trade, forward, distribute, upload, or otherwise disclose another person’s sensitive personal information captured through camera-capable wearable technology.

This includes sharing through:

• Social media.

• Messaging apps.

• Group chats.

• Email.

• Cloud folders.

• AI tools.

• Search tools.

• Data broker platforms.

• Employer systems.

• Public websites.

• Private forums.

• Law enforcement tip lines, unless reporting an immediate and lawful concern.

• Media outlets, unless protected by a clear public interest exception.

Sharing captured sensitive personal information shall be treated as a separate violation from the original capture.

Each further disclosure may create additional liability.

19. Public Interest and Safety Exceptions

This policy is not intended to prohibit lawful recording where necessary to document immediate danger, violence, abuse, police misconduct, public corruption, environmental harm, threats to safety, or other matters of clear public interest.

However, even where recording is justified for public interest or safety reasons, the person recording must take reasonable steps to avoid capturing or sharing unrelated sensitive personal information.

Where possible, sensitive information should be blurred, cropped, redacted, or excluded before any sharing.

The public interest exception does not allow the unnecessary capture, publication, upload, or AI processing of IDs, bank cards, health cards, documents, children’s information, medical information, immigration information, or other sensitive personal information unrelated to the public interest matter being documented.

20. Right to Object and Request Cessation

A person has the right to ask another individual to stop using camera-capable wearable technology where their sensitive personal information is visible or at risk of capture.

A person may ask that the device be:

• Turned away.

• Removed.

• Covered.

• Turned off.

• Placed away.

• Kept at a distance.

• Disabled for the duration of the sensitive interaction.

A refusal to comply may be considered evidence of intentional or reckless conduct where sensitive personal information is captured.

No person may threaten, harass, intimidate, retaliate against, or mock another person for objecting to the use of camera-capable wearable technology near sensitive personal information.

21. Civil Remedies

A person whose sensitive personal information is captured, stored, shared, uploaded, analyzed, or misused in violation of this policy may seek civil remedies.

Remedies may include:

• Statutory damages without requiring proof of financial loss.

• Compensation for actual financial loss.

• Compensation for emotional distress.

• Compensation for identity theft risk.

• Compensation for reputational harm.

• Compensation for safety risk.

• Injunctions preventing further use or disclosure.

• Orders requiring deletion.

• Orders requiring confirmation of deletion.

• Orders requiring removal from online platforms.

• Orders prohibiting further contact.

• Recovery of legal costs.

• Enhanced damages for intentional, concealed, repeated, exploitative, discriminatory, or AI-related misuse.

The absence of proven financial loss shall not prevent recovery.

Unauthorized capture of sensitive personal information is itself a harm.

22. Enhanced Penalties

Enhanced penalties shall apply where the violation involves:

• Children.

• Vulnerable people.

• Patients.

• Victims of crime.

• Survivors of abuse.

• People accessing social supports.

• People accessing shelters.

• People receiving medical care.

• People participating in legal proceedings.

• People voting.

• People showing government documents.

• People exposing banking or payment information.

• Concealed recording.

• Disabled recording indicators.

• Background capture.

• AI processing.

• Facial recognition.

• Uploading to third-party platforms.

• Public posting.

• Doxxing.

• Harassment.

• Discrimination.

• Identity theft.

• Fraud.

• Repeated conduct.

• Commercial exploitation.

Enhanced penalties may include higher statutory damages, punitive damages, device seizure where authorized by law, restrictions on future use of camera-capable wearable technology, and referral for criminal investigation where applicable.

23. Platform and AI Tool Duties

Platforms, AI tools, cloud services, and image-processing services should be required to provide a process for individuals to report the unauthorized upload or processing of sensitive personal information captured through camera-capable wearable technology.

Where a platform or AI tool receives notice that uploaded content contains another person’s sensitive personal information captured without consent, it must take reasonable steps to:

• Remove the content.

• Stop further distribution.

• Prevent indexing.

• Prevent use for AI training.

• Prevent use for facial recognition.

• Prevent use for OCR or document analysis.

• Preserve evidence where required for legal process.

• Provide a reporting pathway for the affected person.

Repeated failure by platforms to respond to such reports may create regulatory liability.

24. Education and Public Awareness

Governments should establish public education campaigns explaining that camera-capable wearable technology creates privacy risks beyond ordinary photography.

Public education should explain:

• Sensitive information remains private even when briefly visible.

• Recording another person’s ID, bank card, documents, or screen can cause serious harm.

• Smart glasses and wearable AI may capture more than the wearer realizes.

• Uploading images of strangers’ documents or faces to AI tools can create lasting harm.

• Recording indicators may not be enough.

• People have the right to object when sensitive information is at risk.

• Children, patients, victims, and vulnerable people require heightened protection.

25. Review and Updating

Because camera-capable wearable technology, AI systems, biometric tools, and image-processing software are changing rapidly, this policy must be reviewed at least every two years.

The review must consider:

• New smart glasses.

• Wearable AI devices.

• Facial recognition systems.

• Document scanning tools.

• Payment card capture risks.

• Background recording functions.

• AI memory systems.

• Social media practices.

• Platform enforcement.

• Privacy commissioner findings.

• Civil claims.

• Public complaints.

• Whether penalties are sufficient to deter violations.

26. Plain-Language Summary

This policy is based on a simple idea:

Just because someone can wear a camera does not mean they should be allowed to record your life.

Your ID, bank card, health card, passport, phone screen, medical documents, legal papers, government forms, employment records, and private information do not become public property because they are briefly visible in a lineup, waiting room, clinic, school, bank, government office, bar, airport, or payment area.

Smart glasses, body-worn cameras, wearable AI, and similar devices make it easier for ordinary people to capture sensitive information without being noticed.

That does not make it acceptable.

Privacy law must recognize that harm can come not only from institutions collecting data, but also from individuals capturing, sharing, uploading, or exploiting the sensitive information of strangers.

This is no longer just a question of whether a business scans your information. It is also a question of who may be silently recording it, where that data goes, whether software is capturing images in the background, and whether the public has any meaningful way to know.

The Camera-Capable Wearable Technology and Sensitive Information Protection Act is a proposed policy standard for places where people are asked to expose sensitive information. Bars, banks, clinics, hotels, government offices, hiring desks, schools, service counters, and payment terminals all create moments where private data can be captured in seconds.

This proposal starts from a simple principle: if an organization requires you to show sensitive information, it has a duty to protect that information from unnecessary recording, whether by staff, contractors, wearable devices, background software, or nearby third parties.

Privacy cannot depend on whether someone notices a tiny light on a pair of glasses.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Camera-Capable Wearable Technology and Sensitive Information Protection Act

Working Policy Proposal

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

1. Purpose

The purpose of this policy is to protect members of the public from the unauthorized capture, storage, transmission, sale, analysis, or misuse of personal, financial, medical, immigration, identity, or other sensitive information through camera-capable wearable technology.

This policy applies in situations where a person, employee, contractor, agent, volunteer, security worker, doorman, server, cashier, receptionist, clerk, inspector, service provider, or representative is handling, viewing, scanning, verifying, accepting, processing, or standing in viewing proximity of sensitive documents, identity cards, payment cards, or other records.

The policy recognizes that modern camera technology, including smart glasses and similar devices, may allow images, video, audio, biometric information, payment information, and document information to be captured without the clear awareness or consent of the person whose information is exposed.

2. Core Principle

No person should be required to expose identification, banking information, credit card information, debit card information, medical information, immigration status, citizenship status, address information, employment records, or other sensitive personal data to an individual wearing camera-capable technology unless strict privacy safeguards are in place.

Public access to services, venues, employment, housing, health care, education, transportation, retail transactions, financial transactions, or government services must not depend on a person accepting unnecessary visual or audio recording of their sensitive information.

The public should not have to guess whether their ID, health card, citizenship status, bank card, private documents, signature, address, or financial information is being silently recorded.

3. Definition: Camera-Capable Wearable Technology

For the purposes of this policy, camera-capable wearable technology means any device worn on the body, face, head, clothing, uniform, badge, helmet, lanyard, eyewear, or accessories that is capable of capturing, recording, storing, transmitting, analyzing, scanning, processing, or interpreting images, video, audio, biometric information, text, documents, payment information, or identifying information.

This includes, but is not limited to:

• Smart glasses.

• Camera-enabled eyewear.

• Body cameras.

• Button cameras.

• Badge cameras.

• Wearable AI devices.

• Head-mounted cameras.

• Augmented reality devices.

• Devices capable of facial recognition.

• Devices capable of text recognition.

• Devices capable of document capture.

• Devices capable of payment card capture.

• Devices capable of biometric analysis.

• Devices capable of background image, video, or audio capture.

• Any similar device capable of visual, audio, biometric, or document recording, whether visible or concealed.

A device does not need to be actively recording to fall under this policy if it is technically capable of recording, capturing, scanning, buffering, processing, or transmitting information while worn in the relevant setting.

4. Definition: Sensitive Information

For the purposes of this policy, sensitive information means any information that could reasonably be used to identify, track, impersonate, profile, discriminate against, financially harm, locate, exploit, or otherwise misuse information about a person.

This includes, but is not limited to:

• Driver’s licence numbers.

• Health card numbers.

• Citizenship status.

• Immigration status.

• Passport information.

• Birth certificates.

• Social insurance numbers.

• Banking information.

• Credit card numbers.

• Debit card numbers.

• Security codes.

• Expiry dates.

• Signatures.

• Home addresses.

• Phone numbers.

• Email addresses.

• Employment records.

• Medical information.

• Insurance information.

• Student records.

• Legal documents.

• Tax documents.

• Government benefit documents.

• Facial images connected to identity documents.

• Licence plates.

• Access cards.

• Security badges.

• Login credentials.

• QR codes or barcodes connected to identity, payment, access, health, employment, education, or government records.

• Any document, card, form, record, screen, or image containing information that could be used for identity theft, financial fraud, stalking, discrimination, unauthorized surveillance, profiling, impersonation, harassment, or targeted exploitation.

5. Clarifying “Misuse”

For the purposes of this policy, misuse means any collection, capture, retention, copying, transmission, analysis, sale, sharing, indexing, scanning, profiling, or use of sensitive information beyond what is strictly necessary for the immediate purpose for which the information was provided.

Misuse includes, but is not limited to:

• Capturing an image of a person’s ID without clear lawful authority.

• Recording payment cards during a transaction.

• Capturing medical, legal, government, financial, housing, or employment documents without lawful authority.

• Capturing documents for personal, business, training, marketing, surveillance, analytics, or AI-related purposes.

• Storing images or video of sensitive documents after the immediate transaction is complete.

• Uploading captured information to third-party platforms, cloud services, AI tools, facial recognition tools, analytics systems, or data brokers.

• Sharing captured information with employers, contractors, advertisers, insurers, landlords, law enforcement, political organizations, or other third parties without lawful authority.

• Using captured information to profile a person’s citizenship, health status, age, disability, income, address, employment status, race, ethnicity, religion, gender, immigration status, political activity, financial status, or other personal characteristics.

• Using captured information for harassment, fraud, blackmail, intimidation, discrimination, doxxing, identity theft, financial theft, commercial targeting, or surveillance.

Misuse does not require proof that harm has already occurred. Unauthorized capture, retention, transmission, or analysis of sensitive information is itself a privacy harm.

6. Prohibited Use in Sensitive Information Settings

A person may not wear or operate camera-capable wearable technology while handling, inspecting, viewing, verifying, accepting, processing, or standing in close viewing proximity to sensitive information unless the device is:

1. Required by law or public safety regulation.

2. Clearly disclosed to the person whose information is visible.

3. Necessary for the specific service being provided.

4. Subject to strict retention, deletion, access, and audit controls.

5. Incapable of storing or transmitting sensitive information beyond the immediate lawful purpose.

6. Configured to prevent background image, video, audio, biometric, text, or document capture.

7. Subject to meaningful oversight by the organization responsible for its use.

Where these conditions are not met, the device must be removed, turned off, covered, disabled, stored away, or replaced with a non-recording alternative before the person’s sensitive information is presented.

7. Viewing Proximity Standard

This policy applies not only when a person directly handles sensitive information, but also when they are in viewing proximity of it.

A person is in viewing proximity when they are close enough that a camera-capable device could reasonably capture, magnify, scan, record, buffer, transmit, or process information from:

• An ID card.

• A driver’s licence.

• A health card.

• A passport.

• A credit card.

• A debit card.

• A phone screen.

• A paper document.

• A payment terminal.

• A government form.

• A medical document.

• A legal document.

• A customer file.

• A personnel file.

• A student file.

• A delivery record.

• A rental application.

• An employment application.

• A benefits application.

• Any document containing sensitive information.

This applies even if the person claims they did not personally look at the information.

If a camera-capable device could capture the information, the duty exists.

8. Business and Employer Duties

Any business, public body, non-profit, contractor, venue, institution, or organization whose workers interact with sensitive information must establish a written policy governing camera-capable wearable technology.

That policy must include:

• A ban on personal smart glasses or similar recording devices in sensitive information areas.

• Clear signage where recording-capable devices are used.

• A requirement that customers, clients, patients, students, applicants, tenants, employees, or members of the public be informed before sensitive information is exposed.

• A non-recording alternative for identity verification or payment processing.

• A process for immediate complaint and review.

• A requirement to delete any unauthorized capture immediately.

• A requirement to report privacy breaches to the affected person and the appropriate privacy authority.

• Disciplinary consequences for employees or contractors who violate the policy.

• A ban on using captured sensitive information for AI training, facial recognition, marketing, analytics, profiling, resale, or unrelated business purposes.

• A requirement that workers be trained on the privacy risks of wearable camera technology.

• A requirement that managers actively enforce the policy.

Employers may not avoid responsibility by claiming that a device belonged to a worker personally.

If a business allows, ignores, encourages, or fails to prevent the use of camera-capable wearable technology in sensitive information settings, the business is responsible for resulting privacy violations.

9. No Consent by Entry

Consent must not be assumed simply because a person enters a venue, store, office, workplace, school, clinic, hotel, bar, restaurant, government office, event, service counter, or public facility.

General signage stating “recording may occur” is not sufficient consent for the capture of IDs, payment cards, medical documents, immigration documents, banking documents, employment documents, legal documents, or other sensitive information.

Consent must be specific, informed, voluntary, and connected to the immediate purpose for which the information is being provided.

A person must be told when camera-capable wearable technology is being used before they are asked to expose sensitive information.

Share

10. Right to a Non-Recording Alternative

A person must have the right to request that camera-capable wearable technology be removed, disabled, covered, turned away, placed out of view, or replaced before they present sensitive information.

A person must not be denied service, entry, employment consideration, housing consideration, medical assistance, education access, public service access, financial service access, or the ability to complete a lawful transaction solely because they object to unnecessary recording or potential recording of their sensitive information.

Exceptions may apply only where recording is specifically required by law, court order, or established public safety regulation.

Third-Party Recording Risk in Sensitive Information Areas

Where an organization requires, requests, or permits a person to expose sensitive information, the organization has a duty to take reasonable steps to prevent unauthorized capture of that information by third parties present in the same area.

This includes other customers, patrons, visitors, applicants, patients, students, tenants, contractors, bystanders, delivery workers, service providers, or members of the public who are wearing or using camera-capable technology.

An organization must not treat the risk of third-party recording as outside its responsibility where the organization has created, required, or controlled the setting in which sensitive information is exposed.

Organizations must establish privacy-protected areas for the handling, viewing, scanning, verification, payment, signing, or presentation of sensitive information. These areas must be designed or managed to reduce the risk that sensitive information can be captured by unrelated individuals.

Reasonable safeguards may include:

• Positioning service counters so IDs, payment cards, documents, and screens are not visible to others.

• Providing privacy screens, document shields, or payment shields.

• Creating separate verification areas.

• Creating distance between lineups and counters where sensitive information is handled.

• Prohibiting camera-capable wearable technology in sensitive information zones.

• Requiring smart glasses or similar devices to be removed, covered, turned away, or disabled before entering sensitive information areas.

• Allowing people to request a more private location before presenting sensitive documents.

• Training staff to recognize and respond when third parties may be recording sensitive information.

• Posting clear notices that recording IDs, payment cards, documents, screens, signatures, or another person’s sensitive information is prohibited.

Where a person reports that another individual may be using camera-capable technology to capture sensitive information, the organization must take reasonable steps to respond immediately. This may include pausing the transaction, shielding the information, moving the person to a private area, asking the third party to stop recording, requiring the third party to move away, or refusing service to a person who continues to create a privacy risk.

An organization shall not be liable for every unforeseeable act by an unrelated person, but it may be liable where the risk was reasonably foreseeable and no meaningful safeguards were provided.

The presence of camera-capable wearable technology in an area where sensitive information is routinely exposed shall be considered a foreseeable privacy risk.

11. High-Risk Settings

This policy should apply with heightened restrictions in settings where sensitive information is commonly exposed.

These include, but are not limited to:

• Bars, clubs, and age-restricted venues checking ID.

• Liquor and cannabis retailers.

• Hotels and short-term rentals.

• Banks and financial institutions.

• Government service offices.

• Medical clinics and hospitals.

• Pharmacies.

• Schools and post-secondary institutions.

• Child care facilities.

• Employment and hiring offices.

• Landlord and tenant offices.

• Car rental agencies.

• Insurance offices.

• Courthouses and legal offices.

• Security checkpoints.

• Retail counters where payment cards are handled.

• Restaurants, bars, and service counters where payment cards are handed to staff.

• Delivery and courier services handling identity or signature documents.

• Public benefits offices.

• Immigration, citizenship, and licensing offices.

• Any workplace where customer, client, patient, student, employee, or applicant records are visible.

In high-risk settings, camera-capable wearable technology should be prohibited unless expressly authorized, necessary, disclosed, and subject to strict oversight.

12. AI, Facial Recognition, and Automated Analysis Ban

Sensitive information captured through camera-capable wearable technology must not be processed through:

• Artificial intelligence systems.

• Facial recognition tools.

• Optical character recognition systems.

• Biometric identification systems.

• Behavioural profiling systems.

• Marketing analytics systems.

• Customer scoring systems.

• Employment screening systems.

• Immigration or citizenship profiling tools.

• Insurance risk tools.

• Predictive policing systems.

• Automated decision-making systems.

• Law enforcement databases, unless required by law.

No sensitive information captured in these settings may be used to train, fine-tune, test, improve, evaluate, or develop AI systems.

The prohibition applies even where the information was captured incidentally, temporarily, passively, or unintentionally.

13. Data Retention and Deletion

Where recording is legally permitted and necessary, only the minimum amount of information required may be captured.

Organizations must establish:

• A clear retention period.

• A deletion schedule.

• Access logs.

• Encryption requirements.

• Limits on who may view the data.

• A ban on copying data to personal devices.

• A ban on uploading data to unauthorized third-party services.

• A process for affected individuals to request access, correction, and deletion.

• A process to verify that deletion has occurred.

• A process to report unauthorized access, capture, transmission, or retention.

Unauthorized recordings must be deleted immediately, but deletion does not erase the violation.

The fact that data was later deleted does not remove responsibility for the original unauthorized capture.

14. Personal Devices

Employees, contractors, security staff, venue staff, delivery workers, clerks, servers, cashiers, receptionists, inspectors, health workers, government workers, and other workers must not use personal camera-capable wearable technology while performing duties that involve sensitive information.

This includes personal smart glasses, body cameras, wearable AI devices, camera-enabled earbuds, hidden cameras, and any other recording-capable device worn on the body.

Employers may not avoid responsibility by claiming the device was not owned, issued, or controlled by the organization.

If a worker uses a personal device in a sensitive information setting, the worker may be personally liable and the organization may also be liable if it failed to prevent or address the conduct.

15. Public Notice Requirement

Where camera-capable wearable technology is used in a setting open to the public, the organization must provide clear notice before sensitive information is requested.

The notice must state:

• What device is being used.

• Whether it can record.

• Whether it is recording.

• Whether it can capture information in the background.

• What information may be captured.

• Why the capture is necessary.

• How long the information will be retained.

• Who can access it.

• Whether it will be shared with any third party.

• Whether it will be processed by AI, facial recognition, OCR, analytics, or cloud services.

• How the person may request a non-recording alternative.

A small indicator light, icon, sound, or manufacturer-provided signal is not sufficient notice.

16. Tampering With, Disabling, or Concealing Recording Indicators

Any person, business, employer, contractor, device manufacturer, software provider, or third-party service provider who disables, removes, covers, alters, bypasses, masks, suppresses, or otherwise interferes with a recording indicator on camera-capable wearable technology shall be subject to enhanced penalties.

For the purposes of this policy, a recording indicator includes any light, sound, icon, screen notice, haptic alert, software notification, system message, device signal, or other feature intended to notify nearby people that image, video, audio, biometric, document, or data capture is occurring.

It shall be a serious violation to:

• Disable a recording light.

• Cover or obscure a recording light.

• Modify software to prevent a recording indicator from activating.

• Use third-party software to suppress a recording notice.

• Use hardware modifications to conceal recording.

• Use a device whose recording indicator is known to be inaccurate, unreliable, disabled, or misleading.

• Market, sell, distribute, or promote tools designed to defeat recording indicators.

• Require, encourage, or knowingly permit workers to use devices with disabled or concealed recording indicators.

• Continue using a device after becoming aware that its recording indicators are inaccurate, unreliable, disabled, concealed, or misleading.

Where a recording indicator has been disabled, concealed, bypassed, suppressed, or made misleading, any recording or capture of sensitive information shall be presumed to be intentional unless the person or organization responsible can prove otherwise.

Penalties for this violation shall be significantly higher than ordinary privacy violations and may include:

• Mandatory breach notification to all affected individuals.

• Statutory damages without requiring proof of financial loss.

• Administrative fines against both the individual operator and the responsible organization.

• Suspension or cancellation of business, security, liquor, cannabis, professional, or operating licences where applicable.

• Civil liability for any resulting harm.

• Personal liability for managers or supervisors who authorized, ignored, or failed to prevent the conduct.

• Prohibition from using camera-capable wearable technology in sensitive information settings.

• Referral for criminal investigation where fraud, identity theft, stalking, harassment, extortion, voyeurism, blackmail, or intentional concealment is involved.

A manufacturer’s default design, software setting, or device limitation shall not be a defence if the organization knowingly deploys the device in a setting where sensitive information is likely to be visible.

17. Passive, Background, or Undisclosed Capture by Device Systems or Software

No camera-capable wearable technology, software system, operating system, application, cloud service, artificial intelligence tool, analytics platform, or third-party service may capture, buffer, store, transmit, analyze, index, scan, interpret, or retain images, video, audio, biometric information, payment information, text, or document information from sensitive information settings unless the operator has knowingly activated recording and the affected person has been provided with clear notice where required by this policy.

This clause applies even where the human operator did not manually press record.

A system shall be considered to have captured information if it:

• Temporarily buffers images, video, or audio.

• Stores pre-recording footage.

• Captures images for AI analysis.

• Scans text, numbers, faces, cards, documents, screens, barcodes, QR codes, or payment terminals in the background.

• Uploads visual, audio, biometric, text, or document data to a cloud service.

• Creates thumbnails, metadata, transcripts, OCR outputs, facial templates, object recognition data, searchable records, or machine-readable records.

• Uses “always-on,” “wake-word,” “context awareness,” “scene understanding,” “memory,” “assistant,” “safety,” “quality improvement,” or similar features to process information in the background.

• Retains information after the operator believes the device is inactive.

• Makes sensitive information available to the device manufacturer, software provider, employer, advertiser, AI model, analytics vendor, or any third party.

The fact that the operator did not knowingly activate recording shall not excuse the business, employer, manufacturer, software provider, or service provider if the device or system was designed, configured, or permitted to capture information in the background.

Any device or software used in sensitive information settings must be configured so that:

• Recording is off by default.

• Background image, video, audio, biometric, OCR, and AI processing are disabled.

• Pre-recording buffers are disabled.

• Cloud syncing is disabled unless legally required and disclosed.

• No sensitive information is retained without express lawful authority.

• The operator and affected person can clearly determine when capture is occurring.

• The device cannot silently collect sensitive information while appearing inactive.

• The device cannot process sensitive information through AI, OCR, facial recognition, biometric analysis, or analytics tools without lawful authority and clear notice.

A violation of this clause shall be treated as a serious privacy breach, whether or not the captured information was later viewed by a human being.

Enhanced penalties shall apply where a manufacturer, software provider, employer, or organization knew or ought to have known that the technology could capture sensitive information without active recording by the operator.

18. Manufacturer and Software Provider Responsibility

Manufacturers, software providers, app developers, cloud service providers, AI system providers, and third-party technology vendors must not design, sell, license, deploy, or enable camera-capable wearable technology for use in sensitive information settings unless the technology includes meaningful privacy protections.

These protections must include:

• Recording indicators that cannot be disabled by ordinary users.

• Clear notice when recording, capture, scanning, buffering, or AI processing is occurring.

• Default settings that prevent background capture.

• Controls to disable cloud uploads.

• Controls to disable AI analysis.

• Controls to disable OCR and document scanning.

• Audit logs where capture is legally permitted.

• Security protections against unauthorized access.

• Clear documentation of what the device captures, stores, transmits, or analyzes.

• A means for organizations to verify that recording and background capture features are disabled.

A manufacturer or software provider may be liable where its design, default settings, marketing, or lack of safeguards makes unauthorized capture of sensitive information reasonably foreseeable.

19. Anti-Retaliation Clause

No person may be punished, refused service, removed, reported, denied entry, denied employment consideration, denied housing consideration, denied medical assistance, denied education access, denied government service, or treated adversely for asking that camera-capable technology not be used while their sensitive information is visible.

A person may also not be punished for asking whether a device is recording, whether it can record, whether it captures information in the background, whether information is stored, or whether a non-recording alternative is available.

20. Public Sector Standard

Government bodies and publicly funded organizations must meet the highest standard under this policy.

No public body may require a person to expose sensitive documents to camera-capable wearable technology unless the collection is expressly authorized, necessary, proportionate, disclosed, and subject to independent privacy oversight.

Public bodies must also ensure that contractors, security firms, service providers, technology vendors, and third-party operators comply with this policy.

Public bodies must not use camera-capable wearable technology to capture, analyze, or retain information related to citizenship, immigration status, health status, disability, income support, employment status, education status, housing status, or identity documents unless expressly authorized by law.

21. Enforcement

Violations may result in:

• Mandatory deletion of captured information.

• Written notice to affected individuals.

• Mandatory breach reporting.

• Administrative fines.

• Statutory damages without requiring proof of financial loss.

• Suspension of licences or permits.

• Civil liability.

• Personal liability for individuals who intentionally capture or misuse sensitive information.

• Organizational liability for employers who fail to prevent, investigate, or report violations.

• Enhanced penalties where information is used for fraud, harassment, discrimination, surveillance, AI training, resale, identity theft, profiling, blackmail, or intimidation.

• Enhanced penalties where recording indicators are disabled, concealed, bypassed, or made misleading.

• Enhanced penalties where devices or software capture sensitive information in the background without active recording by the operator.

• Referral to law enforcement where conduct may constitute a criminal offence.

Penalties should be significant enough that unauthorized capture of sensitive information is not treated as a minor cost of doing business.

22. Complaint and Investigation Rights

Any person who believes their sensitive information may have been captured by camera-capable wearable technology must have the right to file a complaint with the responsible organization and the appropriate privacy authority.

The organization must provide:

• Confirmation of whether camera-capable technology was in use.

• Confirmation of whether the device was capable of recording.

• Confirmation of whether recording, buffering, scanning, AI processing, or cloud transmission occurred.

• The identity of the organization responsible for the device.

• The retention period for any captured information.

• The steps taken to delete or secure the information.

• The names or categories of third parties who had access to the information.

• The steps taken to prevent recurrence.

Failure to provide this information shall be treated as a separate violation.

23. Minimum Safeguards for Lawful Use

Where camera-capable wearable technology is lawfully used in sensitive information settings, the following minimum safeguards must apply:

• The device must be issued or approved by the organization.

• The device must be configured to minimize capture.

• Personal devices must be prohibited.

• Recording must be off by default.

• Background capture must be disabled.

• AI processing must be disabled unless expressly authorized.

• Cloud syncing must be disabled unless expressly required and disclosed.

• Recording indicators must remain visible and functional.

• Workers must be trained.

• Access must be logged.

• Retention must be limited.

• Deletion must be verifiable.

• Complaints must be investigated.

• Breaches must be reported.

If these safeguards cannot be met, the technology must not be used in that setting.

24. Review and Updating

Because camera, wearable, biometric, payment, document-scanning, and AI technologies are changing rapidly, this policy must be reviewed at least every two years.

The review must consider:

• New wearable devices.

• Facial recognition technology.

• AI document scanning.

• Payment card capture risks.

• Identity theft risks.

• Background capture functions.

• Recording indicator reliability.

• Smart glasses and augmented reality systems.

• Privacy commissioner findings.

• Public complaints.

• Enforcement outcomes.

• Whether additional technologies should be restricted.

• Whether penalties are sufficient to deter violations.

25. Plain-Language Summary

If someone is checking your ID, handling your bank card, looking at your credit card, reviewing your medical forms, scanning your documents, or standing close enough to capture that information, they should not be wearing smart glasses or similar camera-capable technology unless there is a clear legal reason, clear notice, strict safeguards, and a non-recording option.

The public should not have to guess whether their ID, health card, citizenship status, bank card, signature, address, private documents, or financial information is being silently recorded.

Disabling a recording light, hiding a recording signal, or using software that captures images in the background should be treated as a serious privacy violation, not a technical mistake.

Sensitive information should not be captured just because technology now makes it easy to capture.

Note on Companion Legislation

This proposal is not intended to stand alone.

The Camera-Capable Wearable Technology and Sensitive Information Protection Act focuses primarily on organizations, businesses, public bodies, employers, contractors, institutions, and controlled settings where people are required or expected to expose sensitive information.

A companion policy should also be developed: the Public Use of Camera-Capable Wearable Technology and Personal Data Protection Act.

That companion policy would address the broader public use of camera-capable wearable technology by individuals who are not acting on behalf of a business, employer, government body, or organization.

It would deal with issues such as:

• Random individuals recording IDs, bank cards, documents, or screens.

• People wearing smart glasses in lineups, waiting rooms, bars, clinics, schools, government offices, voting places, banks, airports, and other public or semi-public spaces.

• Capturing children, vulnerable people, victims, patients, or people accessing social supports.

• Recording documents, cards, screens, or forms held by someone else.

• Uploading images of strangers’ documents, cards, faces, or personal information to AI tools.

• Bystander liability for capturing or sharing another person’s sensitive information.

• Concealed recording in public and semi-public spaces.

• Civil penalties even when the person responsible is not attached to a business, employer, government body, or organization.

Together, these two policies would recognize that sensitive information can now be captured not only by institutions, but also by ordinary individuals using increasingly powerful wearable technology.

Privacy protection must apply both to the organizations that require people to expose sensitive information and to the individuals who may exploit that exposure.

It is about the hidden systems behind that price: transportation, warehousing, distribution centres, supplier fees, real estate, loyalty programs, data collection, and the corporate structures that can take profit long before a product reaches the checkout.

Mark Carney’s food affordability strategy points in the right direction by recognizing the need for stronger domestic supply chains, food hubs, and more competition. But if policy only focuses on retail prices and store-level margins, it risks missing the deeper machinery of grocery profit-taking.

This proposal is an attempt to follow the dollar through the entire food chain.

If a product shrinks, consumers should know. If a grocery company profits through related companies before the product reaches the shelf, regulators should know. If loyalty programs are turning shopping data into revenue, customers should know. And if food prices are being shaped by surveillance, profiling, or hidden algorithms, that should not be allowed to happen in the shadows.

Food affordability requires more than competition at the checkout.

It requires transparency from the farm to the table.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The Food Affordability and Grocery Transparency Act

A Policy Proposal for Honest Pricing, Full-Chain Profit Disclosure, and Consumer Data Protection

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

Introduction

Canada does not have a simple grocery-price problem. It has a food-system transparency problem.

When people walk into a grocery store, they see the final price on the shelf. They do not see the full chain of profit-taking that may have happened before the product reached that shelf. They do not see who profited from farming, ranching, processing, transportation, warehousing, distribution, wholesale access, leasing, real estate, supplier fees, data collection, or internal corporate transfers.

A grocery retailer can point to thin margins at the store level while additional profit is captured elsewhere in the same corporate structure. If the same parent company, subsidiary, major shareholder, affiliated company, or related entity earns money from moving, storing, distributing, financing, leasing, supplying, advertising, or analyzing the sale of that product, then the public deserves to know that too.

Food affordability policy cannot stop at the checkout.

This proposal is designed to ensure that Canadians can see when products have been quietly reduced in size, weight, volume, or content; that governments can measure where grocery profit is actually being taken across the entire supply chain; that essential food prices are not personalized through surveillance-based pricing; and that loyalty-program members can see how their data is being collected, shared, and monetized.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement. They are written to be applied at the appropriate government level, federal, provincial, territorial, municipal, or through cooperation between governments where needed. If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

1. Purpose

The purpose of the Food Affordability and Grocery Transparency Act is to:

• Protect consumers from hidden product reductions.

• Require clear public notice when food products shrink in size, weight, volume, or content.

• Prevent companies from avoiding disclosure through cosmetic packaging changes.

• Require grocery retailers to disclose average, mean, and median grocery markups.

• Require full-chain profit reporting where grocery retailers, parent companies, subsidiaries, major shareholders, or affiliated entities collect revenue from other parts of the food supply chain.

• Prohibit surveillance-based pricing for essential food products.

• Require loyalty-program data monetization transparency.

• Give governments, regulators, journalists, researchers, and the public a clearer view of where grocery profits are actually being taken.

• Support fairer competition for independent grocers, producers, processors, and new market entrants.

2. Definitions

For the purposes of this Act:

Grocery retailer means any business that sells food products directly to consumers through physical stores, online platforms, delivery platforms, wholesale clubs, membership programs, marketplace platforms, or any combination of these.

Essential food product means any food or beverage product reasonably understood to be part of regular household food consumption, including fresh food, frozen food, packaged food, prepared food, staple ingredients, infant food, dietary staples, and other products designated by regulation.

Shrinkflation means the reduction of a product’s weight, volume, count, contents, concentration, serving quantity, or usable product amount without clear public disclosure to consumers.

Related entity means any parent company, subsidiary, sister company, joint venture, major shareholder, holding company, affiliated company, real estate investment trust, logistics company, distribution company, warehousing company, supplier company, private-label manufacturer, or company under common control.

Full-chain profit means profit, revenue, fees, rents, charges, or commercial value captured at any stage between production and retail sale, including farming, ranching, processing, packaging, transportation, warehousing, distribution, wholesale access, real estate, leasing, supplier fees, data monetization, advertising, or related services.

Surveillance-based pricing means changing, raising, lowering, personalizing, or targeting the price of a food product based on personal data, behavioural data, inferred income, purchase history, browsing history, location history, device information, loyalty-program activity, household composition, demographic profile, or any other data used to estimate what a specific consumer may be willing or able to pay.

Data monetization means any practice by which a company earns revenue, receives commercial value, improves advertising performance, strengthens supplier negotiations, supports price-setting, builds consumer profiles, or otherwise benefits financially from collecting, analyzing, selling, licensing, sharing, transferring, or using consumer data.

3. Shrinkflation Disclosure Requirement

Any grocery product sold to the public must carry a high-visibility public notice if, within the previous six months, the product has been reduced in:

• Weight.

• Volume.

• Item count.

• Package contents.

• Serving quantity.

• Concentration.

• Usable product amount.

• Any other measurable quantity that reduces what the consumer receives.

This requirement would apply whether the shelf price changes or not.

If a product becomes smaller, lighter, less concentrated, or contains fewer usable servings, the disclosure requirement would apply.

4. High-Visibility Counter, Shelf, and Online Signage

When a product has been reduced in quantity, the retailer must display a clear notice at the point of sale.

This notice must be:

• Placed directly beside or beneath the product price.

• Easy to read from a normal shopping distance.

• Written in plain language.

• Displayed for no less than six months after the reduced product is introduced.

• Included in online grocery listings, flyers, digital ads, delivery platforms, and app-based shopping platforms.

The notice should use plain language such as:

Product Size Reduced

This product has been reduced from [previous size / count / volume / weight] to [new size / count / volume / weight] within the last six months.

The notice should not be required to include previous or current prices, because prices may vary due to sales, promotions, regional pricing, loyalty programs, or temporary discounts. The purpose of the notice is to disclose the reduction in product quantity, not to create a separate price-tracking burden at the shelf level.

The purpose is not to ban companies from changing product sizes. The purpose is to ensure consumers are not left with the reasonable expectation that they are receiving the same amount of product when the amount has been reduced, whether the product appears in similar packaging, refreshed packaging, renamed packaging, or any other presentation that a reasonable consumer would understand as a continuation of the same or substantially similar product.

5. Anti-Avoidance Packaging Clause

A manufacturer, distributor, supplier, or retailer may not avoid the shrinkflation disclosure requirement by changing packaging, branding, product names, barcodes, container shape, label design, product line classification, or marketing language.

A product would still be considered the same or substantially similar product if it has the same or substantially similar:

• Brand.

• Product type.

• Ingredients.

• Use.

• Flavour or variety.

• Target consumer.

• Retail placement.

• Marketing identity.

• Packaging appearance.

• Consumer expectation.

For example, a company could not avoid disclosure by changing a “500 g family-size cereal” into a “450 g resealable cereal pouch” if consumers would reasonably understand it to be the same or substantially similar product.

The disclosure requirement should follow the product, not the packaging trick.

6. Grocery Markup Reporting

Large grocery retailers must report the average, mean, and median grocery markup across food products sold in their stores and through their online platforms.

This reporting must include:

• Product category.

• Retail price.

• Supplier price.

• Wholesale price, where applicable.

• Retail markup.

• Average markup by category.

• Mean markup by category.

• Median markup by category.

• Changes in markup over time.

• Regional variation in markup.

• Differences between regular pricing, promotional pricing, and loyalty-card pricing.

Reports should be filed regularly with the appropriate regulator and summarized publicly in a format that consumers can understand.

The public version does not need to expose legitimate trade secrets on every individual contract, but it must provide enough information to show whether grocery markups are rising, falling, or being shifted between categories.

7. Full-Chain Profit Disclosure

Grocery profit reporting must include more than store-level retail margin.

Where a grocery retailer, parent company, subsidiary, major shareholder, affiliated company, related entity, or commonly controlled business collects revenue directly or indirectly from a product’s journey to the shelf, that revenue must be disclosed as part of the full-chain grocery profit calculation.

This includes revenue collected from:

• Farming.

• Ranching.

• Food production.

• Food processing.

• Packaging.

• Transportation.

• Trucking.

• Rail access.

• Cold storage.

• Warehousing.

• Distribution centres.

• Wholesale supply.

• Importing.

• Exporting.

• Supplier fees.

• Listing fees.

• Promotional fees.

• Shelf-placement fees.

• Data fees.

• Penalties charged to suppliers.

• Real estate.

• Leasing.

• Property management.

• Financing.

• Insurance.

• Advertising.

• Loyalty-program data use.

• Any other related business activity connected to bringing the product to market.

If a grocery corporation profits from the product before it reaches the store, that profit must not disappear from public view.

Share

8. Related-Entity Disclosure

A grocery retailer must disclose when any part of the food supply chain involves a related entity.

A related entity would include:

• Parent companies.

• Subsidiaries.

• Sister companies.

• Joint ventures.

• Major shareholders.

• Holding companies.

• Real estate investment trusts.

• Logistics companies.

• Distribution companies.

• Warehousing companies.

• Supplier companies.

• Private-label manufacturers.

• Companies under common control.

• Companies with shared directors or officers.

• Companies where ownership, financing, or control creates a reasonable possibility of indirect profit extraction.

The test should be simple:

If the grocery retailer or its ownership network benefits financially from another part of the chain, it must be disclosed.

9. Full-Chain Grocery Profit Formula

For the purposes of public reporting, grocery profit should be calculated in two ways.

A. Retail Markup

Retail Markup = Shelf Price - Direct Product Acquisition Cost

This shows the narrow store-level markup.

B. Full-Chain Markup

Full-Chain Markup = Shelf Price - Independent Arm’s-Length Cost of Product

This calculation must include any additional revenue captured by related entities through transportation, warehousing, distribution, leasing, real estate, supplier fees, data monetization, advertising, or other supply-chain services.

The goal is to prevent companies from claiming low retail margins while extracting profit from other parts of the system.

A grocery company should not be able to say, “We only made a small profit at the store,” if another part of the same corporate ecosystem made money from transporting, storing, leasing, supplying, advertising, analyzing, or distributing the same product.

10. Prohibition on Surveillance-Based Grocery Pricing

Grocery retailers, online grocery platforms, delivery platforms, and affiliated companies may not use surveillance-based pricing for essential food products.

A grocery retailer may still offer clearly advertised public discounts, coupons, loyalty discounts, flyer prices, clearance prices, regional pricing, or time-limited promotions, provided those prices are available on equal terms to all consumers who meet the publicly stated conditions.

A grocery retailer may not charge different consumers different prices for the same food product at the same location or through the same platform based on personal profiling, algorithmic assessment, behavioural prediction, or inferred willingness to pay.

Food pricing should be transparent. A shopper should not have to wonder whether the price they see is based on the product, or based on what a company thinks it knows about them.

11. Loyalty Program Data Monetization Transparency

Any grocery retailer or affiliated company operating a loyalty program must provide members with a clear, accessible data monetization statement.

This statement must show, in plain language:

• What personal, household, purchase, behavioural, location, device, or demographic data is collected.

• Whether that data is sold, licensed, shared, transferred, pooled, analyzed, used for advertising, used for price targeting, or monetized in any other way.

• Which categories of companies, advertisers, brokers, suppliers, platforms, or affiliated entities receive or use the data.

• Whether the data is shared with parent companies, subsidiaries, major shareholders, advertising networks, data brokers, financial partners, insurers, landlords, logistics companies, suppliers, or other commercial partners.

• The estimated revenue, value, or commercial benefit the company received from selling, licensing, sharing, or monetizing loyalty-program data.

• The estimated value of points, discounts, or rewards returned to the consumer.

• A comparison between the commercial value extracted from the consumer’s data and the value returned to the consumer through the loyalty program.

Where technically possible, this information should appear directly beside the consumer’s loyalty points balance in the retailer’s app, online account, or printed account summary.

For example:

Points earned this year: [X]
Estimated value of rewards received: [$X]
Estimated value generated from your data: [$X]
Your data was shared with: [categories / named entities where required]

Consumers must also have the right to request a list of the companies, affiliates, brokers, advertisers, or partners with whom their loyalty-program data was sold, licensed, shared, transferred, or otherwise monetized.

A loyalty program should not operate as a one-way mirror. If consumers are being paid in points while companies profit from their data, consumers deserve to see both sides of the exchange.

12. Loyalty Program Non-Discrimination

Consumers must not be penalized for refusing unnecessary data collection.

Where a grocery retailer offers loyalty pricing on essential food products, the retailer must provide a privacy-protective way for consumers to access the same essential food discounts without being required to consent to broad data collection, tracking, profiling, third-party sharing, or data monetization.

This could include:

• A privacy-protective loyalty option.

• A non-tracking discount card.

• An in-store discount code.

• A publicly available flyer price.

• A limited-data account that collects only what is necessary to administer the discount.

Access to affordable food should not require surrendering personal data beyond what is necessary for the transaction.

13. Public Reporting Dashboard

Governments should create a public food affordability transparency dashboard that reports:

• Average grocery markup by retailer.

• Mean grocery markup by retailer.

• Median grocery markup by retailer.

• Markup by product category.

• Full-chain markup estimates.

• Shrinkflation notices by product.

• Product-size reductions by brand.

• Regional grocery price differences.

• Reported supplier fees.

• Known property controls or restrictive leases.

• Related-entity supply-chain relationships.

• Use of loyalty-program data.

• Data monetization practices.

• Surveillance-based pricing complaints.

• Enforcement actions.

• Penalties issued.

• Corrective orders.

The dashboard should be searchable by product, retailer, brand, category, region, and date.

Consumers should not need a business degree to understand why food is becoming unaffordable.

14. Independent Grocer Protection

Independent grocers should not be forced to compete against vertically integrated giants without transparency into the structures that shape their costs.

Where a dominant grocery retailer also controls or benefits from transportation, warehousing, distribution, wholesale access, retail property, supplier fees, loyalty-data systems, or advertising infrastructure, regulators should assess whether that structure creates unfair barriers for independent grocers.

This review should consider:

• Whether independents are paying higher supply-chain costs.

• Whether access to distribution is being restricted.

• Whether warehouse access is being used to favour related stores.

• Whether transportation pricing disadvantages competitors.

• Whether lease controls prevent new grocery stores from opening.

• Whether supplier terms favour dominant chains.

• Whether private-label products are being used to pressure suppliers or crowd out competitors.

• Whether data advantages are being used to distort competition.

• Whether loyalty programs are locking consumers into dominant retailers.

Competition at the checkout is not enough if competitors cannot affordably reach the checkout.

15. Property Control and Lease Transparency

Grocery retailers must disclose any property control, restrictive covenant, exclusivity clause, lease condition, or related real estate agreement that limits or prevents another grocery retailer, food market, co-operative, independent grocer, farmers’ market, or food retailer from operating nearby.

This includes restrictions created through:

• Lease agreements.

• Landlord agreements.

• Shopping centre rules.

• Sale conditions.

• Development agreements.

• Real estate subsidiaries.

• Holding companies.

• Property management firms.

• Related corporate entities.

Governments should have the authority to review and prohibit property controls that reduce food competition in a community.

No company should be allowed to claim it supports grocery competition while using real estate contracts to keep competitors out.

16. Application to Online Grocery Platforms

The same rules must apply to online grocery platforms, delivery apps, digital flyers, loyalty apps, and third-party grocery marketplaces.

If a product has been reduced in size, the disclosure must appear clearly before purchase.

If prices vary based on loyalty programs, user profiles, dynamic pricing, location, or platform fees, those differences must be included in public reporting.

If an online platform uses consumer data to personalize offers, sort products, target promotions, alter visibility, or influence food purchasing behaviour, those practices must be disclosed.

A disclosure requirement that only applies in physical stores would be incomplete.

17. Audits and Verification

Large grocery retailers and affiliated companies must be subject to independent audits to verify:

• Shrinkflation disclosures.

• Product-size change histories.

• Grocery markup reports.

• Full-chain profit disclosures.

• Related-entity transactions.

• Supplier fees.

• Lease and real estate arrangements.

• Loyalty-program data monetization statements.

• Compliance with the ban on surveillance-based pricing.

• Public dashboard accuracy.

Auditors must have access to the documents needed to verify whether reported margins reflect the true flow of money across the supply chain.

Companies should not be allowed to self-report only the parts of the system that make them look restrained.

18. Enforcement

The Act should be enforced by the appropriate competition, consumer protection, privacy, food pricing, or market transparency regulator.

Enforcement tools should include:

• Mandatory reporting orders.

• Public correction notices.

• Administrative penalties.

• Fines based on company revenue.

• Product-specific disclosure orders.

• Lease and property-control disclosure orders.

• Data monetization disclosure orders.

• Independent audits.

• Whistleblower protections.

• Penalties for false, incomplete, or misleading reporting.

• Penalties for avoiding disclosure through packaging changes.

• Penalties for surveillance-based pricing of essential food products.

• Referral for competition or privacy investigation where unlawful or anti-competitive conduct is suspected.

Penalties must be large enough that non-compliance is not simply treated as a cost of doing business.

19. Whistleblower Protection

Employees, suppliers, truckers, warehouse workers, franchisees, landlords, contractors, data workers, software developers, advertisers, and others involved in the food supply chain must be protected when reporting hidden markups, undisclosed related-party transactions, shrinkflation avoidance, supplier pressure, data monetization practices, surveillance-based pricing, or anti-competitive conduct.

Whistleblower protections should include:

• Confidential reporting channels.

• Protection against retaliation.

• Protection against contract termination.

• Protection against blacklisting.

• Protection against legal intimidation.

• Financial penalties for retaliation.

• Public reporting on the number and type of complaints received.

The people closest to the system often know where the profit is being hidden.

20. Review Period

The Act should be reviewed after three years to assess whether:

• Shrinkflation disclosures are improving consumer awareness.

• Product-size reductions have become less deceptive.

• Grocery markup reporting is accurate and useful.

• Full-chain profit reporting is exposing hidden profit-taking.

• Surveillance-based pricing has been prevented.

• Loyalty-program data monetization is being clearly reported.

• Consumers are receiving fair value for loyalty-program participation.

• Independent grocers are gaining fairer access to supply chains.

• Property controls are being reduced.

• Food affordability is improving.

• Additional anti-competition, privacy, or pricing measures are required.

Food systems change quickly. The law must be reviewed regularly enough to keep up.

Conclusion

Food affordability is not only about the price on the shelf.

It is about who controls the farm, the processor, the truck, the warehouse, the distribution centre, the lease, the property, the supplier relationship, the data, the fees, the loyalty program, the algorithm, and the store.

If governments only look at retail grocery margins, they will miss the hidden layers where profit can be taken before the product ever reaches the checkout.

If a product shrinks, consumers should know.

If a grocery company profits from multiple stages of the food chain, the public should know.

If loyalty programs collect and monetize consumer data, consumers should know.

If food prices are being shaped by surveillance, profiling, or hidden algorithms, regulators should know.

If real competition is blocked by ownership structures, leases, supplier fees, data advantages, or distribution control, governments should know.

Canada does not just need more grocery competition.

Canada needs grocery transparency from the farm to the table, from the warehouse to the lease, and from the loyalty card to the checkout.

A project is announced, a subsidy is justified, a ribbon is cut, and the public is told that hundreds or thousands of jobs will be created. But too often, that number hides more than it reveals.

Are those jobs temporary or long-term? Full-time or part-time? Local or imported? Direct or estimated? Do they pay enough for workers to live in the region where the project is being built?

This proposal is about making job creation claims honest.

The Honest Jobs Reporting Act would require governments to report job numbers in a clear public format: short-term positions, long-term positions, and living-wage long-term full-time-equivalent jobs.

Because “1,000 jobs” means very little if only a few dozen remain after construction, and even less if those jobs do not pay enough for people to live where they work.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement. They are written to be applied at the appropriate level of government, whether federal, provincial, or municipal. In some cases, they may work best when integrated across multiple levels. In all cases, cooperation between levels of government would be in the public interest.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The Honest Jobs Reporting Act

A Public Job Creation Reporting Standard

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

1. Purpose

Governments frequently announce job creation numbers connected to new developments, public subsidies, infrastructure projects, industrial approvals, corporate investments, and economic development programs.

Too often, those numbers are presented in ways that are more promotional than factual.

A project may be described as creating “1,000 jobs” even if most of those jobs are temporary construction jobs, short-term launch jobs, indirect estimates, part-time positions, contractor positions, or jobs that do not pay enough for workers to live in the region where the project is located.

The public deserves better than headline numbers that hide the real employment impact.

The purpose of this policy is to create a clear, standardized, and publicly verifiable method for reporting job creation numbers at all levels of government.

Governments should not be allowed to claim jobs without clearly disclosing what kind of jobs they are.

2. Core Principle

A job creation number should not be treated as meaningful unless the public can understand:

• How many jobs are temporary.

• How many jobs are long-term.

• How many jobs are full-time.

• How many jobs are part-time.

• How many jobs are direct.

• How many jobs are indirect, induced, or estimated.

• How many jobs pay at or above the regional cost-of-living wage.

• How long the jobs are expected to last.

• Whether public money, tax incentives, discounted land, utility subsidies, loan guarantees, or infrastructure supports are being used to create them.

The most important number is not the largest number.

The most important number is the number of long-term, full-time-equivalent jobs that pay enough for workers to live in the region where the project is located.

3. Application

This policy should apply to any job creation claim made by:

• Federal governments.

• Provincial, state, territorial, or regional governments.

• Municipal governments.

• Public agencies.

• Economic development authorities.

• Crown corporations or publicly owned entities.

• Public-private partnerships.

• Government-supported investment offices.

It should apply whenever job creation numbers are used in relation to:

• Project approvals.

• Public subsidies.

• Tax incentives.

• Land sales or leases.

• Infrastructure commitments.

• Utility approvals.

• Rezoning.

• Environmental assessment.

• Procurement.

• Economic development announcements.

• Public funding agreements.

• Loan guarantees.

• Public benefit claims.

This policy is intended to be adaptable to the appropriate level of government. In some cases, it would work best federally. In others, it would be most effective at the provincial, state, territorial, regional, or municipal level. In many cases, the strongest version would involve cooperation between multiple levels of government.

4. Existing Practice and the Policy Gap

Full-time-equivalent reporting already exists in many government, statistical, grant, and program contexts.

The issue is not that governments are incapable of reporting jobs more accurately.

The issue is that public announcements do not consistently require that accuracy.

A government may use careful job definitions inside an application form, funding agreement, or internal report, while still allowing public-facing announcements to use broad, inflated, or incomplete job claims.

This policy would close that gap.

It would require the same honesty expected in internal reporting to appear in public-facing job claims, media releases, subsidy announcements, project summaries, approval notices, and political communication.

5. Standard Public Job Reporting Label

To prevent job creation claims from being inflated, shortened, or selectively reported, every government job creation announcement must include a standard public job reporting label.

The required format is:

Jobs Reported: Short-Term / Long-Term / Living-Wage Long-Term FTE

For example:

Jobs Reported: 1,200 short-term positions / 85 long-term positions / 36 living-wage long-term FTE

This three-part label must appear in the first public-facing summary of the project, including:

• News releases.

• Approval notices.

• Funding announcements.

• Public advertisements.

• Media kits.

• Project webpages.

• Public speeches.

• Social media graphics.

• Government backgrounders.

• Legislative or council briefings.

The three numbers must appear together wherever possible.

A government may not report only the largest number if the smaller long-term or living-wage long-term number is known or reasonably estimable.

6. Definitions

Short-Term Positions

Short-term positions include jobs connected to construction, launch, commissioning, site preparation, installation, testing, buildout, and other temporary project phases.

These jobs are real work and should be reported.

However, they must not be presented as permanent employment.

Short-term jobs must be reported with their expected duration.

Long-Term Positions

Long-term positions are jobs expected to continue after the project reaches stable operation.

Long-term positions may include full-time, part-time, seasonal, or ongoing contract positions, but they must be clearly identified by type.

Long-term positions should not include construction jobs, launch jobs, temporary installation jobs, or indirect economic estimates.

Living-Wage Long-Term FTE

Living-wage long-term FTE means the number of long-term full-time-equivalent jobs that pay at or above the regional cost-of-living wage.

This should be the primary public accountability number.

It measures not only whether a project creates work, but whether that work is stable and pays enough for workers to live in the region where the project is located.

7. Full-Time and Part-Time Job Reporting

This policy does not exclude part-time jobs from job creation reporting .

Part-time jobs are real work and should be reported.

However, part-time positions must not be used to inflate public job creation claims.

Have a look at

The Case for Equal Treatment for Part-Time Workers

Governments must report both:

• The number of positions created.

• The number of full-time-equivalent jobs created.

A full-time-equivalent job, or FTE, measures the actual amount of work created rather than only the number of people employed.

For example:

• One full-time job equals 1.0 FTE.

• Two half-time jobs equal 1.0 FTE.

• Four quarter-time jobs equal 1.0 FTE.

• A full-time job lasting six months equals 0.5 annual FTE.

• A part-time job lasting six months equals the appropriate fraction of annual FTE.

This prevents governments from announcing ten part-time jobs as though they provide the same employment benefit as ten full-time jobs.

8. Standard Formula

Every project must report job creation using the following standardized categories.

A. Total Announced Positions

This is the broadest number and may include construction, launch, direct, indirect, induced, temporary, part-time, and estimated jobs.

This number may be published, but it must not be used as the primary headline number unless all categories are shown beside it.

B. Short-Term Positions

Short-Term Positions = Construction Positions + Launch Positions + Other Temporary Project Positions

These must be reported with expected duration.

C. Long-Term Direct Positions

Long-Term Direct Positions = Permanent Full-Time Positions + Permanent Part-Time Positions + Permanent Seasonal Positions + Ongoing Contract Operational Positions

These must be reported separately from temporary project jobs.

D. Long-Term FTE

Long-Term FTE = Total Annual Hours Worked in Long-Term Positions / Standard Full-Time Annual Hours

This converts full-time, part-time, seasonal, and ongoing contract work into a comparable employment measure.

E. Living-Wage Long-Term Positions

Living-Wage Long-Term Positions = Long-Term Positions Paying At or Above the Regional Cost-of-Living Wage

This shows how many long-term positions actually pay enough for workers to live in the region.

F. Living-Wage Long-Term FTE

Living-Wage Long-Term FTE = Annual Hours Worked in Long-Term Jobs Paying At or Above the Regional Cost-of-Living Wage / Standard Full-Time Annual Hours

This should be the primary public accountability number.

9. Required Public Format

Every public job creation claim must use the following format:

Jobs Reported: [short-term positions] short-term positions / [long-term positions] long-term positions / [living-wage long-term FTE] living-wage long-term FTE

Example:

Jobs Reported: 1,200 short-term positions / 85 long-term positions / 36 living-wage long-term FTE

A government may not announce:

This project will create 1,200 jobs.

If the more accurate statement is:

Jobs Reported: 1,200 short-term positions / 85 long-term positions / 36 living-wage long-term FTE.

The larger number may still be reported, but it must not be allowed to obscure the smaller and more meaningful long-term employment numbers.

10. Construction Job Reporting

Construction jobs are often the largest number attached to a project.

They are also often temporary.

Construction jobs must be reported separately from long-term employment.

Required disclosures:

• Estimated number of construction positions.

• Average expected duration.

• Number of construction FTEs.

• Number expected to be local.

• Number expected to be non-local or rotational.

• Number expected to be unionized, where applicable.

• Number expected to pay at or above the regional cost-of-living wage.

• Whether the jobs are direct, subcontracted, or indirect.

Construction jobs may not be merged with permanent operational jobs in the headline number.

11. Launch and Transition Job Reporting

Some projects create short-term jobs during launch, commissioning, testing, training, or transition into operation.

These jobs must be reported separately.

Required disclosures:

• Estimated number of launch-phase positions.

• Expected duration of the launch phase.

• Number of launch jobs expected to continue into long-term operation.

• Number of launch jobs expected to end after launch.

• Number paying at or above the regional cost-of-living wage.

Launch jobs may not be presented as permanent jobs unless they are expected to continue after the project reaches stable operation.

12. Long-Term Direct Job Reporting

Long-term direct jobs are the jobs that remain after the project reaches stable operation.

Required disclosures:

• Number of permanent full-time positions.

• Number of permanent part-time positions.

• Number of seasonal positions.

• Number of ongoing contract positions.

• Number of temporary recurring positions.

• Total long-term FTE.

• Number of living-wage long-term positions.

• Number of living-wage long-term FTE.

• Number of jobs below the regional cost-of-living wage.

• Number of jobs expected to be local hires.

• Number of jobs expected to require relocation or outside recruitment.

These numbers must be reported separately from construction, launch, indirect, and induced jobs.

13. Indirect and Induced Jobs

Indirect and induced jobs may be reported, but they must never be included in the headline job creation number.

Indirect jobs include supplier, service, maintenance, transportation, and support jobs created outside the direct project workforce.

Induced jobs include jobs estimated to result from worker spending in the broader economy.

Required disclosures:

• Method used to estimate indirect jobs.

• Method used to estimate induced jobs.

• Geographic region used in the calculation.

• Whether the estimate is independently verified.

• Whether the estimate includes jobs displaced from other sectors.

• Whether the estimate includes public-sector jobs created to service the project.

• Whether the estimate is gross or net.

Indirect and induced jobs must be clearly labelled as estimates.

They must not be blended with direct project employment.

14. Regional Cost-of-Living Wage Standard

Every job claim must disclose how many jobs pay at or above the regional cost-of-living wage.

A regional cost-of-living wage should be calculated based on the real cost of living in the community or region where the job is located, including:

• Housing.

• Utilities.

• Food.

• Transportation.

• Child care.

• Health costs not covered publicly.

• Taxes and payroll deductions.

• Basic communications.

• Insurance.

• Debt-neutral household necessities.

• Modest emergency savings.

The regional cost-of-living wage must be updated at least annually.

Where a credible living wage calculation already exists, governments may use that figure. Where no such calculation exists, the government must publish the methodology used.

A job that does not pay enough to live in the region should not be treated as a full public benefit.

15. Job Quality Reporting

Job reporting must include basic job quality measures.

These should include:

• Wage range.

• Median wage.

• Benefits.

• Pension or retirement contributions.

• Paid sick leave.

• Scheduling stability.

• Full-time or part-time status.

• Temporary or permanent status.

• Contractor or employee status.

• Union coverage, where applicable.

• Health and safety risk category.

• Required education, certification, or training.

• Whether training is publicly funded.

• Whether workers can realistically live in the region on the wage offered.

The purpose is not only to count jobs, but to identify what kind of jobs are being created.

16. Local Employment Reporting

Governments must disclose how many jobs are expected to be filled by workers living in the affected region.

Required categories:

• Local workers.

• Regional workers.

• Out-of-region workers.

• Temporary rotational workers.

• Relocated workers.

• Remote workers.

A project should not be presented as a strong local employment benefit if most jobs are expected to be filled from outside the community.

Where local hiring commitments are made, they must be measurable and subject to annual reporting.

17. Displacement and Replacement Rule

Governments must disclose whether claimed jobs are genuinely new or whether they may replace existing jobs.

A job should not be counted as new if it is primarily:

• Relocated from another region.

• Shifted from another facility.

• Reclassified from contractor to employee or employee to contractor without net new work.

• Created by closing or reducing employment elsewhere.

• Created through public outsourcing of existing public-sector work.

• Created by replacing local businesses that already provided similar employment.

Where displacement is possible, governments must publish a net job estimate.

A gross job number should not be presented as a net public benefit.

18. Automation and Job Reduction Disclosure

For highly automated projects, governments must disclose whether employment is expected to decline over time.

This is especially important for projects such as:

• Data centres.

• Warehousing and logistics facilities.

• Manufacturing plants.

• Resource extraction projects.

• Large-scale agricultural processing.

• AI-enabled service operations.

• Automated retail or distribution systems.

If a project creates many short-term construction jobs but few long-term jobs because of automation, that must be made clear.

If the number of jobs is expected to decline after construction, launch, or early operation, that decline must be reported.

19. Public Subsidy Reporting

Where public money or public support is involved, the government must also report the public cost per job.

Public support should include:

• Direct grants.

• Tax holidays.

• Tax credits.

• Discounted land.

• Public infrastructure.

• Utility upgrades.

• Loan guarantees.

• Public insurance.

• Below-market leases.

• Training subsidies.

• Publicly funded road, water, sewer, grid, or broadband expansion.

• Any other public contribution.

Required calculations:

Public Cost Per Announced Position

Total Public Support / Total Announced Positions

Public Cost Per Long-Term Direct Position

Total Public Support / Long-Term Direct Positions

Public Cost Per Long-Term FTE

Total Public Support / Long-Term FTE

Public Cost Per Living-Wage Long-Term FTE

Total Public Support / Living-Wage Long-Term FTE

The final number should be treated as the primary public accountability figure.

20. Required Subsidy Label

Where public support is involved, the standard job reporting label must include the public cost per living-wage long-term FTE.

Example:

Jobs Reported: 1,200 short-term positions / 85 long-term positions / 36 living-wage long-term FTE. Public cost: $2.1 million per living-wage long-term FTE.

This allows the public to evaluate whether the government is receiving a reasonable return for the support provided.

21. Independent Verification

Any project receiving public support above a defined threshold must have its job creation claims independently reviewed.

The review should verify:

• Job categories.

• Wage assumptions.

• Duration assumptions.

• FTE calculations.

• Living-wage calculations.

• Public cost per job.

• Local hiring assumptions.

• Indirect job methodology.

• Whether claims are gross or net.

• Whether jobs are direct, indirect, or induced.

• Whether jobs meet the regional cost-of-living standard.

The independent review must be published before final approval of major subsidies, tax incentives, or public benefits.

22. Annual Reporting

For projects receiving public support, job creation reports must be updated annually for at least ten years or for the duration of the public benefit, whichever is longer.

Annual reports must disclose:

• Jobs promised.

• Jobs actually created.

• Jobs retained.

• Jobs lost.

• Short-term positions created.

• Long-term positions created.

• Long-term FTE created.

• Living-wage long-term FTE created.

• Average wages.

• Median wages.

• Local hiring rates.

• Public money received to date.

• Public cost per actual long-term job.

• Public cost per actual living-wage long-term FTE.

• Any clawbacks triggered.

The public should be able to compare promised jobs with actual jobs.

23. Public Registry

Each jurisdiction should maintain a public job creation registry.

The registry should include:

• Project name.

• Company name.

• Location.

• Public support provided.

• Jobs promised.

• Jobs created.

• Jobs retained.

• Short-term positions.

• Long-term positions.

• Long-term FTE.

• Living-wage long-term FTE.

• Public cost per living-wage long-term FTE.

• Reporting status.

• Clawbacks applied.

• Compliance history.

The registry should be searchable, downloadable, and updated at least annually.

24. Plain-Language Public Disclosure

All job reporting must be published in plain language.

The public should not need to understand economic modelling, subsidy law, or labour statistics to know what is being promised.

Each project must include a public job summary answering:

• How many jobs are temporary?

• How many jobs are long-term?

• How many are full-time?

• How many are part-time?

• How many are direct?

• How many are estimates?

• How many pay enough to live in the region?

• How many are expected to be local?

• How much public money is being spent?

• What is the public cost per real long-term job?

• What happens if the jobs do not materialize?

25. Media and Public Communication Rule

Because media outlets, headlines, social media posts, and public summaries often shorten government announcements, the three-number label must be treated as the minimum public reporting standard.

The three numbers must appear together and in the same sentence wherever possible.

The short-term number may not be separated from the long-term and living-wage long-term numbers in a way that misleads the public about the actual employment benefit.

The preferred public format is:

Jobs Reported: Short-Term Positions / Long-Term Positions / Living-Wage Long-Term FTE

Example:

Jobs Reported: 1,200 short-term positions / 85 long-term positions / 36 living-wage long-term FTE

This format allows media, governments, and the public to discuss job creation without stripping away the most important context.

26. Prohibited Reporting Practices

Governments should not be allowed to:

• Report short-term jobs as though they are permanent.

• Merge construction jobs with long-term operational jobs without disclosure.

• Use indirect or induced jobs as the headline number.

• Count part-time jobs as full jobs without FTE conversion.

• Announce jobs without disclosing expected duration.

• Announce jobs without disclosing whether they pay a regional cost-of-living wage.

• Count relocated jobs as newly created jobs.

• Count jobs displaced from other local employers as net new jobs.

• Use “up to” job numbers without publishing the assumptions behind them.

• Use public money to support job claims without reporting public cost per actual job.

27. Clawbacks and Penalties

If a company receives public support based on job creation claims and fails to meet those claims, clawbacks should apply.

Clawbacks may be triggered by:

• Failure to create promised long-term jobs.

• Failure to maintain jobs for the required period.

• Misclassification of temporary jobs as permanent jobs.

• Misrepresentation of wage levels.

• Failure to meet cost-of-living wage commitments.

• Failure to meet local hiring commitments.

• Failure to submit annual reports.

• Use of public funds for jobs relocated from elsewhere rather than newly created.

• Repeated failure to provide accurate employment data.

Penalties should be proportional to the public benefit received and the size of the shortfall.

Where misrepresentation is deliberate, additional penalties should apply.

28. Public Right to Challenge

Members of the public, journalists, unions, community organizations, local governments, Indigenous governments, and affected workers should be able to challenge job creation claims.

A challenge process should allow the public to request:

• The assumptions behind job numbers.

• Wage information by job category.

• FTE calculations.

• Duration estimates.

• Local hiring projections.

• Public subsidy calculations.

• Actual job creation reports.

• Independent verification documents.

Governments should be required to respond within a defined period.

29. Implementation

This policy could be implemented through:

• Federal legislation.

• Provincial, state, territorial, or regional legislation.

• Municipal bylaws.

• Treasury board directives.

• Public funding rules.

• Economic development agency requirements.

• Procurement standards.

• Subsidy agreements.

• Infrastructure funding conditions.

• Public-private partnership agreements.

The standard should apply wherever public authority is used to approve, promote, fund, subsidize, or justify a project on the basis of job creation.

30. Summary

Governments should not be allowed to turn temporary, part-time, low-wage, indirect, or speculative employment into inflated headlines.

A project that creates thousands of short-term construction jobs but only a few dozen permanent living-wage jobs should be reported honestly.

The public deserves job numbers that distinguish between a pay cheque, a promise, and a press release.

Every public job claim should answer three basic questions:

How many jobs are short-term?

How many jobs are long-term?

How many long-term jobs actually pay enough to live there?

The standard public label should be:

Jobs Reported: Short-Term Positions / Long-Term Positions / Living-Wage Long-Term FTE

This policy does not prevent governments from celebrating economic development.

It simply requires them to tell the truth about it.

It asks for time, attention, employment history, education history, references, contact information, salary expectations, and often enough personal detail to build a profile of a person’s working life.

That exchange should come with obligations.

If a job is not real, not active, already filled, only posted to build a résumé database, or dependent on a contract that does not yet exist, applicants deserve to know that before they apply.

Job postings should not be allowed to function as fake labour-market signals, unpaid market research, or personal data harvesting tools.

The following proposal is a working framework for a Truth in Job Advertising and Applicant Data Protection law. It is meant to protect job seekers, improve labour-market data, and require employers, recruiters, and hiring platforms to be honest about what they are advertising and what they are doing with applicant information.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

Truth in Job Advertising and Applicant Data Protection Framework

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

1. Purpose

The purpose of this framework is to protect job seekers, improve labour-market transparency, prevent deceptive employment advertising, and regulate the collection, retention, use, sharing, sale, and analysis of applicant data.

Job postings should exist to advertise real employment opportunities, not to harvest résumés, inflate perceptions of growth, test labour-market wages, create misleading job-market data, or collect personal information without meaningful disclosure.

No person should be required to surrender personal data to apply for a job that does not exist, is not actively being filled, or is being advertised for purposes other than hiring.

2. Guiding Principles

This framework is based on the following principles:

1. Truth in advertising
   A job posting should accurately represent the status of the position being advertised.

2. Applicant dignity
   Job seekers should not be misled, exploited, or used as a source of unpaid market intelligence.

3. Data minimization
   Employers and platforms should collect only the information required for a specific hiring process.

4. Purpose limitation
   Applicant data collected for one job should not be reused for unrelated purposes without clear, separate consent.

5. Retention limits
   Résumés and application materials should not be stored indefinitely.

6. Transparency
   Applicants should know who is collecting their information, why it is being collected, how long it will be kept, and whether it will be shared.

7. Platform accountability
   Job boards, recruitment platforms, and hiring software providers should not be passive beneficiaries of deceptive or exploitative job advertising.

8. Public data integrity
   Labour-market data used by governments, researchers, and the public should not be distorted by large volumes of fake, inactive, recycled, or misleading job postings.

3. Scope

This framework would apply to:

• Employers.

• Recruiters.

• Staffing agencies.

• Executive search firms.

• Third-party hiring firms.

• Job boards.

• Online employment platforms.

• Applicant tracking system providers.

• Labour-market data brokers.

• Public-sector employers.

• Crown corporations and government agencies.

• Contractors advertising jobs connected to public funding, grants, procurement, or government-supported projects.

It would apply to any publicly advertised job posting, including postings on:

• Company websites.

• Job boards.

• Social media.

• Recruitment platforms.

• Government employment portals.

• Staffing agency websites.

• Educational institution career boards.

• Professional association job boards.

• Automated hiring or recruitment systems.

4. Definitions

Job Posting

A public communication inviting people to apply for employment, contract work, temporary work, paid placement, internship, apprenticeship, or other work opportunity.

Active Vacancy

A real, approved, funded, and currently available position that the employer intends to fill within a stated hiring period.

Talent Pool Posting

A posting used to collect potential applicants for future opportunities where no current active vacancy exists.

Conditional Posting

A posting for a role that depends on a future event, including contract award, grant approval, project approval, budget approval, client demand, or government procurement.

Internal Candidate Posting

A posting where an internal or preferred candidate already exists, but external applications are still being accepted.

Evergreen Posting

A recurring or continuously active posting used to gather candidates for roles that may open periodically.

Ghost Job

A job posting that is presented as an active vacancy when the employer does not have a real, approved, funded, and current intention to hire for that role within the stated hiring period.

Ghost jobs may include postings created to:

• Collect résumés without a current vacancy.

• Build a talent database.

• Test wage expectations.

• Create the appearance of company growth.

• Signal expansion to investors or competitors.

• Satisfy internal policy requirements despite a predetermined candidate.

• Gather market intelligence.

• Make an employer appear more active or successful than it is.

• Produce misleading labour-market data.

• Funnel applicant data into third-party systems.

Applicant Data

Any information submitted, collected, inferred, generated, or analyzed during a job application process, including:

• Name.

• Address.

• Email address.

• Phone number.

• Employment history.

• Education history.

• Credentials.

• References.

• Cover letters.

• Résumés.

• Work samples.

• Portfolios.

• Salary expectations.

• Availability.

• Immigration or work authorization status.

• Disability accommodation information.

• Demographic information.

• Assessment results.

• Interview notes.

• Screening scores.

• AI-generated rankings.

• Personality test results.

• Background check information.

• Metadata collected through online platforms.

• Any profile created about the applicant.

5. Job Posting Classification Requirement

Every public job posting must clearly identify the status of the opportunity.

The posting must be labelled as one of the following:

5.1 Active Vacancy

The employer has:

• An approved position.

• Budget or funding for the position.

• Authority to hire.

• A real intention to hire.

• A defined hiring timeline.

• A role that is currently available.

5.2 Talent Pool

No current vacancy exists. The employer is collecting applicants for possible future opportunities.

A talent pool posting must not be presented as an active vacancy.

5.3 Conditional Opportunity

The job depends on a future event, such as:

• Contract approval.

• Grant approval.

• Budget approval.

• Client demand.

• Procurement award.

• Project start.

• Regulatory approval.

The posting must clearly state the condition that must be met before hiring can occur.

5.4 Internal or Preferred Candidate Exists

If an internal or preferred candidate already exists, the posting must disclose that external applications are being accepted, but that an internal or preferred candidate is under consideration.

5.5 Evergreen Posting

If a posting is continuously used for recurring recruitment, it must be labelled as an evergreen posting and must state that applications may not correspond to an immediate vacancy.

6. Required Information in Every Job Posting

Every public job posting must include:

1. Employer name.

2. Whether the employer is hiring directly or through a recruiter.

3. Job classification status.

4. Work location.

5. Whether the role is remote, hybrid, or on-site.

6. Whether the job is full-time, part-time, temporary, seasonal, contract, casual, or internship.

7. Expected compensation range.

8. Expected hours of work.

9. Whether the position is unionized.

10. Application deadline.

11. Anticipated interview period.

12. Anticipated hiring decision period.

13. Expected start date or start-date range.

14. Whether AI or automated screening tools will be used.

15. Applicant data retention period.

16. Applicant data use policy.

17. Applicant data sharing policy.

18. Applicant deletion or withdrawal process.

19. Contact information for privacy or applicant-data concerns.

7. Hiring Timeline Requirement

An active vacancy must include a reasonable hiring timeline.

The employer must identify:

• Application closing date.

• Expected review period.

• Expected interview period.

• Expected decision date or decision window.

• Expected start date or start-date window.

If the employer does not intend to review applications within the stated period, the posting cannot be classified as an active vacancy.

If the hiring timeline changes, the posting must be updated.

If the employer cancels the hiring process, applicants must be informed.

8. Applicant Data Notice

Before an applicant submits any personal information, the employer, recruiter, or platform must provide a plain-language applicant data notice.

The notice must explain:

1. What information is being collected.

2. Why the information is being collected.

3. Whether the information is required or optional.

4. Who will access the information.

5. Whether the information will be shared with third parties.

6. Whether the information will be stored outside the applicant’s jurisdiction.

7. Whether AI, automated screening, ranking, or profiling tools will be used.

8. Whether the information will be added to a broader talent database.

9. Whether the information will be used for analytics, benchmarking, or training.

10. Whether the information may be sold, licensed, transferred, or monetized.

11. How long the information will be retained.

12. How the applicant can request deletion.

13. How the applicant can withdraw from consideration.

14. Who is legally responsible for the information.

This notice must be visible before the applicant uploads a résumé or enters personal information.

It must not be buried only in a privacy policy, terms of service, or external legal document.

9. Consent Rules

Applying for a job may constitute consent to use applicant data for that specific hiring process only.

Separate, clear, opt-in consent must be required for:

• Adding the applicant to a general talent database.

• Sharing the applicant’s information with affiliated companies.

• Sharing the applicant’s information with unrelated employers.

• Using applicant data for labour-market analytics.

• Using applicant data to train AI or automated hiring systems.

• Selling, licensing, or transferring applicant data.

• Using applicant data for marketing.

• Keeping applicant data beyond the standard retention period.

Consent must not be bundled.

An applicant must be able to apply for a specific job without being forced to consent to unrelated data uses.

10. Data Retention Limits

Applicant data must be deleted after the hiring process ends unless:

• The applicant gives separate consent to longer retention.

• A specific legal obligation requires retention.

• The applicant is hired and the information becomes part of an employment record.

• The applicant has requested continued consideration for future opportunities.

A standard retention period should be established by law.

A possible model:

• Unsuccessful applicants: delete within 12 months.

• Withdrawn applications: delete within 90 days.

• Talent pool applicants: renew consent every 12 months.

• Assessment or screening data: delete within 12 months unless legally required.

• AI-generated applicant profiles: delete within the same period as the underlying application.

Applicants must receive a simple way to request earlier deletion.

11. Limits on Collection

Employers and platforms may only collect information that is reasonably necessary for the specific stage of the hiring process.

Initial applications should not require unnecessary sensitive information.

Unless legally required or directly relevant at that stage, employers should not require:

• Government identification numbers.

• Full birth date.

• Full home address.

• Driver’s licence number.

• Passport details.

• Banking information.

• Credit information.

• Medical information.

• Disability information beyond accommodation needs.

• Family status information.

• Unrelated demographic information.

• Video recordings.

• Voice recordings.

• Personality testing.

• Social media access.

• Unnecessary references before interview selection.

More sensitive information should only be collected later in the process when genuinely required.

12. AI and Automated Screening

Where AI or automated tools are used in hiring, the posting and applicant data notice must disclose:

• That automated tools are being used.

• The type of tool being used.

• What the tool evaluates.

• Whether it ranks, scores, filters, or rejects applicants.

• Whether a human reviews automated decisions.

• Whether applicants can request reconsideration.

• Whether applicant data is used to improve, train, or test the system.

• Whether the tool was developed internally or by a third party.

Applicants should have the right to request human review of any rejection or ranking substantially influenced by automated systems.

Employers should not be allowed to use applicant data to train AI hiring systems without separate, explicit consent.

13. Ban on Résumé Sale and Unrelated Secondary Use

Applicant data must not be sold, licensed, traded, transferred, or monetized without specific, separate, informed, opt-in consent.

Employers, recruiters, job boards, and platforms must not use applicant data for unrelated secondary purposes without consent.

Prohibited secondary uses should include:

• Selling résumé databases.

• Sharing applicant profiles with unrelated employers.

• Training AI systems without consent.

• Creating commercial labour-market intelligence products without consent.

• Using applicant data for advertising.

• Using applicant data for unrelated behavioural profiling.

• Transferring applicant information through mergers or data-broker arrangements without notice and protection.

A résumé submitted for a job should remain an application, not become a commodity.

14. Ghost Job Prohibition

It should be unlawful to advertise a job as an active vacancy if:

• No approved position exists.

• No budget exists.

• No hiring authority exists.

• There is no intention to hire.

• The employer is only collecting résumés.

• The employer is only testing wages or availability.

• The employer is only creating an appearance of growth.

• The employer is using the posting for market intelligence.

• The employer has already decided not to fill the role.

• The role is contingent but not labelled as conditional.

• The posting is evergreen but not labelled as evergreen.

• An internal or preferred candidate exists but that fact is not disclosed where required.

This does not prohibit talent pools, conditional postings, evergreen postings, or internal postings.

It simply requires them to be labelled honestly.

15. Applicant Notification Requirement

Applicants must be notified when:

• The hiring process is cancelled.

• The job is filled.

• The posting is withdrawn.

• The role changes materially.

• The compensation range changes materially.

• The location or remote-work status changes materially.

• The hiring process is delayed beyond the stated timeline.

• Applicant data will be retained beyond the standard period.

• Applicant data has been shared with a third party.

• A data breach affects applicant information.

For large-volume hiring, notice may be automated, but it must still be clear and meaningful.

16. Platform Accountability

Job boards and hiring platforms must take reasonable steps to prevent deceptive postings.

Platforms should be required to:

1. Verify employer identity.

2. Identify third-party recruiters.

3. Require job classification labels.

4. Require applicant data notices.

5. Remove expired postings.

6. Flag continuously reposted jobs.

7. Provide a process for reporting suspected ghost jobs.

8. Investigate repeat offenders.

9. Preserve posting records.

10. Publish transparency reports.

11. Provide applicants with access to platform-level data policies.

12. Prevent scraping or unauthorized resale of applicant data.

13. Clearly disclose whether the platform itself uses applicant data for analytics, AI training, advertising, or commercial data products.

A platform that profits from job advertising should share responsibility for the integrity of that advertising.

17. Posting Record Requirement

Employers, recruiters, and platforms must retain records of public job postings for a defined period.

Records should include:

• Original posting.

• Posting classification.

• Date posted.

• Date removed.

• Compensation range.

• Job location.

• Hiring timeline.

• Number of applicants.

• Whether interviews occurred.

• Whether the role was filled.

• Whether the successful candidate was internal or external.

• Whether the role was cancelled.

• Applicant data retention settings.

• Third parties that received applicant data.

These records should be available to regulators during audits or investigations.

18. Labour-Market Data Integrity

Governments should not treat all job postings as equal evidence of labour demand.

Public labour-market reporting should distinguish between:

• Active vacancies.

• Talent pool postings.

• Evergreen postings.

• Conditional postings.

• Internal/preferred-candidate postings.

• Cancelled postings.

• Reposted positions.

• Duplicate postings.

• Third-party recruiter duplicates.

• Platform-generated duplicates.

Government agencies using job-posting data should adjust for ghost jobs, recycled listings, and inactive postings before making claims about labour shortages, skills gaps, employment demand, or regional economic conditions.

No government should rely on unverified job-posting volume as the sole basis for labour policy, immigration planning, training subsidies, education funding, or corporate subsidy decisions.

19. Public Funding and Subsidy Conditions

Any employer receiving public funding, tax credits, grants, procurement contracts, wage subsidies, training subsidies, or economic development support should be subject to stricter job-posting rules.

Publicly supported employers must disclose:

• How many jobs were promised.

• How many jobs were posted.

• How many were active vacancies.

• How many were filled.

• Whether jobs were filled locally.

• Whether postings were conditional.

• Whether postings were cancelled.

• Whether applicant data was shared with third parties.

• Whether AI or automated screening was used.

A company should not be allowed to use ghost postings to exaggerate job creation connected to public subsidies.

20. Applicant Rights

Applicants should have the right to:

1. Know whether a job is real, active, conditional, evergreen, or a talent pool.

2. Know how their data will be used before applying.

3. Apply without consenting to unrelated data use.

4. Request deletion of their applicant data.

5. Withdraw from consideration.

6. Know whether AI or automated screening was used.

7. Request human review of automated rejection.

8. Know whether their information was shared with third parties.

9. File a complaint about deceptive postings.

10. File a complaint about misuse of applicant data.

11. Receive notice if the hiring process is cancelled.

12. Receive notice if their data is affected by a breach.

21. Employer Rights and Safe Harbours

This framework should not punish honest employers for ordinary hiring changes.

An employer should not be penalized simply because:

• A budget is unexpectedly cut.

• A candidate declines an offer.

• Hiring is paused for legitimate reasons.

• A project is delayed.

• A role changes during recruitment.

• No suitable candidate is found.

• Business conditions change.

However, the employer must update the posting, notify applicants where appropriate, and avoid presenting inactive or uncertain roles as active vacancies.

A safe harbour may apply where the employer can show:

• The posting was accurate when published.

• The employer had a genuine intention to hire.

• The employer updated the posting when circumstances changed.

• Applicant data was handled according to the stated policy.

• Applicants were not misled for data-harvesting purposes.

22. Enforcement

Enforcement could be handled through employment standards offices, privacy commissioners, consumer protection agencies, or a dedicated labour-market integrity office.

Regulators should have the power to:

• Investigate complaints.

• Audit employers and platforms.

• Require posting records.

• Require applicant data records.

• Order correction of misleading postings.

• Order deletion of improperly collected applicant data.

• Suspend deceptive postings.

• Penalize repeat offenders.

• Publish names of serious violators.

• Restrict access to public job boards.

• Restrict eligibility for public funding or procurement.

• Refer serious privacy violations to privacy regulators.

• Refer fraud-like conduct for further legal action where appropriate.

23. Penalties

Penalties should be scaled based on severity, intent, size of employer, number of applicants affected, and whether the violation was repeated.

Possible penalties include:

• Warning for first minor violation.

• Mandatory correction.

• Applicant notification order.

• Data deletion order.

• Administrative monetary penalty.

• Higher penalty for repeat violations.

• Higher penalty for deliberate ghost postings.

• Higher penalty for selling or transferring applicant data without consent.

• Temporary ban from public job boards.

• Loss of eligibility for public hiring subsidies.

• Loss of eligibility for government contracts.

• Public listing of serious violators.

Where applicant data has been sold, transferred, or used for unauthorized AI training, penalties should reflect the seriousness of the loss of control.

Once applicant data has entered external databases, data-broker systems, or AI training pipelines, the harm may be impossible to fully reverse.

24. Transparency Reports

Large employers, recruitment firms, and job platforms should publish annual transparency reports.

Reports should include:

• Number of job postings.

• Number of active vacancies.

• Number of talent pool postings.

• Number of evergreen postings.

• Number of conditional postings.

• Number of cancelled postings.

• Number of reposted roles.

• Number of roles filled.

• Average hiring timeline.

• Use of AI screening tools.

• Applicant data retention practices.

• Number of deletion requests.

• Number of complaints received.

• Number of confirmed deceptive postings.

• Number of postings removed for misrepresentation.

• Third-party data-sharing categories.

These reports would help applicants, governments, researchers, and regulators understand whether job postings reflect real employment opportunities.

25. Public Job Board Standards

Government-run or publicly funded job boards should meet the highest standard.

They should:

• Require job classification labels.

• Require compensation ranges.

• Require hiring timelines.

• Require applicant data notices.

• Remove expired postings.

• Flag reposted roles.

• Ban repeat ghost-job offenders.

• Prevent duplicate postings from distorting labour-market data.

• Publish aggregate statistics by job classification.

• Refuse postings that do not disclose applicant data practices.

A public job board should not become a public résumé-harvesting tool.

26. Special Rules for Recruiters and Staffing Agencies

Recruiters and staffing agencies must disclose whether they are hiring for:

• A specific employer.

• A confidential employer.

• A talent pool.

• A possible future contract.

• A general recruitment database.

• A role that is contingent on client approval.

If the employer is confidential, the recruiter must still disclose:

• Whether the vacancy is active.

• Whether the position is funded.

• Whether the client has authorized recruitment.

• Whether applicant data will be shared with one employer or many.

• How long the data will be retained.

• Whether the applicant will be contacted before being submitted to any employer.

Recruiters should not be allowed to collect résumés under the appearance of a specific job when no specific job exists.

27. Special Rules for Public-Sector Hiring

Public-sector employers should be required to disclose when a posting is:

• Open competition.

• Internal competition.

• External posting with internal candidate.

• Expression of interest.

• Talent inventory.

• Conditional on funding.

• Conditional on project approval.

Public-sector hiring should not invite external applicants into a process that is effectively predetermined without disclosure.

Where public-sector postings are used to satisfy procedural requirements, the posting should state that clearly.

28. Data Breach and Security Requirements

Applicant data must be protected with appropriate security safeguards.

Employers, platforms, recruiters, and vendors must protect applicant data against:

• Unauthorized access.

• Data scraping.

• Unapproved sharing.

• Employee misuse.

• Vendor misuse.

• Data breaches.

• Unsecured storage.

• Indefinite retention.

• Unauthorized AI training.

• Unauthorized transfer to third countries.

Applicants must be notified if their information is compromised.

Because job applications often contain enough information for identity theft, fraud, profiling, discrimination, and long-term employment harm, applicant data should be treated as sensitive personal information.

29. Deletion and Withdrawal Process

Every applicant must have access to a simple deletion and withdrawal process.

This process must allow the applicant to:

• Withdraw from the hiring process.

• Request deletion of application materials.

• Request deletion from a talent pool.

• Revoke consent for future use.

• Request a list of third parties who received the information.

• Request confirmation that deletion has occurred.

Deletion requests should be completed within a defined period, such as 30 days, unless a specific legal obligation requires retention.

If data cannot be deleted because it has already been transferred, anonymized, aggregated, or used in AI training, that must be disclosed to the applicant.

30. Anti-Retaliation Protection

Employers, recruiters, and platforms must not penalize, blacklist, or disadvantage applicants for:

• Asking whether a job is active.

• Asking how their data will be used.

• Refusing unrelated data consent.

• Requesting deletion.

• Filing a complaint.

• Reporting a suspected ghost job.

• Requesting human review of automated screening.

Applicants should not have to choose between privacy and employability.

31. Implementation Timeline

A phased implementation model could be used.

Phase 1: Disclosure

Require job classification labels, hiring timelines, compensation ranges, and applicant data notices.

Phase 2: Retention and Consent

Create standard retention limits, deletion rights, consent rules, and restrictions on secondary use.

Phase 3: Platform Accountability

Require job boards and platforms to verify postings, preserve records, remove misleading listings, and publish transparency reports.

Phase 4: Enforcement and Audits

Introduce penalties, audits, public reporting, and stricter rules for publicly funded employers.

32. Model Posting Disclosure

Every job posting should include a disclosure similar to the following:

Job Status: Active vacancy
Hiring Timeline: Applications close June 30. Interviews expected July 8–19. Hiring decision expected by July 31.
Applicant Data Use: Your application will be used only for this hiring process unless you separately consent to future consideration.
Retention Period: Unsuccessful applications will be deleted within 12 months.
Third-Party Access: Applications will be processed through [platform/vendor name]. Data will not be sold or used for AI training.
Automated Screening: Automated screening will / will not be used.
Deletion Requests: Applicants may request deletion by contacting [contact information].

33. Rationale

Job seekers are often required to submit detailed personal information before they know whether a job is real, whether hiring is active, or what will happen to their data.

This creates several harms.

First, ghost jobs waste applicant time and emotional energy. Applying for work is labour. It requires tailoring résumés, writing cover letters, preparing portfolios, completing forms, answering screening questions, and sometimes doing unpaid assessments. When the job does not exist, that labour has been extracted under false pretenses.

Second, ghost jobs distort the labour market. They can make it appear that employers are hiring when they are not. This can mislead workers, governments, schools, training providers, immigration planners, and economic development agencies.

Third, job applications contain valuable personal data. Résumés reveal employment history, education, location, skills, salary expectations, career movement, references, and sometimes sensitive personal information. Without clear rules, this data can be retained indefinitely, shared widely, sold, analyzed, or used to train automated systems.

Fourth, deceptive job postings can benefit employers and platforms while applicants carry the cost. Employers can test wages, build databases, signal growth, satisfy internal optics, or gather market intelligence. Platforms can increase listing volume and collect user data. Applicants receive little transparency in return.

A fair labour market requires honest job advertising.

A fair privacy system requires meaningful control over applicant data.

This framework recognizes that a job application is not just a document. It is a transfer of personal information, trust, time, and hope. That transfer should come with legal obligations.

34. Core Policy Statement

No employer, recruiter, platform, or third-party hiring service should advertise a job in a manner that misleads applicants about whether the job exists, whether hiring is active, or how applicant data will be collected, retained, used, shared, sold, or analyzed.

Job seekers deserve truth before they apply.

They deserve control over their data.

They deserve a labour market where advertised opportunities are not allowed to become traps for personal information.

Sometimes those tools are obvious AI systems. Sometimes they are not. They may be file converters, AI detectors, plagiarism checkers, résumé scanners, transcription tools, PDF editors, image enhancers, or workplace productivity platforms. But once a file is uploaded, control over that material may be lost.

This policy proposal is built around one simple principle:

If it is not yours, and you do not have permission or legal authority, you should not be able to upload it into an AI or AI-adjacent system.

The law should not require artists, writers, students, workers, clients, patients, businesses, or communities to prove exactly how much harm was caused after their work or private material was uploaded without consent. In many cases, that harm cannot be properly measured. The loss of control is the harm.

The AI Upload Consent and Data Authority Act is a proposal to create clear rules, visible warnings, meaningful consent, platform accountability, and enforceable consequences before people hand someone else’s work or private documents to systems that may store, share, analyze, or train on them.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The AI Upload Consent and Data Authority Act

A Public Policy Proposal

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

Purpose

The purpose of this Act is to prevent individuals, companies, institutions, contractors, employees, students, clients, or third parties from uploading artwork, documents, images, writing, contracts, records, research, schoolwork, business files, personal files, or other protected material into artificial intelligence systems or AI-adjacent digital tools unless they have the legal ownership, consent, licence, employment authority, contractual authority, or copyright permission to do so.

This Act recognizes that many online tools now collect, process, retain, analyze, share, or use uploaded content in ways that are not obvious to the person uploading the file. These tools may include, but are not limited to:

AI writing tools.
AI image tools.
AI detectors.
Plagiarism checkers.
File converters.
OCR tools.
PDF tools.
Transcription tools.
Résumé scanners.
Contract-review tools.
Image-enhancement tools.
Cloud-based editing tools.
Educational technology platforms.
Business productivity tools.
Any service that uses uploaded material to train, improve, fine-tune, evaluate, benchmark, or develop artificial intelligence systems.

The central principle is simple:

No person should be allowed to upload someone else’s work, private material, confidential document, copyrighted content, creative file, or personal data into an AI or AI-adjacent system unless they have clear lawful authority to do so.

Core Requirement

Any digital service that allows users to upload files, documents, images, artwork, audio, video, code, writing, educational material, professional material, or other user-submitted content must provide a clear, visible, plain-language notice before upload.

This notice must not be hidden in the terms of service, privacy policy, footer, account settings, or secondary menu.

The notice must appear at the point of upload.

Required Upload Warning

Before accepting an uploaded file, the service must display a warning substantially similar to the following:

By uploading this file, you confirm that you own this material or have the legal authority, consent, licence, workplace authorization, contractual permission, or copyright permission required to upload it to this service.

Do not upload artwork, documents, images, writing, contracts, records, private files, confidential files, schoolwork, professional work, or copyrighted material that you do not own or have authority to submit.

Unauthorized uploading of protected, private, confidential, or copyrighted material may result in legal liability, penalties, civil claims, regulatory enforcement, or charges under applicable law.

The user must actively confirm this statement before the upload proceeds.

Pre-checked boxes, implied consent, passive acceptance, or blanket terms of service are not sufficient.

Service Disclosure Requirements

Any service that accepts uploaded material must clearly disclose, before upload:

1. Whether uploaded files are stored.

2. How long uploaded files are retained.

3. Whether uploaded files are reviewed by humans.

4. Whether uploaded files are shared with third parties.

5. Whether uploaded files are used to train, fine-tune, evaluate, improve, benchmark, or develop AI systems.

6. Whether metadata is collected from uploaded files.

7. Whether uploaded files may be used for product development.

8. Whether uploaded files may be transferred outside the user’s jurisdiction.

9. Whether users can permanently delete uploaded files.

10. Whether the service claims any licence over uploaded material.

These disclosures must be short, plain-language, and visible before upload.

A company may not rely only on a general terms of service agreement to obtain consent for AI training, model improvement, data sharing, or secondary use of uploaded content.

Prohibited Conduct

It shall be prohibited for a person to knowingly upload material into an AI or AI-adjacent system if they do not have lawful authority to do so.

This includes, but is not limited to:

Uploading an artist’s work without permission.
Uploading an author’s unpublished manuscript without permission.
Uploading a student’s work without permission.
Uploading a client’s file without permission.
Uploading an employee’s work product outside authorized workplace use.
Uploading a confidential business document without authority.
Uploading legal, medical, financial, educational, or government records without authority.
Uploading private family photos without consent from the appropriate rights holder.
Uploading Indigenous cultural material, ceremonial material, community records, or traditional knowledge without proper community authority.
Uploading copyrighted books, articles, images, music, scripts, photographs, designs, or other works without permission.
Uploading documents obtained through employment, contracting, volunteering, caregiving, education, public service, or professional access for purposes not authorized by the owner, client, employer, institution, or rights holder.

Duties of AI and Digital Tool Providers

Any service that accepts uploaded material must take reasonable steps to prevent misuse.

These duties include:

Clear upload warnings.
Plain-language data-use disclosures.
Active uploader confirmation.
Accessible deletion tools.
A public policy on AI training use.
A process for rights holders to report unauthorized uploads.
A process for removal, deletion, and confirmation of deletion.
Retention logs for uploaded files where legally appropriate.
Audit records for high-risk or commercial services.
Special protections for minors, students, patients, clients, employees, and vulnerable persons.
Special protections for confidential, professional, legal, medical, educational, cultural, and government records.

Where a service uses uploaded material for AI training or model improvement, it must obtain specific, informed, opt-in consent from the lawful rights holder or authorized representative.

Consent from the uploader alone is not valid if the uploader does not own or control the uploaded material.

No Hidden AI Training Consent

A company must not treat upload as automatic consent for AI training.

A company must not bury AI-training permission in a general terms of service.

A company must not use vague language such as “service improvement,” “product development,” “analytics,” “quality assurance,” or “machine learning enhancement” as a substitute for clear disclosure.

If uploaded material may be used to train, improve, test, evaluate, or develop an AI system, the service must say so plainly before upload.

Rights Holder Remedies

Rights holders must have the right to:

Request confirmation of whether their material was uploaded.
Request deletion of unauthorized material.
Request information about whether the material was used for AI training or model improvement.
Request information about third-party sharing.
File a regulatory complaint.
Seek damages where harm has occurred.
Seek penalties for repeated, commercial, reckless, or intentional misuse.
Require platforms to preserve records where a legal claim is pending.

Where material has already been used for AI training, the service must be required to disclose what remedial steps are technically possible, what steps will be taken, and why any requested remedy cannot be fully completed.

Enforcement

Enforcement under this Act should recognize that unauthorized uploading is not a minor or reversible act.

Once a document, image, artwork, manuscript, contract, record, private file, cultural material, school assignment, client file, business document, or creative work is uploaded into an AI or AI-adjacent system, the original rights holder may lose meaningful control over it.

The harm may not be easy to measure.
The harm may not be visible immediately.
The harm may not be monetized in any simple way.
The rights holder may never know whether the file was stored, copied, analyzed, shared, reviewed, transferred, used for AI training, used for product development, or retained in a dataset.

For that reason, enforcement should not depend only on proving financial loss, market damage, or malicious intent.

The unauthorized upload itself should be recognized as a legally significant harm.

Strict Liability for Unauthorized Uploads

Where a person uploads protected, private, confidential, copyrighted, proprietary, cultural, professional, educational, medical, legal, employment, government, or personal material without lawful authority, the act of unauthorized upload should be sufficient to trigger liability.

The burden should not fall entirely on the rights holder to prove what happened after the upload.

The uploader should bear responsibility for confirming that they had the authority to upload the material before doing so.

Intent may still matter when determining the severity of penalties, but lack of malicious intent should not erase liability.

A person who uploads material without authority may be liable even if they did not understand the full consequences of the upload.

Penalty Factors

Penalties should consider:

Whether the uploaded material belonged to someone else.
Whether the uploader had lawful authority.
Whether the material was private, confidential, unpublished, sensitive, cultural, commercial, professional, educational, legal, medical, or personal.
Whether the upload involved a minor, student, client, patient, employee, artist, author, contractor, Indigenous community, or vulnerable person.
Whether the service used uploaded material for AI training, model improvement, product development, human review, sharing, resale, or third-party processing.
Whether the uploader ignored a clear warning.
Whether the uploader acted in a personal, institutional, professional, commercial, reckless, or repeated capacity.
Whether the uploader gained or attempted to gain benefit from the upload.
Whether the upload exposed the rights holder to privacy, reputational, professional, financial, creative, cultural, legal, or safety risks.
Whether deletion, containment, or confirmation of non-use is possible.

No Requirement to Prove Exact Monetary Harm

A rights holder should not be required to prove exact financial damage in order for the law to apply.

Many harms caused by unauthorized AI uploads cannot be properly monetized.

These may include:

Loss of control over unpublished work.
Loss of control over private records.
Loss of control over confidential documents.
Loss of control over cultural material.
Loss of control over student work.
Loss of control over client files.
Loss of control over creative style, voice, image, likeness, or process.
Loss of first-publication rights.
Loss of trust.
Loss of privacy.
Loss of professional confidentiality.
Loss of negotiating power.
Risk of future misuse.
Risk of model training or dataset retention.
Risk of downstream copying.
Risk of unknown third-party access.

Because these harms are difficult or impossible to calculate, the Act should allow statutory penalties, presumed damages, regulatory fines, deletion orders, audit orders, and other remedies without requiring the rights holder to prove a precise dollar value.

Platform and Service Provider Liability

Services that accept uploads must not escape responsibility by saying the uploader clicked “agree.”

Where a service accepts uploaded material, it must provide clear warnings, clear data-use disclosures, meaningful consent options, deletion mechanisms, and rights-holder complaint procedures.

If a service fails to clearly warn users that unauthorized uploading may be unlawful, fails to disclose retention or AI-training practices, or uses uploaded material beyond the lawful authority of the uploader, the service may also be liable.

Services should face heightened penalties where they:

Hide AI-training permissions in terms of service.
Use vague consent language.
Retain uploaded material without clear disclosure.
Use uploaded material for training without rights-holder consent.
Share uploaded material with third parties without clear disclosure.
Fail to delete unauthorized material when notified.
Fail to maintain records of upload, retention, deletion, and use.
Mislead users about whether uploaded material is stored, reviewed, or used.
Rely on uploader consent when the uploader did not own or control the material.

Share

Required Remedies

Where unauthorized upload has occurred, regulators or courts should be able to order:

Immediate deletion of the uploaded material.
Confirmation of whether the material was stored, copied, reviewed, shared, or used for AI training.
Disclosure of all third parties that received the material.
Preservation of records for investigation.
Deletion from active systems where technically possible.
Removal from training datasets where technically possible.
A statement explaining whether the material has already been used in model training or product development.
A statement explaining what remediation is technically possible and what is not.
Notice to affected rights holders.
Administrative penalties.
Statutory damages.
Civil damages.
Institutional discipline or professional consequences where appropriate.
Procurement bans or licence restrictions for repeat-offending service providers.

Aggravated Violations

Higher penalties should apply where unauthorized upload involves:

Unpublished creative work.
Confidential legal, medical, financial, educational, or employment records.
Student work.
A minor’s personal information or creative work.
Indigenous cultural material, community records, traditional knowledge, or ceremonial material.
Private family photos or personal records.
Trade secrets or proprietary business information.
Client, patient, student, or employee files.
Repeated conduct.
Commercial use.
Institutional use.
Deceptive use.
Retaliatory use.
Malicious use.
Upload after a clear warning.
Upload into a system known to retain, share, or train on submitted material.

Core Enforcement Principle

The law should not ask rights holders to prove the impossible.

Once unauthorized material enters an AI or AI-adjacent system, the damage may be unknown, untraceable, irreversible, or impossible to fully price.

Therefore, the law should treat unauthorized upload as the actionable harm.

Intent may affect the penalty.

But the absence of intent should not erase the violation.

Public Institutions

Public institutions, schools, universities, libraries, health systems, courts, municipalities, police services, correctional systems, and government departments must not upload public records, student records, patient records, legal records, government documents, Indigenous records, personal information, or copyrighted material into AI systems unless they have explicit legal authority and the service has been approved through a public procurement, privacy, security, and data-governance review.

Public institutions must maintain a public registry of approved AI and upload-based tools.

Workplace Protections

Employers must clearly inform workers which AI tools are approved for workplace use.

Workers must not be required to upload client files, confidential documents, creative work, personal information, or copyrighted material into AI systems unless the employer has confirmed that the use is lawful, authorized, secure, and compliant with this Act.

Employees should not be personally liable for uploads made under direct employer instruction unless the employee knowingly violated the law or acted outside authorized duties.

Employers, contractors, vendors, and institutions should bear responsibility for the tools they require workers to use.

Education Protections

Schools, colleges, universities, teachers, professors, administrators, and education technology vendors must not upload student work into AI detectors, grading tools, plagiarism tools, writing tools, or assessment systems unless students and, where appropriate, parents or guardians have been clearly informed of:

What tool is being used.
What data is uploaded.
Whether the material is retained.
Whether it is used for AI training.
Whether it is shared with third parties.
How long it is kept.
How deletion can be requested.
What alternatives exist.

Student work should not become training data simply because a school, teacher, or platform used an AI-related tool.

Exceptions

This Act should not prevent lawful uses where proper authority exists.

Exceptions may include:

Material uploaded by the copyright owner.
Material uploaded with clear permission from the rights holder.
Material uploaded under a valid licence.
Material uploaded under a valid employment or institutional policy.
Material uploaded under court order or statutory authority.
Material uploaded for accessibility purposes where no data is retained or used for training.
Material uploaded for security scanning where no secondary use occurs.
Material uploaded for private personal use where the uploader owns the material or has lawful authority.
Material in the public domain.
Material covered by a lawful exception, provided the upload does not create unauthorized retention, sharing, commercial exploitation, or AI-training use.

Guiding Principle

This Act is not intended to stop people from using technology.

It is intended to stop people, companies, schools, employers, institutions, and governments from quietly transferring other people’s work, private records, confidential material, or copyrighted content into AI systems without consent, authority, or accountability.

The rule should be simple enough for everyone to understand:

If it is not yours, and you do not have permission or legal authority, you cannot upload it into AI.

It begins much earlier, with the land itself.

Across Canada, agricultural land is increasingly being valued not only for what it can grow, but for what it might become: subdivisions, recreational estates, corporate land banks, industrial sites, warehouses, data centres, or other non-farm uses.

When that speculative value pushes up land prices, assessments, and property taxes, farmers are left carrying costs created by people who may never plant a seed, raise livestock, or produce food.

Those costs do not disappear. They move into the food system.

This policy proposal is built around a simple idea: if land is being used to feed people, it should be taxed as farmland. If someone profits from taking it out of food production, the public should recover part of that speculative gain.

The Productive Farmland Protection and Valuation Act is a proposal to protect family farms, support food affordability, reduce speculative pressure on agricultural land, and recognize farmland as food-system infrastructure rather than just another real estate asset.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The Productive Farmland Protection and Valuation Act

A policy proposal to protect food-producing land from speculative taxation

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

Purpose

Agricultural land should be valued and taxed as agricultural land for as long as it remains in active food production.

Across Canada, farmland is increasingly being priced not only for what it can grow, but for what it might become: recreational estates, subdivisions, corporate land banks, industrial sites, data centres, logistics hubs, and other non-farm uses.

When that speculative value pushes up assessments and property taxes, the cost does not stay on a spreadsheet. It moves into the cost of food production. Farmers pay more to hold the same land. New farmers face higher barriers to entry. Family farms become harder to pass down. Food-producing land becomes easier to sell off than to keep in production.

This policy would create a protected valuation class for productive farmland, ensuring that land used for food production is assessed according to its agricultural use, not its speculative development value.

The goal is simple:

If land is feeding people, tax it as farmland. If someone wants to profit from taking it out of food production, tax the conversion.

1. Productive Farmland Valuation

Qualifying agricultural land would be assessed at a protected productive-use value.

This value would be based on factors such as:

• Soil quality.

• Agricultural productivity.

• Water access.

• Pasture, crop, or livestock capacity.

• Actual farm use.

• Regional agricultural conditions.

• Long-term food-production potential.

It would not be based on:

• Nearby housing development.

• Recreational land demand.

• Industrial speculation.

• Corporate land assembly.

• Data-centre or warehouse interest.

• Subdivision potential.

• Non-agricultural market pressure.

The purpose is to separate the value of farmland as food-producing infrastructure from the speculative value of land as a future development asset.

2. Protected Assessment Status

Once land qualifies, its agricultural assessment would remain stable and low for as long as the land remains in active agricultural use.

The protected value could be adjusted modestly for agricultural realities, such as soil productivity, farm income conditions, inflation in farm operations, or changes in land quality.

However, it could not be increased simply because surrounding land has become attractive to developers, recreational buyers, corporate investors, or non-farm users.

Farmers should not be taxed on the fantasy value of what someone else wants to build on their land.

3. Family Farm Continuity

The protected farmland valuation would transfer when the farm is passed down within a family, provided the land remains in active agricultural production.

This would include transfer to:

• Children.

• Grandchildren.

• Siblings.

• Nieces or nephews.

• Other family successors involved in maintaining the farm operation.

The purpose is to protect intergenerational farm continuity.

A family should not be forced to sell productive farmland simply because the market around them has decided the land is worth more as something other than a farm.

4. Sale to Another Farmer

The protected valuation should also be able to transfer to a non-family buyer when the land is sold as an active farm to another qualifying farmer or farm family.

This is important because not every farmer has children or relatives able to take over the farm.

The policy should not trap retiring farmers. It should protect farmland.

A sale to another active farmer should preserve the protected agricultural valuation, provided the buyer commits to keeping the land in agricultural use for a defined period.

A reasonable commitment period could be 10 to 20 years, depending on provincial law and local agricultural conditions.

5. Conversion Trigger

The protected valuation would end when the land is no longer being used as productive farmland.

A conversion trigger would apply if the land is sold for non-agricultural use, rezoned, or substantially repurposed for uses such as:

• Residential subdivision.

• Recreational estate development.

• Commercial or industrial development.

• Corporate land banking.

• Data centres.

• Warehousing or logistics facilities.

• Resource extraction.

• Speculative holding.

• Non-farm investment use.

• Any other purpose that removes the land from food production.

A conversion trigger should also apply where the owner enters into a long-term lease, purchase option, development agreement, land assembly agreement, beneficial-control arrangement, financing arrangement, secured interest, side agreement, or other contract that gives another party effective control over the land or its future non-agricultural use, even if legal title has not yet changed hands.

Approval of rezoning, subdivision, development permits, area-structure plans, servicing agreements, or other land-use changes that materially increase the land’s non-agricultural value should trigger an immediate review of protected farmland status.

Where the approved change removes the land from food production, enables non-agricultural development, materially increases non-agricultural value, or creates a clear development pathway, the farmland conversion tax should apply even if the land has not yet been sold.

Where only part of a protected farmland parcel is converted to non-agricultural use, the farmland conversion tax should apply to the converted portion, and the remaining land should be reviewed to determine whether it still qualifies for protected agricultural valuation.

The conversion trigger would not punish farmers for selling. It would apply when the land leaves agriculture or when another party gains effective control over the land for a non-agricultural purpose.

6. Farmland Conversion Tax

When protected farmland is converted to a non-farm use, a farmland conversion tax would apply.

This tax would be based on the gap between the protected agricultural value and the actual market value or sale price at the time of conversion.

For example:

• Protected agricultural value: $500,000.

• Sale price for development: $2,500,000.

• Conversion gain: $2,000,000.

A percentage of that conversion gain would be taxed on a sliding scale based on how long the current owner held the land, with short-term speculative ownership taxed at a much higher rate than long-term farm stewardship. (For example, land converted after two years or less of ownership could face a conversion tax of up to 90% of the gain, while land held for ten years or more could face a lower rate, such as 50%, with the rate declining gradually based on years of ownership.)

Transfers between related parties, family-controlled corporations, trusts, partnerships, nominees, beneficial owners, or other associated entities should not reset the ownership clock for the purpose of calculating the farmland conversion tax.

For the purpose of the sliding-scale conversion tax, the holding period should be based on the earliest date the land came under the ownership, control, or beneficial interest of the current owner or any associated person or entity.

If protected farmland is sold and then resold, rezoned, or converted to non-agricultural use within five years, a portion of the conversion gain should be shared with the previous agricultural landholder. (For example, 50% of the conversion gain could be returned to the previous landholder when the land is converted within five years of purchase, with the remaining taxable gain subject to the farmland conversion tax.)

This would discourage speculative buyers from acquiring farmland at agricultural value, misrepresenting their intentions, and then quickly profiting from development, corporate land assembly, or non-farm resale.

The purpose is to ensure that the people profiting from the removal of farmland from food production pay a portion of the public cost of that conversion.

Farmers should not carry the tax burden created by speculation. Developers, investors, and non-farm buyers who profit from conversion should.

Share

7. Use of Conversion Tax Revenue

Revenue from the farmland conversion tax should be dedicated to food-system protection, not absorbed into general revenue.

Eligible uses could include:

• Supporting young and new farmers.

• Farmland preservation funds.

• Local food infrastructure.

• Irrigation and water resilience.

• Soil conservation.

• Small farm succession programs.

• Agricultural disaster support.

• Public food-security programs.

• Municipal tax stabilization in rural areas.

If farmland is removed from production, some of the private profit from that conversion should be used to protect the remaining food system.

8. Anti-Abuse Rules

The policy would require strong anti-abuse provisions.

To qualify for protected farmland valuation, landowners would need to demonstrate genuine agricultural use.

Eligibility should be based on a combination of agricultural production, farm income, acreage use, livestock or crop activity, soil or pasture management, and operational records. The test should be flexible enough to include small farms, new farmers, mixed farms, Indigenous food production, market gardens, drought years, disaster recovery, illness, disability, and succession transitions, while still excluding token or artificial agricultural activity used only to obtain a lower tax rate.

Possible requirements could include:

• Active farm operation.

• Farm income reporting.

• Agricultural production records.

• Lease transparency.

• Beneficial ownership disclosure.

• Disclosure of the real beneficial owners and controlling interests behind any corporation, trust, partnership, lease, or holding structure connected to the land.

• Disclosure of long-term leases, purchase options, development agreements, land assembly agreements, financing arrangements, secured interests, side agreements, and other arrangements that may transfer effective control of the land.

• Disclosure of rezoning applications, subdivision approvals, development permits, servicing agreements, and other land-use changes that may affect protected farmland status.

• A minimum agricultural-use threshold based on production, land use, farm activity, and operational records.

• Limits on shell-company ownership.

• Limits on speculative land holding.

• Restrictions on fake or token agricultural activity.

• Penalties, back taxes, interest, and loss of eligibility for misrepresentation or abuse.

Protected valuation should not be available where the true ownership, control, financing, lease structure, or development interest in the land is hidden through corporations, trusts, partnerships, nominees, long-term leases, purchase options, side agreements, or other holding arrangements.

A family farm designation should require meaningful participation by family members or qualifying farm successors in the actual operation, management, risk, and decision-making of the farm.

Protected family-farm status should not apply where the land is merely owned by a family while the agricultural work, management, financial risk, and operational control are entirely contracted out to outside operators, management firms, corporate tenants, or other third parties.

Meaningful participation may include physical labour, day-to-day farm management, production planning, livestock care, crop decisions, equipment operation, marketing, bookkeeping, maintenance, succession training, or other substantial contributions to the farm operation.

Contracted services should still be allowed for specialized, seasonal, occasional, or necessary farm work, including harvesting, seeding, veterinary care, equipment repair, transport, spraying, fencing, accounting, custom work, accessibility-related support, temporary illness coverage, or emergency labour.

Temporary reliance on outside labour or management due to illness, disability, death, estate transition, disaster, equipment failure, or succession planning should not automatically disqualify a farm, provided the land remains in agricultural production and the family or qualifying successor retains genuine operational control.

However, the core operation of the farm must remain substantially directed, controlled, and economically carried by the farm family or qualifying farm successor. The protected designation should not be available to passive landholders whose main role is ownership rather than farming.

The test should distinguish between a family that uses contractors to keep farming and a family that uses farming as a label to hold land cheaply while waiting for development value to rise.

A corporation, investor, or developer should not be able to buy farmland, run a minimal or artificial agricultural activity, and hold the land at a low tax rate while waiting for its development value to rise.

Where protected status was obtained or maintained through misrepresentation, artificial farming activity, hidden beneficial ownership, undisclosed development intent, undisclosed control arrangements, false reporting, or token agricultural activity, the owner should owe back taxes, conversion taxes, penalties, and interest.

Repeat or serious violations should result in loss of eligibility for protected farmland valuation for a defined period.

Protected farmland valuation must be for food production, not land speculation.

9. Municipal Protection

Municipalities should not be financially punished for protecting agricultural land.

If farmland is assessed at a lower productive-use value, municipalities may worry about reduced property-tax revenue. The policy should include a municipal stabilization mechanism so rural governments are not forced to encourage development simply to maintain their tax base.

This could include:

• Provincial transfers.

• A share of conversion-tax revenue.

• Farmland protection grants.

• Infrastructure support for agricultural communities.

• Regional food-security funding.

Protecting farmland should not mean starving rural municipalities of revenue.

10. Public Registry and Transparency

A public registry should identify land enrolled in the protected farmland valuation system.

The registry should include:

• General location.

• Protected status.

• Agricultural use category.

• Date of enrollment.

• Conversion history, if applicable.

• Beneficial ownership information where legally appropriate.

This would allow the public to see whether the policy is protecting active farms or being misused by land speculators.

Transparency is essential.

11. Relationship to Food Affordability

Food affordability does not begin at the grocery store.

It begins with land, water, soil, labour, energy, transportation, equipment, and the ability of farmers to keep producing food without being priced off the land.

If agricultural land is taxed as future development land, the cost of that speculation enters the food system before a seed is planted or an animal is raised.

This policy addresses one of the lowest levels of food cost: the cost of holding the land that produces the food.

A national food affordability strategy that does not protect farmland from speculative taxation is missing part of the foundation.

12. Core Principle

The core principle of this policy is simple:

Farmland should be valued for feeding people, not for the profit someone could make by ending its ability to feed people.

When land remains in food production, it should receive stable, protected agricultural valuation.

When land is converted out of agriculture, the public should recover part of the speculative gain.

This protects farmers, supports food affordability, strengthens rural communities, and recognizes agricultural land as public-interest infrastructure.

Summary

The Productive Farmland Protection and Valuation Act would:

1. Assess active farmland based on productive agricultural value, not speculative market value.

2. Keep that valuation stable while the land remains in food production.

3. Allow protected valuation to transfer within families.

4. Allow protected valuation to transfer to another qualifying farmer.

5. End protected status when land is converted to non-farm use.

6. Tax the conversion gain when farmland is sold or repurposed for development, corporate land banking, recreation, or other non-agricultural uses.

7. Use conversion-tax revenue to support farmland preservation, new farmers, food infrastructure, and rural municipalities.

8. Prevent abuse through active-use requirements, ownership transparency, and penalties.

9. Protect municipalities from revenue loss.

10. Treat farmland as food-system infrastructure, not merely real estate.

Food-producing land should not be taxed into disappearance.

If it feeds people, tax it as farmland.

If someone profits from taking it out of production, tax the conversion.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The Shared Standard Compensation Act

A Civic Sketches Policy Proposal

There is a basic test of fairness that should apply to every government.

If the cost of living has risen enough that elected officials need more money, then it has also risen enough that people receiving disability supports, income assistance, family supports, housing supplements, seniors’ benefits, and other basic-needs programs need more money too.

Governments should not be able to recognize inflation at the top while denying it at the bottom.

That is the purpose of the Shared Standard Compensation Act: to link increases in political compensation to increases in core social support programs, and to ensure that when governments reduce or freeze supports for the most vulnerable, elected officials feel the same reduction or freeze in their own compensation.

This is not about punishing politicians.

It is about ending insulation.

The Problem

Across governments, elected officials often have access to salaries, pensions, expense accounts, travel allowances, housing allowances, meal allowances, per diems, and other forms of compensation that are reviewed, adjusted, and defended as necessary for the cost of public service.

At the same time, people relying on public supports are often told to wait.

They are told the budget is tight.

They are told there is no room for increases.

They are told that benefits cannot keep pace with rent, food, utilities, transportation, disability costs, medical needs, or the rising price of simply remaining alive.

This creates a structural imbalance.

Those with the most power over public spending are insulated from the consequences of their own decisions, while those with the least power are forced to absorb the damage.

A person on disability support cannot vote themselves a raise.

A low-income senior cannot increase their housing supplement.

A parent relying on family support cannot index their own benefit to inflation.

But elected officials can debate, recommend, approve, or accept increases to their own compensation systems while leaving survival supports frozen, clawed back, or politically delayed.

That should not be acceptable.

Share

The Principle

The principle is simple:

No government should improve the financial position of elected officials while refusing to improve the financial position of people who rely on basic public supports to survive.

If elected officials receive a raise, the designated social support programs should rise by the same proportional amount.

If elected officials receive an increase to housing allowances, travel allowances, daily living allowances, or cost-of-living adjustments, the relevant support programs should also be increased.

If social supports are reduced, frozen, clawed back, or de-indexed, elected officials should experience the same proportional reduction, freeze, clawback, or de-indexing in their own compensation.

A government should not be able to impose austerity downward while protecting comfort upward.

The Policy

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

The Shared Standard Compensation Act would require that any increase to the salary, pensionable compensation, living allowance, housing allowance, travel allowance, meal allowance, per diem, or cost-of-living adjustment of elected officials automatically trigger an equal or greater proportional increase to designated social support programs.

These programs could include, depending on the jurisdiction:

• disability income supports

• income assistance

• family and child benefits

• seniors’ low-income supports

• caregiver supports

• housing supplements

• basic-needs allowances

• other legislated social support programs intended to cover essential living costs

The exact list would vary by province, territory, municipality, or federal program. The principle would remain the same.

If political compensation rises by 3%, designated social supports must rise by at least 3%.

If elected officials receive a 5% increase to housing-related allowances, housing-related supports for low-income recipients must increase by at least 5%.

If elected officials receive increases to meal, travel, or daily living allowances, the basic-needs portions of social support programs must be adjusted by the same proportional amount.

The Reduction Rule

The policy should also work in reverse.

If a government reduces, freezes, claws back, or de-indexes social supports, then elected officials must experience the same proportional reduction, freeze, clawback, or de-indexing in their own compensation and allowances.

If disability supports are frozen for a year, elected officials’ salaries and allowances should be frozen for that year as well.

If income supports are cut by 2%, elected officials’ compensation should be cut by 2%.

If housing supports are reduced, elected officials’ housing allowances should be reduced proportionally.

If basic-needs benefits are de-indexed from inflation, elected officials’ compensation should lose the same indexing protection.

The point is not to encourage cuts at the bottom. The point is to make sure governments cannot impose hardship on the most vulnerable while shielding themselves from the same policy choices.

Shared austerity should mean shared austerity.

Shared prosperity should mean shared prosperity.

Legislative Model

A government shall not approve, authorize, or implement an increase to the salary, pensionable compensation, housing allowance, living allowance, travel allowance, meal allowance, per diem, or cost-of-living adjustment of elected officials unless designated social support programs are increased by an equal or greater proportional amount within the same fiscal year.

No compensation increase for elected officials shall take effect until the corresponding social support adjustment has been enacted, funded, and scheduled for payment.

Where a government reduces, freezes, claws back, limits, suspends, or de-indexes designated social support programs, the salary, pensionable compensation, housing allowance, living allowance, travel allowance, meal allowance, per diem, and cost-of-living adjustments of elected officials shall be reduced, frozen, clawed back, limited, suspended, or de-indexed by an equal or greater proportional amount for the same period.

Reductions to elected officials’ compensation shall not be used to justify, require, or trigger reductions to social support programs. The upward link shall be automatic. The downward link shall apply only when governments choose to reduce, freeze, claw back, or de-index supports for people receiving designated benefits.

Share

Why This Matters

People receiving social supports are often the least able to respond to rising costs.

They cannot simply absorb a rent increase.

They cannot always take on extra work.

They may not have savings.

They may already be choosing between food, medication, transportation, heating, school costs, disability needs, and basic participation in community life.

For many people, a frozen benefit is not neutral. It is a cut.

A support payment that does not keep up with inflation means less food, less housing security, less access to care, less mobility, less dignity, and more stress placed on families, charities, shelters, emergency rooms, schools, and local communities.

Meanwhile, political compensation is often discussed in terms of fairness, recruitment, inflation, travel costs, housing costs, and the realities of doing the job.

Those realities may be valid.

But they are not unique to politicians.

If the price of food matters to an elected official, it matters to a person on income assistance.

If housing costs matter to an elected official, they matter to a low-income senior.

If travel costs matter to an elected official, they matter to a disabled person trying to get to appointments.

If inflation matters at the top, it matters more at the bottom.

Safeguards

The Shared Standard Compensation Act would need clear safeguards.

First, governments should not be able to avoid the policy by renaming compensation. A raise should not escape review simply because it is called an allowance, adjustment, stipend, modernization, reimbursement, supplement, or expense update.

Second, social support increases should be automatic. They should not require a separate political vote that can be delayed, watered down, or defeated.

Third, the policy should establish a floor, not a ceiling. Governments should always be free to increase social supports by more than the proportional increase given to elected officials.

Fourth, cuts to political compensation should never trigger cuts to social supports. The reverse link should only apply when governments choose to reduce or freeze support programs first.

Fifth, the policy should apply across the full compensation package, not merely base salary. Housing allowances, daily living allowances, travel allowances, meal allowances, per diems, and cost-of-living adjustments all reflect the cost of living. They should all be part of the calculation.

The Democratic Argument

This policy would not eliminate disagreement over budgets.

It would not solve poverty by itself.

It would not replace the need for adequate disability supports, housing policy, food security, seniors’ benefits, employment standards, public health care, or serious anti-poverty measures.

But it would change the political incentives.

It would force governments to confront the double standard that often sits at the centre of public budgeting.

When elected officials are financially insulated from the effects of inflation, austerity, and underfunded social programs, they can make decisions that do not meaningfully touch their own lives.

The Shared Standard Compensation Act would make that harder.

It would say: if you believe there is room for a raise at the top, there must be room for relief at the bottom.

And if you believe there must be restraint at the bottom, then that restraint must begin with you.

Plain-Language Summary

If politicians get a raise, people on basic social supports should get a raise too.

If politicians receive higher housing, meal, travel, or living allowances because costs have gone up, then the supports people rely on for housing, food, transportation, and daily survival should increase by the same proportion.

If governments freeze, cut, claw back, or de-index social supports, politicians should experience the same freeze, cut, clawback, or de-indexing in their own compensation.

No government should be able to protect comfort at the top while imposing hardship at the bottom.

Closing Thought

This proposal is built on a simple idea: political leadership should share the economic reality it creates.

If the cost of living justifies more money for elected officials, it justifies more support for the people least able to absorb those costs.

If austerity is necessary, it should not be aimed only at those with the least power to resist it.

A government that can afford to adjust political compensation can afford to adjust survival supports.

And if it cannot do both, it should not do the first.

It is water, electricity, land, noise, heat, taxes, subsidies, emergency planning, public consultation, privacy, artificial intelligence, sovereignty, ownership, and accountability gathered inside one fence.

Over the past while, there has been a sudden and growing interest in data center development. In Alberta, across Canada, and around the world, communities are being asked to consider projects that are often described with the language of innovation, investment, digital infrastructure, economic development, and the future.

But the public conversation often moves faster than the public understanding.

That is a problem.

Because data centers are not just buildings full of servers. They are large-scale industrial and digital infrastructure projects with physical, economic, environmental, and democratic consequences. They connect to public grids. They may draw on local water systems. They occupy land. They produce heat. They can create continuous sound. They require backup systems, emergency planning, roads, transmission infrastructure, cooling systems, public approvals, and, in many cases, public support.

And yet, too often, communities are expected to respond to these proposals without having the full language needed to question them.

That is why I created The Data Center Anarchists’ Handbook: A Public Interest Guide to Data Center Development.

This handbook began as something smaller.

As an author, I spend a lot of time researching the systems that sit behind the stories I write: artificial intelligence, technology, climate, public infrastructure, environmental pressure, corporate power, and the places where all of those things collide. Some of that research was originally meant to feed into future fiction. Some of it came from the same questions that sit behind The Symbiosis Sequence, my conceptual science-fiction series about technology, humanity, artificial intelligence, and the systems we build before we fully understand them.

But the real world kept catching up.

The questions were no longer only useful as background for fiction. They were becoming necessary in public.

So I pulled together my research notes, policy concerns, and the questions I kept asking, and the handbook took life.

Share

This Is Not an Anti-Data-Center Manifesto

The handbook is not an argument that all data centers are bad.

It is not a technical manual.
It is not a legal opinion.
It is not an engineering assessment.
It is not a regulatory submission.
It is not a substitute for local expertise, Indigenous governance, public consultation, environmental review, municipal planning, utility analysis, or legal advice.

It is a handbook of questions.

What is actually being proposed?

Who benefits?

Who pays?

Who decides?

What happens to water?

What happens to electricity demand?

What happens to nearby homes, farms, animals, wetlands, wildlife corridors, and future land use?

What public subsidies are involved?

Who owns the land, the building, the servers, and the project company?

What happens if the facility changes tenants, expands, is sold, or shuts down?

What is the public being asked to commit to before it fully understands the consequences?

These are not fringe questions. They are basic public-interest questions.

A community cannot meaningfully consent to what it has not been allowed to understand.

What the Handbook Covers

The handbook is organized as a civic reference tool. It is designed so readers can open it to the issue they care about and begin there.

It includes sections on:

• what is actually being proposed

• public benefit and private gain

• decision-making authority

• public consultation and consent

• water use

• electricity and grid burden

• land use and community fit

• sound, vibration, and light

• heat, cooling, and waste heat

• air emissions and backup systems

• animals, plants, agriculture, and ecosystems

• cumulative impacts

• data sovereignty

• ownership, tenants, and corporate structure

• cybersecurity and critical infrastructure

• privacy, surveillance, and public data

• jobs and economic claims

• tax incentives and public subsidies

• infrastructure costs and ratepayer burden

• decommissioning and exit plans

• monitoring, reporting, and enforcement

• emergency planning

• conditions, clawbacks, and public remedies

• community benefit agreements

• artificial intelligence

• public hearing questions

• documents communities should request

Each chapter follows a repeated structure: a plain-language explanation of the issue, core questions, red flags, documents or information communities should ask for, and a public-interest standard.

The repetition is intentional.

This is not a narrative book. It is a tool. Most people will not read it from beginning to end. They will come to it because they are worried about water, or electricity, or noise, or farmland, or subsidies, or public consultation, or AI infrastructure. The structure is meant to let them find what they need quickly.

Why There Are No Citations Inside the Handbook

There are no references in the handbook by design.

That may seem unusual, especially for a document built from research, but the choice is intentional. Laws change. Projects change. technologies change. Cooling systems change. AI workloads change. Utility agreements change. Water conditions change. Ownership structures change. Public claims change.

What matters in one jurisdiction may not apply in another.

Rather than pretending the handbook can freeze a fast-moving issue in place, it gives readers a framework for inquiry.

If you can ask the question, you can take the next step and ask who holds the answer: the utility regulator, the water licensing authority, the environmental review agency, the municipality, the public health authority, the emergency services department, Indigenous governments, peer-reviewed research, public records, or independent journalism.

The goal is not to replace research.

The goal is to make research possible.

Share

Why This Matters Now

Data centers are often presented as inevitable.

We are told they are part of the future. We are told they are needed for cloud computing, artificial intelligence, health systems, education, business, research, public services, and modern life.

Some of that may be true.

But inevitability is not a substitute for public accountability.

If a project requires public land-use approval, public infrastructure, public water systems, public grid capacity, public subsidies, public emergency services, public trust, or public tolerance of long-term impacts, then the public has the right to ask hard questions before approval.

Not after.

Not once the land has been assembled.

Not once the utility agreements are signed.

Not once tax incentives are in place.

Not once the first phase is approved and every future phase is described as merely administrative.

Before.

Communities deserve to know what is being built, how large it can become, who controls it, what it will use, what it will cost, what it will change, what it will leave behind, and whether promised benefits are real, measurable, local, durable, and enforceable.

A Free Public Resource

The Data Center Anarchists’ Handbook is being released as a free public document.

It is available as a PDF and EPUB through Zenodo and the Internet Archive.

It is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. That means it can be copied, shared, quoted, adapted, translated, and redistributed, including for commercial purposes, as long as appropriate credit is given, changes are indicated, and adaptations are released under the same licence.

I chose that licence because this is meant to be used.

Use it in public hearings.

Use it in council meetings.

Use it in classrooms.

Use it in journalism.

Use it in community groups.

Use it when reading a proposal.

Use it when writing to elected officials.

Use it when asking for documents.

Use it when someone says, “The project will use minimal water,” or “The grid can handle it,” or “The impacts will be managed,” or “The benefits will be significant,” or “Those details will be finalized later.”

Those may be answers.

They may also be invitations to ask better questions.

The Public Interest Standard

The heart of the handbook is simple:

No community should be asked to approve a data center it cannot clearly describe.

No community should be asked to approve a project without knowing who benefits, who pays, who decides, who monitors, who enforces, and what happens if the promises are not kept.

No community should be asked to trade water, power, land, quiet, public money, public infrastructure, privacy, sovereignty, or future options for vague assurances of digital progress.

Data centers may be part of our future.

But if they are, the public must have the right, the language, and the tools to ask what that future will cost — and who will be expected to pay for it.

The Data Center Anarchists’ Handbook is my contribution to that conversation.

It is free.
It is public.
It is meant to be shared.

They do not always appear as direct cheques. Sometimes they come as tax incentives, royalty reductions, low-interest loans, loan guarantees, land discounts, infrastructure commitments, utility discounts, or other forms of public support that are harder for the public to see and harder to measure.

These subsidies are often announced with promises of jobs, investment, growth, competitiveness, or economic stability. Sometimes those promises may be real. Sometimes the public return may justify the public cost.

But that should never be assumed.

At all three levels of government — municipal, provincial, and federal — corporate subsidies should be subject to the same basic standard: public money must produce public value.

A town that gives up tax revenue to attract a company should be able to prove the community benefited.

A province that lowers royalties, offers tax incentives, or supports a sector should be able to prove the public received more than it surrendered.

A federal government that provides grants, loans, guarantees, or industry supports should be able to prove that the benefit stayed in the country and did not simply flow outward to shareholders, parent companies, or private profit.

This is not an argument that every corporate subsidy is wrong.

It is an argument that every corporate subsidy should be accountable.

If governments can audit social programs, schools, hospitals, municipalities, workers, small businesses, and individual taxpayers, then they can audit the public money given to corporations.

The principle is simple:

Public money should produce public return.

The following proposal outlines a four-year review model that would require governments to evaluate corporate subsidies regularly, measure whether promised benefits were actually delivered, identify long-term public costs, and reform, reduce, suspend, or end subsidies that no longer serve the public interest.

These proposals are not party platforms or final answers; they are working drafts meant to invite discussion, challenge, and refinement.

They are also written with the understanding that not every policy belongs at the same level of government. Some proposals may be best suited to federal legislation. Others may belong at the provincial, territorial, municipal, or local level. In some cases, the strongest approach would involve cooperation across multiple levels of government, with each taking responsibility for the parts within its authority.

Where responsibilities overlap, cooperation should be treated as a strength, not an obstacle. Federal, provincial, territorial, municipal, Indigenous, and local governments all have roles to play in building policies that are practical, enforceable, and responsive to real public needs.

If this idea seems worth debating, please share it with others, add your own perspective, and help widen the conversation beyond slogans.

The Public Return on Corporate Subsidies Act

A Four-Year Review Model for Corporate Subsidies

This policy is published under the Creative Commons Attribution 4.0 International Licence (CC BY 4.0).

You are free to copy, share, adapt, translate, and build upon this policy for any purpose, including use by governments, organizations, advocates, researchers, and members of the public, provided appropriate credit is given to Lawrence Nault and any changes are clearly identified.

Purpose

Governments regularly provide financial support to corporations and corporate sectors through direct grants, tax incentives, royalty reductions, low-interest loans, loan guarantees, land discounts, infrastructure support, utility discounts, procurement advantages, and other forms of public assistance.

These subsidies are often justified as necessary for job creation, economic development, investment attraction, industry stability, or national competitiveness.

However, once created, subsidies can become permanent features of the economy without regular proof that they continue to serve the public interest.

The Public Return on Corporate Subsidies Act would require every major corporate subsidy to be reviewed on a four-year cycle to determine whether it is producing a public return greater than its public cost.

Core Principle

Corporate subsidies should not be treated as entitlements.

They should be treated as public investments.

And like any public investment, they should be measured, audited, justified, and, where necessary, reduced, redesigned, or ended.

Public money given to private industry must produce public benefit.

What Would Be Reviewed

The review would apply to all major forms of corporate subsidization, including:

• Direct cash grants

• Tax credits and tax exemptions

• Royalty reductions

• Low-interest or forgivable loans

• Loan guarantees

• Publicly funded infrastructure primarily benefiting private industry

• Land discounts or below-market leases

• Sector-specific regulatory exemptions

• Government-backed insurance or risk protection

• Procurement advantages

• Training subsidies tied to private employers

• Energy, water, or utility discounts

• Cleanup, closure, or remediation costs transferred to the public

The purpose is not to assume every subsidy is bad.

The purpose is to require proof that each subsidy continues to serve the public interest.

The Four-Year Review Cycle

Every corporate subsidy would be reviewed at least once every four years.

Each review would examine whether the subsidy has delivered the benefits promised when it was created or renewed.

The review would apply several public-interest tests.

1. The Job Creation Test

The first question is whether the subsidy created real, stable, fairly paid employment.

This review would consider:

• The number of full-time jobs created

• The number of part-time, temporary, or contract jobs created

• The average wage of those jobs

• The duration of those jobs

• Whether the jobs remained after the subsidy ended

• Whether the jobs likely would have existed without the subsidy

• Whether the subsidy merely shifted jobs from another region, sector, or employer

A subsidy should not be considered successful simply because jobs were promised.

It should be considered successful only if those jobs were delivered, sustained, and worth the public cost.

2. The Public Revenue Test

The second question is whether the subsidy generated more public revenue than it cost.

This review would consider:

• Corporate taxes generated

• Payroll taxes generated

• Income taxes paid by workers

• Local, provincial, and federal tax effects

• Secondary economic activity

• Reduced need for public support programs, if applicable

• Long-term revenue projections

If a subsidy costs more than it returns, the public deserves to know why it should continue.

3. The Domestic Retention Test

The third question is whether the economic benefit remains in the country, province, or region that provided the subsidy.

This review would examine:

• How much profit remains locally

• How much is transferred to foreign or out-of-province shareholders

• How much is paid to parent companies

• How much is used for executive compensation

• How much is used for dividends or stock buybacks

• Whether local suppliers, workers, and communities actually benefit

A subsidy should not be judged only by whether a corporation became more profitable.

The real question is whether the public received enough benefit in return.

4. The Public Liability Test

The fourth question is whether the subsidized company or sector is leaving behind public costs greater than the value of the subsidy.

This review would consider:

• Environmental cleanup costs

• Abandoned infrastructure

• Abandoned oil and gas wells

• Tailings, waste, or emissions liabilities

• Water contamination

• Public health impacts

• Road, grid, water, and municipal infrastructure strain

• Long-term monitoring and enforcement costs

• Future legal, closure, or remediation costs

No subsidy should be judged only by short-term economic activity while ignoring long-term public liability.

If a company profits today but leaves the public to pay tomorrow, the subsidy has not created true public value.

5. The Completion and Clawback Test

The fifth question is whether the public can recover its money if the company fails to meet its obligations.

Every subsidy agreement should include enforceable clawback provisions.

Subsidies should be returned, in whole or in part, if:

• Promised jobs are not created

• Promised jobs disappear before the agreed period ends

• The company leaves the jurisdiction

• The project is abandoned

• The company sells subsidized assets for private gain

• The company enters insolvency after receiving support

• The company violates environmental, labour, tax, or reporting obligations

• The company closes before completing the subsidy agreement

Public money should not become a private reward for promises that were never fulfilled.

Required Public Reporting

Every four-year review should produce a public report.

That report should include:

• The total value of the subsidy

• The original purpose of the subsidy

• The companies, industries, or sectors receiving support

• Jobs promised versus jobs delivered

• Wages and duration of those jobs

• Public revenue generated

• Economic benefit retained locally

• Economic benefit transferred outside the jurisdiction

• Environmental and infrastructure liabilities created

• Cleanup, closure, or remediation obligations

• Compliance with labour, tax, and environmental rules

• The final recommendation

The recommendation would fall into one of five categories:

1. Continue

2. Reform

3. Reduce

4. Suspend

5. Terminate and recover funds where possible

Confidential business information could be protected where genuinely necessary, but the public must still be able to determine whether public money is producing public benefit.

Share

Built-In Sunset Clause

Every new corporate subsidy should include a sunset clause.

That means the subsidy would automatically expire unless renewed after review.