Retention and Deletion

How retention is determined

Retention takes account of whether the account or task is active, the purpose for which information was collected, customer instructions, contractual commitments, accounting and other legal requirements, security investigations and disputes. Records are not all governed by one fixed period.

Account closure or a cancelled subscription does not itself confirm deletion of every related record. Ask us to confirm the scope and outcome of a deletion request when that confirmation matters for your requirements.

Workspace content and Company Memory

Messages, files, Company Memory and generated outputs support ongoing work and can have separate records or copies. A file added to Company Memory or pending that process is handled separately from an ordinary temporary attachment. Removing an attachment alone does not necessarily remove the information from Company Memory, an output, a conversation or a connected service.

When requesting deletion, identify the relevant workspace and the categories or items involved, including Company Memory where applicable. We can then establish the appropriate authorised steps and any retention requirements.

Temporary attachment expiry and deletion

An expired attachment can become unavailable for a task without being physically erased at that exact time. Deleting an eligible attachment first disables application access; storage deletion may remain pending if the storage operation fails. A pending status should not be interpreted as a completed physical deletion.

Keep your own copy of files needed for ongoing business use. Temporary upload access is not a permanent archive, and the expiry shown in a workflow is not a promise that all related records or external copies are erased on that date.

Operational, approval and billing records

Job history, approval decisions, security and audit records, billing and correspondence may remain after a task or individual file has ended. They support accounting, integrity, investigation, support and the resolution of disputes. Retaining a minimal record that an action or deletion occurred is different from retaining the original file content.

A displayed expiry can describe when an action is no longer permitted, rather than when its decision history is deleted. Product lifecycle settings and cleanup processes do not by themselves establish a universal retention guarantee.

Copies in other services

Information you publish, send or store in a connected service is subject to that recipient's access and retention arrangements. Revoking the connection stops future authorised access through Relsor; it does not recall an email, unpublish a document or delete a third party's copy. Coordinate those steps with the relevant service or recipient.

Make a return or deletion request

An authorised workspace contact can email hello@relsor.ai with the workspace identifier, the information concerned and whether the request is for a copy, deletion or account closure. Do not attach additional sensitive content unless needed through an agreed channel. We may need to verify identity and authority before acting.

We will assess the request against applicable rights, the customer's instructions, contractual terms and any legal need to retain particular records. For customer-controlled data, we coordinate with the customer responsible for that workspace. An applicable DPA can set additional return, deletion and confirmation requirements.