Skip to content

Privacy Policy

Last updated 14 September 2026

Draft: this document has been prepared as a template and has not yet been reviewed by legal counsel. It will be finalised before Openwell accepts paying customers.

1. Who we are

Openwell provides automated accessibility testing, fix generation, and reporting. [Placeholder: legal entity, address, and contact for privacy requests.]

2. What we collect and why

Account data

Name, email address, and a password hash (Argon2id) — to create and secure your account. If you sign in with Google or GitHub, the identifier and email that provider shares.

Organisation and billing data

Organisation name, plan, and a Stripe customer reference. Card details are entered on Stripe's hosted pages and never reach Openwell's servers.

Scan data

For each site you scan: the pages crawled, their rendered markup, screenshots, accessibility tree, the issues found, and the code changes generated. Scanned pages may contain personal data belonging to your site's visitors or staff; you are the controller of that data and Openwell processes it on your instructions (see the Data Processing Addendum).

Usage and product data

Events such as sign-ups, scans run, and whether a generated fix was accepted, edited, or rejected — to operate the Service, enforce plan limits, and improve fix quality. Server logs and error reports (Sentry) that may include IP address and request metadata, kept for operational security and debugging.

Public scans

Scans run from the public scanner without an account are stored under a throwaway organisation keyed by the scan, together with the requesting IP address for rate limiting.

3. Cookies

Openwell sets only strictly necessary cookies: a session cookie once you sign in, and the security tokens needed to sign in. No advertising or cross-site tracking cookies are set, and no analytics cookies are set today. If analytics that require consent are ever added, a consent prompt will be shown before any such cookie is set.

4. Legal bases (EU/UK)

  • Performance of a contract: account, billing, and scan data.
  • Legitimate interests: security, abuse prevention, product improvement from de-identified fix outcomes.
  • Legal obligation: financial records.

5. Who else sees it

Sub-processors, each under a data processing agreement: [Placeholder: hosting (Vercel), worker compute (Fly.io), database (Neon), queue (Upstash), payments (Stripe), email (Resend), error monitoring (Sentry), AI model provider (Anthropic) for judgement and fix generation.] Openwell does not sell personal data.

6. International transfers

[Placeholder: transfer mechanism — e.g. EU Standard Contractual Clauses / UK IDTA — and hosting regions to be confirmed by counsel.]

7. How long we keep it

  • Screenshots and page snapshots: 90 days by default, then deleted. Deletable earlier on request.
  • Issue records, clusters, and generated fixes: for the life of your account.
  • Account and billing records: for the life of your account plus any period required by law.
  • Public scans: 30 days.

8. Security

Data is encrypted in transit and at rest. Tenant data is isolated by organisation at both the application and database layers. Access is limited to staff who need it to operate the Service.

9. Your rights

You can access, correct, export, or delete your data, and object to or restrict processing, by contacting [placeholder]. EU/UK residents can also complain to their supervisory authority.

10. Changes

We will notify account holders by email of material changes.

Privacy Policy — Openwell