# How Accesserty Handles Website Data This plain-language summary explains data collection, access, and retention for Pulse signals, Signal reports, and optional DevCheck AI checks. It does not replace the Privacy Policy or Terms of Service. Traditional Chinese version: https://accesserty.com/ai/data-handling.md Page version: https://accesserty.com/en/data-handling/ ## 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 provides a pre-adoption summary. ## What Pulse may collect - Page URL. - 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. - Browser and device context needed to understand the event. - Page-level scan summaries when available, such as counts of machine-detectable WCAG A/AA and best-practice risks. ## What Signal reports 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. ## 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. ## 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. - 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. ## Pulse script 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. ## Data visibility 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. Signal reports are not formal legal complaints or official support requests to the website owner. 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. Interaction events become eligible for scheduled deletion only when they are both older than 30 days and outside the latest 1,000 associated with the same current domain access. Historical events no longer associated with domain access share one combined 1,000-event allowance, rather than a separate allowance per original domain. This is separate from Free/Pro viewing limits, not a 30-day expiry for every event. Console reads the latest scan summary per page; an older summary becomes eligible for deletion when a newer one exists for the same current access and URL and its scan date is more than 30 days old. Summaries no longer associated with domain access are compared by URL. 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](https://accesserty.com/en/privacy/#data-retention) for full retention, backup, and deletion-request details. ## 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 pages - Privacy Policy: https://accesserty.com/en/privacy/ - Terms of Service: https://accesserty.com/en/terms/ - Accesserty Signal: https://accesserty.com/en/signal/ - Accesserty Pulse: https://accesserty.com/en/pulse/