Skip to main content :::
:::

How Accesserty Handles Website Data

Understand data collection, access, and retention for Pulse signals, Signal reports, and optional DevCheck AI checks.

Before you install or use the tools

Accesserty is built to help people notice, report, and review accessibility barriers without turning accessibility into hidden tracking or an unverifiable compliance promise.

The Privacy Policy and Terms of Service provide the full legal explanation. This page gives website maintainers a plain-language summary before they install the Pulse script.

What Pulse may collect

When a website maintainer installs Accesserty Pulse, Pulse may collect lightweight interaction signals and page-level summaries, such as:

  • Page address without the query string or fragment; path segments whose format suggests personal data or a secret are replaced before sending.
  • Event type, such as repeated clicks, possible keyboard dead interactions, focus reversals, Escape close difficulties, possible keyboard traps, focus being pulled back, or repeated form attempts.
  • Timestamp.
  • A structural path to the affected element (names of standard HTML, SVG and MathML elements and Accesserty UI Kit components, and positions only, with any other element name replaced by its position; without element IDs, classes or attribute values), and a short event note, which can include the path of a dialog that is still open.
  • A random page-view ID that exists only in that page’s memory.
  • For possible keyboard traps and focus being pulled back, a viewport width band (narrow, medium or wide).
  • Page-level scan summaries when available, such as counts of machine-detectable WCAG A/AA and best-practice risks, with a few sample selectors.

Element IDs, classes, attribute values and element names other than standard elements and UI Kit components are not sent. Page addresses are still sent: Pulse replaces only path segments whose format clearly suggests personal data or a secret, such as an email address, a UUID, a number of six or more digits or a long token. A name, a short order number or other words a site puts in page addresses are not recognized and can be sent as they are. Pulse does not send page text or form field values. Before installing Pulse on pages for signed-in users, check whether their addresses contain such information; if they do, exclude those pages with the script’s data-exclude-paths attribute, and Pulse sends nothing on them.

What Signal reports may include

When a user sends a report through Accesserty Signal, the report may include:

  • The reported page URL.
  • Selected issue types.
  • An optional “Other” issue description and contact email.
  • Browser user agent.
  • Public accessibility signal context for that page when available.
  • The submission service separately stores an identifier derived from the IP address with a secret key, request counts and timestamps to limit repeated submissions. The raw IP is not stored in these records; they are not shared with maintainers or used for advertising tracking. Unsuccessful requests may still leave rate-limit records without saving report content.

After receipt and before storage, the server removes the main URL’s query string and fragment and hides path values matching email, UUID, long-ID or token formats, including paths in certification scopes and match keys. The extension may still send the original path. This is not a complete personal-data filter; public source links retain record identifiers, and older reports are not rewritten.

DevCheck local checks and optional AI

DevCheck simulations, manual review, axe-core scans, and PDF structure checks run locally. Only when you start AI Check does it send bounded page text, link names, and selected images to Google Gemini. Your own key sends the request directly to Google; the shared free service routes it through Accesserty.

URLs within samples and visually hidden naming text may still be sent. Read the Privacy Policy for sampling, quota records, and Google data-use details before enabling AI. This is not a sensitive-data filtering service.

Privacy Policy

Generative UI experiment

The experiment’s examples, demo forms, file uploads, automated accessibility check, and screen history all stay in your browser. Screen history lives only in the current tab and disappears when you reload.

Only where live generation is enabled, and only when you press Generate or choose a follow-up option, are your request (up to 500 characters) and a description of the current layout sent through Accesserty to Google Gemini. The layout description does not include what you typed into demo forms. Accesserty’s code does not log or store the request text, the layout, or your IP address; Cloudflare processes connection data such as your IP address as our hosting provider. Under Google’s unpaid-service terms, inputs and responses may be used to improve products and models and may be reviewed by people. Do not enter personal or confidential information. Connections from the European Economic Area, Switzerland or the United Kingdom are offered the prepared examples only, and nothing entered is sent.

Website security policy reports

When a browser finds a resource on accesserty.com that conflicts with the Content Security Policy (CSP), it may send a minimized security report so we can verify that the security settings do not accidentally block normal functionality. This is not advertising tracking and does not require analytics tools.

The report retains only the Accesserty page path, violated policy directive, a category or origin for the blocked resource, an HTTP status when supplied, and aggregate occurrence timestamps. It does not retain the raw report, IP address, complete URL or query string, referrer, source-file path, or script sample. It is deleted automatically 30 days after it was last seen.

What Pulse does not intentionally collect

This list concerns Pulse on monitored websites. It does not cover information you submit through contact forms or Signal reports, or optional DevCheck AI samples. Pulse does not intentionally collect:

  • Passwords.
  • Payment card data.
  • Form input values.
  • Full page content.
  • Private messages.
  • Browsing history across unrelated websites.
  • Keystroke logs.
  • Screen recordings.
  • Advertising identifiers.

Signal is not a search ranking system. Pulse is not an advertising tracker. Accesserty does not sell website visitor data.

What the Pulse script does

The Pulse script runs only on websites where a maintainer installs it. It records selected accessibility-related interaction signals and sends them to the maintainer’s Accesserty Console.

The Pulse script does not change the website interface for visitors. It does not inject accessibility overlays, floating toolbars, or automatic fixes.

Installing Pulse does not mean a website is accessible, compliant, or fully audited.

Why Accesserty uses these signals

Accessibility issues often appear after launch. A page can look fine during review and later become harder to use because of new content, layout changes, form changes, third-party services, or real user behavior.

Accesserty uses these signals to help maintainers know where to look first. A signal is not proof of failure. It is a clue that a page may deserve review.

Who can see the data

A maintainer with current eligible domain access can view the Pulse signals and Signal reports associated with that access in Console. A reporter’s optional contact email is visible only to Accesserty and is not shared with maintainers. Once the domain is removed and the original access is released, adding and verifying it again, even with the same account, does not restore the previous private records. Another account taking over does not inherit them either.

Signal reports go to Accesserty first. If no maintainer had verified access when a report was submitted, it may remain with Accesserty; delivery to or action by the website maintainer is not guaranteed.

Public certification records, statement links, and ALLY signals are separate from private reports. Search-result badges do not publish private Pulse data, private Signal reports, or reporters’ contact details.

How do I stop collection and end access?

After removing the Pulse script, pages that no longer load it do not start new Pulse collection. Already-open tabs running the script may need to reload before it stops. Existing records remain viewable in Console only while the account retains current eligible domain access.

Removing the registered domain in Console ends data access; it does not immediately delete all stored records.

When is stored data deleted?

Signal submission rate-limit records become eligible for deletion after more than 24 hours without use, and are removed on the next daily cleanup run while that job is operating. This does not delete report content. Infrastructure providers’ network logs and backups follow their own policies.

Signal reports expire 12 months after creation, including the optional email, browser information, public signal snapshot and related resolution conversations. This also applies to open reports; replies or status changes do not extend the period. Expired reports are no longer available to read or reply to and are deleted on the next daily cleanup run while that job is operating.

Pulse interaction events expire 30 days after creation, regardless of how few events are stored. Expired events are no longer available for review and are deleted on the next daily cleanup run while that job is operating. Free/Pro limits of 100/1,000 events are account-wide viewing limits, not retention periods.

Pulse scan summaries expire 30 days after the scan, including the latest summary. Console and weekly reports use only summaries within that period: the latest summary of each page, and a baseline to show new and resolved problems: the page’s last summary before the compared period, or its first one inside it. Expired summaries and stale scan-cache entries that no longer support a retained summary are deleted on the next daily cleanup run while that job is operating. No available summary does not mean that a page has no issues.

Automatic deletion applies to the live database and does not rewrite backups. Provider backups follow the applicable plan and policy. Manual recovery-test backups are saved directly to encrypted local storage and kept for no more than 7 days from the first data collected for that backup. Restored copies and temporary files have the same deadline and are removed by operations staff. See the Privacy Policy for full retention, backup, and deletion-request details.

Privacy Policy

Relationship to accessibility review

Accesserty is not an accessibility audit service, certification body, legal service, or automated compliance guarantee.

Accesserty helps people notice, report, inspect, and maintain accessibility-related issues more easily. Complete accessibility review still requires professional judgment, manual testing, assistive technology testing, and real user feedback.

Related documents

  • Privacy Policy

    Legal details about data collection, use, storage, and user rights.

  • Terms of Service

    Service use, subscriptions, refunds, responsibility scope, and limitations.

  • Accesserty Pulse

    Learn how maintainers use Pulse to review interaction events, page summaries, and Signal reports.

Frequently asked questions

Does Pulse record sessions or replay user behavior?

No. Pulse is not currently a session replay or heatmap tool. It does not record screens or full interaction sessions.

Does Pulse collect form content?

No. Pulse does not intentionally collect form input values. Its purpose is to provide page-level and interaction-event clues, not to read what users type.

Does installing Pulse mean a website is compliant?

No. Pulse provides maintenance clues. It does not replace a full manual audit, assistive technology testing, or legal compliance analysis.