Use Verachi

Data Collection

See what Verachi stores, what connected tools keep, and how AI uses context.

UpdatedMay 13, 2026

On this page

Verachi stores the data it needs to run your workspace, remember decisions, connect source tools, answer grounded questions, and show risks.

What Verachi stores

Data	Examples
Account data	Name, email, role, login status, workspace membership
Workspace data	Organizations, teams, members, invites, settings, plan limits
Work records	Projects, decisions, comments, links, dependencies, guidelines, risks
Uploaded files	File metadata, the stored file, extracted text when supported
AI and chat data	Conversations, messages, model settings, token usage, cost estimates
Audit and legal records	Activity history, accepted terms, request metadata
Notifications	Notification text, read state, delivery state, preferences
Contact requests	Contact form details, source page, user agent, hashed IP

Connected tools

Slack, Microsoft Teams, Jira, and GitHub stay the source of record.

When you mark something for capture, Verachi may read source content to understand it. Verachi then stores:

a Verachi-written conclusion
the source link
the smallest source IDs and routing metadata needed to find the source again

Verachi does not store raw Slack or Teams threads, Jira issue descriptions, GitHub PR or issue bodies, comments, review comments, linked issue bodies, repository contents, or patches for connector captures.

Uploaded files

Uploaded files are different from connector captures.

If you upload a file, Verachi stores the file and its metadata. For supported files, Verachi also stores extracted text so the file can be previewed, searched, linked to records, and used by AI when allowed.

Documents marked restricted are excluded from AI retrieval and prompt assembly.

AI use

AI features use workspace settings and plan controls.

Verachi may send selected workspace context to the configured AI provider when you ask a question, extract decisions, summarize source content, or evaluate risk. AI usage logs store model, token, duration, and estimated cost data.

Analytics and telemetry

If Google Analytics is configured, Verachi collects browser page-view events. Google Analytics does not receive workspace records, uploaded documents, chat messages, or source tool content from the app.

Server telemetry and operational metrics can be enabled for service health, queue health, errors, and performance.

What Verachi does not store