Contact support
A person reads every message. Picking the right address below just gets it to the right person faster.
Where to write
- Product questions, feedback, and anything general: [email protected]
- Billing, invoices, and refunds: [email protected]
- Accessibility barriers in Complaudax itself: [email protected]
- Security vulnerabilities and responsible disclosure: [email protected]
Reporting from inside the app
If you are signed in, the Feedback screen in the dashboard sidebar is the fastest route for bugs and ideas. It files straight into our backlog with your workspace attached, so we do not have to ask which account you are on.
Answers that are already written
A few questions come up often enough that the answer is already on the site:
- Setup and pairing the extension: getting started with Complaudax.
- Partial coverage, cross-origin frames, and unassigned audits: how to run an audit on any page.
- Plans, the Stripe portal, and invoices: billing, plans, and invoices.
- What we store and what never leaves your browser: how Complaudax handles your data.
Our own accessibility
We audit the Complaudax website, dashboard, and extension panel with the same engine we ship, and publish the result on our accessibility statement. If you hit a barrier we have not listed there, that is a gap in our testing and we want to hear about it.
Common questions
How quickly do you reply?
We aim to reply within two business days. Security reports are triaged the same day we receive them.
What should I include in a bug report?
The page or screen where it happened, what you expected, what happened instead, and the browser you were using. If it involves an audit, the site name and roughly when you ran it is enough for us to find it.
I found an accessibility barrier in Complaudax itself.
Please tell us at [email protected]. Barriers in our own product are treated as defects, not feature requests, and our own conformance status is published on the accessibility statement page.