Privacy Policy

DBF Rescue Pro is built around local-first workflows. By default, your DBF data stays on your machine. This policy explains what the public website and backend services collect when you use licensing, account recovery, billing (when enabled), telemetry, and optional lead capture.

1. Who we are

“DBF Rescue Pro”, “we”, and “us” refers to the operators of the DBF Rescue Pro website and services. Contact: dbfrescue@gmail.com.

2. What we collect

2.1 Information you provide

Email address when you request the free health-scan guide, request a sign-in code, recover a license, or contact support.
License/account details tied to your email, including plan, license status, activation count, and timestamps.

2.2 Usage and diagnostic information

Service logs generated by our hosting providers (for example, request metadata for reliability and security). These may include IP address, user agent, and timestamps.
Telemetry events (if enabled in a build) that include an anonymous identifier, event name, app version, and sanitized properties. We block common sensitive keys (for example, email and license key) from telemetry payloads.

2.3 Payment information (when checkout is enabled)

Payments are processed by Stripe. We do not receive your full card number. Stripe may collect billing details (for example, name, email, address) as required to process the payment.
We store billing event records and license provisioning information (for example, plan, status, timestamps) to make licensing and refunds work reliably.

2.4 What we do not collect by default

The website’s free DBF health scan reads your DBF header locally in your browser. We do not upload DBF row data by default.
We do not intentionally collect sensitive personal information (for example, government IDs).

3. How we use information

Provide licensing, activation checks, and account recovery.
Send transactional emails (for example, sign-in codes and health-scan follow-ups) when configured.
Operate, secure, and debug the services.
Improve product quality using aggregate telemetry (when enabled).
Comply with legal obligations and enforce our terms.

4. Legal bases (where applicable)

Contract: to provide licenses and account functionality you request.
Legitimate interests: to secure, maintain, and improve the service.
Consent: where required for marketing-style follow-ups; you can opt out by contacting us.

5. Sharing and subprocessors

We use service providers to run the product:

Cloudflare: website hosting, edge delivery, Workers runtime, and security features.
Turso/libSQL: database storage for licenses, activations, leads, and telemetry events.
Resend: transactional email delivery (when configured).
Stripe: payment processing (when enabled).

We do not sell personal information. We may share information if required by law or to protect rights, safety, and security.

6. Data retention

We retain information only as long as necessary for the purposes described above. Typical retention patterns:

License records: for as long as needed to provide access and support, and for accounting/audit where required.
Account recovery tokens: short-lived and time-limited.
Health-scan leads: until no longer needed for follow-up, or you request deletion.
Telemetry events (when enabled): retained for product analytics and debugging, then deleted or aggregated.

7. Your choices and rights

Request access, correction, or deletion by emailing dbfrescue@gmail.com.
Opt out of non-essential follow-ups by contacting us.
If telemetry is enabled in a given build, you can request guidance on disabling it for your environment.

8. International transfers

Our service providers may process data in multiple countries. We use contractual and technical safeguards where appropriate.

9. Security

We use reasonable administrative, technical, and organizational measures designed to protect information. No method of transmission or storage is 100% secure.

10. Changes

We may update this policy. The effective date at the top of the page indicates the latest revision.