Your agreement with us

Data Retention, Export and Deletion Policy

In force from 20 September 2026. Version 2026-09-20.

1. Scope and roles

This policy explains how TrueValue Technologies Ltd handles retention, export and deletion across the service. It forms part of the Terms of Service and Schedule 4 of the DPA for Customer Personal Data. Company number 17462580; registered office 66 Paul Street, London, England, United Kingdom, EC2A 4NA. Contact privacy@truevalue.business.

Customer-controlled workspace content is processed according to the customer's lawful instructions. TrueValue separately controls certain account, billing, security and legal records for the purposes described in the Privacy Notice. These categories may have different retention requirements; a reason to keep an invoice is not a reason to keep an entire acquisition data room.

2. Cancellation, closure and individual requests

Stopping renewal normally leaves the paid workspace available until the end of its paid billing period. That is not the same as immediately closing the account or erasing its data. Effective termination is the date paid access ends, unless an earlier termination remedy or agreement applies.

A verified administrator may instruct deletion of customer-controlled content, subject to appropriate authority and applicable legal restrictions. An individual rights request is assessed separately: deleting a person's login does not necessarily remove their name from another controller's lawfully retained transaction record. We do not require closure of an entire organisation account merely to consider an individual's rights.

3. Exports and return of customer content

Use available export functions before termination where possible. You may request a standard export before termination or within seven calendar days afterwards. We will deliver it within seven calendar days of the verified request, subject to a lawful restriction or a different written arrangement. Following termination, restricted assistance or export access is for return of data, not continued use of paid functionality.

A standard export covers customer-controlled records and uploaded files within the service's agreed scope, together with relevant available output and signing evidence. Structured records are supplied in a commonly usable format such as CSV or JSON where appropriate; documents are returned in their available original or export format. We identify any material limitations rather than describing an incomplete extract as a full export.

The export does not include other customers' information, licensed third-party datasets beyond the permitted licence, TrueValue source code or confidential internal security materials. These exclusions do not remove a right to personal data or a copy of customer-owned content required by law or the DPA. We will explain a relevant restriction and provide a lawful alternative where possible.

A standard contractual export is included without an exit fee. Bespoke transformation or migration work outside the standard obligation may be separately quoted and accepted. A payment dispute does not permit us to withhold statutory assistance or an otherwise required export solely to obtain leverage.

4. Active-content deletion

Customer-controlled active content is deleted or irreversibly anonymised within 30 calendar days after effective termination or a verified earlier deletion instruction, except where law requires retention or the customer separately agrees a lawful, time-limited export extension. We will explain a relevant exception and restrict use accordingly.

Deletion must cover relevant database records, uploaded files, derived document text, search indexes, embeddings, generated content, caches and service copies, not merely removal of the user interface. We pass appropriate instructions to appointed subprocessors and manage their residual retention within their agreed terms.

Removing one item may leave a minimal record needed to show that it was deleted or to maintain security, without retaining the unnecessary original content. Irreversible anonymisation must prevent reasonable re-identification; replacing a name with a reversible identifier is not equivalent to erasure.

5. Protected backups

Residual copies in protected backups expire within the verified maximum periods in section 6. They are not available for ordinary customer access, analytics, AI use or marketing. They remain protected by the DPA and may be restored only for authorised recovery purposes, with deletion instructions reapplied before normal processing resumes.

Backup expiry is distinct from active deletion. We do not promise immediate removal from an immutable backup when that is not technically true, and do not use “backups” as an indefinite retention exception. A stricter existing contractual promise must be separately honoured or lawfully varied; this policy does not silently weaken it.

6. Retention schedule

Information categoryRetention ruleResponsibility and scope
Active workspace content, uploaded files and derived contentWhile needed for the subscribed service and customer instructions; delete or irreversibly anonymise within 30 calendar days after effective termination or a verified earlier deletion instruction, subject to the lawful exceptions described above.Customer-controlled content; DPA applies. Earlier valid rights instructions are assessed promptly.
Protected database backupsMaximum seven calendar days after the relevant live deletion, with no routine reuse.Daily backups of the database, taken by our hosting provider in the same London region; each backup is deleted seven days after it is taken, so a deleted record is out of every backup within seven days.
Protected file/object-storage backupsNo separate backup copy of uploaded files is kept: a file deleted from the service is deleted from storage at the time of deletion.Uploaded files are held in our hosting provider's storage in London; database backups do not include them.
Security, access and administrative action logsFor the life of the workspace, then deleted under the active-content rule, for the records the Service keeps of who did what (the audit log, data-room access records, signing events and the Agent's receipts); 90 days from the start of a session for sign-in session records; seven days for the platform request logs our hosting provider keeps; longer only for a documented active incident or legal hold, with periodic review.Identifiers and confidential content minimised. The workspace records are customer-controlled; the session and platform request logs are controlled by us.
Customer documents and signature audit evidenceCustomer instructions and the active-content rule, unless a separately agreed archive term applies. Any independent legal-evidence retention: none. TrueValue keeps no copy of signing evidence outside the customer's workspace; when that content is deleted, the executed documents, certificates and signing events go with it.Customers should retain their own executed records. Do not assume all signing evidence can lawfully be erased or kept indefinitely.
AI prompts, files, outputs and provider-side logsService copies follow the active-content rule; provider residual retention is limited to each provider's published abuse-monitoring period as recorded in the Subprocessor Register: 55 days at Google, the model provider behind our AI gateway, and 30 days at OpenAI or Anthropic where either is used. The gateway operator, Lovable, holds requests under its own data processing terms.Documents reach a provider as extracted text within a request; no file is placed in any provider's file store. No general-purpose model-training reuse.
Support messages and diagnostic attachmentsFor the life of the account that raised them, then deleted with it; unnecessary deal attachments are removed when a ticket is closed where practicable.Controller support records distinguished from customer-instructed content.
Necessary accounting and tax recordsNormally six years from the end of the last company financial year to which they relate, or longer where a specific legal requirement applies.Limited billing and accounting evidence, not blanket retention of workspace content.
Marketing preferences and suppression recordsPreference records for the relevant marketing relationship; minimal suppression information for as long as reasonably necessary to avoid restarting objected-to marketing.Use suppression records only to honour objections and demonstrate compliance.
Contract and complaint evidenceFor the period reasonably necessary to administer the matter and establish, exercise or defend legal claims, assessed against applicable limitation periods; review when the matter closes.Retain only relevant evidence, with restricted access. A disputed matter does not justify indiscriminate retention.

Each period must be supported by a documented purpose and implemented deletion process. A supplier's default retention does not automatically become an acceptable TrueValue retention period.

8. Confirmation, requests and changes

We may verify the identity and authority of a requester proportionately. A material export or deletion instruction should identify the workspace, scope and destination, and whether retention of any specific records is lawfully requested. No ordinary confirmation process extends a statutory deadline unlawfully.

On reasonable request we confirm completion of relevant deletion steps and explain any residual backup cycle or lawful hold. We review this policy and the underlying schedule when systems or legal requirements change. A new policy date alone does not authorise retention for a new incompatible purpose.