Contact
Reach the right team, carefully.
Route every kind of enquiry — participant, partner, press, cause, developer, legal — to the right place quickly.
Veraq is built to be checked, so most questions can be answered before you ask one. The mechanism behind every wave is published to the open record, every outcome and contribution is written down, and the pages across this site link to the proof. Start there if you can.
When you do need a person, the fastest answer comes from reaching the right team directly. Below, each kind of enquiry is routed to the people who can act on it. Pick the one that fits, and you will skip the front desk entirely.
We answer carefully rather than quickly. A considered reply usually takes a few working days. Time-sensitive security matters are the exception and are handled first.
Where to write
Participant support
Questions about your account, a wave you took part in, or how to verify an outcome on the open record. support@veraq.example
Partnerships
Platforms, organisations, and teams that want to build with Veraq or integrate the open record. partners@veraq.example
Press
Journalists and editors on deadline. Approved language, facts, and assets are on the press page; this contact is for everything they do not cover. press@veraq.example
Cause partnerships
Organisations applying to be a verified cause, or asking how verification and the defined share work. causes@veraq.example
Developers
The open record, commit-reveal-v1, and the published contracts and protocol references. Most answers are in the docs; this is for the rest. developers@veraq.example
Responsible disclosure
Suspected vulnerabilities, or anything that could affect participants or the integrity of the record. Handled first. security@veraq.example
General enquiry
If none of the routes above fit, write to hello@veraq.example and we will pass your message to the right team. Tell us plainly what you need and, where relevant, the wave or record entry it concerns. A specific reference lets us answer with a specific link.
For anything legal, compliance, or regulator-facing, the legal page lists the direct contacts and the documents most enquiries turn out to be about.
Reporting a vulnerability
- 01
Write to security, not to support
Send the report to security@veraq.example. Keep the details out of public channels, issues, and social posts until we have confirmed a fix is in place.
- 02
Describe what you found
Include the steps to reproduce, the affected surface, and what a participant or the record could be exposed to. Concrete detail shortens the time to a fix.
- 03
Give us time to act
We acknowledge disclosures first, before other enquiries. We confirm receipt, work the issue, and tell you when it is resolved. We do not pursue researchers who report in good faith.
Locations
Veraq operates as a distributed team. Correspondence is handled by email rather than by post, which keeps a clear record of what was asked and answered. Where a postal or registered address is required for legal or regulatory purposes, it is listed on the legal page alongside the relevant jurisdiction notes.
Availability differs by market. If you are checking whether Veraq operates where you are, the compliance page is the current source.
Most of what you might ask, you can already check. Write to us for the rest.