Compliance
Lawful, to recognised standards, across jurisdictions.
How Veraq operates lawfully and to recognised standards across the jurisdictions it serves.
Veraq is built to be lawful in the open, the same way it is built to be checked in the open. Compliance is not a layer added after the fact; it shapes which jurisdictions a wave is offered in, who may take part, and what is written to the open record. This page describes that approach in plain language.
It is a description of how Veraq operates, not the binding text itself. Where a specific obligation, threshold, or eligibility rule applies, it lives in the relevant policy document and is stated there exactly. Here we set out the shape of the system so that a participant, a partner, or a regulator can see how the pieces fit before reading any one of them in full.
Regulatory approach
Veraq treats each market it serves on its own terms. A wave is offered in a jurisdiction only where Veraq has assessed that it can operate lawfully and to recognised standards there, and availability follows that assessment rather than the other way around.
The same property that makes a wave auditable makes it easier to evidence: the mechanism is committed to the open record before the wave runs, and every participation, outcome, and contribution is recorded. Where a regulator needs to follow what happened, the record is the same one anyone else can read.
What compliance covers
Availability by jurisdiction
Whether a wave is offered in a given market, decided per jurisdiction and kept current as rules change.
Identity and eligibility
Checks that confirm a participant may take part — age, residence, and any market-specific requirement — applied before participation.
Recognised standards
The security, data-protection, and operational standards Veraq holds itself to, and the reviews that test them.
Reporting and audit
How Veraq evidences its operation to regulators and independent reviewers, drawing on the same open record participants can read.
Public-benefit handling
That the defined share routed to verified causes is recorded from outcome to cause, so its handling can be checked rather than asserted.
A route for regulators
A direct way for a regulator or compliance officer to reach the team responsible, named on this page.
Jurisdictions and availability
Where Veraq is available, and where it is not yet, is determined market by market. A wave that is open in one jurisdiction may be unavailable in another, and a participant’s eligibility is confirmed against the rules of the market they are in.
The current list of supported jurisdictions, and the conditions that apply in each, is maintained as part of Veraq’s binding policy documents rather than fixed in this description. Availability can change as assessments are completed or as rules change, so the authoritative list is the one published alongside the policies, not this page.
Identity and eligibility checks
- 01
Eligibility is confirmed first
Before a participant joins a wave, Veraq confirms they may take part in their jurisdiction — including age and residence requirements and any market-specific condition.
- 02
Identity is verified proportionately
Identity checks are applied to the degree the market requires, using established providers, and are designed to ask for no more than is needed.
- 03
Records are kept as required
Information needed to evidence eligibility is retained for as long as the applicable rules require and no longer. The specific periods are set in the Privacy Policy, not invented here.
- 04
Access reflects the outcome
A participant who does not meet the requirements of their jurisdiction is not able to take part there. Eligibility is a gate, applied before participation, not a check made after the fact.
Standards, certifications, and audit posture
Veraq holds itself to recognised standards for security, data protection, and operational integrity, and intends to evidence them through independent review rather than self-assertion. The principle is consistent with the rest of the platform: a claim is worth what it can be checked against.
Specific certifications, the bodies that issue them, and the dates they apply from are stated only once they are genuinely held. Where a standard is in progress rather than complete, it is described as in progress. This page will not list a certification Veraq does not yet hold, and the reporting and audit cadence is documented in the binding compliance materials as it is finalised.
The binding legal and compliance text is drafted and reviewed with legal counsel, and is not yet final. Treat this page as a plain-language description of the approach, not as the policy itself; where the two differ, the published documents govern, and any figure shown here is illustrative.
Reaching the compliance team
A regulator, auditor, or compliance officer can reach the team responsible for these matters directly. Enquiries are routed to the people who can answer them, and Veraq answers carefully rather than quickly. Use the contact route to reach compliance, and reference the jurisdiction your enquiry concerns so it can be directed without delay.