Compliance

Retention

Compliance document

Retention

(English original)

Last reviewed: 2026-10-20 · Version: 1.3

The customer is the controller and sets the retention periods for its own data. The product stores everything in the customer's own tenant, so those periods are applied there. The customer's own country sets some minimums that must be followed, above all its bookkeeping law's minimum retention periods for accounting records, and its conditions for keeping those records in another country — for example Germany's HGB § 257 and AO § 147, or Norway's bokføringsloven and bokføringsforskriften. Each country's rules, with their official sources, are on its page in our country notes, sent on request. The install template defaults to an Azure region in Norway.

What the product keeps, and for how long

DataWhereKeptNotes
Data in the connected source systemsEach source systemUnder the customer's policy for that systemFundarem does not change it except through an approved proposal
Ontology objects (the model of the business)The database in the customer's tenantUntil the customer deletes itKept up to date by syncing from the source systems
Object historyThe database in the customer's tenantAppend-onlyThe application cannot change or delete a history row; removal is an administrator task in the customer's database
Proposals and their decisionsCustomer's tenantKept for auditWho proposed, who approved, the outcome
Tool-call auditCustomer's tenantKept for auditParameters and a hash of the output, never the output
Fault logCustomer's tenantKept for operationsA short reason only; no prompt, message or personal data
Pseudonym mapCustomer's tenantWhile the tenant existsKeyed hashes only, never raw values
Assistant threads and memoriesCustomer's tenantUntil deletedStored pseudonymised
AI model callsCustomer's tenant (Azure AI Foundry)Not kept by usThe model keeps no state between calls
Public website request logsHosting provider (see Sub-processors)Per the provider's termsDemo only

Retention in practice

Retention periods are set by the customer and applied by the customer's administrator, with our help.

Back to the overview