Skip to content

Contact

Reach the right team, carefully.

Route every kind of enquiry — participant, partner, press, cause, developer, legal — to the right place quickly.

See the FAQ

Veraq is built to be checked, so most questions can be answered before you ask one. The pages across this site describe how the system is designed and say plainly which parts are live today. Start there if you can.

When you do need a person, write to founder@veraq.io. Veraq is a small team, so every kind of enquiry below goes to that one address. Start your subject line with the name of the kind that fits, exactly as listed, and it reaches the person who can act on it without a round trip.

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.

Kinds of enquiry

Participant support

Questions about your account, a prediction you made in the sandbox, or how to check an entry on the open record.

Partnerships

Platforms, organisations, and teams that want to build with Veraq or integrate the open record.

Press

Journalists and editors on deadline. Approved language, facts, and assets are on the press page; write for everything they do not cover.

Cause partnerships

Organisations applying to be a verified cause, or asking how verification and the defined share work.

Developers

The open record, commit-reveal-v1, and the contracts and protocol references. Most answers are in the docs; write for the rest.

Legal

Legal, compliance, and regulator-facing enquiries. The legal page indexes the documents most of those enquiries turn out to be about.

Security

Suspected vulnerabilities, or anything that could affect participants or the integrity of the record. Handled first; the steps are below.

General enquiry

If none of the kinds above fit, write anyway. Tell us plainly what you need and, where relevant, the record entry it concerns. A specific reference lets us answer with a specific link.

Reporting a vulnerability

  1. 01

    Mark it as security

    Send the report to founder@veraq.io with “Security” at the start of the subject line. Keep the details out of public channels, issues, and social posts until we have confirmed a fix is in place.

  2. 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.

  3. 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. Veraq does not publish a postal or registered address yet.

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.