Accessibility Widget: Privacy

Accessibility widget for Sylius - what is stored in the browser (localStorage), why no cookies are set, that no data goes to the server or to third parties, and what lives on the server side.

Deutsche Version

Back to overview

Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net

This page describes what the plugin technically stores and transmits. It is not legal advice and makes no legal assessment for your shop.

What lives in the visitor's browser

The widget stores a visitor's choices exclusively in the browser's localStorage, under the key mmd-accessibility-settings.

Entry	Possible values
`fontSize`	`small`, `large`
`contrast`	`high`, `inverted`
`colorFilter`	`protanopia`, `deuteranopia`, `tritanopia`
`blueLight`	`true`
`reduceMotion`	`true`

Only what differs from the normal state is stored. If every tool is on "Normal" or off (or the visitor clicks "Reset all settings"), the entry is deleted.
Unknown keys and values in localStorage are discarded when reading.
If storage is unavailable (for example in private mode), the choice applies to the current page only.

No cookies, no requests

The plugin neither sets nor reads any cookie.
The widget's JavaScript sends no requests: the choice does not leave the browser and reaches neither your server nor third parties.
Stylesheet and scripts come from your own server (/bundles/mmdsyliusaccessibilityplugin/); no external resources are loaded.

What lives on the server

The table mmd_sylius_accessibility_channel_settings contains only channel settings (channel code, on/off, position, tools), no visitor data.
If the table cannot be read, the plugin writes a warning with the channel code and the database exception to the log (Monolog channel mmd_accessibility), likewise without visitor data.

Uninstall

When you remove the plugin, localStorage entries already set stay in visitors' browsers; the shop no longer reads them. Remove the table as described under Installation.