Privacy, data and uninstalling

What leaves your site

Nothing.

There is no API, no account, no telemetry and no phone-home. The scanner, the fixes, the Images screen, the statement generator and the reports all run entirely on your own server. The plugin works the same whether or not your server can reach the internet.

That is also why there are no scanning limits. Nothing is metered because nothing is being paid for per page.

No AI

Nothing here is generated and nothing is sent to a model.

Where a correct answer depends on what your content means — what an image is for, what a link promises — the plugin says so and gives you the fastest way to write it yourself. The alternative is a plausible sentence that you then have to check, which is more work than writing it and far easier to get wrong without noticing.

What it stores on your site

Data	Where	Why
Scans and findings	Its own database tables	The report, and comparing one scan to the next
Dismissals and their reasons	Its own tables	So decisions survive re-scanning
Applied markup fixes	A reversible override layer	So every fix can be undone and your content is never overwritten
Settings and enabled fixes	WordPress options	Configuration
Alt text you type	WordPress’s own alt text field	So it applies everywhere and outlives this plugin
CSS fixes	Your site’s Additional CSS	So you can read, edit or delete them without this plugin

No visitor data is recorded. The plugin runs in your admin, against your own pages, on demand.

Background work

Long jobs — checking many pages at once — run through Action Scheduler, a library by Automattic bundled with the plugin, so a large scan never blocks an admin page or times out half finished.

Action Scheduler makes no outbound requests of its own. It is licensed GPLv3 or later; this plugin’s own code is GPLv2 or later.

Removing the plugin

Deactivating stops it running. Your data stays where it is, so reactivating picks up where you left off.

Uninstalling removes the plugin’s own data: its tables, its options, and the capabilities it granted, including any roles added through wsak_role_capabilities.

What stays behind, deliberately:

• Your alt text. It is in WordPress’s own field, which is content, and it is yours.
• CSS fixes in Additional CSS. They are in your theme’s customiser, visible and editable, and silently deleting working styles would be worse than leaving them.

What goes back to how it was:

• Markup fixes. They lived in the override layer, never in your content, so removing the plugin returns your markup to exactly what it was.
• Site-wide fixes. They were applied at render time and stop immediately.

For your own privacy notice

If you need to describe this plugin in your site’s privacy policy, the accurate statement is short: it processes your own content, in your own admin, and transmits nothing to any third party.