For compliance and regulatory teams

Every obligation you cite, checked against the text that sets it.

Velydian reads the regulation, guideline or standard behind each statement in a submission and checks that the statement matches it: the wording, the scope and the strength of the obligation.

Free trial, no card needed.

  • Cited or not. Every claim checked, and stronger sources found where the evidence is weak.
  • A record you can keep. Annotated document, audit trail and exports, in minutes.
  • Swiss and private. Data residency in Switzerland, processing in Switzerland and the EU, GDPR compliant.
VerdictIllustration
CLAIM IN YOUR SUBMISSIONNeeds Revision

“The guideline requires annual validation of all internal models.”

What the source says
“Institutions should validate material internal models at least annually.”

Cited guideline, section 4.2

The source says “should” and covers material models only. The submission says “requires” and “all”.

Illustration of a verdict.

The stakes

What an unsupported claim costs.

€35M

Maximum fine under the EU AI Act for prohibited practices, or 7% of worldwide annual turnover, whichever is higher.

Regulation (EU) 2024/1689, Article 99(3)
53%

Environmental claims examined across the EU that were vague, misleading or unfounded. 40% had no supporting evidence at all.

European Commission (2020), study on environmental claims
42%

Green claims on company websites that EU consumer authorities had reason to believe were exaggerated, false or deceptive.

European Commission and national authorities, website sweep (2021)

What it catches

Six things that go wrong in submissions.

Each one with the claim, the passage Velydian reads, and the verdict. Examples for illustration.

“Should” read as “must”

“The guideline requires annual validation of all internal models.”

“Institutions should validate material internal models at least annually.”
Needs Revision

Guidance, and only for material models.

A threshold that does not match

“Transactions above CHF 15,000 must be reported.”

“…CHF 100,000 or more…”
Not Supported

The cited article sets a different threshold.

A deadline from an old version

“Firms have 30 days to notify.”

Current version: “within 72 hours”.
Needs Revision

The cited text was amended.

Scope applied too widely

“The regulation applies to all employers.”

“…applies to undertakings with more than 250 employees.”
Needs Revision

The obligation has a size threshold.

Guidance cited as law

“The law requires a named AI officer.”

The cited document is a supervisory FAQ; the regulation itself does not require this.
Not Supported

Guidance, presented as a legal requirement.

A correctly cited article

“Personal data must be kept no longer than necessary.”

“…kept in a form which permits identification for no longer than is necessary…”
Supported

Matches the regulation, with the article quoted for the file.

Not another fact checker

Not just right or wrong. Supported or not.

Velydian checks the thresholds and deadlines. It also weighs what a submission does with the rule: who it says the rule covers and how strongly it states the obligation. A deadline can be right and the statement around it can still mislead the regulator.

One claim, three levels · illustration“The regulation requires all providers to submit a complete incident report within 72 hours.”Needs RevisionSource: the regulation the submission cites. Example for illustration.
  1. Level 1

    Facts

    Thresholds, deadlines, article numbers and quotations, checked against the text that sets them.

    Does the article say 72 hours or 15 days?

    Velydian findsSupportedThe 72-hour deadline is in the article cited.A citation check stops here: true.
  2. Level 2

    Interpretation

    Whether the rule says what the statement says: must or should, everyone or a defined group.

    Does the rule cover everyone, or a narrower group?

    Velydian findsStretchedThe article applies to providers of high-risk systems only. The submission says all providers.
  3. Level 3

    Judgement

    Whether the statement is as strong as its evidence, and what was left out.

    Is this what the regulator will read in the text?

    Velydian findsOverstatedThe same article asks for an initial notice within 72 hours and the full report later. The submission commits the firm to more than the rule asks.Verdict: Needs Revision. The deadline is right; the statement applies it further than the text does.

How it works

Upload the submission. Every obligation comes back with its evidence.

PDF, Word, text or Markdown, or paste it in. Velydian finds each statement about a rule and checks it in one of three ways.

Against the texts it cites

When a statement cites a regulation, a guideline or a standard published online, Velydian opens it and checks the wording, the scope and whether it says must or should.

Statements with no citation

Velydian searches regulators’ and other official websites, research databases and the wider web, keeps the strongest sources and checks the statement against them.

Against your own files

Attach the regulation, your internal standard or the auditor’s findings, and every statement is checked against them. You see the price before it starts.

Three layers of checking

Surface tools check that a source exists. Velydian reads it.

Layer 1

Distortions and inaccuracies

Thresholds that drift, deadlines from an old version, a scope quietly widened.

A notification deadline taken from a version that was amended.

Layer 2

Bias and fabrication

Obligations the text does not contain, guidance cited as law, and what was left out.

Favourable test results cited; the adverse ones in the same report are not.

Layer 3

Stronger sources

When a statement rests on a summary, Velydian looks for the regulator’s own text.

A law-firm blog is flagged, with the regulation itself offered instead.

One verdict per claim

Four verdicts, each with its evidence.

Supported

The text checked backs the statement as written.

Needs Revision

Close, but the threshold, the deadline, the scope or must against should does not match.

Not Supported

The text does not back the statement, or sets something different.

Unverifiable

No text could be read or found that settles it, for example an internal standard you did not attach.

Open any verdict to see the passage and the reasoning behind it. Correct a line or swap a source and it is checked again. Velydian weighs the evidence; your team decides what to change.

  1. Drop the submission inPDF, DOCX, TXT, MD or pasted text.
  2. Every statement is checkedAgainst the cited text, your own files or independent sources.
  3. Review and correctFix a statement or swap a source; it re-checks.
  4. Take the resultAnnotated submission, regulatory audit trail, executive summary, CSV/JSON exports.

How we test it

Test it on a document you already know.

Our published test results so far are on company reports: see Velydian for Finance. For every other kind of document, the best test is one of your own.

Every verdict, open to inspectionSource + reasonEach verdict shows the passage it rests on and why, so you can check Velydian itself.In every result
When the sources cannot settle itUnverifiableThe claim is marked Unverifiable, with the reason, for a person to check.One of four verdicts
Your own testYour documentRun a submission where you already know the mistakes, and see whether Velydian finds them.First check free

Review the verdict and the reasoning yourself: every one shows its evidence. Your first check is free.

Today and with Velydian

From hours of checking to minutes.

Manual compliance review

Days per submission, risk at the regulator

  • Each citation traced to the source by hand
  • A changed obligation slips through unnoticed
  • Selective use of a source is hard to spot under deadline
  • Little record of how each statement was checked
Velydian on your submissions

Checked before the regulator reads it

  • A full submission checked in minutes
  • Every statement checked against the authoritative text
  • Weak secondary sources flagged, with the primary text offered
  • The quoted passage behind every verdict, kept as an audit trail

What it checks

The documents your team signs.

  • Regulatory submissions
  • Policies and procedures
  • Risk and control assessments
  • AI Act and data-protection documentation
  • Marketing and product claims
  • Board compliance reports
  • Audit responses
  • Training materials

Who uses it

Across the team.

  • Chief compliance officersSign off submissions with the evidence attached.
  • Compliance analystsTrace each obligation to its text in minutes.
  • Legal and riskCheck that policies still match the current rules.
  • Marketing reviewCheck product and green claims before they go out.

What you get back

A record you can keep.

  • The annotated submissionEvery statement marked with its verdict, in place.
  • A regulatory audit trailFor each citation, the passage relied on and the reasoning.
  • Primary textsWhere a source is secondary, the regulator's own text to cite instead.
  • ExportsExecutive summary, CSV and JSON for your records.

Cost

You see the price before you start.

Checking a submission by handCHF 450your rate × your hours
With Velydian, pay as you goCHF 4.8094× cheaper30 cited claims drawn from 10 sources: 160 credits
At the Founder rateCHF 1.60281× cheaperthe same submission, CHF 0.01 per credit

Checking a claim costs 5 credits and reading a source costs 1. Deeper source audits cost more. Your reviewers still read the verdicts; Velydian takes the tracing off their desk.

Questions

Before your first submission.

Does it know which version of a rule applies?

It reads the version your document cites, or the one it finds. If the text it reads differs from your statement, you see both, so you can confirm which version applies.

Can it check our internal policies against the regulation?

Yes. Attach the regulation or your internal standard as your own file, and every statement in the policy is checked against it.

Does it replace our legal review?

No. It does the tracing: finding and reading the text behind each statement. Your reviewers keep the judgement, with the evidence laid out for them.

Can it check marketing claims?

Yes. Paste the claims or upload the material, and attach the test reports or certificates behind them. Each claim is checked against them.

Where do the sources come from?

Three places. The sources your document cites; sources Velydian finds on official websites, research databases and the wider web for claims without a citation; or your own files, if you attach them.

What happens to my document?

When you run a check, your document’s text is sent over an encrypted connection to our servers and AI services in Switzerland and the EU. To find evidence, short search queries built from your claims are sent to web and scholarly search services. Your document’s content and results are deleted automatically about 24 hours after your check; source links and summary data are kept.

Which languages does it check?

English is measured and in daily use. German and French are in validation.

Can I rely on Velydian as my only check?

Velydian supports human review. It shows the evidence behind every verdict so you can decide. In high-stakes work, expert judgement stays essential.

A Swiss company

Data in Switzerland. Processing in Switzerland and the EU.

  • Data residency in Switzerland, processing in Switzerland and the EUGDPR and Swiss data protection terms are covered by our Data Processing Agreement.
  • A Swiss companyVelydian is built by MindtheGap Sàrl in Geneva.