Veriteca

Truth, rules and privacy for sensitive AI01

Unlock your data’s power.
Keep it yours.

Build an AI agent from the documents you already own, around the rules your work demands. Choose the boundary it works inside, inspect the evidence behind each answer, and keep the decisions that need your judgement in your hands.

Watch the story Explore the product

Interactive preview · no signup needed

Product updates by email. No trackers. How we use your email.

A private reading room where cited source paths converge on one open evidence folio
01 Your documents stay yours 02 Your sources define truth 03 Your rules govern answers 04 Every claim carries proof

The story in 73 seconds

Why we built Veriteca.

AI is useful enough to create pressure and careless enough to create exposure. See what changes when the boundary, the rules and the proof are yours.

Narrated, with English captions. Prefer to read? Scroll on and the story plays out at your own pace.

The problem

You know the feeling.

AI is useful enough to create pressure—and careless enough to create exposure.

Case 01 · Legal

The solicitor

A weekend of reading, and firm policy rules out the public chatbot.

Privilege is not a prompt setting.

Case 02 · Health

The clinician

Paste in patient notes and they leave your hands.

Confidentiality survives convenience.

Case 03 · Rules

The contract manager

Chat tools can find the words. Strict rules decide the answer.

A match isn’t an answer.

The model shouldn’t decide where your data goes—or which rules apply.

Bring AI to the work that needs care.

With Veriteca

Your boundary. Your rules.

01Privacy

Your documents stay yours.

Build an agent from the documents you choose. Lock the boundary, and outside tools are denied.

02Sources

Your sources define truth.

Point it at the documents that count, down to the version and the date.

03Rules

Your rules govern answers.

Give it the rules your work demands, and every answer is held to them.

04Proof

Every claim carries proof.

Answers come from your sources, with every claim cited and your rules applied. When the evidence isn’t there, it says so.

Meet your next agent

Your expertise.
An agent built around it.

From a library of documents to a conversation you can check. Walk through the five steps.

Interactive product preview. Fictional documents and prepared answers; no model runs and no files are uploaded. Some illustrated receipt features are still in development.

VeritecaSupplier desk · setup preview

01 · Documents

Choose what your agent knows.

Connect folders or individual files. Review the selection, leave out irrelevant material and see what needs attention before processing.

Supplier desk / Documents

  • renewal-addendum.mdCurrent terms · selected✓
  • supplier-agreement.mdEarlier terms · selected✓
  • working-notes.txtDraft notes · excluded—

2 selected · 1 excluded · sample library

Why keep a file out?

An unapproved working note should not become the authority for an answer. Selection lets you decide what belongs in this agent’s evidence.

02 · Rules

Tell it how the work should be done.

Describe a rule or propose rules from an authoritative source. Review proposals and explicitly adopt the ones your agent should follow.

Supplier desk / Rules

  • R-01Use the terms effective on the signing date.
  • R-02Ask for the signing date when it is missing.

2 adopted rules · illustrative policy

What does adoption change?

A suggestion is not yet part of your agent. You review it before including it in the configuration submitted for launch.

03 · Tools

Give it capabilities. See their boundaries.

Search the catalogue and inspect each tool’s purpose, version, permissions and route. Privacy policy determines whether an external tool is allowed or needs approval.

Catalogue preview / Locked policy

Calculator · local route

Purpose: deterministic arithmetic. Inspect a calculation’s inputs and output instead of relying on arithmetic written by a language model.

Web search · denied in Locked mode

An external route can send a query to another service. Review the destination and information sent before considering a different privacy policy.

Catalogue registration and runtime availability are separate. Available tools depend on your installation.

04 · Review

Know what you are launching.

Check the documents, adopted rules and enabled tools together. Resolve blockers, then build and launch a specific agent configuration.

Supplier desk / Review

Documents
2
Rules
2
Tools enabled
0

This sample agent only needs its sources and rules. A tool is a choice, not a requirement.

Preview only · no agent is launched from this page

05 · Conversation

Ask. Inspect. Decide.

Continue a saved conversation, inspect answer evidence and respond when the agent needs your judgement. A missing fact should become a question, not a guess.

Supplier desk / Conversation

What changed in the renewal terms?

The notice period changed from 30 to 60 days for agreements signed on or after 1 July 2026.

Explore the answer and its evidence

The whole workspace, working together.

One place to shape, use and manage your agents.

Your evidence library
Folders, individual files, exclusions, processing progress and recovery when a document needs attention.
Rules you approve
Propose, inspect, adopt or reject rules before including them in an agent.
Tools with context
Catalogue search, manifests, versions, permissions, policy decisions and installation management.
Conversations with evidence
Saved history, answer activity, citations, evidence receipts and explicit human decisions.
Agents you can manage
Resume setup, rename agents, archive a launched agent and prepare a new launch from its draft.
Privacy you can inspect
Review privacy modes, external-tool policy, disclosure requests and the available audit record.

In development: richer rule-source and exclusion receipts, in-app reauthentication and the remaining local launch checks. Join the waitlist to follow progress towards the beta.

Privacy controls

Choose the boundary.
Inspect the route.

Three policies, using the same names you will see in Veriteca. Explore what each means for external tools.

Locked

Keep external routes closed.

Locked policy denies external tools. Local work requires locally available models and tools; a mode label alone is not proof of zero network traffic.

External tools
Denied
Models
Local setup
Verification
Required

Controlled

Inspect a request before approving it.

Controlled policy requires approval for external tools. Review the destination, purpose and proposed disclosure instead of treating a tool switch as permission to send data.

External tools
Approval
Destination
Reviewed
Decision
Explicit

Connected

Connect deliberately.

Connected policy can permit configured external routes. Check tool permissions and provider settings, and use the available disclosure records to understand what was sent.

Route
Configured
Permissions
Visible
Records
Reviewable

These examples explain policy. Actual privacy guarantees depend on the configured deployment and its verified controls.

Try the difference

An answer is
only the beginning.

Check the source. Supply a missing fact. See what happens when the evidence cannot answer the question.

Interactive product preview. Fictional documents and prepared answers; no model runs and no files are uploaded. Some illustrated receipt features are still in development.

Supplier deskPrepared examples · not a live agent

Question

What changed in the supplier renewal terms?

Cited answer

The notice period changed from 30 to 60 days for agreements signed on or after 1 July 2026. Earlier agreements keep their original terms.

Read sample source: renewal-addendum.mdClause 2.1 · sample excerpt
For agreements signed on or after 1 July 2026, the renewal notice period is 60 days. Earlier agreements retain their existing notice period.
Read sample source: supplier-agreement.mdClause 8.2 · sample excerpt
The renewal notice period is 30 days, unless a later addendum applies to this agreement.

Question

How much notice does our agreement need?

Your judgement needed

The answer depends on when it was signed. Which terms apply to your agreement?

Your decision · D-1

You selected: signed before 1 July 2026. The original agreement applies.

Sample answer: 30 days.

Your decision · D-1

You selected: signed on or after 1 July 2026. The renewal addendum applies.

Sample answer: 60 days.

Question

What will the supplier charge next year?

Not enough evidence

I cannot establish next year’s price from these documents. They describe renewal notice periods, not the future pricing schedule.

Next step: add the approved pricing schedule, then ask again.

Read sample source: renewal-addendum.mdClause 2.1 · sample excerpt
For agreements signed on or after 1 July 2026, the renewal notice period is 60 days. Earlier agreements retain their existing notice period.

Build this around your work Join the waitlist for beta invitations.

Built like it means it

Proof points, not privacy theatre.

Veriteca treats every network boundary as something to justify, minimize and record.

  1. 01

    No trackers on this site

    No analytics tags, ad pixels, remote fonts or third-party requests. Even the interactive visual is served by Veriteca. Open developer tools and look.

  2. 02

    Local-first, with checks

    Local-first operation is a development priority. Offline availability depends on the installed models, tools and verified deployment controls.

  3. 03

    Every route is explicit

    External destinations are allow-listed and purpose-bound. Unknown routes fail closed.

  4. 04

    Architecture enforces the promise

    Tests reject stray providers and unapproved disclosure paths before they can become product behaviour.

Private beta

Be first in the reading room.

Help shape Veriteca for your work. Join the waitlist for beta invitations and product updates.

Product updates by email. No trackers. How we use your email.