Privacy policy
TidyExport is designed so the spreadsheet-cleaning workflow runs locally in your browser.
Your files
CSV and XLSX files selected in the workspace are read and processed on your device. The current product does not upload file contents to a TidyExport server, store them in a database, or use them to train models.
Downloaded results
Cleaned files are generated in your browser and downloaded directly to your device. Refreshing or closing the tab clears the in-memory working copy.
Saved recipes
If you choose “Save locally,” the recipe name, column names, schema fingerprint, ordered cleanup rules, and any literal find/replace text you enter are stored in this browser's local storage. If you explicitly copy a recipe to your signed-in account, those same recipe fields sync to the cloud. Recipes never include spreadsheet rows. You can export, delete, or clear browser-local recipes and delete synced recipes separately.
Accounts, billing, and support
Account services store identifiers such as your email, sessions, and provider identity. PayPal or Stripe processes payment details; TidyExport stores provider references, amounts, currency, status, refunds, subscription state, and entitlement history, but not card or bank credentials. Support stores a ticket reference and short subject. The message is encrypted while queued for email delivery and cleared after delivery; attachments are not accepted.
Website operations
Our hosting provider may process standard technical logs such as IP address, browser type, requested page, and timestamps for security and reliability. We do not intentionally place advertising trackers in the workspace.
Your choices
You can inspect and edit locally without creating an account. Downloading a complete cleaned file requires sign-in, and all free and paid export allowances are recorded on the server. Use “Clear library” to remove browser recipes. From Account, you can export account and cloud-recipe data as JSON. Account deletion requires recent authentication and completion or cancellation of pending billing activity; it deletes cloud recipes and authentication data while required transaction records may be retained only in de-identified form. Browser-local recipes remain until you remove them.
Changes
We may update this policy as the product adds accounts, payments, or optional cloud features. Any feature that uploads file contents will be clearly identified before use.