AI data, privacy, and the model

What CLVR sends to the AI model and what it never sends, the Claude model behind every feature, how decisions stay auditable and GDPR-compliant, and where to read the full policy.

Every time you open AI Settings in CLVR, the first thing you see is a Data and privacy panel that sits above all the AI toggles. It applies to every AI feature, not just one, and it spells out exactly what CLVR sends to the AI model, what is never sent, and where to read the full policy. This article walks through what that panel says, names the model behind each feature, and explains how decisions stay auditable and GDPR-compliant, so you can answer the questions your team will ask before turning anything on.

What data is sent

CLVR sends only the minimum each feature needs to do its job. The panel lists this under What data is sent when AI features are used?, and what actually goes depends on which toggles you have enabled:

• Receipt images or PDFs, for the report being scanned or evaluated.
• Benefit category names, so the model can suggest the best match.
• Company policy documents, but only when Company file context is enabled.

If you only have receipt scanning on, no policy documents are involved. The company files are read by the AI only after you turn on Company file context under Auto-approve expense reports.

What is never sent

The panel is just as explicit about what stays inside CLVR. Under What we do not send, it lists:

• Employee names, emails, or other personal data.
• Company information beyond category names.
• Data from other expense reports or benefits.

So a receipt is evaluated on its own, with the relevant category names, and nothing about the person who submitted it or any of their other claims travels to the model.

The AI model behind each feature

Every AI feature in CLVR is powered by Claude from Anthropic. The last part of the panel, AI model and processing, names the model and the handling rules in one place:

• AI features are powered by Claude (Anthropic).
• Only the minimum data needed for each feature is sent.
• Your data is not used to train models.
• CLVR retains only what is necessary for the features to work and for audit compliance.

All three features use the Claude Haiku model from Anthropic. There is no separate provider or model to choose, and nothing for your HR team to configure beyond turning each feature on:

• Allow AI to scan and prefill receipts reads an uploaded receipt and pre-fills the expense form.
• Auto-approve expense reports evaluates wellness (friskvård) reports and approves, declines, or defers them.
• Company file context reads your company policy documents so auto-approval can take your own rules into account.

A person stays in the loop

When AI auto-approval is on, CLVR can approve or decline wellness reports in seconds, but it never takes a person out of the loop. Your HR team has full access to every expense report and can review, revert, or override any AI decision at any time.

• Decisions where AI confidence is below 85% are automatically deferred to manual review, so a borderline call always lands with a person.
• Approved and declined reports both show an AI decision card in the HR expenses view, with the confidence score and the reasons behind the call.
• Any decision can be undone with Revert AI Decision, which sets the expense back to Pending for manual review.

This is the human-in-the-loop principle that GDPR Article 22 asks for: a customer is never left subject to a purely automated decision with no way for a person to step in.

Every decision is logged

Each time AI evaluates a report, CLVR stores a full record of the call:

• The decision (approved, declined, or deferred).
• The confidence score, from 0 to 100.
• The reasons, up to three short bullet points.
• The decline reason, when a report is declined.
• The exact AI model version used for the evaluation.

When your HR team reverts a decision, that is recorded too, including who reverted it, when, and the reason they typed in the Why are you reverting this decision? box. Nothing is overwritten, so the trail of what AI decided and what a person changed stays intact. Receipt scans are also recorded against the employee and report, so there is a history of what the AI suggested.

Employees can push back

A declined report is never a dead end. The employee who submitted it can:

• Open the report, read the decline reason, fix the issue, and use Edit & Resubmit to send it for review again. Resubmitting puts it back through the normal approval flow.
• Contact your HR team directly, who can revert the AI decision and review it by hand.

Transparency you can point to

AI use is disclosed in three places, so nothing is hidden:

• The AI Settings page itself, under How auto-approval works and Data and privacy.
• Your CLVR privacy policy, for how CLVR handles personal and company data.
• The CLVR Trust Center, for security and compliance information.

Both documents open in a new tab from the AI model and processing text. Changes to the AI toggles are also recorded as settings changes for your company, so there is a record of when a feature was turned on or off, and by whom.

Good to know

• The panel does not change based on your toggles: it always describes the full set of what may be sent, so the parts about company policy documents apply only once Company file context is on.
• Reading the panel changes nothing. It is informational, and turning a feature on or off is a separate, deliberate action that you confirm with Save changes.
• AI is an optional capability tied to your environment. If it has not been set up, receipt scanning returns a short "not configured" message instead of scanning (the employee fills in the form by hand), and auto-approval is skipped silently (the report follows the normal review route to your approvers). Nothing breaks: expenses are still uploaded, reviewed, and reimbursed, just without the AI assist.

Troubleshooting

• Which model is running? Claude Haiku from Anthropic, for all three features. There is no model picker.
• I need to undo an AI approval or decline. Open the report in the HR expenses view and select Revert AI Decision. A reason is required, and the expense returns to Pending for manual review.
• An employee disagrees with a decline. They can correct the report and use Edit & Resubmit, or you can revert the decision and review it by hand.
• I want to show our DPO what AI receives. Open the Data and privacy panel on the AI Settings page, then link them to the privacy policy and Trust Center for the full detail.