Orders and support

An account-erasure request arrives while an order is still unresolved

Do not process or refuse the request until it is mapped to the actual account, the open order and every record that still has an operational purpose. Erasure is a conditional right, and an unresolved order is not an automatic exemption from it; a documented operational purpose is evidence for the decision, not a substitute for it. The decision needs a record-by-record account of what each system holds and why. Identify the person authorized to make the retention or erasure decision — including the applicable lawful basis, erasure grounds, exceptions and response deadline — and hand them the map, not a guess. Any legal conclusion about retention duties belongs to qualified privacy review, not to this worksheet.

For: An authorized staff member at a research-only store preparing an account-erasure request for decision while a related order, refund or support case is still open.

Updated 2026-10-01

Match the request to one real account and one real order

Start by confirming which account, order or support thread the request actually concerns, using your normal authorized verification process. A name or email address can locate candidate records, but it does not prove that two records belong to the same person or that the requester is that person. Record how the match was established and leave uncertain matches unresolved rather than merging records to make the request tidy.

Then identify the unresolved obligation in concrete terms: an order awaiting fulfillment, a refund in progress, a replacement under discussion, a dispute with the payment provider, or a support case with a promised follow-up. Write down what remains to be done and which team owns it. An erasure action taken before this mapping can destroy the very records needed to finish the obligation, and a refusal issued before it can rest on a purpose the business does not actually have.

An open order is a purpose, not a blanket exemption

The ICO's guidance on the right to erasure describes erasure as conditional: it applies in defined circumstances and is subject to exceptions that require consideration, including how backups are handled. Its storage-limitation guidance says retention must be justified by a purpose and reviewed, and that moving data to offline storage is not the same as erasing it. Both pages are UK guidance; the law applicable to your business may differ, and this page does not determine it.

The practical consequence is narrower than either extreme. An unresolved order can give specific records a current purpose, and that purpose is evidence the decision owner weighs — it is not, by itself, authority to retain. Whether an erasure ground applies to a given record, whether an exception covers it, and what response deadline the applicable law imposes are determinations for the authorized privacy owner, with qualified advice where needed. The reviewable unit is the record category and its documented purpose, not the account as a whole.

For each category, ask whether the open obligation actually uses it. Order items, amounts and delivery details may be needed to fulfill or refund. Marketing preferences, old account metadata or analytics identifiers may have no connection to the open work at all. Where you cannot articulate a current purpose for a category, mark it for the decision owner rather than inventing one.

Inventory every system that carries the person's data

An erasure decision that covers only the store admin misses the copies that matter. List the systems an authorized administrator can identify: the store's order and account records, the support mailbox or helpdesk, the fulfillment or warehouse handoff, the payment provider's records, any shipping service, and any exports or backups under your control. For each, record the category of data and the owner who can act on it. Do not paste the customer data itself into this worksheet; references and categories are enough.

Note where your control ends. A payment provider's own records follow that provider's processes, and a fulfillment partner's copy follows yours only to the extent your agreement and instructions reach it. Record those as separate action items with their own owners rather than implying one store action erased them. Backups deserve an explicit line: the ICO notes backup treatment requires consideration, so record what your backup cycle is and leave the handling decision to the authorized owner.

Sequence the decision around the open work

For each record category, the decision owner has three practical branches: act now because no current purpose exists, hold where the owner determines that an applicable lawful basis or erasure exception supports retention, or escalate because the applicable retention duty is unclear. An open obligation using the record is evidence for that determination, not a substitute for it, and the request is not automatically deferred until the order completes. Where a hold is chosen, record the basis relied on, the trigger that ends it, such as the order reaching completion, the refund settling or the dispute closing, and name the person who will revisit the request then. A hold without a recorded basis and a trigger is an unmade decision.

Communicate to the requester only what has actually been decided and done. Receiving the request, verifying it, deciding it and completing the applicable actions are separate events, and a reply should not claim erasure of records that are being retained under a determination the decision owner has recorded or that sit in systems still being handled. Where the applicable law requires a response within a period, that deadline comes from the law, not from this page; have the decision owner confirm it with qualified advice.

If the recurring problem is that your store's data handling is undocumented and every request becomes an investigation, that is a storefront and operations question you can raise in a Prism consultation. Describe the systems involved and the mapping gap in ordinary language; confirm scope, responsibilities, fees and terms before work. Keep the customer's records, identity material and any request details out of the public inquiry form.

Erasure request mapping sheet

Complete one sheet per verified request. Record categories, purposes, owners and decision branches without copying customer data into the sheet. A row stays open until its decision branch and revisit trigger are recorded by the authorized owner. This sheet does not determine legal retention duties or promise deletion.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Erasure request mapping sheet. The last column is for temporary notes.
Record or checkWhat it decidesYour finding
Request identity match: how the account, order and requester were verified through the authorized process.Whether this request governs these records at all; unresolved matches stop the review before any action.
Open obligation: the specific unfinished order, refund, replacement, dispute or support promise, with its owning team.Which record categories have a live operational purpose, and which have none.
Store order and account records: categories held and the settings or procedures that govern them.What the store system alone could erase, and what it would still leave elsewhere.
Support, fulfillment, shipping and payment-provider copies: system, category and acting owner for each.The separate actions and owners required; one store action does not reach these systems.
Exports and backups under your control: locations, cycle and the owner who can direct handling.Whether backup treatment was explicitly decided; offline storage is not erasure.
Decision branch per category: act now, hold where the authorized owner records the lawful basis or exception relied on with a named revisit trigger, or escalate for qualified advice.A defensible sequence that neither destroys needed records nor ignores the request.
Requester communication: what was decided, what was actually completed, and what remains held and why.An accurate reply that does not claim erasure of retained or unhandled records.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.

Limits

  • This workflow prepares an authorized decision; it does not determine the retention or erasure duties applicable to your business, which require qualified privacy review in your jurisdiction.
  • An unresolved order is not an automatic exemption from erasure, and a current operational purpose is evidence for the decision owner to weigh rather than retention authority in itself; retention, erasure grounds, exceptions and response deadlines are determined by the authorized privacy owner under the applicable law.
  • ICO guidance cited here is UK-specific and does not establish obligations or timelines in other jurisdictions.
  • Keep customer records, identity documents and request details in authorized systems; the worksheet holds references and categories only.

Sources

  • ICO: Right to erasure — checked 2026-10-01. The right to erasure is conditional, applies in defined circumstances and is subject to exceptions; backup treatment requires consideration. UK-specific guidance.
  • ICO: Storage limitation — checked 2026-10-01. Retention must be justified by a documented purpose and reviewed; holding data longer, including offline, is not the same as erasure. No universal retention period is stated.
  • Prism solutions — checked 2026-09-21. Consultation scope, responsibilities, fees and terms are discussed before work; a request does not itself book work or decide any legal question.

Get help with store operations

Need help with the order, email or fulfillment step itself?