Documentation
Your visitors' privacy
What the widget stores in your visitors' browsers, what it sends to allyWay, why it is safe on your pages and what your Content Security Policy needs.
Updated October 22, 2026
The allyWay widget runs in your visitors' browsers. This page shows what it stores there, what reaches allyWay's servers, and why it is safe to add to your website.
What the widget stores in a visitor's browser
Only small technical entries in the browser's storage for your website (local storage and session storage) – never cookies. None of it is sent to allyWay.
| Entry | What it holds |
|---|---|
aw_prefs |
The visitor's widget choices, for example text size or contrast – only saved once the visitor changes something. |
a11yLanguage |
The widget language the visitor picked. |
aw_hidden_… |
Saved when the visitor uses Hide toolbar: "For this visit" in session storage (gone when the tab closes); "24 hours" and "One week" with an end time, removed afterwards. |
aw_cfg_… |
A copy of your widget settings – only used for up to one hour, if allyWay's servers can't be reached, and removed when your widget is switched off. |
aw_ping_… |
The time the widget last told allyWay it is on your website – a number, nothing about the visitor. |
In the widget, Reset settings switches all tools off and clears the saved tool choices (the chosen language stays). To remove everything, visitors can clear the stored data for your website in their browser settings.
What a visitor's browser sends to allyWay
When the widget loads, the browser asks allyWay's servers for the widget's files, your widget settings, your AI fixes (image descriptions and names for screen readers) and – when the visitor opens it – your accessibility statement. At most once an hour per visitor, it also sends a short installation signal with the page address. Embedded badges are images loaded from allyWay's servers, too.
As with any website request, our servers see the visitor's IP address, browser type and which website the request comes from. allyWay uses the website to make sure your widget only switches on for your own website.
The widget never sends the content of your pages, what visitors type, where they click or how they move the mouse:
- Forms: the widget's tools change how the page looks or reads for the visitor, inside their own browser. Nothing a visitor enters leaves the page through allyWay. To name form fields that have no label, our check reads the field's code and the words next to it on your published page – never anything a visitor typed.
- Read page aloud: it uses the speech voices built into the visitor's own browser or device. allyWay doesn't receive the text that's read out.
- No statistics: the widget collects no statistics about which tools your visitors use, allyWay records no visitor analytics, and the dashboard has no usage report. It shows whether allyWay is installed on your website – visitors' choices stay in their own browsers.
Is the widget safe on my website?
- It doesn't change your website. It never touches your website's files, code or content management system. Its changes happen only in each visitor's browser, while the page is shown. When a visitor turns a tool off, the page goes back exactly to how it was.
- It keeps to itself. Its button and menu live in their own sealed-off part of the page (a "shadow DOM"), so your styles and the widget's don't affect each other.
- Only allyWay's own code. The embed code loads the widget only from allyWay's own servers over a secure connection – no third-party code, no ads, no trackers. Like every script you add to a website, it runs with the same rights as your page's own scripts; that's why allyWay keeps what it does on your page limited to accessibility.
- Clean content. Statement text shown in the widget keeps only basic formatting and normal web or email links. A custom icon can be a PNG or SVG file of up to 200 KB: an SVG is cleaned of scripts, links, animations and anything that would load from another server before it's saved, and a PNG is resized to at most 256 pixels.
- Nothing breaks. If your plan ends or allyWay's servers can't be reached, the widget simply doesn't appear. It waits at most 5 seconds for its settings and loads in the background, after your page's content is ready.
- Your embed code only works for you. The code isn't secret – anyone can see it in your page's source. But your widget only switches on for the website address you added (with or without "www") and its subdomains; on any other website it stays off.
No widget alone makes a website accessible. Barriers in your content and design still need to be fixed on your website – see What allyWay fixes – and what it can't.
If your website uses a Content Security Policy
Add allyWay's addresses to your policy – otherwise visitors' browsers block the widget, and allyWay's AI fixes aren't applied either.
Allow the widget's scripts and fonts
Add the address from your embed code –
https://app.allyway.aiin the code the dashboard shows you – toscript-srcandfont-src.Allow its connections and images
Add
https://api.allyway.aitoconnect-src. Add the address from your embed code,https://api.allyway.ai(uploaded icons and embedded badges) anddata:(the button's built-in icons) toimg-src.Allow its styles
The widget adds its own styles to the page as style blocks, so
style-srcneeds'unsafe-inline'.Test it
Reload your website and look for blocked requests in the browser's developer console.
The Installation page can show Active even when your policy blocks the widget, because allyWay finds the embed code in your page. Our checks see your pages with your policy in force, just like visitors: if it blocks the widget, problems the AI has fixed can show up again as open. With a very strict connect-src, the Stop animations tool may not be able to pause animated images.