Privacy Policy
What we collect, why, who else sees it, how long we keep it, and how to make us delete it.
What we have done so these pages and the product can be used by more people, where we have not got there yet, and how to report something that does not work.
This statement covers the marketing pages under this address and the product itself. It describes what we have actually done and tested, not a standard we would like to be measured against.
We aim at WCAG 2.2 level AA. We have not yet had an independent third-party audit, so we describe our own work honestly rather than claiming a certification we do not hold.
They work without JavaScript. Every page here is real HTML that renders with scripting disabled, which is why they are readable by search engines and by assistive technology that does not run scripts — and it means the pages work on very old or very restricted browsers.
The pages are written in twelve languages, each at its own address, with the language declared in the page itself. Arabic is laid out right to left rather than mirrored from a left-to-right design.
Headings are in order, the main content is marked as the main content, navigation is a labelled navigation region, and the language picker is a real disclosure control that keyboard users can open and close.
The text is sized so that zooming does not hide content or force sideways scrolling, and the colour contrast of the text — including on the buttons and in the footers — has been checked rather than assumed.
There is no advertising tracker and no autoplaying media on these pages, so nothing moves or makes noise while you are reading.
The product is a conversation, and a conversation is a demanding thing to make accessible: it asks you to type, to read an answer, and to follow a thread that changes as it goes.
The interface is keyboard navigable and its controls carry labels for assistive technology, and the text is real text that a screen reader can read and a user can resize. The composer and the message history are ordered so that a screen reader reaches them in the order they appear.
What we have not done is test the whole product end to end with the full range of assistive technology and browsers, and we are not going to claim otherwise in a paragraph of marketing.
No independent accessibility audit has been carried out yet on either the pages or the product.
Most translations of the pages and of the legal documents are produced by a machine translation pipeline and reviewed by us rather than written by a native speaker. Clarity, not only accuracy, can suffer, and we would rather you tell us than struggle.
The product's payment step is a hosted page belonging to our payment provider, so its accessibility is governed by them rather than by us. If it is a barrier for you, write to us and we will find another way to take your payment.
Write to the address on the Contact page and describe what you were trying to do and what happened. If you can, say which browser and which assistive technology you used — it shortens the search for the cause.
We treat an inaccessible page as a bug, not as a feature request, and we will tell you what we are going to do about it.