Privacy Consent Training: Coaching Your Developers
Many organizations assume that once they've placed a consent banner on their website, they're in compliance with privacy law. But the banner can only function properly if the infrastructure it governs — such as the tags and cookies you've placed on your site — is coded properly.
Anyone, external auditors and the public alike, can check whether your website is compliant. The majority of privacy enforcement action so far has centered around this misfiring infrastructure.
This training gives your developers and the product and fundraising teams that manage them the tools to prevent these problems before they start. It teaches teams what to look for, what to ask, and what to require so that privacy is part of the build at the outset — not something tacked on afterward.
GET MORE INFORMATIONHow Does the Way Your Website is Built Impact Compliance?
Commonly, features such as maps, videos, donation forms, and testing tools are added to websites through third-party embeds, plugins, and code. These elements bring the third party's own tracking code with them (clever, right?), which means your organization is set up to collect and transfer visitor data to those third parties before — and sometimes in spite of — a visitor's consent choices.
These problems are difficult and expensive to fix after launch, forcing organizations to choose between a compliant website and a working one.
What This Training Offers
This training is designed to meet your team where they are — whether privacy best practices are new to them, or whether they just need more hands-on understanding of how and why designing with consent in mind applies to them.
The training can be tailored to your specific needs and teams, but commonly, we teach for one of two audiences:
- Product management and digital fundraising teams This group will learn to coach developers and vendors with confidence, so privacy expectations are set before work begins. No expertise in web development is required. This is about empowering your team to understand and communicate the why so the development team can advise on the how.
- Developers This group will learn the standards their organization expects them to meet, so they can build around those standards from the start and/or determine how they might re-design current experiences with compliance in mind. This creates shared context and vocabulary among teams.
Participants will learn how to:
- Recognize the website features and build choices that most often create consent problems.
- Understand why some tracking code can be controlled by a consent banner and some cannot.
- Ask the right questions about where and how data is flowing and what consent choices their audience needs to be offered before a feature is built or changed.
- Set the expectation that every feature should still work when a visitor declines consent.
- Identify the warning signs that a site is collecting data outside of consent.
- Make privacy review a standard step in web projects rather than a fix after launch.
Organizations that complete this training avoid costly rework, reduce their compliance risk, and protect the experience of every visitor who chooses not to be tracked.
Participants leave with a set of build expectations their team can share at the start of every web project.
GET MORE INFORMATIONFrequently Asked Questions
Ready to Chat?
Submit your contact information, and Elyse will be in touch to talk more about your organization's needs. There's no obligation to purchase.
After submitting your information, you can opt out at any time.
