Jakten Assurance AI Data Handling

Audience: Company administrator, IT and security reviewers

Last updated: 2026-10-16

Applies to: Jakten Assurance with a Jakten AI subscription, under the *Jakten AI Data Processing Terms* version 1.2

This page summarizes what Assurance's AI features send, where it goes, and what is kept. The *Jakten AI Data Processing Terms* (https://jakten.net/legal/ai_data_processing/v1.2), Schedule C, are the full list and govern where the two differ.

1. Summary

AI is off until a company administrator opts in to the *Jakten AI Data Processing Terms*, and the company has a Jakten AI subscription.
AI proposes; a person decides. Nothing an AI feature suggests becomes part of your estimate, its Knowledge, a metric, the Basis of Estimate or a review until someone on your team accepts it.
AI never writes an estimate value. It never enters a quantity, rate or amount. When an answer gives a figure Assurance counted from your estimate, Assurance's own code counted it from the Version's verified totals, and the answer says it was calculated and what was counted. Every other figure in an answer cites the governed figure or the basis document it came from, or is simple arithmetic on figures already in the answer, shown as its own expression and recomputed by Assurance's check.
Assurance works without AI. Imports, the crosswalk, the estimate, Knowledge, metrics, the Living BoE, reviews, publication to Jakten Risk and every report work with AI off and with no internet.

2. What each feature sends

Feature	What it sends
Import suggestions	The column headers of the workbook being imported and a sample of its cells (at most 20 rows); the WBS codes Assurance could not match, with their descriptions; your project's WBS (each element's code, name, parent and unit); and your company's units with their other spellings
Ask the estimate	Your question (earlier questions are not sent). To decide what to count: the Version's measures, units and cost types, your project's WBS and your company's classification library. To answer: the Version's verified totals by package and by WBS element, with any missing value marked missing; its current Knowledge; the text of its Basis of Estimate; the basis documents attached to the Version; and, for a counted question, a summary of the count (what was counted, in words, the result and its unit, the number of items, and what was left out)
Draft metric with AI	Your description of the metric; your company's measures, units and cost types and its classification library; and, when a draft is retried, the earlier draft and the reasons Assurance's checks refused it
Reading a basis document	The pages of the document a person asked Assurance to read (their text, or page images of scanned pages), and the titles of the Version's current Knowledge, so it does not propose them again
Draft with AI, in the BoE composer	The heading of the block and the labels of the blocks around it; your instruction, if any, and the text already in the block; the Version's verified totals and other governed facts; its current Knowledge; the text of its Basis of Estimate; and the basis documents a person selected
Draft with AI, in the review slide builder	The review's name and milestone; the slide's title and the labels of what else is on it; your instruction, if any, and the text already on the slide; the review's findings (each one's title, severity and status), the decisions it requests and the risk position it shows, as the review's slides show them; the text of the Basis of Estimate; the Version's Knowledge (once a review session has started, the Knowledge the session pinned); and the basis documents a person selected

Text a person types is sent as typed, and documents as they are, including any names in them.

Never sent: people's names, user names and user identifiers, including a decision maker's name; the web links recorded as evidence (Assurance never opens a link to fetch a document: it reads only the file a person attached); the estimate's individual line items and their amounts, other than the import sample above; a finding's statement, conclusion or recommended action, and a review's actions and the people assigned to them; superseded or reversed revisions; and any other project's or Version's data.

3. The route

Your Platform Server (or, in a single-user deployment, your workstation) sends each AI request to Jakten's gateway at licensing.jakten.net, the same host already used for license activation and validation. The gateway forwards it to Anthropic, PBC, the provider of the Claude models, and returns the answer.

Jakten holds the provider account. Your deployment holds no AI provider credentials, and you have no separate agreement with Anthropic. Anthropic is a subprocessor of Jakten for this service.
Requests identify the person who used a feature only by a coded reference, never by name or email address.
A basis document read overnight is sent as a batch, held at Anthropic under Jakten's account until Jakten retrieves the result.

4. What is kept

By Jakten's gateway: a usage record of each request (your company and installation, the feature, the model, the tokens, the credits, the time, the coded reference to the person, and the AI provider's reference for the request), and the provider's error message when it returns an error. It does not store the documents, questions or answers.
In your own Jakten database:
each suggestion and draft, with its sources, the reason given for it, and who accepted, edited or rejected it and what they changed;
every question asked of Ask the estimate, with its answer, its sources, what was counted, who asked and the state of the estimate it was answered from, readable by everyone who can open the Version. A counted answer is kept as what to count, not as a number, and Assurance counts it again when it is opened, saying so when the estimate has changed since;
a working copy of each attached basis document and the text read from it, marked as a copy and removed after 30 days unused or when a person asks. The evidence for anything accepted from it is the document's link in your own document system, never the copy.
At Anthropic: Anthropic states that it does not use inputs or outputs of its commercial API to train its models by default, and deletes them within 30 days, except content it must keep by law or flags under its Usage Policy (kept up to 2 years). Jakten does not opt your data in to training. The terms, section 5, give the dates these statements were confirmed.

5. Turning AI on and off

To turn AI on, a company administrator opens Administration → Licensing → Subscription and billing and, in the AI panel under AI data processing, selects Opt in…, reads the *Jakten AI Data Processing Terms* it links, and confirms. The opt-in covers the whole company and every Jakten module. Your company also needs a Jakten AI subscription (Company Administrator Guide, section 10).

To turn AI off, an administrator selects Withdraw… in the same place. Jakten's gateway then refuses AI requests for your company, so "off" does not depend on each workstation. A new version of the terms pauses AI until an administrator opts in to it.

Withdrawing deletes nothing already in your Assurance database: accepted values, suggestions and decisions, and the questions asked, stay yours.

6. What still works without AI or without internet

Works with AI off or offline	Needs AI and internet
Importing, exact matches to your WBS and the crosswalk, and mapping by hand	Import suggestions
Counting an estimate with a metric, and opening a kept answer, which is counted again	Ask the estimate
Building and publishing metrics by hand	Draft metric with AI
Knowledge, design basis records and their links	Reading a basis document
The Living BoE, reviews and the review deck	Draft with AI in the BoE composer and the review slide builder
Publishing to Jakten Risk, and every report	—

When an AI feature cannot run, Assurance shows why: offline, AI off, not opted in, no subscription, or credits used up. It never skips the step silently.