Wolvy Video

The plugin adds suggested text to Settings → Privacy , and registers the stored identifier with WordPress’s own personal-data export and erase tools.

External services

This plugin relies on the Wolvy video platform, a third-party service, and cannot work without it.

1. Wolvy Developer API — https://api.wolvy.net

Used in wp-admin only, and only when you have entered an API key. Called when you browse your video library, open the analytics or health screens, register a webhook, or verify your credentials.

Data sent: your API key, and the parameters of what you asked for — video identifiers, search terms, folder and status filters, date ranges. Requests carry a user-agent string containing your site’s address and its WordPress version. No visitor data is ever sent to this endpoint.

When: in wp-admin, whenever you load one of the plugin’s screens, open the Elementor panel, or press one of its buttons. On the front end, the plugin also looks up a video’s title and poster image the first time that video is rendered — the title becomes the player’s accessible name, and the poster is used in click-to-play mode. That lookup is cached (10 minutes by default), so it happens at most once per video per cache period, and it contains no information about the visitor.

2. Wolvy player embed — https://embed.wolvy.stream

The video player itself, loaded in an iframe on any page where you have placed a video.

Data sent: the visitor’s browser connects to Wolvy directly, so Wolvy receives their IP address, user agent and referring page, as any embedded media provider would. The embed URL also carries your Wolvy account number, the video identifier, and a signed identifier for the signed-in viewer (see Privacy above). Wolvy uses these to record a viewing session and, if you have enabled it, to draw a watermark.

When: whenever a visitor loads a page containing a video. In click-to-play mode, only once they click.

3. Wolvy CDN — https://*.wolvy-cdn.net

Video segments — and the poster images shown in click-to-play mode, in the WordPress admin library and in the block picker — are fetched from Wolvy’s CDN by the browser. Same data as above, by virtue of the connection.

If you enable webhooks under Wolvy → Settings, the plugin sends Wolvy this site’s REST endpoint address, and Wolvy then posts signed event notifications (video.ready, video.failed, video.deleted, caption.ready) back to it. Remove the endpoint on the same screen to stop them.

Wolvy’s terms of service: https://wolvy.net/legal/terms Wolvy’s privacy policy: https://wolvy.net/legal/privacy

The plugin also makes one request to your own site’s home page on the Health screen, to read its Referrer-Policy header. Nothing leaves your server in that request.