Talk to someone who has read the code.
For a walkthrough, a security review, a licensing question or a correction to something on this site.
There is one form and one address. Both reach the same place, and a security questionnaire gets answered with the documents rather than with a page.
What to write about
Four reasons, because the reply differs and saying which one you are helps.
A walkthrough
The most useful session has your own decision in it. Use the walkthrough form, which asks for enough detail to decide whether the session is worth your time.
A security or procurement review
Ask for the data-flow document, the third-party licence scan and the governance status. If something on the security page contradicts what you find, that is a defect in the page and we would rather hear it.
A correction
If a figure, a claim or a limitation on this site is wrong, the repository is the source of truth and the page follows it. Corrections are the most welcome kind of message here.
Licensing
Terms are described in a conversation rather than on a page, because the answer depends on deployment and on how many decisions are in scope.
Send a message
If it is about a specific decision, say what the decision is. If it is a correction, say which page — the more specific the message, the more useful the reply.
Or copy this address into your email service: sales@ananthq.com
This opens your email app. Nothing is submitted by this website; review and send the email to reach us. Please do not include patient data, credentials, financial account information or other sensitive production data.
That address reaches the same mailbox as the ones on the privacy notice. For a security review or a vulnerability disclosure, write to security@ananthq.com.