Delete your data or your workspace

AffCheck holds as little as it can and deletes it on a schedule you can read. This page is what is there, how long it stays, and how to get rid of it sooner.

What is stored in the first place

Neither of your files is kept. Not the network export, not the Shopify orders export, not the file's name. What is saved is the rows read from them, on your device, with the customer columns already dropped:

• Orders — the order name and id, the dates, the currency, the totals, the refunded amount, the cancellation date, the financial status, discount codes, tags and the number of line items.
• Transactions — the network's transaction id, the order reference, the date, the publisher, the voucher code, the sale amount, the commission, the currency, the status and the row number in your file.
• Flags and decisions — the reason, the evidence behind it and what you decided.
• Your workspace — its name, the Shopify domain you typed, the currency, the timezone, the networks and their validation periods.

There is no field anywhere for a customer name, an email, an address, a phone number or a payment reference. The upload is rejected outright if one appears.

How long it is kept

Thirteen months for merchant data, counted from the row's own date: orders by the order date, transactions by the transaction date, flags and decisions with the transaction they belong to. A job runs once a day and is the only thing that deletes by age.

One deliberate exception: an order past thirteen months is kept while a decision's evidence still names it. A decline you told a network about should stay explainable for as long as the decision behind it exists. The decision itself expires with its transaction, so nothing is kept for ever.

Some supporting rows have their own, shorter lives — the send-once keys behind emails, the anonymous rate-limit hashes behind the free check. Every table's age, in the same words, is on the privacy page.

Download everything we hold

Store settings → Download my data gives you a JSON file with your account, your workspaces and every product table belonging to them — plus the retention map itself, so the file answers "how long do you keep this?" on its own. The same screen has the store's queue and its activity log as CSVs.

Deleting a workspace

Deleting a workspace deletes its orders, transactions, flags, decisions, imports, voucher rules, networks and activity rows. It happens immediately, in one database transaction, and it cannot be undone.

You do it on Store settings → Delete this store, and you type the word delete to confirm. A workspace that still has a live subscription has to tick that it understands deleting the store does not stop the billing — we would rather you were not paying for nothing. The whole screen is described under store settings.

Deleting your account

Account → Delete account deletes your user and signs you out everywhere. Workspaces where you are the only member are deleted with all their data; workspaces you share stay for the other members.

If you want to leave but keep the data for a colleague, add them to the workspace first.

Deleting one import

You do not have to delete everything to undo a mistake. An import can be taken back on its own, with a rule that protects the work you have already done: undo an import.