This article lists exactly what the plugin stores, what it sends and when, and what it adds to your pages. It is useful for your privacy policy and for anyone who asks how the tools work.
Your visitors:
- Every choice a visitor makes (profile, colour mode, text settings, reading aids, Listen speed and voice, whether they answered the question, whether they hid the button for today) is saved in their own browser's local storage for your site. It is not a cookie, and it is not sent to your server or to us.
- A tiny script at the top of the page reads those choices back on the next visit and applies them before the page paints.
- A visitor can clear their choices at any time with the Reset button in the panel, or by clearing their browser's data for your site.
- Visitors never sign in. Once the page has loaded, the reading tools make no requests to any other service.
- Listen uses the browser's own speech. The plugin does not send the page text anywhere.
- The two reading fonts, Atkinson Hyperlegible (Clear letters) and Lexend (Reading font), come with the plugin and load from your own site. Choosing one never calls a public web font service or any other outside service.
You, the site owner:
- Getting the free key sends your name, your email and your site's domain to the ResultsAiX licence server, which issues the key and emails it to you.
- Once a day the plugin checks the key with the licence server, sending the key, your site's domain and the plugin version.
- WordPress checks the ResultsAiX update server for new versions, in the normal way.
With PRO and an AI key:
- Fix with AI sends each picture it describes, the post title, and the address of any embedded frame it cannot name by itself to the AI provider you chose. Pictures are sent one at a time.
- In short sends the post title and up to the first 6,000 characters of its text.
- These requests go from your server straight to your provider with your own key, only when you press the button or, for In short, when a post is first published with Write In short with AI at first publish switched on.
- Your AI key is stored in your WordPress database and shown only partly once saved.
What is stored on your site:
- The plugin's settings, in your WordPress options.
- In short summaries, saved with each post.
- With PRO: each post's latest check result, saved with the post, and a summary of the last whole-site check plus the last twelve check totals for the Dashboard chart.
- The error log, in daily files kept for 7 days in a folder the web cannot read. Nothing about your visitors is written to it.
Performance:
- On pages where the button shows, the plugin adds one stylesheet, one script and a tiny inline script in the page head. The script needs no other libraries.
- On pages where it does not show, and whenever The Accessibility button and panel is switched off, nothing is added at all.
- The heavier work, such as splitting the article into sentences for Listen or tracking paragraphs for Focus, happens only when a visitor first uses that feature.
- Page caching is fine. Every choice is applied in the visitor's browser, so a cached page never carries one visitor's settings to another.
- When a page is printed, the button, panel, bar, reading guide and mask are left off the print.
Questions visitors may ask:
- Is my reading choice shared with the site? No. It stays in your own browser.
- Does Listen record me or send the page anywhere? No. Your browser's own voice reads the page on your device.
- How do I clear my choices? Press Reset in the panel, or clear your browser's data for the site.
A real example:
Maya adds one paragraph to the privacy policy of Green Lane Garden Studio: The Accessibility button on this site remembers your reading choices in your own browser so they apply on your next visit. They are not sent to us and you can clear them with the Reset button in the panel. That covers the visitor side completely.
Tips:
- If you use a caching or optimisation plugin, clear its cache after changing the Reading tools tab.
- Diagnostics shows whether a page cache is on. Cached pages work fine with the tools.