WeGo.ca Website Developers Inc. – Website Design & Management.

Privacy Compliance for Agricultural Societies

privacy in agricultural societies

Navigating PIPEDA Requirements

As both a website developer with over 25 years of experience and a fair volunteer for more than 35 years, I’ve had the unique opportunity to bridge two worlds that don’t often intersect. This perspective has given me special insight into the privacy challenges Agricultural Societies face in our increasingly digital world.

A Recent Conversation That Sparked Important Questions

Recently, I was working with Glenda Simeone from the Caledon Fair on designating a Privacy Officer for their website. During our discussion, she raised an interesting point: “While you, as a business, MUST comply, the Ag Society, as a charitable organization is not actually required to do so.”

This got me thinking about the broader implications of privacy compliance for Agricultural Societies across Ontario. Glenda’s concern reflected what many fair organizations are wondering: Do we really need to worry about privacy regulations?

Her email continued with a crucial insight: “We have young volunteers and Ambassadors and we want to protect them, as well as the Board, members and customers from harm due to any inadvertent release of information.”

This perspective perfectly captures why privacy matters, regardless of legal requirements.

Understanding PIPEDA for Agricultural Societies

First, let me be clear: I am not a lawyer. My knowledge comes from working with organizations like Termageddon and UserCentrics, plus my extensive experience developing websites for Agricultural Societies.

That said, there’s a common misconception that needs addressing. Many Agricultural Societies assume their charitable or not-for-profit status automatically exempts them from PIPEDA (Personal Information Protection and Electronic Documents Act). The reality is more nuanced.

PIPEDA applies to organizations collecting personal information during “commercial activities.” For Agricultural Societies, this can include:

  • Selling tickets to fairs and events
  • Accepting vendor registrations with payment
  • Selling memberships
  • Renting facilities
  • Managing paid exhibitions

If your Agricultural Society engages in any of these activities, PIPEDA likely applies to those specific functions, regardless of your overall not-for-profit status.

Who Are We Protecting?

When we talk about privacy at Agricultural Societies, we’re protecting:

  • Young volunteers and Ambassadors who may share personal information for programs
  • Board members whose contact information might be publicly listed
  • Fair visitors who purchase tickets online or register for events
  • Vendors and exhibitors who provide business and personal details
  • Donors and supporters who share financial information

Each of these groups trusts your organization with their personal information, expecting it will be handled responsibly.

Building Goodwill Through Voluntary Compliance

Even in scenarios where an Agricultural Society might technically fall outside PIPEDA’s scope, I’ve consistently advised my clients that voluntary compliance is valuable. Here’s why:

  1. It demonstrates respect for your community – Privacy protection shows you value people’s rights
  2. It prepares you for future regulatory changes – Privacy laws continue to evolve and expand
  3. It aligns with your organizational values – Fair and equal treatment of all stakeholders
  4. It builds trust – People are increasingly concerned about how their data is used

As I explained to Glenda: “I like to recommend that by complying, even when not required, we are providing a more inclusive service. We build goodwill with our community by showing that we care about their rights and that we treat everyone fairly and equally.”

Practical Steps for Agricultural Societies

Based on my experience working with numerous Agricultural Societies, here are key steps to enhance your privacy practices:

1. Designate a Privacy Officer

Every Agricultural Society should have someone responsible for privacy matters. This role:

  • Serves as the point of contact for privacy questions
  • Helps ensure compliance with relevant regulations
  • Coordinates responses to any privacy incidents
  • Is typically named in your privacy policy

The Privacy Officer doesn’t need specialized training—it could be a board member, staff person, or volunteer with good organizational skills and a willingness to learn.

2. Create a Comprehensive Privacy Policy

Your website should have a clear privacy policy that explains:

  • What personal information you collect
  • How you use and protect it
  • Who your Privacy Officer is (contact information)
  • How individuals can access their personal information
  • Your cookie usage (if applicable)

3. Review Your Data Collection Practices

Take inventory of the personal information your Agricultural Society collects:

  • Membership forms
  • Volunteer applications
  • Vendor registrations
  • Online contact forms
  • Ticket sales
  • Donation records

For each type of information, ask: Do we really need this? How are we protecting it? Have we obtained proper consent?

4. Implement Basic Security Measures

Privacy protection isn’t just about policies—it’s about practices:

  • Use strong passwords for digital systems
  • Limit access to personal information
  • Secure physical records in locked storage
  • Use reputable service providers for your website and data storage
  • Regularly review and update your security measures

How I Can Help

With my dual background in website development and Agricultural Societies, I’m uniquely positioned to help your organization navigate privacy compliance. My services include:

  • Creating compliant website privacy policies
  • Setting up proper cookie notices
  • Implementing secure contact forms
  • Training board members and volunteers on privacy basics
  • Ongoing support for privacy-related questions

Whether you need comprehensive privacy compliance or simply have questions about your website’s privacy practices, I’m glad to help. My experience spans over 25 years of working with Agricultural Societies, creating websites and providing reliable hosting, maintenance, and security.

Final Thoughts

Privacy compliance shouldn’t be viewed as a burden but as an opportunity to demonstrate your commitment to protecting the people who make your fair successful. As the digital landscape continues to evolve, Agricultural Societies that prioritize privacy will be better positioned to maintain community trust and adapt to future requirements.

If you’d like to discuss how I can help your Agricultural Society with privacy compliance or other website needs, please don’t hesitate to reach out.

Disclaimer: While I have extensive experience with website development and privacy implementation, I am not a lawyer. For legal advice specific to your situation, please consult a qualified legal professional.

 

Want To Know More About PIPEDA Compliance for Agricultural Societies in Ontario?

The following text is a deep dive using AI to research if an Ag Society must have a privacy policy on their website. Is a cookie policy also a requirement? Are there any other criteria?

PIPEDA Compliance for Agricultural Societies in Ontario

Agricultural Societies in Ontario are often non-profit organizations, but this does not automatically exempt them from PIPEDA. PIPEDA (Personal Information Protection and Electronic Documents Act) is Canada’s federal private-sector privacy law, and it applies to any organization that collects, uses, or discloses personal information in the course of commercial activitiescba.orgcba.org. The nature of the activity – not the tax status of the organization – determines PIPEDA’s application. In fact, PIPEDA’s definition of “commercial activity” explicitly includes selling, bartering or leasing membership, donor or fundraising listscba.org. The Office of the Privacy Commissioner of Canada (OPC) has stated that “whether or not an organization operates on a non-profit basis is not conclusive in determining the application of the Act”cba.org.

For an Ontario Agricultural Society, this means if you engage in any commercial transactions involving personal information, PIPEDA likely applies. Examples might include selling tickets or memberships, running a fair with paid admission/vendors, or renting facilities – all of which involve personal data (names, contact info, payment details) in a commercial context. Even if most activities are charitable or educational, any commercial component (e.g. selling a mailing list of exhibitors or donors) would trigger PIPEDA for those activities. In provinces like Ontario (which has no general private-sector privacy law of its own), PIPEDA applies by default to such commercial data practices. If PIPEDA does apply, the organization must meet its requirements for handling personal information.

Requirement for a Privacy Policy on the Website

Yes – if PIPEDA applies, an Agricultural Society should have a clear privacy policy, ideally posted on its website. PIPEDA is built on 10 Fair Information Principles, one of which is Openness. The law requires organizations to be transparent about their personal data practices:

“An organization shall make readily available to individuals specific information about its policies and practices relating to the management of personal information.”​laws-lois.justice.gc.ca

In practice, this means you must disclose how you collect, use, and protect personal information. A common way to comply is to publish a Privacy Policy on your website (or otherwise provide it to people). PIPEDA even notes that organizations may provide “online access” to information about their privacy practices​laws-lois.justice.gc.ca.

A Privacy Policy for an Agricultural Society should outline things like what personal information you collect (e.g. member or volunteer names, addresses, emails, event registrations), the purposes for collection, how consent is obtained, how information is used and disclosed, and contact information for questions or complaints. PIPEDA’s Openness principle specifies that the information made available should include the name or title of the person accountable for privacy (a privacy officer), how an individual can access their own information, a description of the types of information held and its uses, and any brochures or other materials explaining the organization’s privacy practices​laws-lois.justice.gc.calaws-lois.justice.gc.ca. Essentially, a public-facing Privacy Policy is expected so that individuals know how their personal data is handled and how to contact the organization about privacy issues.

It’s worth noting that this isn’t just a formality – having a Privacy Policy is a legal requirement under PIPEDA’s openness and accountability duties, not merely a best practice. Even small nonprofits engaged in commerce are expected to be transparent. Many Agricultural Societies in Ontario already post privacy policies referencing PIPEDA compliance​woodstockfairgrounds.com, reflecting the understanding that they need to adhere to Canadian privacy laws.

Cookie Policy and Online Tracking Requirements

Many Agricultural Society websites use cookies (for example, for site analytics or social media integration). Unlike the EU, Canada does not have a law specifically dedicated to cookies. Instead, cookies are covered under general privacy law (PIPEDA) and Canada’s anti-spam law for certain aspects​lexology.com.

Under PIPEDA, data collected via cookies can be considered personal information if the cookie can identify an individual (e.g. tracking a user’s device or behavior). The OPC has clarified that information collected through tracking cookies used for online behavioral advertising “will generally constitute personal information” subject to PIPEDA​fasken.comfasken.com. This means if your site’s cookies gather any data that could potentially identify or profile a visitor (for instance, via IP addresses, login tokens, or unique identifiers), then PIPEDA’s rules on consent apply.

PIPEDA requires organizations to obtain meaningful consent for the collection, use, or disclosure of personal information. In the context of cookies, this typically means you should inform users about what data your cookies collect and why, and get their consent – which can be implied consent in some cases. The OPC’s guidelines allow implied consent for cookies used in online advertising or analytics provided that certain conditions are met: users must be informed at or before the time of collection about what is happening in plain language, and given an easy ability to opt-out of non-essential cookies, and the information collected should not be sensitive​fasken.com. In other words, transparency is key – a website should have a clear notice (for example, a banner or a section in the privacy policy) explaining its use of cookies and offering choices if appropriate. If cookies are used for anything beyond what a user would reasonably expect (such as purely functional purposes), it’s safer to obtain explicit consent via a notice or pop-up.

Canada’s Anti-Spam Legislation (CASL) also touches on cookies. CASL generally requires express consent to install software on someone’s device, but it deems consent for cookies in many cases. Specifically, CASL regulations state that a person is considered to have consented to cookies if their behavior implies it – for example, if they have not disabled cookies in their browser​crtc.gc.ca. (If a user has disabled cookies, you do not have consent to place them​crtc.gc.ca.) This means that under CASL, you typically don’t need a user to click “I agree” for standard cookies, so long as users have been given information and a choice (i.e. they could refuse by changing browser settings). However, because what constitutes adequate implied consent can be uncertain, the practical advice is to have a brief cookie notice or include cookie details in your privacy policy. Many Canadian organizations use a banner to alert users to cookie use and refer to their privacy/cookie policy, even though there isn’t a law exactly like the EU’s cookie consent rule.

Bottom line: PIPEDA does not explicitly mandate a separate “Cookie Policy” page or a pop-up banner, but it does require consent and transparency for any personal information collected by cookies. To comply, an Agricultural Society should at minimum disclose its use of cookies (e.g. analytics or tracking tools) in the privacy policy and obtain at least implied consent. If the cookies are doing more invasive tracking (especially third-party advertising or profiling), providing a clear notice and opt-out mechanism is recommended to meet PIPEDA’s “meaningful consent” standard​fasken.com. While not strictly required by law, having a concise Cookie Policy or notice is a good practice to ensure users are informed at first visit, which aligns with PIPEDA’s expectations.

Other Data Privacy Compliance Obligations for Agricultural Societies

In addition to having a privacy policy and handling cookies appropriately, Agricultural Societies must meet other PIPEDA compliance criteria whenever the law applies. Key obligations include:

  • Accountability: You must assign someone to be responsible for privacy compliance. PIPEDA requires organizations to “designate an individual or individuals who are accountable for the organization’s compliance” with the law​laws-lois.justice.gc.ca. In practice, the Agricultural Society should name a Privacy Officer (even if it’s a part-time role) who oversees compliance, handles inquiries, and manages any privacy complaints or breaches. This person’s contact info should be in the privacy policy​laws-lois.justice.gc.ca.

  • Consent & Purpose Limitation: Collect personal information only for purposes that a reasonable person would consider appropriate in the circumstances, and get individuals’ consent. Identify the purposes for which you collect personal info at or before the time of collectionlaws-lois.justice.gc.ca – for example, on membership forms or online signup forms, clearly state why you need the information (such as for society membership management, newsletter distribution, event registration, etc.). Obtain proper consent (implied or express as suitable) for those purposes. If you want to use or disclose personal info for a new purpose, you must seek new consent unless required by law​laws-lois.justice.gc.ca. For any minors’ data (e.g., youth exhibitors at a fair), ensure to obtain consent from a parent/guardian as minors may not be able to consent on their own.

  • Limiting Collection, Use, and Disclosure: Collect only the personal information necessary for the identified purposes, and do not use or share it for other purposes without consent​laws-lois.justice.gc.calaws-lois.justice.gc.ca. For example, if people provide their contact info to enter a competition or buy a fair ticket, do not automatically add them to a mailing list for unrelated updates unless they agreed. Do not sell or trade personal information (like member or donor lists) without consent – doing so would not only violate PIPEDA’s consent requirements but also clearly falls under “commercial activity” bringing you under PIPEDA’s scope​cba.org.

  • Safeguards: Protect the personal data you hold with appropriate security measures. PIPEDA states that “personal information shall be protected by security safeguards appropriate to the sensitivity of the information.”laws-lois.justice.gc.ca. Practically, an Agricultural Society should ensure that electronic records (e.g. membership databases, email lists) are password-protected and access is limited, and any paper records are stored securely. If you collect payments or financial info for tickets or donations, that data is sensitive and should have higher safeguards (encryption, secure payment processors, etc.). Train any staff or volunteers who handle personal info on their privacy responsibilities (for example, they shouldn’t share someone’s address or email without authorization).

  • Retention and Destruction: Only keep personal information for as long as necessary to fulfill the stated purposes. After that, securely destroy or anonymize it. This means, for instance, if someone is no longer a member and there’s no legal need to keep their data, you should purge it after a reasonable period. While PIPEDA doesn’t specify exact timelines, it expects organizations to have retention policies. Also, if someone withdraws consent, you generally should stop using their data (except if needed for legal reasons).

  • Access and Corrections: PIPEDA gives individuals the right to access their personal information held by an organization and request corrections. Be prepared to respond if someone (say, a member) asks, “What information do you have about me?” You should verify identity and then provide the info within the time PIPEDA allows (generally 30 days). They also have the right to challenge accuracy and have errors corrected​laws-lois.justice.gc.calaws-lois.justice.gc.ca. Your privacy policy should mention how individuals can exercise these rights or contact the Privacy Officer.

  • Data Breach Reporting: Since November 2018, PIPEDA has a mandatory breach notification regime. If the Agricultural Society experiences a security breach that involves personal information under its control, and the breach poses a “real risk of significant harm” to individuals (e.g. a leak of sensitive personal data), you must notify the affected individuals and report the breach to the Privacy Commissioner of Canada without undue delay. You also must keep a record of all privacy breaches (even those not requiring notification) for at least two years​cba.org. Failing to report or record breaches when required can result in fines. For example, if a Society’s member list (with names and contact info) is hacked or lost, the Society would need to assess the risk and likely inform members and report it. It’s wise to have a basic breach response plan in place as part of compliance.

  • Additional Laws (if applicable): While PIPEDA is the main law, be aware of other laws that might apply. For instance, if you send out mass emails (newsletter or promotions), Canada’s Anti-Spam Law (CASL) requires consent for sending commercial electronic messages and an easy unsubscribe mechanism. Fortunately, registered charities have some exemptions for purely fundraising messages, but if your communications are commercial (selling tickets, etc.), CASL’s consent rules apply. Ensure people opt-in to emails, or qualify under an exemption, and always include an unsubscribe link. Another example: if the Society handles any personal health information (unlikely, but perhaps in a fall fair’s medical emergency forms), Ontario’s health privacy law (PHIPA) could apply for that specific data. Generally, though, most of an Agricultural Society’s data (names, contact info, perhaps ages for youth exhibitors, etc.) is covered by PIPEDA.

Finally, even if an Agricultural Society believes PIPEDA might not strictly apply (say, if it contends it has no commercial activities, operating purely on donations and volunteer membership), it is strongly recommended to voluntarily comply with PIPEDA’s principles. Privacy is a public expectation and best practice. By implementing a privacy policy and good privacy practices, the Society demonstrates accountability and builds trust with its community​torkin.comtorkin.com. It also future-proofs the organization, because if any activity does fall under “commercial” now or later, it will already be in compliance. In summary, an Ontario Agricultural Society should treat PIPEDA as applicable and ensure it meets the law’s requirements: have a clear privacy policy, get proper consent, safeguard personal info, and be prepared to uphold individuals’ privacy rights.

Practical Summary for an Agricultural Society

  • Post a Privacy Policy: Maintain a publicly accessible privacy policy (e.g. on your website) explaining what personal information you collect, why you collect it, how you use and share it, and how you protect it, in compliance with PIPEDA’s openness principle​laws-lois.justice.gc.ca. Include contact information for your privacy officer or a board member responsible for privacy issues​laws-lois.justice.gc.ca.

  • Appoint a Privacy Officer: Designate an individual in your organization to oversee privacy compliance and be accountable for protecting personal data​laws-lois.justice.gc.ca. This person should track privacy obligations, handle requests or complaints from individuals, and educate the board or volunteers on privacy duties.

  • Obtain Consent and Limit Collection: Collect personal info only for necessary purposes and ensure individuals consent. For any form (membership signup, event entry, online contact form), explain why you need the data​laws-lois.justice.gc.ca and get the person’s consent (explicit sign-off or implied by submission, depending on context). Do not use the data for new purposes without additional consent.

  • Implement Safeguards: Use appropriate security measures to protect personal data (lock cabinets for paper files; use passwords/encryption for digital files; restrict access to data on a need-to-know basis). Train anyone handling data on confidentiality. This fulfills PIPEDA’s safeguard principle requiring protection appropriate to sensitivity​laws-lois.justice.gc.ca.

  • Include Cookies/Online Practices in Policy: If your website uses cookies or tracking (Google Analytics, etc.), disclose this in your privacy policy or a cookie notice. While a European-style cookie banner is not legally mandated in Canada, you should inform users about any non-essential cookies and give them a way to opt out if they choose​fasken.com. At minimum, state that by using the site, users agree to the use of cookies for stated purposes, and explain how they can disable cookies. This addresses PIPEDA’s consent requirement for online data collection and aligns with CASL’s implied consent for cookies when users do not disable them​crtc.gc.ca.

  • Honour Access and Correction Rights: Be prepared to respond if someone requests access to their personal information or asks for a correction. PIPEDA gives individuals this right, so set up a simple process (the privacy officer can manage it) to verify identity and provide the data or make corrections within the required time.

  • Have a Breach Response Plan: Know what to do if personal information is lost, stolen, or mistakenly disclosed. PIPEDA requires notifying affected individuals and the OPC if a breach could cause significant harm​cba.org. Document all breaches even if they’re minor. Ensure your team knows to report incidents to the privacy officer immediately so you can take quick action.

  • Comply with Related Regulations: If you send emails, make sure to follow CASL (get consent to email people, honor unsubscribe requests). If you operate in multiple provinces or collect data from residents of BC, Alberta, or Quebec, remember those provinces have their own private-sector privacy laws similar to PIPEDA (though if you’re based in Ontario, PIPEDA will cover your activities in most cases)​cba.org.

By fulfilling these requirements, an Agricultural Society in Ontario will not only comply with PIPEDA but also demonstrate good stewardship of personal information. This helps avoid legal issues and maintains the trust of members, volunteers, and the public – an important asset for any non-profit organization.

Sources:

  • Government of Canada – Personal Information Protection and Electronic Documents Act (PIPEDA), Principles 1 (Accountability), 2 (Identifying Purposes), 7 (Safeguards), 8 (Openness)​laws-lois.justice.gc.calaws-lois.justice.gc.calaws-lois.justice.gc.calaws-lois.justice.gc.ca.

  • Office of the Privacy Commissioner of Canada – Interpretation and guidance on PIPEDA’s application to non-profits and definition of “commercial activity”​cba.orgcba.org.

  • Office of the Privacy Commissioner of Canada – Guidelines for Online Consent (implied consent for cookies and requirements for user information/opt-outs)​fasken.com.

  • Canadian Radio-television and Telecommunications Commission – CASL Guidance on Installing Computer Programs (deemed consent for cookies unless user disables them)​crtc.gc.ca.

  • Canadian Bar Association – Why charities and not-for-profits should comply with PIPEDA (overview of PIPEDA’s impact and breach reporting rules)​cba.orgcba.org.

 

Citations

Favicon

Why charities and not-for-profits should comply with PIPEDA | Canadian Bar Association

https://www.cba.org/Sections/Charities-and-Not-for-Profit-Law/Articles/2019/comply-with-PIPEDA

Favicon

Personal Information Protection and Electronic Documents Act

https://laws-lois.justice.gc.ca/eng/acts/p-8.6/page-7.html

Favicon

Your Privacy – Our Policy | Woodstock Agricultural Society

https://woodstockfairgrounds.com/privacy

Favicon

Website cookies in Canada: is consent required? – Lexology

https://www.lexology.com/library/detail.aspx?g=9a2dd4b7-bf75-4957-ac97-331ac98cebca

Cookies: A Bite in Cybernauts’ Privacy? A Canadian-European Overview | Knowledge | Fasken

https://www.fasken.com/en/knowledge/2020/05/cookies-croquee-vie-privee-internaute
Canada’s Anti-Spam Legislation Requirements for Installing Computer Programs | CRTC
https://crtc.gc.ca/eng/internet/install.htm

Favicon

Charities and Not-for-Profits: Obligations for Compliance with Privacy Legislation

https://www.torkin.com/insights/publication/charities-and-not-for-profits-obligations-for-compliance-with-privacy-legislation