Legal

Privacy Policy

Last updated: June 1, 2026

Information We Collect

WCAGWatch collects account information such as name, email address, company name, billing email, and plan details when you create or manage an account.

WCAGWatch stores website scan information such as submitted URLs, saved website domains, crawl settings, ignored paths, scan cadence, scan status, and accessibility findings generated by scans.

WCAGWatch stores report information such as report metadata, issue summaries, export history, and scheduled report settings.

WCAGWatch records technical information such as IP address, device information, browser type, pages viewed, timestamps, session information, and application logs for security, debugging, analytics, and service operation.

How We Use Information

WCAGWatch uses account information to provide access to saved websites, scans, dashboards, reports, billing, notifications, and account settings.

WCAGWatch uses submitted URLs and scan results to run accessibility checks, show issue history, generate reports, schedule monitoring, and improve product reliability.

WCAGWatch uses technical information to operate the service, prevent abuse, troubleshoot errors, measure product usage, and improve performance.

WCAGWatch uses contact information to send sign-in links, account notices, scan summaries, report notifications, billing messages, and product updates.

Website Scan Data

WCAGWatch scans public website pages submitted by users or configured in saved website settings.

WCAGWatch keeps scans focused on public pages. Private account pages, admin pages, payment pages, checkout flows, and restricted areas are excluded unless an authenticated testing workflow is added.

Automated scan results include page URLs, issue descriptions, selectors, severity levels, WCAG references, screenshots, reports, and scan history when those records are available.

Scan results are stored as product records for reports, history, exports, and account review.

Billing Information

A third-party billing provider such as Stripe handles payment processing.

WCAGWatch does not store full credit card numbers on its own servers. Billing providers collect and process payment details according to their own privacy and security terms.

WCAGWatch stores billing status, plan type, subscription identifiers, invoice metadata, usage limits, and payment status so the service can enforce plan access.

Cookies And Analytics

WCAGWatch uses cookies, local storage, session storage, or similar technologies to keep users signed in, remember preferences, measure product usage, improve security, and understand site performance.

WCAGWatch uses analytics tools to understand how visitors and account users interact with WCAGWatch pages and product flows.

Users can control cookies through browser settings. Some account, billing, and dashboard features depend on required cookies being enabled.

How We Share Information

WCAGWatch does not sell personal information.

WCAGWatch shares information with service providers that help operate the service, including hosting, database, email delivery, analytics, error logging, payment processing, and security providers.

WCAGWatch discloses information when required by law, legal process, security needs, fraud prevention, or when needed to protect users, WCAGWatch, or others.

Data Rights And Requests

Users can request access to, correction of, export of, or deletion of account-related data by contacting WCAGWatch through the contact page.

Requests can be subject to identity verification and operational, billing, legal, security, and abuse-prevention retention requirements.

Some records need to be retained for service operation, billing records, fraud prevention, security logs, dispute resolution, or legal obligations.

Data Retention

WCAGWatch keeps account, billing, scan, report, and history data for as long as needed to provide the service, maintain records, comply with legal obligations, resolve disputes, prevent abuse, and improve the product.

Users can request deletion of account data, subject to operational, billing, legal, and security retention requirements.

Deleted account data can remain in backups or logs for a limited period before being permanently removed according to normal retention practices.

Security

WCAGWatch uses administrative, technical, and organizational safeguards designed to protect account data, scan data, reports, and billing-related records.

Security protections are reviewed and updated as the service changes. Users should choose strong email account security and protect access to sign-in links and account dashboards.

Changes To This Policy

WCAGWatch updates this Privacy Policy as the product, legal requirements, service providers, or business operations change.

The updated policy is posted on this page with a revised date. Continued use of WCAGWatch after updates means the updated policy applies.

Contact

Privacy Questions

For privacy questions, account deletion requests, data access requests, or correction requests, contact WCAGWatch through the contact page.

Information We Collect

WCAGWatch collects account information such as name, email address, company name, billing email, and plan details when you create or manage an account.

WCAGWatch stores website scan information such as submitted URLs, saved website domains, crawl settings, ignored paths, scan cadence, scan status, and accessibility findings generated by scans.

WCAGWatch stores report information such as report metadata, issue summaries, export history, and scheduled report settings.

How We Use Information

WCAGWatch uses account information to provide access to saved websites, scans, dashboards, reports, billing, notifications, and account settings.

WCAGWatch uses submitted URLs and scan results to run accessibility checks, show issue history, generate reports, schedule monitoring, and improve product reliability.

WCAGWatch uses technical information to operate the service, prevent abuse, troubleshoot errors, measure product usage, and improve performance.

WCAGWatch uses contact information to send sign-in links, account notices, scan summaries, report notifications, billing messages, and product updates.

Website Scan Data

WCAGWatch scans public website pages submitted by users or configured in saved website settings.

WCAGWatch keeps scans focused on public pages. Private account pages, admin pages, payment pages, checkout flows, and restricted areas are excluded unless an authenticated testing workflow is added.

Automated scan results include page URLs, issue descriptions, selectors, severity levels, WCAG references, screenshots, reports, and scan history when those records are available.

Scan results are stored as product records for reports, history, exports, and account review.

Billing Information

A third-party billing provider such as Stripe handles payment processing.

WCAGWatch does not store full credit card numbers on its own servers. Billing providers collect and process payment details according to their own privacy and security terms.

WCAGWatch stores billing status, plan type, subscription identifiers, invoice metadata, usage limits, and payment status so the service can enforce plan access.

Cookies And Analytics

WCAGWatch uses analytics tools to understand how visitors and account users interact with WCAGWatch pages and product flows.

Users can control cookies through browser settings. Some account, billing, and dashboard features depend on required cookies being enabled.

How We Share Information

WCAGWatch does not sell personal information.

WCAGWatch shares information with service providers that help operate the service, including hosting, database, email delivery, analytics, error logging, payment processing, and security providers.

WCAGWatch discloses information when required by law, legal process, security needs, fraud prevention, or when needed to protect users, WCAGWatch, or others.

Data Rights And Requests

Users can request access to, correction of, export of, or deletion of account-related data by contacting WCAGWatch through the contact page.

Requests can be subject to identity verification and operational, billing, legal, security, and abuse-prevention retention requirements.

Some records need to be retained for service operation, billing records, fraud prevention, security logs, dispute resolution, or legal obligations.

Data Retention

Users can request deletion of account data, subject to operational, billing, legal, and security retention requirements.

Deleted account data can remain in backups or logs for a limited period before being permanently removed according to normal retention practices.

Security

WCAGWatch uses administrative, technical, and organizational safeguards designed to protect account data, scan data, reports, and billing-related records.

Security protections are reviewed and updated as the service changes. Users should choose strong email account security and protect access to sign-in links and account dashboards.

Information We Collect

How We Use Information

Website Scan Data

Billing Information

Cookies And Analytics

How We Share Information

Data Rights And Requests

Data Retention

Security

Changes To This Policy

Privacy Questions

Preparing Your WCAGWatch Page

Information We Collect

How We Use Information

Website Scan Data

Billing Information

Cookies And Analytics

How We Share Information

Data Rights And Requests

Data Retention

Security

Changes To This Policy

Privacy Questions