Is consent required for Bynder on my website?

No. Bynder primarily serves brand assets via CDN — images, videos, and documents that are part of the page content. Its cookies serve functional purposes like portal authentication and session state. No marketing tracking is involved. Disclosure in a cookie policy is sufficient.

What does Bynder track?

Bynder tracks asset download and view counts for DAM reporting, portal session data for authenticated users, and CDN performance metrics. Public CDN usage collects no visitor identification or behavioral profiling data. No advertising cookies are set.

How does ConsentStack handle Bynder?

ConsentStack classifies Bynder as functional. CDN asset delivery and portal session cookies are treated as necessary for serving brand content. ConsentStack allows Bynder scripts to load without a consent gate and does not flag it as a marketing or analytics vendor.

What tracker domains does Bynder use?

ConsentStack has catalogued tracker domains for Bynder including bynder.com. These are the network destinations Bynder's scripts contact, which a consent platform blocks until a visitor agrees.

Bynder - Asset Delivery Tracking Consent

Back to Vendor Library

Overview

Bynder is a digital asset management (DAM) platform used by marketing teams to store, organize, and distribute brand assets — images, videos, documents, templates, and creative files. On websites, Bynder integrates through its Content Delivery Network (CDN) and embedded asset viewers that serve brand-approved media directly from the DAM. This ensures websites always display the latest, approved versions of brand assets. Bynder's web presence is primarily a content delivery mechanism rather than a tracking or analytics tool.

What This Script Does

Bynder's web integration operates through CDN delivery and optional embedded components.

Asset delivery (CDN):

Serves images, videos, and documents from *.bynder.com CDN endpoints
Delivers dynamically transformed assets (resized, cropped, format-converted) via URL parameters
Provides responsive image delivery with automatic format selection (WebP, AVIF)

Embedded components (optional):

Media galleries and asset browsers embedded via iframe or JavaScript widget
Brand portal viewers for public or authenticated access to approved assets
Video players for Bynder-hosted video content

Cookies set:

Authentication cookies for access-controlled brand portals (requires login)
Session cookies for embedded gallery browsing state
CDN performance cookies for optimizing asset delivery
No marketing or advertising cookies are set

Data collected:

Asset download and view events (which assets are accessed, download counts)
Portal session data for authenticated users
CDN performance metrics (cache hit rates, delivery latency)
No visitor identification or behavioral profiling data is collected from public CDN usage

Consent & Compliance

Bynder falls under the functional consent category. Under GDPR, the CDN delivery of assets is a functional part of the website — serving images and media that are part of the page content. The session and authentication cookies for brand portals serve the functional purpose of managing access to protected assets.

The asset usage tracking (download counts, view metrics) is operational data for the DAM platform rather than visitor analytics. This data is typically aggregated and tied to assets rather than individual visitors.

Under CCPA/CPRA, Bynder's CDN-based asset delivery does not collect personal information from public visitors beyond standard server logs. Brand portal users who authenticate should be informed about data collection in the portal's privacy policy.

Should You Block This Without Consent?

No. Bynder's primary function is content delivery — serving brand assets that are part of the website's visual content. Blocking CDN-delivered assets would break images, videos, and media on the page. The cookies serve functional purposes (authentication, session state) and no marketing tracking is involved. Disclosure in the cookie policy is sufficient.

Is Bynder GDPR compliant?

Bynder typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Bynder can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Bynder, not on Bynder itself.

Visit website