Exporting your data as CSV from PixelProof, EntryProof, and TariffWatch

Every Digital Empire product ships a CSV export of the primary data it holds on your account. Data portability is not a nice-to-have. It is a hard requirement under the California Consumer Privacy Act and every equivalent state statute, and it is a promise we make on the Data privacy and account deletion help article at /help/portfolio/data-privacy-and-account-deletion. This guide covers where each export lives, what fields it includes, and how the row shape is stable across time so downstream tooling does not break on a schema drift.

Every scan run against a store, whether through the web UI or the Chrome extension, is logged and available as a CSV. From the account page at /meta-monitor/account, scroll to the Exports section and click "Download scan history." The CSV exports every scan on your account for the past 12 months, one row per scan, with columns: scan id, scanned URL, timestamp, Shopify detected flag, critical count, warning count, and a semicolon-delimited list of finding labels. Direct API access is exposed via the OpenAPI docs at /docs/api for Agency-tier customers when that plan ships.

The scan id column is stable across exports, so re-downloading a month later gives you the same id for the same scan. This lets you incrementally sync into a warehouse without re-processing rows. The finding-labels column is truncated at 32 kilobytes per cell to fit Excel's per-cell character cap documented on Microsoft's Excel specifications and limits reference at support.microsoft.com; the full finding detail is available via the JSON API surfaced at the OpenAPI spec.

The EntryProof account page at /cpsc-efile/account exposes a "Download scan history" button that produces the same shape as PixelProof: one row per product scan (ASIN or URL), a stable scan id, a readiness score, and a comma-separated evidence-flags list. The current v0 heuristic-only scoring caveat, spelled out on the scan tool itself and mirrored on the How to interpret your CPSC readiness score help article at /help/cpsc-efile/how-to-interpret-your-cpsc-readiness-score, applies to the exported score column too. The CSV format for EntryProof exports follows the same convention required by the CBP eFile technical schema at cbp.gov so downstream customs brokers can ingest without transformation.

TariffWatch exports two distinct row types. The exposure-scan history CSV on the TariffWatch account page has one row per HTS-code exposure calculation, with columns for the codes queried, annual value entered, and the computed duty exposure at each rate scenario. The comment-letter export lists every draft you have generated using the comment-letter builder, with the article slug, generation date, and (redacted for privacy) commenter-field hash so you can reconcile against your own filing records. The export shape is compatible with the docket-log format described in the regulations.gov API documentation at regulations.gov for downstream reconciliation against your regulations.gov filing receipts.

If you have collected emails via a PixelProof exit-intent modal, a landing-page waitlist form, or a TariffWatch exposure-scan lead magnet, the subscriber list is exportable per product from the same Exports section on each product's account page. The CSV includes email, source (waitlist_page, exit_intent, landing_hero, etc.), timestamp, and CAN-SPAM-compliant unsubscribe token so any downstream mail sending honors unsubscribes automatically per the requirements documented in the FTC CAN-SPAM compliance guide at ftc.gov.

CSV exports use RFC 4180 quoting, UTF-8 encoding, and Unix line endings (LF, not CRLF), matching the format Excel and Google Sheets both accept without a warning dialog per the RFC 4180 specification at rfc-editor.org. Column order is preserved across releases; we only add new columns to the right of existing columns, never insert or reorder, so downstream code that positional-indexes will not break. New columns are announced in the release notes at each product's changelog page.

If the CSV export does not have the fields or resolution you need, the JSON API surface at /api/openapi.json exposes the raw per-scan JSON structure with all finding-level detail, evidence blobs, and per-rule confidence scores. That surface is currently public + rate-limited; Agency-tier customers get higher rate quotas + optional authenticated access.

• Data privacy and account deletion
• Billing across PixelProof, EntryProof, and TariffWatch
• How to interpret your CPSC readiness score

How long is scan history retained? 12 months on the default tier. Longer retention is available on the Agency plan. After 12 months, scans older than the retention window are hard-deleted from production, consistent with the data-privacy article.

Are subscriber-list exports GDPR-compliant? Yes. The export includes an unsubscribe token per subscriber and honors the same purge-on-request timeline documented on the data-privacy help article. If a subscriber has requested deletion, their row is not included in the export.

Can I schedule automatic weekly exports to S3 or Google Drive? Not from the UI. That is on the Agency-plan roadmap; the current workaround is to hit the JSON API on a cron and pipe to your own storage.

What character encoding do CSVs use? UTF-8 with no BOM, LF line endings, RFC 4180 quoting. Excel opens these correctly; if you see Mojibake it usually means the file was double-decoded somewhere in your pipeline.

Still stuck? Email hello@citationsafe.com or hello@argushq.ai.