Privacy Policy

1. Information We Collect

A. Account Data

When you sign in to Accesserty Console or CRM through Google OAuth, we receive your email address, display name, avatar, and the user identifier issued by Google. We use this information to authenticate you, create your user profile, generate your Pulse view_key, and determine which domain data you may access.

We do not receive your Google password, nor do we access Gmail, Google Drive, or other Google service content.

B. Subscription and Billing Data

When you subscribe to Pulse Pro, Lemon Squeezy handles checkout, payment methods, taxes, and invoices. Accesserty may store Lemon Squeezy customer and subscription identifiers, plan status, subscription start and end times, and information needed to open the customer portal. We do not directly store full payment-card numbers or security codes.

C. Contact Form and CRM Data

When you submit our website contact form, we collect your name (optional), email, referral sources, message body, UTM source information, and User-Agent. We use this information to respond to inquiries, keep service records, and improve our website communication flow.

D. Accesserty Pulse Behavior Events

When a website administrator installs pulse.js on their website, Pulse records interaction events that may indicate usability or accessibility difficulties, such as repeated clicks, possible keyboard dead interactions, focus reversals, Escape close difficulties, possible keyboard traps, focus being pulled back, and repeated form attempts.

Pulse event data may include the view_key, domain, page URL, event type, CSS selector of the affected element, a short event note, a random session ID, and the User-Agent.

Pulse does not collect form field contents, actual keystrokes, full DOM, page text, screenshots, mouse-movement trails, or cross-site browsing history.

When you register a Pulse domain, we store the normalized domain and account identifier. Access to that website's Pulse data and Signal reports begins only after our verification service finds your account's static Pulse script in the server-returned homepage HTML. We then store the registration status, verification checks, claim identifier, and claim/release timestamps. This confirms control of the website installation for Accesserty access control; it is not proof of legal ownership. Removing the domain releases the claim. A later claimant receives a new claim identifier and does not inherit the previous claimant's Pulse history or Signal reports.

E. Accesserty Pulse Page Scan Summaries and Weekly Reports

Pulse may also run low-frequency axe-core summary scans in the browser after an end user opens a page. These scans provide a machine-detectable overview of WCAG A/AA and best-practice risks. To avoid repeated scans, the same view_key, URL, and scan version are usually not scanned again within a short period.

Scan summaries may include the view_key, domain, scan time, URL, scan version, rule IDs, impact levels, issue counts, axe-core help text, help URLs, a small number of sample selectors, a random session ID, and the User-Agent. They are not a full manual accessibility audit and do not mean that a website conforms to WCAG 2.2 AA or any legal requirement.

Pro users may opt in to a weekly email report. The report aggregates Pulse events, scan summaries, and Signal reports for their currently registered and claimed domains and is delivered to the account email through Resend as semantic HTML with a complete plain-text fallback. The same report can also be viewed in Console. Administrators may preview or manually send the same type of report when needed for service support.

F. Accesserty Signal Reports and Search-Result Labels

Accesserty Signal is a browser extension that mainly runs on Google and Bing search-result pages. It may display public accessibility certification, recognition, award, or badge records from supported sources, accessibility-statement links, and Accesserty ALLY active-maintenance information.

When you actively submit a report through Signal, we collect issue types, the reported page URL, domain, User-Agent, and email address if you choose to provide one. The report may also include a snapshot of publicly visible accessibility signals for that page, such as whether the site is an Accesserty ALLY, whether it has a supported public signal record, source and level, report date, validity date, and known accessibility-statement URL. Signal does not send your full browsing history to us in the background.

Signal reports are received by Accesserty. Maintainers may review reports associated with their current active claim in Console. Releasing a claim ends that access. Reports for unclaimed domains may remain with Accesserty and may not be made available to or resolved by the website maintainer.

G. Accesserty ALLY Applications and Maintenance

When a maintainer with an active domain claim applies for ALLY, we process the account, application status, claimed domains, review outcome, and relevant timestamps. To maintain the program, we may also store revocation time and reason, the date after which reapplication is allowed, Signal report-resolution status, owner-reminder timestamps, and administrator-created spot-check records such as the domain, finding, optional evidence URL, status, and action timestamps.

We use this information to review applications, make reports available to current claim holders for their domains, support reasonable report follow-up, send service reminders or administrator digests through Resend, record spot-check follow-up, and make administrator decisions about whether ALLY remains active. Verified domains present at application and review time are retained as audit snapshots. After approval, ALLY is an account-level maintainer status: later verified active claims may display it, while pending, suspended, released, or reclaimed domains do not. Changing the registered domain set does not automatically revoke ALLY, and other maintenance findings do not cause automatic revocation.

H. Accesserty DevCheck

Accesserty DevCheck's simulations, manual review aids, axe-core scans, and PDF structure checks primarily run locally in your browser or extension. DevCheck does not automatically upload scanned page content, PDF files, manual-review results, or scan results to Accesserty.

If you actively run DevCheck's AI Semantic Check, the extension extracts a bounded sample of the current page's visible text, link names, and selected images that the page itself permits the extension to read, then sends that content to Google Gemini for analysis. Cross-origin images that the page does not permit the extension to read are skipped. If you provide your own Gemini API key, the request is sent directly to Google. If you use Accesserty's free quota, the request is sent to Accesserty's Supabase Edge Function first, then forwarded to Google Gemini. A random extension-instance identifier and an IP hash are recorded to enforce usage limits.

The sample can include link context, alt text, ARIA naming fields, explicitly referenced accessible-name text, and SVG titles, even when those names are visually hidden. Editable content and some CSS-hidden text are excluded. Clipped or off-screen text may still be sampled; the extractor is not a sensitive-data detector.

The AI Semantic Check omits dedicated page/destination/image-source URL fields and does not send the full DOM, browsing history, form input or PDF files to the AI service. URLs appearing in sampled text, names or images may still be transmitted. Google may use inputs and generated responses under its unpaid-service terms to improve products and models, and human reviewers may process them. With your own key, Google's data-use terms depend on that project's billing status and applicable regional terms; supplying a key does not itself guarantee exclusion from model improvement. See the Gemini API Additional Terms of Service. Do not submit confidential, unauthorized, or personal information to unpaid AI services.

Your optional Gemini API key is stored locally in your browser and sent to Google for authentication, not to Accesserty. If you choose to copy or download a report, it can include the current page URL, sampled text, and AI suggestions. This export is created locally; review it before sharing.

I. Accesserty UI Kit

Accesserty UI Kit is an open-source Web Components library. Merely using or downloading UI Kit does not cause us to automatically collect your personal data. If you obtain the package through GitHub, npm, or another third-party platform, that platform may process data under its own policy.

J. Cookies and Local Storage

• Supabase Auth: Used to maintain your Console sign-in session.
• i18n_redirected: Used to remember language preference.
• UTM localStorage: Used to remember first-touch and last-touch website source information.
• pulse_sid and scan cache: Stored in the end user's tab sessionStorage to group one browsing session and avoid duplicate scans in the same tab.
• Extension storage: Signal and DevCheck may use browser extension storage for settings, cache, or temporary state.

Our website may load analytics or diagnostic tools through Google Tag Manager, such as Microsoft Clarity when enabled. These tools may process usage data under their own policies.

2. How We Use Information

• Provide sign-in, Console, Pulse, Signal reports, CRM, and related services.
• Manage Pulse Pro plans, subscription status, feature access, and optional weekly reports.
• Help website administrators view Pulse events and scan summaries for their registered domains.
• Process user reports, contact requests, and service support.
• Review ALLY applications, follow up on reports and spot checks, send maintenance reminders, and record administrator decisions.
• Improve product detection logic, interfaces, and documentation.
• Prevent abuse, forged origins, unauthorized domain use, and security risks.
• Where necessary, use de-identified or aggregated data to understand accessibility and usability trends.

3. Pulse Website Maintainer Responsibilities

Pulse is provided to website owners and maintainers as a maintenance tool. If you install Pulse on a website, you are responsible for deciding whether your own privacy notice, consent flow, accessibility statement, or internal data-processing documentation needs to mention Pulse or similar monitoring tools.

Pulse is designed to collect limited maintenance signals for an account that is authorized to maintain the site and holds the current active claim. It does not provide session replay, heatmaps, screen recordings, full page text collection, form-value capture, or advertising tracking. Pulse data is shown to authorized maintainers for their registered domains and may be used by Accesserty for service support, abuse prevention, diagnostics, and product improvement.

Maintainers may remove a registered domain to release its active claim and may ask Accesserty to remove related Pulse records where deletion is technically and operationally reasonable. End users of a website where Pulse is installed should normally contact that website administrator about the site’s disclosure, consent, and data-processing practices; they may also contact Accesserty if they need help identifying the relevant maintainer, disputing an unauthorized claim, or reporting a concern.

4. Third-Party Services

We use third-party services to provide infrastructure and functionality, including Supabase (database, Auth, Edge Functions), Google OAuth, Google Gemini (DevCheck AI Semantic Check and image alternative-text suggestions), Lemon Squeezy (subscriptions, payments, and taxes), Resend (weekly reports and service email), Cloudflare Pages / CDN, Google Tag Manager, and analytics or diagnostic tools that may be enabled through GTM.

We do not sell your personal data. We may disclose necessary information where required by law, to protect rights, investigate security matters, or in connection with a business transfer.

5. Data Retention

• Account Data: Retained while you use the Service. You may request deletion of your account and related personal data.
• Subscription and Billing Records: Retained during the subscription and for periods required for plan access, accounting, tax, refund, and dispute handling. Payment-card data is handled by Lemon Squeezy under its policies.
• Weekly Reports: Report content is generated from existing Pulse and Signal records. Delivery records may be retained for service support and troubleshooting.
• Contact Form: Retained for response and service records, then deleted automatically 24 months after submission. You may also request deletion before that.
• Signal Reports: Retained to support report review, current-claim access where available, service records, and abuse prevention. Releasing a claim ends maintainer access but does not necessarily delete the report from Accesserty. The report itself is kept, but an email address you chose to provide is cleared automatically after 12 months — the report is a record in an accessibility dispute, while the contact detail is only needed for follow-up.
• Domain Claim Audit: Claim identifiers, normalized domains, account identifiers, and claim/release timestamps may be retained for abuse prevention, dispute handling, and operational audit. Account identifiers are cleared from this audit when the account is deleted where implemented by the database lifecycle.
• ALLY Applications and Maintenance Records: Application decisions, reminder and resolution state, spot-check findings, and revocation records may be retained for program operation, abuse prevention, and audit history. Active domain claims remain separate from ALLY status.
• Pulse Events: Retained for Console display, the weekly report, and diagnostics. An event is deleted automatically once it is both older than 30 days and beyond the most recent events a site can display. Both conditions must hold: on a low-traffic site the visible history can span a long period, so an age rule alone would remove records those sites can still see.
• Pulse Scan Summaries: Only the most recent summary per page URL is kept; superseded summaries are deleted automatically after 30 days. Console and the weekly report only ever read the most recent one.
• Operational Alerts: System failure alerts may include technical detail used for troubleshooting. Resolved alerts are deleted automatically after 6 months; unresolved alerts are kept until they are resolved.
• DevCheck AI Quota Records: The device instance identifier and IP hash used to enforce the daily quota are deleted automatically after 7 days.
• Local Data: DevCheck and browser-extension local data can be cleared through your browser or extension settings.
• About Backups: The automatic deletion described above runs against the live database. System backups are rotated automatically by our infrastructure provider (Supabase) on its own backup cycle, so deleted data may continue to exist in a backup until that backup rotates out. Backups are used for disaster recovery only, never for routine queries, analysis, marketing, or support work. Access to backups is limited to Accesserty operations staff and that infrastructure provider. If we ever restore from a backup, the deletion rules above are applied again on the next scheduled run (daily), so a restore does not bring expired data back for long.

6. Your Rights

You may request access to, correction of, or deletion of personal data we hold about you, and you may ask us to stop unnecessary communications. If you are an end user of a website where Pulse is installed, you may also contact that website administrator about their disclosure, consent, and data-processing practices.

7. International Transfers

Because we use international cloud providers such as Supabase, Google, and Cloudflare, data may be transferred to and stored on servers outside your location or region.

8. Children's Privacy

The Service is not directed to children under 13. We do not knowingly collect children's personal information. If you believe children's data has been improperly provided to us, please contact us.

9. Policy Updates

We may update this policy when our products, legal obligations, or data-processing practices change. Updates will be posted on this page with a revised effective date.

10. Contact Us

If you have questions about this Privacy Policy or wish to exercise your rights, please contact us: service@accesserty.com