Privacy Policy

Collection

We collect only the information needed to run DAC Web Auditor.

DAC Web Auditor

• Account details from Clerk sign-in, including email address, name, and authentication identifiers.
• Audit project data for auditor and admin users, including project names, scan results, and evidence you upload.
• Usage analytics from Vercel Analytics, such as page views. This is not used to identify you.

DAC Web Auditor

• Account email, role, and an extension session token after you sign in with your DAC account.
• The role you choose in the welcome dialog (for example developer or designer), stored only in the extension.
• The URL of the page you scan and the accessibility results.
• On fallback scans, a JPEG screenshot of the visible tab so the report can show the page as you saw it.
• If you opt in: cookies for the current tab (name, value, domain, and path). Cookies are not read until you agree in the side panel.
• Extension settings, such as highlight preferences, stored in Chrome sync storage.

Handling

We use this information to operate the products you asked for. We do not use it for advertising.

• Account data signs you in, keeps your session, and chooses whether the extension shows Open full results or Open in Audit Workbench.
• The scanned URL, accessibility results, and optional screenshot produce the accessibility report.
• Cookies, when you opt in, are sent to DAC’s scanner so it can open a page you are already signed into. They are used only for that scan.
• Newsletter email is used to send the updates you subscribed to. You can unsubscribe at any time.
• Disconnecting the extension revokes the current session token. Signing out of DAC Web Auditor ends your Clerk session.

Storage

• Extension account email, role, and token are stored in chrome.storage.local on your device.
• The welcome-dialog persona is stored only in chrome.storage.local.
• Extension settings, including cookie consent, are stored in chrome.storage.sync.
• Scan progress for the open tab is stored in chrome.storage.session and is cleared when the browser session ends.
• Scan jobs, including optional cookie values, are queued in Redis and kept until the job is removed. Cookie values are not written into scan result records in Postgres.
• Accessibility results, account records, bookmarks, newsletter subscriptions, and audit project data are stored in Postgres used by DAC Web Auditor and the scanner API.
• Fallback screenshots are sent to the scanner API over HTTPS and stored with the scan job they belong to.

Sharing

DAC does not sell this information. We share it only with the services that run the product:

• DAC Web Auditor is hosted on Vercel.
• The scanner API runs on Railway at api-production-2a66.up.railway.app.
• Clerk provides sign-in and account authentication.
• Redis holds scan queue jobs until they are removed.
• Postgres stores scan results and DAC Web Auditor application data.

We may also disclose information if required by law. For access or deletion requests, contact contact@auditor.digitalaccessibilitytraining.org.

Changes

If this policy changes, we will update this page and the date above. Continued use of DAC Web Auditor after an update means you accept the revised policy.