Jakten AI Data Processing Terms
Document ID: JKT-LEGAL-AIDP-1.2
Version: 1.2
Effective Date: October 16, 2026
Last Updated: October 16, 2026
Document Owner: Northland Ventures LLC (d/b/a Jakten)
Applies To: The AI features of every Jakten module and of Jakten Stafett, the Jakten AI gateway operated on the Jakten Licensing Authority, and any Jakten AI subscription.
These AI Data Processing Terms ("AI Terms") describe how Northland Ventures LLC, doing business as Jakten ("Jakten," "we," "us," or "our"), processes your data when your company uses Jakten's AI features. They supplement the Jakten End User License Agreement, Terms of Service and Privacy Policy, and, for Jakten Stafett, the Jakten Stafett terms. Where these AI Terms and those documents address the same subject for AI features, these AI Terms control for AI features only.
These AI Terms have two parts. Sections 1 to 11 apply to every Jakten AI feature. Each schedule at the end describes the AI features of one Jakten product and what those features send. A product's AI features are available only when a schedule for that product is part of the AI Terms your company has accepted, as Section 10 describes.
In these AI Terms, a "Jakten product" is a Jakten Platform module, such as Jakten Quote, or Jakten Stafett, the workflow product Jakten hosts for your company. Jakten Stafett is "linked" to your company when your company's Jakten account and your Stafett organization have been joined, by a link code made by a company administrator in Jakten Platform or by your company's first Jakten AI purchase made in Jakten Stafett.
1. Opt-In Only
AI features are off until your company accepts these AI Terms. A company administrator accepts them in Jakten Platform. In Jakten Stafett, a Stafett architect of your company's linked organization may accept them on your company's behalf.
Accepting these AI Terms is never required to activate, validate, update or use any Jakten product. A company that does not accept them can use every Jakten feature that does not require AI.
Acceptance applies to the company and to the AI features of every product in the accepted schedules, not to a single user or a single product. It is recorded with the name and email address of the person who accepted, the version accepted, the time of acceptance, and the product it was accepted in. Jakten Stafett is told who accepted by display name only, never by email address.
Using AI features also requires an active Jakten AI subscription.
2. What Is Sent
When your company uses an AI feature, Jakten sends only what that feature needs. The schedule for each product lists what its AI features send and what they never send.
Every AI request also carries instructions written by Jakten that tell the model what to produce. In Jakten Stafett, a request also carries the instructions a Stafett architect of your organization wrote for that step, as Schedule E describes.
No AI feature adds user names, email addresses, passwords or license keys to a request. Requests identify the person who used the feature only by a one-way coded reference.
Some AI features run as a step of a workflow, with no person pressing a button at the time. Such a request carries the coded reference of the person the step is assigned to, and no reference when the step is assigned to no one.
Text a person types, and the content of documents a person asks a feature to read, are sent as they are, including any names they contain.
3. The Route and Our Subprocessors
Each AI request travels to Jakten's AI gateway at licensing.jakten.net, the same host your installation already uses for license activation and validation. A Jakten Platform module sends its requests from your Jakten installation. Jakten Stafett, which Jakten hosts, sends its requests from Jakten's own servers at Vercel. The gateway forwards each request to Anthropic, PBC ("Anthropic"), the provider of the Claude models, and returns the answer to the product that sent it.
Anthropic is a subprocessor of Jakten for AI features. Jakten holds the Anthropic account. Your installation and Jakten Stafett hold no AI provider credentials, and your company has no separate agreement with Anthropic.
Jakten Stafett runs on Vercel, provided by Vercel Inc., and stores its data in Neon, provided by Databricks, Inc., Neon's parent company, both in the eastern United States. For Jakten Stafett's AI features, Vercel carries each request and answer between Jakten Stafett and the gateway, and Neon stores what Schedule E says Jakten Stafett keeps. Both are subprocessors of Jakten for Jakten Stafett.
4. What Jakten Keeps
For each AI request, the gateway records your company, the installation or Jakten product that sent it, the feature used, the model, the number of tokens processed, the credits charged, the time, the coded reference to the person who used the feature when the request carries one, and the AI provider's reference for the request. For a request from Jakten Stafett it also records the link and Jakten Stafett's own reference for the run, so a request repeated after an interruption is answered once and charged once. When the AI provider returns an error, the gateway also keeps the provider's error message.
The gateway does not store the documents, instructions or answers of AI requests.
Where a Jakten Platform module's AI feature produces suggestions or drafts, they are stored in your own Jakten database, together with the person who accepted, edited or rejected each one. That data stays in your database under your control.
Where Jakten Stafett's AI features produce text, it is stored in Jakten Stafett's database for your Stafett organization, as Schedule E describes.
Where an AI feature answers questions, its schedule says whether the questions and answers are kept. Ask Jakten (Schedule B) keeps neither: the conversation ends when the person closes it. Ask the bids in Jakten Quote (Schedule A) and Ask the estimate in Jakten Assurance (Schedule C) keep each question and its answer in your own Jakten database, where the people who can open the package or the estimate version can read them.
Where an AI feature reads a document, its schedule says whether a copy of the document is kept. Jakten Assurance (Schedule C) keeps a working copy of a basis document in your own Jakten database, removed after 30 days unused or when a person asks.
5. Training and Retention at Anthropic
Anthropic states that, by default, it does not use inputs or outputs from its commercial products, including the Anthropic API, to train its models. Jakten does not opt your data in to model training, and Jakten's AI features contain no function that sends feedback to Anthropic.
Anthropic states that it deletes API inputs and outputs within 30 days of receipt or generation, except content that must be kept by law and content flagged as violating Anthropic's Usage Policy, which may be kept for up to 2 years.
To answer follow-up requests faster and at lower cost, some features ask Anthropic to hold a request's documents and context in a cache for up to one hour after their last use. Where a feature processes requests in batches, their results are held at Anthropic, under Jakten's account, until Jakten retrieves them. Both are subject to the retention above.
These statements reflect Anthropic's published commercial terms as confirmed by Jakten on October 15, 2026. If Anthropic changes these terms in a way that affects this section, Jakten will publish a new version of these AI Terms, and AI features will stop for your company until your company accepts the new version.
6. Acceptable Use
Your company agrees to use each AI feature only for the purpose its schedule describes, in connection with your company's projects or its use of Jakten, and in compliance with Anthropic's Usage Policy as it applies to Jakten's use of the Anthropic API.
Your company must not submit content it has no right to process, and must not use AI features to create content that violates law or third-party rights.
Jakten may suspend AI features for a company whose use violates this section.
7. AI Suggestions Are Suggestions
AI features propose; a person decides. No AI suggestion or draft becomes part of your company's work until a person in your company accepts it. Each suggestion shows what it was drawn from, or the reason given where it names no source, and a draft, such as an award narrative or a letter, can be edited before it is accepted.
AI features never enter your estimate's quantities, rates or amounts, or a risk event's probability, cost or schedule impact: a person or an import enters every one. Where an answer gives a figure that Jakten counted from your estimate, Jakten's own code counted it, not the AI model, and the answer labels it as calculated and says what was counted.
In Jakten Stafett, an AI feature that runs as a workflow step writes its text to the step's record, where the people who can read that record can see it before anyone has reviewed it. The step does not close until a person approves, edits or rejects the text, as Schedule E describes.
Some AI features answer questions instead of proposing values. Their answers are information only and never change your company's data. A feature that answers questions is instructed to cite the sources an answer was drawn from, to label any figure it calculated, and to say so when it draws on general practice rather than your documents. Check answers against their sources.
AI output can be incomplete or wrong. Your company remains responsible for reviewing suggestions before accepting them, for checking answers against their sources, and for every decision it makes.
8. Withdrawal
Your company may withdraw acceptance of these AI Terms at any time. A company administrator withdraws from the AI section of the Subscription and billing page in Jakten Platform, where acceptance is given. A Stafett architect of your company's linked organization may withdraw from the Jakten AI section of the organization's settings in Jakten Stafett. After withdrawal, Jakten's gateway refuses AI requests for your company, for every Jakten product, wherever the withdrawal was made.
To stop only Jakten Stafett's AI features while the others continue, set Jakten Stafett's AI spending limit to zero (Section 9), or remove the link between your company and your Stafett organization.
Withdrawal does not delete suggestions, decisions and text already stored in your own Jakten database or in Jakten Stafett.
9. Credits and Limits
AI features consume credits from your company's AI subscription. Every Jakten product your company uses draws on the same credits. Jakten enforces monthly allowances, daily ceilings and per-request limits before any request is sent, and refuses a request that would exceed them. The subscription itself is governed by the Jakten Terms of Service and the terms presented at purchase.
Your company may also limit what one Jakten product spends, monthly and, if it chooses, daily. Jakten Stafett makes no AI request for your company until a Stafett architect sets its monthly limit, and the gateway refuses a Jakten Stafett request that would exceed the limit set.
10. Changes
Jakten may update these AI Terms, including to add a schedule when a Jakten product gains AI features.
A version that only adds one or more schedules, and changes nothing else in these AI Terms, leaves your company's acceptance in force. Once it is published, the added schedules form part of the AI Terms your company has accepted, and the products they describe may use AI features under them. Jakten publishes each version at https://docs.jakten.net/legal, naming the schedules it adds, and the AI section of the Subscription and billing page in Jakten Platform shows which schedules your company's acceptance covers. Your company may withdraw acceptance at any time (Section 8) or set an added product's spending limit to zero where Section 9 allows.
Any other new version takes effect for your company only after your company accepts it. Until then, AI features are unavailable to your company, and every other Jakten feature continues to work.
11. Contact Information
Questions about these AI Terms may be sent to:
Schedule A: Jakten Quote
Purpose. Jakten Quote's AI features help your company evaluate vendor bids and quotations for its projects. They read bids, map bid lines to your project, propose adjustments for leveling, analyze qualifications, draft the award narrative, polish clarification, RFI and BAFO letters, and answer questions about a package's bids (Ask the bids).
What is sent. Reading bids, mapping, proposing adjustments, analyzing qualifications and Ask the bids each send the package's name, reference and scope description. In addition:
Reading bids: the bid and package documents a person asked Jakten Quote to read. That is the text of each page with its position on the page, page images of scanned or photographed pages, the paragraphs of Word and text documents, and the rows of a workbook that Jakten Quote could not read itself
Mapping: each bid line's description, section, quantity, unit and area as the bid states them, and the vendor's name; your project's work breakdown structure (WBS), with each element's code, name, parent and unit, the package's scope within it and any scope note; your project's areas and your company's units, with their codes and names; and up to 100 examples of mappings your company previously confirmed, from any of its projects (the line description and unit as written, the codes chosen, and whether the suggestion was corrected)
Proposing adjustments: the package's takeoff (descriptions, quantities, units and WBS codes); the bidders' names and currencies; the bidder's own lines with their rates and amounts, and the text of any exclusion. As evidence, the comparable lines of the other bidders; the lines of the Jakten Assurance package basis bound to the package, where there is one (description, quantity, unit and amount); and rate statistics from your company's rate library, which draws on your company's other packages and projects (the low, median and high rate, the number of rates and of bidders, the period searched, and the WBS code and unit, without the projects or bidders they came from)
Analyzing qualifications: the bidder's name and currency, its qualifications and commercial terms, its lines with descriptions, quantities, units and amounts, and Jakten Quote's checklist for the kind of scope
Drafting the award narrative: what the award recorded: each bidder's name, revision, stated, raw and leveled totals and rank, and the spread between them; the adjustments, with their type, the takeoff row each applies to, and the reasons written for them; the package's risk register (each entry's bidder, type, title, severity, status, disposition, exposure and clarification text); the carried bid's qualifications; and the open items acknowledged with the award
Polishing letters: the letter's text as written, and the questions, notes and quoted qualifications it was assembled from
Ask the bids: the question as the person typed it; each current bid's bidder name, revision, status, currency and stated total; the file names of the package's and the current bids' documents, including those not sent; the documents (PDF and text files in full, the paragraphs of Word documents, the rows of workbooks, and the lines, qualifications and terms a person accepted from scanned bids); and the package's risk register (each entry's title, severity, status, disposition, exposure and clarification text). Earlier questions and answers are not sent
Anything a person types, such as a question, a letter, an adjustment's reason or a clarification, is sent as typed. Do not type personal or confidential details into them that the feature does not need.
What is never sent by Jakten Quote's AI features:
Jakten Risk data
Your Jakten Assurance estimates, other than the package basis lines sent when proposing adjustments
Other projects' bids, documents, lines or takeoffs. The only data drawn from other projects is the mapping examples and the rate statistics described above
Batch processing. When a person chooses to have a package's bids read or mapped overnight, Jakten Quote sends them as a batch under Section 5.
What is kept. Suggestions and drafts are stored in your own Jakten database under Section 4. Ask the bids keeps each question and its answer there, with the name or email address of the person who asked, and everyone who can open the package can read them.
Schedule B: Jakten Platform
Purpose. Ask Jakten answers questions about how to use Jakten, from Jakten's own published customer documentation, with each answer citing the documentation it was drawn from. A person can ask from the Help page or from the top bar of any Jakten module.
What is sent:
The question as the person typed it, and the earlier questions and answers of the same open conversation
Jakten's own published customer documentation
When the person asks from a module's top bar, the name of the module and the name of the section they have open, such as "Living BoE"
Anything a person types into a question is sent as typed. Do not type confidential project details into a question.
What is never sent by Ask Jakten:
Your projects, estimates, risk models, bids or any other data stored in Jakten
Files, record identifiers, or the content of the page the person has open
What is kept. Neither your installation nor the gateway stores the question or the answer (Section 4). The gateway keeps only the usage record described in Section 4.
Schedule C: Jakten Assurance
Purpose. Jakten Assurance's AI features help your company build and explain its estimates. They suggest how an imported workbook's columns and codes map to your project, answer questions about an estimate version (Ask the estimate), draft metric definitions, read the basis documents a person attaches to propose assumptions, exclusions and other Knowledge, and draft text for the Basis of Estimate and the slides of an estimate review.
What is sent:
Import suggestions: the column headers of the workbook being imported and a sample of its cells (at most 20 rows); the codes Jakten Assurance could not match, with their descriptions; your project's work breakdown structure (WBS), with each element's code, name, parent and unit; and your company's units with their alternative spellings
Ask the estimate: the question as the person typed it. To decide what a question asks Jakten to count: the estimate 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 value that is missing marked as missing; the version's current Knowledge; the text of its Basis of Estimate; the basis documents a person attached to the version; and, for a question Jakten counted, a summary of the count (what was counted, in words, the result and its unit, the number of items, and what was left out). Earlier questions and answers are not sent
Drafting metric definitions: the person's description of the metric; your company's measures, units and cost types; your company's classification library; and, when a draft is retried, that earlier draft and the reasons Jakten Assurance's own checks refused it
Reading basis documents: the pages of the basis document a person asked Jakten 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
Drafting for the Basis of Estimate: the heading of the section being drafted and the labels of the blocks around it; the person's instruction, if any, and the text already in the block; the version's verified totals and other governed facts; the version's current Knowledge; the text of its Basis of Estimate; and the basis documents a person selected
Drafting for a review slide: the review's name and milestone; the slide's title and the labels of what else is on it; the person's instruction, if any, and the text already on the slide; the review's findings (each one's title, severity and status), the decisions the review requests, and the risk position the review shows, from Jakten Risk, as the review's slides show them, or as they were captured when the review was marked ready to present; the text of the Basis of Estimate; the version's current Knowledge, or, once a review session has started, the Knowledge the session pinned; and the basis documents a person selected. The review's actions, and the people they are assigned to, are not sent
Anything a person types, such as a question or a description, is sent as typed.
What is never sent by Jakten Assurance's AI features:
People's names, user names and user identifiers, including the name of a decision maker
The web links recorded as evidence. Jakten Assurance never opens a link to fetch a document; a basis document is read only from 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, which never reach a slide
Superseded or reversed revisions, and any other project's or estimate version's data
Batch processing. When a person chooses to have a basis document read overnight, Jakten Assurance sends the requests as a batch under Section 5.
What is kept, in your own Jakten database under Section 4:
Each suggestion and draft, with its sources, the reason given for it, and what the person changed when accepting it
Each question asked of Ask the estimate, with its answer, its sources, what was counted, who asked, and the version of the estimate it was answered from. A counted answer is kept as the description of what to count, not as a number, and Jakten Assurance counts it again when it is opened; it shows when the estimate has changed since
A working copy of each attached basis document's file and the text read from it, marked as a copy. It is removed after 30 days unused, or when a person asks. The record of evidence for anything accepted from it is the link to the document in your company's own document system, never the copy
Schedule D: Jakten Risk
Purpose. Jakten Risk's AI features help your company describe its project risk. They draft the summary of a sealed analysis for the full report, and draft risk events for a person to complete.
What is sent:
Drafting the analysis summary: the sealed analysis result's figures and the drivers of its contingency (such as estimate uncertainty, quantity growth and risk events), as the seal froze them
Drafting risk events: the scenario's estimate, by WBS element and cost type, with each element's description (at most its 400 largest lines; for the scenario bound to an estimate version, as Jakten Assurance published it); the Knowledge Jakten Assurance published for that version (each item's type, title, statement, rationale and category), when the scenario is bound to that version; the risks recorded in the Jakten Quote awards bound to the project that were accepted or are awaiting clarification and that the bidder does not carry (each one's title, type, severity, and exposure where it was priced, with its currency); the names and WBS elements of the risk model's existing events; and the names of the project's drafted events still awaiting a decision, so none is drafted twice. Dates, and the names Jakten Risk records for owners, are removed from the text Jakten Risk holds before it is sent. The Knowledge and the Quote risks are sent as Jakten Assurance and Jakten Quote published them, including any date or name a person wrote in them
What is never sent by Jakten Risk's AI features:
User names and user identifiers, and the names Jakten Risk records for owners
Recorded actions and their due dates
The scenario's name, and any other project's data
By drafting the analysis summary: the working risk model, other scenarios, and the settings or results of any simulation run other than the sealed result being summarized
By drafting risk events: the risk model's probabilities, impacts, delays and ranges, its other settings, and the results of any simulation run
What AI never does in Jakten Risk. It never proposes a risk event's probability, cost impact or schedule impact: the person accepting a drafted event enters every number. It never runs inside a simulation, changes its inputs or seeds, or changes a sealed result.
What is kept, in your own Jakten database under Section 4:
Each drafted analysis summary, with the text drafted, the result of Jakten Risk's check, the model and who drafted it, and the person's decision on it. Only an accepted summary prints, on the full report of the sealed result it was drafted from
Each drafted risk event, with its name, notes, WBS element, its sources, and the published records it was drafted from
Schedule E: Jakten Stafett
Purpose. Jakten Stafett's AI features help your Stafett organization run its estimating workflows. As a step of a workflow, they write a short summary of how a deliverable's run compares with the previous run (Estimate Delta Summary) and a brief of whether a committed date still holds (Commitment Brief). Import workflow reads a picture or PDF of a workflow so a person can build it in Jakten Stafett.
What is sent:
Estimate Delta Summary: the deliverable's name and code; the workflow's steps, each with its name, planned and actual working days, and slip; the steps completed, the elapsed days and the number of rework loops; the same figures for the previous completed run of the same workflow on the same project; and the steps that overran in both runs
Commitment Brief: the deliverable's name and code; how its date was committed, the committed date, and the basis a person typed when committing it, such as a revision or a letter reference; the latest start that still meets the date, the open steps, the step with the least slack and its slack, and how many days short the date is; and the other deliverables it waits for in the newest schedule revision imported for the same project, with their dates and how many days short each is
Both: the instructions and guardrails a Stafett architect wrote for the step's skill, inside Jakten Stafett's own instructions
Import workflow: one picture, or one page of a PDF, of a workflow that a person chose to upload, sent as it is with everything it shows. A picture can show people's names, for example a lane named for a person, and Jakten Stafett cannot remove them; it says so before anything is sent. When a person chooses a page of a PDF, only that page is sent. The request carries the coded reference of the person who sent it (Section 2)
Names of deliverables, steps and workflows, and the basis typed for a commitment, are sent as people typed them.
What is never sent by Jakten Stafett's AI features:
People's names, email addresses and user identifiers, except where a picture or PDF page a person chose for Import workflow shows them. The facts name no person; a request carries only the coded reference Section 2 describes
Comments, notes, corrections, review edits and notifications
Files and attachments, other than the picture or PDF a person chose for Import workflow
Any other project's or Stafett organization's data
Any Jakten Platform module's data, such as estimates, risk models or bids
Steps that run with no person pressing a button. When a workflow reaches a step whose skill an architect has set to use Jakten AI, Jakten Stafett queues the step and sends its request within minutes, with no person pressing a button. A person may also retry a step that failed. Each request carries the coded reference of the person the step is assigned to, or none when the step is assigned to no one (Section 2), and counts against Jakten Stafett's spending limit (Section 9). Every step's text then waits for a person's review (Section 7).
What is kept, in Jakten Stafett's database for your Stafett organization:
For each AI step: the facts sent, the text returned, the text a person approved or edited, the model, the tokens and credits used, and the gateway's and the AI provider's references for the request. No record maps a coded reference back to a person
Who can read it: the people in your organization who can see every workflow, such as architects and managers, and anyone who can see the step's work item. Only architects see the list of every AI step in the organization
How long: while your organization exists. It is deleted with the organization, or 90 days after its Jakten Stafett subscription ends. It is included in your organization's export
Import workflow: the picture or PDF page is not kept. It is held only while the request runs, and is shown in the person's browser only while the page is open. What was read from it (the steps, the words of the lane each step sits in, which can be a person's name, and the arrows) is kept only if the person chooses to keep it, as a reading of the project, kept, deleted and exported like the project's other readings; a lane's words become the step's responsible text. Each read's charge is recorded whether or not it is kept: the credits, the gateway's reference, the file type, the outcome and the number of steps read, and nothing from the picture