DRAFT — not approved for public service use
Version: 2026-09-18.6
Effective: 2026-09-18

# Data Return, Account Closure and Deletion

This policy describes how to leave **Free S3** and what happens to data. It supplements the [Terms](/legal/terms), [Privacy Notice](/legal/privacy) and, where applicable, the [Data Processing Agreement](/legal/data-processing).

## 1. Export before leaving

You can download your objects with a compatible S3 client while access is active. Export all required objects and metadata, verify the copy and keep it on independent storage. The service does not provide a promised undelete, point-in-time restore or customer backup archive.

Ordinary downloads use your account's existing S3 endpoint and credentials. Contact support@backends.co.uk if you cannot obtain a safe export. We will consider a reasonable alternative where lawful and technically possible, including after an account restriction; we cannot provide another person's information or material whose release is unlawful.

## 2. Deleting objects yourself

An authorised S3 delete request removes the addressed object from ordinary active access, subject to the storage system's actual semantics and any lawful preservation requirement. Clean up unwanted multipart uploads separately. Deleted content may remain in restricted infrastructure copies until their retention cycle ends; no restore capability is promised.

Revoking a key only changes access. Suspension only restricts service. Neither action, on its own, deletes your objects or closes your portal account.

## 3. Requesting account closure

Email support@backends.co.uk from your account address where possible, or sign in and open an account-closure case. Say whether you have finished exporting and want deletion now, or need to agree an export window. We will verify authority proportionately, confirm the scope and record the agreed closure/deletion trigger. There is no cancellation fee and no requirement to explain why you are leaving.

The portal case form starts and tracks an operator-handled closure process; it is not an instant self-service account deletion button. Its checklist and completion markers are operator records, not proof of an unverified storage action. Do not assume that opening a case, sending a support message, suspending access or completing a checklist item has deleted your bucket until you receive an accurate confirmation. A privacy erasure request can also be sent to privacy@backends.co.uk and is handled under the applicable legal timescales.

## 4. Active deletion and residual copies

After confirmed instructions or the agreed end of the export period, we revoke access and remove active Customer objects within **30 days**, subject to lawful preservation. We remove unnecessary ordinary account information within that period and retain only the categories and for the reasons disclosed in the Privacy Notice.

Existing backups/snapshots follow this verified schedule: **Daily backups retained 30 days; monthly restore tests; deletion reapplied after restore**. Their locations are **Enderby, United Kingdom**. Residual copies are restricted, not used for ordinary service, and deleted or overwritten on the applicable cycle. If a backup is restored, relevant deletion instructions must be reapplied before data is returned to ordinary use.

Logical deletion does not imply an immediate physical overwrite of every storage sector. We use appropriate sanitisation and media-disposal practices and do not promise a per-object physical-destruction certificate which the service cannot produce.

## 5. Holds, evidence and confirmation

A lawful preservation requirement, legal claim or security investigation may require limited retention. We record the reason, scope, access restrictions and review date, retain no more than necessary, and delete when the reason ends. We tell you what can be explained without breaching a law or prejudicing a legitimate investigation.

On request, we confirm completion of the agreed active deletion or explain outstanding restricted copies and the applicable expiry/review schedule. For processing governed by the DPA, the Customer chooses return or deletion and existing copies are deleted unless a lawful exception applies.

## 6. Planned service closure and inactivity

For an ordinary planned service shutdown, the Terms normally provide at least 30 days' notice and a reasonable export opportunity. Urgent legal or security circumstances may limit this. We do not introduce an undisclosed inactivity-deletion timer: any future inactivity policy must be notified, fairly applied and reflected in these documents before use.

Once deletion has been completed, reopening an account does not recover old objects. Keep a verified independent copy until you no longer need the information.