DawsonyWeb – Media Library
Your files and data.

What this notice covers

This notice describes DawsonyWeb Media Library 1.1.0, a self-hosted WordPress plugin. It processes files and organisation data on the website where it is installed. The site owner controls that data. DawsonyWeb does not receive media files or library usage data from the plugin.

Our website downloads, enquiries and support follow the dawsony.com website privacy policy. The plugin itself does not require a DawsonyWeb account or licence.

Data stored on your website

Media files, attachment metadata, titles, alt text, captions and descriptions are stored using WordPress. The plugin adds virtual folder terms and relationships, folder creator user IDs, archive markers and image revision records. Folder names are visible to users with media upload access.

Favourite attachment IDs are stored in user metadata separately for each site. The browser uses local storage for the grid or list preference. It does not contain media files, conversation history, tracking identifiers or authentication credentials. Normal WordPress authentication is used.

Image processing and temporary files

Cropping, resizing, conversion, compression and replacement run through the server’s WordPress image editor. No external image API, telemetry, analytics SDK or third-party processing service is included.

Staging and one previous edited version can be held in a private system temporary directory outside WordPress. Snapshots contain image bytes and the metadata needed to restore them. They are protected with local filesystem permissions and are not exposed through a public download endpoint. The host may clear temporary files. ZIP downloads are generated temporarily and removed after streaming.

Retention and removal

The next successful edit replaces the previous snapshot. Deleting an attachment removes its available snapshot. Other temporary snapshots can be cleared by the host. The plugin does not promise permanent version history.

Deactivating or deleting the plugin retains virtual folders, personal favourites and archive markers for reinstallation. Media files and edits remain. Site administrators should remove plugin organisation records through an appropriate database maintenance process if they no longer need them, and account for normal server and backup retention. Removing a WordPress user normally removes that user’s metadata; folder creator IDs may remain until the site administrator removes or reassigns them.

Clear the browser’s site storage to remove the view preference. This also affects other data stored locally by that site.

Permissions and site-owner responsibilities

The workspace and API require a signed-in WordPress user with upload access. Editing and downloads also check attachment permissions. Site owners should give accounts only the media access they need and protect normal WordPress uploads and backups according to the content they hold.

Standard media URLs can be publicly accessible, as in WordPress. A virtual folder or workspace archive is not an access restriction for visitors. The usage scan respects post-editing permissions but cannot find every reference.

Support and privacy enquiries

Contact DawsonyWeb through the support page for plugin questions. Send only the information needed to explain the issue and remove passwords, keys and private customer or media details from screenshots.

For requests concerning media, favourites, user records, site logs or backups, contact the website owner hosting the plugin. WordPress, hosting, CDN and offload-provider processing is governed by their own arrangements and the site’s policies.