Blue Billywig

The Blue Billywig plugin enhances Blue Billywig’s capabilities by integrating with WordPress. This plugin allows users to seamlessly upload media directly to their Blue Billywig publication.

Documentation: See USER-GUIDE.md in the plugin directory for a complete walkthrough of all features.

Third-Party Service Integration

This plugin relies on the Blue Billywig Online Video Platform to provide video uploading capabilities. By using this plugin, you acknowledge and agree to the following:

• The plugin sends data to bbvms.com and bluebillywig.com for video management tasks.
• Your usage of Blue Billywig is subject to their Privacy Policy.

Privacy & GDPR

What data is transmitted to Blue Billywig from site visitors?

Every page that embeds a Blue Billywig video loads the player from {publication}.bbvms.com. When the script runs, the visitor’s IP address, User-Agent, Referer and page URL are transmitted to Blue Billywig so the player can fetch the clip, apply geo/language rules, and record analytics.

Consent integration (GDPR / ePrivacy / TTDSG).

The plugin exposes a WordPress filter bluebillywig_consent_granted so consent-management plugins (Complianz, Cookiebot, Iubenda, Osano, …) can defer loading the player until the visitor opts in:

When this filter returns false, BB embed blocks, channel blocks, Shorts blocks, shortcodes, and oEmbed all render a neutral placeholder explaining that loading will transmit data to bbvms.com. No IP/UA is shipped to Blue Billywig until consent is granted (or until the visitor reloads after accepting).

Cookies and local storage.

• The plugin itself does not set any cookies or write to local storage from admin pages.
• On the frontend, the CTA email-capture overlay (when enabled by the editor) writes bbtl_{clipId} to the visitor’s localStorage after a successful submit, so the form does not re-ask an engaged visitor. This key only carries the submitted email and a timestamp.
• The Blue Billywig player itself may set first-party cookies on the .bbvms.com domain for playback/analytics. See Blue Billywig’s privacy statement for details.

CTA email capture — consent.

The CTA editor can optionally include an email-capture form. The plugin requires an explicit consent checkbox on the form and rejects non-https submit endpoints. Captured emails are sent to the customer-configured endpoint (if any); Blue Billywig’s own backend does not receive or store these emails.

Content protection JWT.

When you enable JWT-based content protection and a logged-in WordPress user requests a protected clip, a short-lived token (≤ 7200s, clamped) is minted. The user-ID claim in the token is an HMAC of the WordPress user ID (never the raw ID) using wp_salt('auth'). Pages carrying a JWT emit Cache-Control: private, no-store to keep shared caches from serving one user’s token to another.

Admin-side third-party code.

On plugin admin pages, the Uppy uploader library is bundled locally (admin/assets/vendor/uppy/) — no request to releases.transloadit.com on every admin page load.

Uninstall.

Uninstalling the plugin deletes every blue-billywig-* option (including stored API keys and the content-protection shared secret) and every bb_* transient. A reinstall starts from a clean slate.

Translators

The plugin ships with starter translations for German, French, Swedish, Danish, Norwegian Bokmål, Finnish, and Dutch (in /languages/). They were generated automatically and cover every string, but they have not been reviewed by native speakers.

Please help us improve them. Once the plugin is listed on wordpress.org, any translation you contribute at translate.wordpress.org/projects/wp-plugins/blue-billywig automatically rolls out to every site running that locale — no plugin release required. If you already translate other WordPress plugins, the process is the same; if you don’t, it takes about five minutes to sign up and suggest a correction.

Adding a new language.

Once the plugin is listed on translate.wordpress.org, that is the preferred home for every language — translators suggest a locale and the site creates the project on first approval. If you want to kick-start a language ahead of that: copy languages/blue-billywig.pot to languages/blue-billywig-<locale>.po (e.g. blue-billywig-it_IT.po for Italian), translate the msgstr values, run msgfmt blue-billywig-<locale>.po -o blue-billywig-<locale>.mo, and send the files to support.bluebillywig.com. We’ll bundle them in the next release so translate.wordpress.org starts with a baseline.