Skip to main content

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, title and aria-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 sendBeacon caveat. Most beacons are sent with navigator.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. The fetch fallback sends none — it sets credentials: 'omit'.

Browser storage

Four sessionStorage keys, all cleared when the tab closes, none holding anything about the visitor personally:

KeyPurpose
a11y_rumSession state for Monitoring (cleared when the tab closes).
a11y_rum_seenSession state for Monitoring (cleared when the tab closes).
a11y_rum_routesSession state for Monitoring (cleared when the tab closes).
a11y_rum_session_sentSession state for Monitoring (cleared when the tab closes).