Disclaimer & Refund Policy

This policy explains the limits of what Access Rescue does and how refunds work. It works together with our Terms of Service and Privacy Policy.

1. Recovery is best-effort

Access Rescue attempts to recover data using fault-tolerant, browser-local parsing. Before you pay we show you, table by table, the row count the database declares and how many rows we read back — measured from your file, not estimated, so you know the outcome up front.

We do not guarantee that any specific file, table, or row can be recovered. Some files are too damaged to yield usable data.

We also do not guarantee that every value inside a recovered row is unchanged — see §4 for what we can and cannot verify.

2. Reports are decision support, not advice

The Migration Readiness Report is generated automatically from the file’s structure and metadata. It is provided for your own decision reference and is not professional, legal, or migration consulting. You are responsible for any migration or business decision you make using it.

3. Refund policy (digital product)

Because the Rescue package is a digital download generated from your own file, refunds are limited to the cases below. Each case is one we can verify objectively.

Window. You can request a refund within 180 days of purchase. That is the longest period our payment processor can return money to your card, so we publish that number rather than a shorter one we would have to argue about.

We will refund if:

• (a) No usable data — the paid package contains zero recoverable rows, or validation failed. Contact us at admin@mdbrescue.com within the window above.
• (b) The download does not match the preview — the values you saw in the free preview differ from the values in the delivered export. Send us the job reference (and the file, if we ask) so we can reproduce; if we confirm the delivered data is not what we showed you, we will refund.
• (c) The download is unusable — the export cannot be opened, or fails to parse, because of a defect in what we generated.

What we cannot refund for:

• Value-level damage we cannot detect. Some kinds of corruption change a value while leaving the row structure intact. When that happens there is nothing in the file for any single-file tool to flag — not us, and not Microsoft Access itself. We surface this limit before you pay (see §4) and show you real rows to check. If the preview already shows values you do not recognise, please do not buy — that is the signal the tool is giving you.
• A change of mind after a successful download.
• Free diagnostics are not refundable because they are free.

If the export fails on our side, you do not pay again. If a rescue does not complete because of a defect in our tool — an error, a crash, or an output file that cannot be opened — we will run the same rescue for the same order again at no charge. This is not a refund; it is us finishing the job you paid for.

A second rescue of the same file is a new rescue. Once a rescue has been delivered successfully, running it again (on the same file, or on a different set of tables) is a new rescue and is charged as one. We say this here, before you pay, and not only after.

3.1 Your statutory rights

Where the law gives you rights that are stronger than this policy, those rights apply, and nothing in this policy reduces them.

If you are a consumer in the EU/EEA or the UK. You normally have 14 days to withdraw from a distance purchase. The Rescue package is delivered immediately, so we ask you to agree to immediate delivery and to acknowledge that you lose the 14-day right of withdrawal once delivery has started. We record that agreement at checkout and confirm it in your order email. If that agreement has not been properly obtained, your statutory withdrawal period is preserved in full.

Refunds are processed through our payment processor, Stripe. If the 180-day window above has closed, we may not be able to return funds to the original card; in that case we will arrange an alternative method with you.

4. What we verify — and what we cannot

This section is a plain-language limit of the service, and applies to everything above.

We can verify: how many rows we recovered, how many we could not read, and how many we never reached. These counts are reported to you before you pay.

We cannot verify: that every value inside a recovered row is unchanged. Text fields in Access databases carry no checksum and no duplicate copy, so a value altered by damage can look exactly like a valid one. We do not claim otherwise, and we do not report a row as verified when only its structure was checked.

5. Chargebacks

If you dispute a charge, contact us first — most issues are resolved faster directly at admin@mdbrescue.com. We may ask for the order number shown on your payment confirmation. A chargeback costs both of us more than a refund does, and we would rather fix the problem.