Workspace / Stores / Privacy
Privacy request
Review exact data, prepare the subject response, and authorize verified cleanup.
Review each authorization separately
Counts and scan results do not certify that no personal data exists. Reviewing an inventory does not authorize disclosure or erasure. Response review, recipient verification, and exact cleanup approval are separate actions below. Source CSV and review downloads remain available until an approved cleanup affects that exact source.
Inventories capture one point in time. New activity, shared sources, missing installation provenance, and later installations can require further review. An unreadable, missing, unsupported, or unscanned item is unresolved. The inventory list contains safe metadata; restricted response content is loaded only when you request a preview.
Return to StoresRequest
Workspace permission permits this metadata review. It does not verify that you are the entitled recipient of customer data.
Inventory snapshot
Creating another snapshot preserves earlier snapshots. It does not update their contents or authorize any deletion.
| Item | Scope / review status | Scan status | Match counts |
|---|
Content scan
A scan is bound to the inventory ID and exact version below. Matching counts identify findings that need review; they do not expose the matched text. A finished scan is not privacy fulfillment.
Request fulfillment
Attribute additional source jobs
A workspace owner can add exact known job IDs from this workspace. This records scope attribution, preserves shared-source classification, and invalidates existing plans and response grants. It does not establish that no other copies exist.
Fence erasure scope
Fencing stops new research, content updates and artifact writes for affected scope and pauses store automation. It cannot undo calls already sent. Outstanding writes must be resolved before cleanup can be certified.
Verify outstanding producer outcomes
A workspace owner can resolve a specific pending artifact or AI operation only with documented evidence of its actual outcome or that it was never sent. An expired lease or elapsed time is insufficient. A timeout can still be followed by a write. This does not resolve unknown store delivery outcomes.
Exact cleanup plan
The server derives the item list from the reviewed inventory. Shared files are preserved unless a separately reviewed action accounts for unaffected content. Job files are retained until an owner deletes them or an approved privacy plan removes them.
| Item | Disposition / progress | Review |
|---|
Prepare a reviewed content replacement
Inspect the exact downloaded source first. Only the server’s permitted content fields are offered. Preserve unrelated subjects and shared data. Saving prepares a new plan version; it does not apply the replacement. Record the item’s redaction decision and approve the new plan separately.
Approval allows the worker to execute only the bound plan. Progress distinguishes completed items, retained items and unresolved outcomes. Retained copies are never described as erased.
Subject-specific response
Prepare only data belonging to the request subject after reviewing its context and related fields. Scanner matches alone are insufficient. Never paste a whole shared workbook. Empty entries need an explanation of reviewed coverage; they do not certify that no personal data exists.
The invitation permits a Shopify owner verification attempt. It does not disclose the response or grant workspace access. Share the code only with the intended recipient through your established channel. For an eligible direct request, only the initiating workspace owner can receive its response through the separate recipient page.
The service permits completion only when all required evidence is recorded. A held or retained outcome remains visible; this button cannot override unresolved work.