NeatRow Exports — Privacy Policy

Last updated: August 27, 2026

Development-stage notice: this page describes the current local implementation. Retention, redaction, deployment, and live service behavior must be revalidated before production use.

What we collect

NeatRow Exports collects and stores the following data from your Shopify store:

• Order metadata: order ID, order name, financial status, fulfillment status, currency, financial amounts (subtotal, discounts, tax, shipping, total), line item counts, SKUs, titles, and quantities, order tags, and shipping address (country, province, city)
• Shopify OAuth session tokens in shop-scoped PostgreSQL session records
• Export template names and run history (row counts, timestamps, status)

What we do not collect

NeatRow does not collect or store:

• Customer names, email addresses, or customer IDs — these fields require Shopify Protected Customer Data approval, which has not been granted. These columns are exported as empty strings.
• Payment card or financial account details
• Personal information about store owners beyond what Shopify provides via OAuth

How we use your data

Order data is used solely to generate CSV export files on your request. Export files are written to Cloudflare R2-compatible object storage. The current code records a 14-day expiry timestamp for export-file metadata, but this repository does not prove automated deletion of the stored object. Production retention behavior remains to be verified.

Data retention

Export-file metadata records an expiry 14 days after generation. The current repository does not contain a verified job or R2 lifecycle rule that deletes the corresponding object at that time. Export run history contains metadata such as row counts, timestamps, status, and object keys.

The current local shop/redact path lists and deletes objects under the authenticated shop's R2 prefix, then deletes that shop's export-file, export-run, schedule, template, and session records in one database transaction. Automated tests cover repeat delivery and partial failures; live webhook and storage behavior still must be revalidated before production use.

Data security

Export downloads use signed URLs configured for a five-minute lifetime. OAuth session tokens are stored in PostgreSQL and are not intentionally returned to client-side code. This local baseline does not establish production transport, access-control, or logging guarantees.

GDPR compliance

NeatRow processes customer-adjacent order data on behalf of Shopify merchants. We respond to Shopify's mandatory GDPR webhooks:

• customers/data_request — the current handler authenticates and acknowledges the webhook; end-to-end request fulfillment is not yet verified.
• customers/redact — acknowledged. No customer PII is stored by NeatRow.
• shop/redact — the local handler performs shop-scoped PostgreSQL and R2 cleanup; current live delivery and object absence remain unverified.

Contact

For privacy questions or data deletion requests, contact: privacy@neatrow.com

Changes to this policy

We may update this policy. Material changes will be communicated via the Shopify App Store listing or directly to merchants. Continued use of the app constitutes acceptance of the updated policy.