Cookie Statement
Placeholder for board review. Final publication requires legal counsel review. Contact privacy@bridgetobold.org · info@bridgetobold.org
Purpose
This Cookie Statement explains how the website may use cookies, pixels, tags, scripts, local storage, analytics identifiers, and similar technologies.
Cookie Category
Purpose
Consent Approach
Strictly necessary
Security, page navigation, forms, donation checkout, fraud prevention, accessibility tools, and session management.
May be active without optional consent where legally permitted.
Preference
Language, accessibility preferences, region, and saved settings.
Consent or user selection where required.
Analytics
Website usage, page performance, visitor paths, errors, campaign performance, and content improvement.
Consent before use for EU/UK visitors and others where required.
Marketing and fundraising
Campaign attribution, advertising pixels, retargeting, donor outreach, and social media integrations.
Opt-in consent before use where required.
Embedded media and social
Video players, maps, event widgets, donation widgets, social sharing tools, and third-party embeds.
Consent may be required before loading non-essential third-party content.
Cookie controls
The website should provide a cookie banner or preference center with Accept All, Reject Non-Essential, and Customize choices.
The website should not place analytics, marketing, fundraising pixels, social media, or other non-essential cookies until required consent is obtained from visitors in jurisdictions requiring opt-in consent.
Visitors should be able to change cookie preferences through a persistent footer link labeled Cookie Preferences.
Cookie consent records should be retained as required to demonstrate compliance.
Do Not Track and global privacy signals
The website should honor browser or platform-based opt-out signals where technically feasible and legally required. If the website does not honor a particular signal, the policy should clearly state that and explain available controls.
Cookie table maintenance
Developers should maintain a live cookie inventory showing cookie name, provider, purpose, category, duration, and whether consent is required.