Privacy & Network Boundaries
Understand the no-account, browser-local, same-site network boundary of the GetWebP WordPress.org Free plugin.
Privacy & Network Boundaries
The GetWebP WordPress.org Free plugin does not require a GetWebP account, license key, paid plan, optimization credits, or external job authorization.
Encoding runs in the administrator's browser. Generated files are saved back to the same WordPress site through authenticated admin requests.
Table of Contents#
- No GetWebP Service Connection
- What Stays in the Browser
- What WordPress Stores
- What Is Not Sent to GetWebP
- Normal Site Network Activity
No GetWebP Service Connection#
The Free plugin does not call a GetWebP API to scan the Media Library, preview quality, encode images, save generated files, record history, undo a run, clean up generated files, or serve generated WebP URLs.
There is no sign-in, service token, remote approval, usage reservation, or job-completion request in this workflow.
What Stays in the Browser#
The administrator's browser:
- reads eligible source images from the WordPress site's media context
- decodes JPEG, PNG, or BMP inputs
- runs the bundled WebAssembly encoders
- creates WebP and optional AVIF output bytes
- shows quality previews before files are written
The plugin does not load executable conversion code from a remote service.
What WordPress Stores#
Authenticated admin requests send generated files back to the same WordPress installation. WordPress stores:
- plugin settings
- generated-file paths and attachment status
- library statistics and recent run history
- generated WebP and optional AVIF files in uploads
Original uploads remain in place.
What Is Not Sent to GetWebP#
The WordPress.org Free plugin does not send the following to a GetWebP API:
- original image files or decoded pixels
- generated WebP or AVIF files
- filenames or upload paths
- attachment IDs, dimensions, presets, or run status
- site authorization or usage-accounting metadata
Normal Site Network Activity#
This boundary does not make WordPress itself offline. The administrator's browser still communicates with the WordPress site, and the site's hosting, CDN, object storage, backup, cache, security, and logging systems may process requests according to their own configuration.
Documentation and support links open getwebp.com only when an administrator chooses them. They are not conversion API calls and do not receive image data from the plugin.