Privacy
What leaves the page when Monitoring is running, and what the four sessionStorage keys hold.
On this page
What leaves the page
- No text. Text content never leaves the page.
- Attributes are limited. Attributes that can carry text, like
alt,titleandaria-label, never leave the page as their value, and links are sent as a path only. - Paths only. Query strings and fragments never leave the page.
- A random per-tab session id. 16 random bytes, kept in
sessionStorage. It isn't persisted beyond the tab and is never correlated across visits or sites. - No cookies. The collector itself never reads or writes cookies.
- The
sendBeaconcaveat. Most beacons are sent withnavigator.sendBeacon, which has no option to omit cookies, so the browser may attach cookies it holds for the endpoint's host under its normal rules. Thefetchfallback sends none — it setscredentials: 'omit'.
Browser storage
Four sessionStorage keys, all cleared when the tab closes, none holding anything about the visitor personally:
| Key | Purpose |
|---|---|
a11y_rum | Session state for Monitoring (cleared when the tab closes). |
a11y_rum_seen | Session state for Monitoring (cleared when the tab closes). |
a11y_rum_routes | Session state for Monitoring (cleared when the tab closes). |
a11y_rum_session_sent | Session state for Monitoring (cleared when the tab closes). |