Customer files stay out of FileCheck servers.

Last updated August 21, 2026

Browser-only file processing

Declaration files and supporting documents are read and processed in browser memory. They are not submitted to a FileCheck upload endpoint, database, object store, application log, analytics payload, or third-party inference service. Corrected files and reports are created locally in the browser.

Temporary browser-local recovery

To survive a checkout redirect or an accidental refresh, FileCheck may keep the declaration file, supporting files, processing result, and output state in browser-local IndexedDB for up to 24 hours. Selecting Start over removes it. This local state never reaches FileCheck servers. Browser/device cleanup, private browsing, or storage clearing can remove it sooner.

Purchase, delivery, and funnel evidence

FileCheck stores a separate non-sensitive commercial record for up to 18 months: checkout email, opaque order or job identifier, selected package, amount/currency, payment/session identifier where applicable, policy versions and consent time, payment/processing/unlock/download timestamps, support/refund status, and privacy-safe file/output matching hashes. These hashes compare an exact reprocessed input or generated output; they cannot reconstruct a file and do not prove regulatory correctness. File contents, filenames, field values, extracted text, species, product descriptions, values, and supplier information are not part of this record. Funnel analytics retain only an anonymous session identifier, product mode, event name, and timestamp for up to 90 days.

Google Ads purchase measurement

After FileCheck verifies that a Stripe Checkout payment is complete and paid, Google Ads receives a purchase event with only the package price and USD currency. FileCheck does not include uploaded file contents, filenames, declaration data, checkout email, receipt or order identifier, payment or session identifier, or other customer or file data in that event.

Technical requests and future payments

Our hosting provider necessarily handles ordinary web request data needed to deliver the site. When live payments are enabled, card details will be entered directly into Stripe Checkout, not FileCheck. Stripe and any configured support provider will have their own notices. We will not send customer-file content or sensitive regulatory data in Stripe metadata.

Your choices

Because FileCheck does not hold a server-side customer-file archive, there is no FileCheck server copy to delete. Browser-local recovery can be removed with Start over or browser storage controls. Non-sensitive purchase evidence is retained only for the stated commercial period. For help with a paid delivery problem, use Support; do not send source files by ordinary email.