Privacy and trust

Customs files deserve a trustworthy first stop.

The free estimator runs in your browser. The paid workflow stores only what is needed to deliver, re-deliver, and reconcile your pack.

Open the calculator
The free estimator runs in your browser
Parsing and totals happen locally. Your CSV leaves the device only if you create a paid workflow session.
We store what the paid pack needs, and say so plainly
Creating a paid workflow writes the following to our database: the source file name, the analysis snapshot (totals, detected fields, warnings, per-entry routing rows), the generated pack artifacts, the buyer email supplied at Stripe checkout, Stripe identifiers (customer, checkout session, payment intent, charge), the currency and amounts of the purchase, and an audit log of workflow events. We also store the Stripe webhook event payload for the purchase so we can replay or reconcile a charge. Stripe separately handles card data under its own policy.
We do not train models on your customs data
Uploaded files and analysis snapshots are not used to train, fine-tune, or evaluate models.
We do not resell or syndicate your data
We do not sell customer customs data, importer lists, or refund estimates.
Magic-link access, not password vaults
Paid packs use a reusable, time-limited email link. No persistent login is created until we ship one explicitly.
Deletion on request
We do not currently run an automatic retention schedule for paid workflow data. Email support to request deletion of a paid workflow, its artifacts, its access tokens, and the associated Stripe event rows, and we will confirm and remove them.

What we store, by surface

Free uploads stay local. Paid packs store the records needed for delivery, access, payment reconciliation, and deletion.

  • Free calculator (this site)

    Nothing on our servers. Parsing runs in your browser.

  • Paid workflow session (our database)

    Source file name, analysis snapshot (totals, detected fields, warnings, routing rows), generated pack artifacts, buyer email supplied at Stripe checkout, Stripe customer / checkout / payment intent / charge IDs, purchase currency and amounts, and an audit log of workflow events.

  • Stripe webhook events (our database)

    The full Stripe webhook event payload for checkout events is stored alongside the event ID so that payments can be replayed, reconciled, or audited. Stored payloads do not contain full card numbers.

  • Stripe Checkout

    Payment data is handled by Stripe under their privacy policy. We do not see or store full card details.

  • Email delivery

    We use a transactional email provider to deliver the magic link to the address you supplied at checkout. The email contains a reusable, time-limited access token tied to your workflow.

Questions, deletion requests, or due diligence
For deletion, retention, or due-diligence requests, contact support with the workflow ID shown on the paid page. We target deletion responses within five business days.