Records, originals and data lifecycle
Information handling follows the owner and purpose of each record. Company-local party presentation, immutable commercial evidence, preserved originals, query projections and temporary retrieval links have different lifecycles. Removing one relationship does not automatically erase every copy or invalidate evidence already issued.
Access control determines who can read or change data now. Retention determines which facts remain and why. A signed-link lifetime, cache expiry or source deletion signal does not supply a system-wide retention schedule.
Lifecycle reference
Section titled “Lifecycle reference”| Information class | Owning mechanism | Important limit |
|---|---|---|
| Shared party and company-local profile | Explicit company relationship and private profile/presentation | Another company’s relationship does not reveal this profile |
| Accepted quote/issued financial evidence | Versioned snapshot and immutability/append-only rules | Editing current contact data does not rewrite historical evidence |
| Application files | Object plus linked metadata/resource/audience policy | Removing metadata, deleting an object and revoking admission are separate operations |
| Estate mail/original source | Preserved source identity, policy and lifecycle signal | Toolora’s projection is not a second invented archive expiry policy |
| Signed retrieval URL | Authorized issuance and bounded URL/cache lifetime | Expiry is not physical deletion; already returned bytes cannot be recalled |
| Soft-deleted operational record | Owning domain’s read/write and retained-evidence rules | Soft deletion does not imply ledger/commitment erasure |
| AI/review input | Authorized bounded context with source references | A proposal is not authority to retain or publish unrestricted source material |
| Test and review artifacts | Synthetic/minimized inputs and deliberate distribution selection | Live payloads, personal data and credentials stay out of Git and bundles |
Current presentation and retained facts
Section titled “Current presentation and retained facts”A company profile describes that company’s current presentation of a shared party. It is not the person’s Auth identity. Customer/contact membership, recipient selection and portal admission remain separate relationships. Customer access must establish the exact live person/company context before returning protected data.
Issued invoice and accepted agreement evidence retain their own snapshots. A corrected current address or deleted contact does not silently rewrite what was sent or accepted. Household-work commitment rules retain relevant evidence through soft deletion; deletion is not a way to free a previously consumed deduction commitment without the owning correction lifecycle.
Protected identity data also needs its field-level gate. A valid recipient role or project link is not permission to expose full identity values to every staff, customer or AI audience. Deduction evidence explains the separate review inputs.
Source deletion and incomplete preservation
Section titled “Source deletion and incomplete preservation”The current mail contract records a source policy and uses source_observation.lifecycle for deletion. Toolora reflects source removal when synchronization applies it. A revoked account/administrator relationship is checked on the next API request, while a source-sync lag is a different boundary.
The archive contract does not define a separate expiry schedule that Toolora can promise. Original/attachment coverage remains explicitly incomplete. Do not infer deletion, complete preservation or a new retention duration from a missing projected row. Original preservation owns the source evidence and coverage.
Storage retrieval similarly has its own limits. The browser signed-URL helper caches its authorized URL within the requested lifetime and clears its cache on relevant auth/context changes. Cache clearing is neither object deletion nor a guarantee that a previously issued URL stops working immediately. The Storage reference owns audience-specific retrieval and upload/link recovery.
Synthetic deletion example
Section titled “Synthetic deletion example”A synthetic customer contact loses its customer-wide grant. Future portal admission must re-evaluate all live bases, including any independent direct-project contact. An old downloaded PDF remains a copy; revocation does not recall it. The accepted quote snapshot also remains historical evidence rather than adopting today’s contact profile.
Deleting a draft can release its billing reservation under the domain contract. That does not justify deleting the original of an issued invoice or erasing its audit trail. Billing basis keeps those operations distinct.
Evidence and remaining policy scope
Section titled “Evidence and remaining policy scope”The inspected contracts establish these named lifecycles. They do not establish a complete organization-wide retention/deletion schedule or every legal requirement for every record class. Unspecified durations and external-source coverage remain explicit rather than replaced with a generic number. This documentation pass performs no private-data read, bulk deletion or cleanup.