DPA version history
Current and superseded versions of the Fronset Data Processing Agreement, published by KAPUA Labs LLC, doing business as Fronset.
KAPUA Labs LLC, doing business as Fronset — Fronset inference and evaluation API
This page is the version history referred to in DPA §15.4. The version a customer accepted or executed governs the relationship between the parties until it is amended under §14.4 or replaced by a later version that customer accepts or executes.
Current
| Version | Effective | Document |
|---|---|---|
2026-09-15 | On acceptance | Data Processing Agreement |
Superseded
| Version | Status | What changed |
|---|---|---|
2026-09-14 | Superseded by 2026-09-15 | The Service is renamed Fronset and the trading name is added to the Processor’s entity line; the register and version-history addresses in §7.4, §15.4 and Annex B move to fronset.ai/legal/. No term changed. |
2026-09-08 | Superseded by 2026-09-14 | Retention. §6 now states that Model Output on the shared_anon and private tiers is retained only until it has been delivered and evaluated, then deleted, with an undelivered result held for at most seventy-two hours — the fixed expiry that §6.2 of this version undertook to give notice of; 2026-09-14 is that notice. A Registered Template’s taxonomy evaluation is one-time and bounded (new §6.6), after which the customer may delete the Template text; evaluation evidence is retained for the customer’s own review only on the customer’s own criteria and for a window the customer controls (new §6.7). §8.1’s retrieval and export rights are narrowed to what §6 retains on the tier. The §8.3(a) exclusion of Registered Template content from erasure is withdrawn — Template text is now erased under §8.2(a), and registered output schemas take the exclusion’s place. §9.4 describes the continuous retention sweep. |
2026-08-21 | Superseded by 2026-09-08 | §7.1’s Model Providers row and Annex B’s enumeration are brought into line with §7.2A (operator-supplied serving), which they contradicted; Metronome, Cloudflare and tawk.to are added to the Subprocessor register; and §9.5’s error-monitoring description is corrected to state what the configuration does. |
1.1 | Superseded by 2026-08-21 | Same terms. The version namespace moved from semantic versioning to the date-based scheme shared with the Terms of Service and the Privacy Policy, so that one version string identifies one text across all three documents and across the consent record. |
1.0 | Superseded by 1.1 | §4.2(c) warranted without qualification that customer content is never submitted within another customer’s evaluation or judge prompt. 1.1 added the shared-judging exception for the free and shared_anon tiers, under which model output — and no other customer content — may be scored in the same judge prompt as another customer’s output for the same capability, without identity and without disclosure of either party’s output to the other. The exception does not apply on private. |
No version of this DPA has been executed by signature. Versions 1.0 and 1.1 were
published for acceptance but superseded before any customer accepted one, so no customer
relationship is governed by them.
How amendments work
Where the DPA was accepted at sign-up (§15.1, free and shared_anon), we may amend it on
thirty days’ notice to your registered account address. If an amendment materially
reduces the protections given to your content, you may terminate the affected service
without penalty by notice given before it takes effect.
Where the DPA was executed by signature (§15.2, private), no amendment takes effect
without your written agreement, except one strictly necessary to comply with a change in
applicable privacy law.