Export, uninstall, and data retention
Download your registry and understand the 30-day uninstall recovery and permanent purge policy.
Your real Serial Trail registry is exportable on every plan. After uninstall, it is recoverable for 30 days unless Shopify sends a mandatory deletion signal earlier.
Export your data
Open Settings → Account and download:
units.csv— unit identity, binding, status, order reference, and timestamps.unit-events.csv— serial, lifecycle event, actor type, metadata, and timestamp.pools.csv— pool binding, status, pattern, and next sequence.warranty-claims.csv— claim status, resolution type and status, buyer-safe resolution summary, replacement references and linked replacement serial.
Exports stream from the database and exclude demo data. Spreadsheet-formula prefixes are escaped.
After uninstall
Serial Trail clears active integration credentials immediately but retains the serial domain for 30 days so a reinstall can restore continuity. Reinstalling during that window starts a new install cycle and cancels the old purge eligibility.
After 30 days, a fenced job permanently deletes units, event trails, pools, batches and staging rows, uploaded import files, fulfillment rows, stock snapshots, reconciliation findings, and Serial settings. A permanent receipt records table-level deletion counts without retaining the deleted registry.
Shopify privacy requests
shop/redactschedules immediate domain purge only when the merchant is still uninstalled.customers/redactremoves matching order, line, and fulfillment references, claim and registration contact data, private evidence files, free-text resolution details, and pending delivery payloads.customers/data_requestreturns matching registration and claim records, evidence, evidence verdicts, and resolution history. The serial registry itself does not require buyer contact data.
Replacement shipping addresses entered in the claim resolution flow are transmitted directly to the commerce platform and are never stored in Serial Trail.
Was this article helpful?
Let us know — your feedback helps us improve our documentation.