Written by DROPS.ST.
Give each customer privacy request a named owner. Clarify the request, verify the person’s authority through the approved process, locate the relevant records and document the response decision. A short signup form does not establish that the shop holds nothing else.
DROPS connects Customer Accounts with orders and order items, giving your team a concrete starting point for finding relevant shop information. Account separately for correspondence, copied files and connected services.
Track the request from receipt to an explained response without exposing another person’s information or promising an unverified deletion.
Distinguish the request from a routine order change
A request to change tomorrow’s order concerns an operational transaction. A request to see personal information held about the customer, correct a record or remove information raises a different set of decisions.
Clarify the person’s meaning without requiring technical wording. One message may contain several requests. Give coordination to the person responsible for privacy requests.
For businesses subject to PIPEDA, the Office of the Privacy Commissioner of Canada describes access and correction obligations, including exceptions and response requirements. Other applicable privacy regimes and obligations need their own assessment. OPC access-request guidance.
Open a scope-and-decision register
This original working register belongs in the approved business process; it is not a claimed native DROPS form.
| Record | What the responsible person establishes | Completion evidence |
|---|---|---|
| Receipt and responsibility | Date received, request channel and coordinating owner | Request is assigned and tracked |
| Request scope | Information, correction or deletion being requested | Scope is understood; unresolved points are identified |
| Identity and authority | Approved method for confirming the requester’s authority | Verification is sufficient for the intended disclosure or action |
| Record locations | Relevant shop records, correspondence and connected services | Search scope and gaps are documented |
| Decision | Proposed response and any applicable limitations or retained records | Required review has taken place |
| Response and follow-up | Approved delivery method, due date and outstanding actions | Response was provided and remaining work has an owner |
Record references and necessary evidence, not passwords or unnecessary identity-document copies. If further information is needed, explain its purpose and use the approved submission route.
Put the legal due date beside the internal update commitment
Determine the applicable response requirement as soon as the request is received. Where PIPEDA governs, OPC guidance specifies a response within 30 calendar days, with extensions allowed only in specified circumstances. An acknowledgment alone is not the completed response described in that guidance. OPC response timing.
Your next-update commitment is useful for communication, but it does not replace the applicable deadline. If the request involves an exception, uncertain authority or another organization, obtain the appropriate review early rather than discovering the issue when the response is due.
Locate the information without assuming one download is complete
Start with the Customer Account and linked orders, then check the business’s actual information map for correspondence, working copies and connected providers.
Available DROPS account and order downloads have different access boundaries. Account-data export requires the appropriate account access and export authority; individual order downloads follow order-view authorization. Neither fact proves that a download contains everything responsive to a privacy request or removes information about other people automatically.
Review any output before release. A familiar order reference alone is not sufficient authority to disclose personal information. The export permissions guide explains the separate download boundaries.
Hypothetical example: access and a correction in one message
A customer asks for information the shop holds about them and says a contact number is wrong. The coordinating owner records both parts of the request.
After the approved identity check, the owner finds the relevant shop records and correspondence. The correction is reviewed separately, including whether copies or connected services need follow-up. A profile edit is not assumed to update every historical record.
The response explains what was provided, corrected and left outstanding. This hypothetical process does not establish automated synchronization or privacy handling.
Review a deletion request before promising the result
An account closure, removal of optional information and disposal of historical records are different outcomes. Determine the requested result, relevant retention obligations and supported tools before authorizing an action.
Do not promise that every copy, backup or connected provider will erase information immediately. Record what can be done, what must be retained, the reason for that decision and how remaining actions will be coordinated. OPC use and retention principles.
Make connected records support an accountable response
DROPS gives your shop customer-linked order context. Pair it with an accountable coordinator, a verified search scope and an understandable decision. Evaluate the demonstrated process rather than assuming a one-click privacy outcome.
Explore DROPS.ST and the shop demos. Use a synthetic customer with records in more than one agreed location to rehearse how your team would coordinate the request without disclosing real information.