dariMods

Privacy Policy

Version 2026-10-24.1 · Last updated: 22 October 2026

Operator: dariMods. Support: [email protected]. Details are on the Contact page.

This policy explains what the operator processes for the dariMods website, account, and client. Our payment providers are separate controllers for the payment; see their privacy notices.

1. Data we process

  • Account. Email address, a hash of the sign-in code (the code itself is not stored), account id, and an optional forum user id if an account is linked. The username is a label, not a separate identity check.
  • Session. An HttpOnly cookie (dari_account_session) and the matching session in Redis, plus a CSRF token used only to submit forms on the account.
  • Checkout acceptance. When you tick the box and open checkout: time, email, IP address, user agent, Accept-Language, document version, language of the page, plan key, our order reference, and later the provider transaction id.
  • Device fingerprint. For the one-device license: system UUID, MachineGuid, BIOS serial, baseboard serial, processor id, BIOS product and vendor, CPU name, and evidence fields (disk serial, MAC addresses, volume serial, OS build). The lock uses a stable subset. Volatile fields are stored but are not meant to lock you out after a disk, network, or Windows update. Components are stored so a mismatch can be reviewed.
  • Network. IP address and user agent on sign-in, loader issuance, download, and when a telemetry IP changes. Cloudflare may see the connecting IP and country (the CF-IPCountry header) because the site is served through Cloudflare.
  • Telemetry. Host process, loaded modules, error and status records, and signals used to detect debuggers, analysis tools, and tampering with the client.
  • Download watermark. The executable issued to an account carries a per-download attribution block naming the installation and the account, so a copy that is redistributed can be traced. It is written only by the server at download.
  • Installed applications. At download, the name, version, and publisher of applications listed in the uninstall registry of that computer. Used to explain a client that never ran and to see security software. Not used for advertising.
  • Payment. We store the provider order id, plan key, payment status, and transaction id. We do not receive or store card numbers. Our payment provider processes the card, billing address, and tax data.

2. Why, and the legal basis

  • Contract (GDPR art. 6(1)(b) where it applies): account, license, delivery, support, and the checkout record of what you accepted.
  • Legitimate interests (GDPR art. 6(1)(f) where it applies): security, abuse prevention, the device fingerprint, telemetry, the installed-application list, and keeping evidence for a payment dispute. The interest is keeping a paid license to one person and being able to answer a bank. It is not used to sell data or to advertise.
  • Legal obligation (GDPR art. 6(1)(c) where it applies): answering a lawful request, and keeping what a dispute or a tax authority may require. The payment provider issues the payment receipt.

The checkout box is acceptance of the license and a request for immediate access. It is not a consent for unrelated processing, and it is not a marketing opt-in. The payment provider's checkout may set its own cookies; those are the provider's.

3. Retention

  • Sign-in codes: a hash, for 10 minutes, then deleted.
  • Account sessions: 12 hours after the last use, unless you sign out sooner.
  • Checkout acceptance, IP logs, hardware-fingerprint history, loader attempts, and the installed-application list: kept, and not deleted on a fixed timer. A card dispute can be raised months after delivery. We keep them while the account exists and afterwards for as long as a dispute, a legal claim, or security review may need them.
  • Telemetry and state snapshots: kept for security, stability, and support. A retention setting exists in the server configuration (90 days for deltas, 365 days for checkpoints) but an automatic purge is not running. Until a purge is in place, do not rely on those numbers as a deletion promise.

4. Who receives it

We do not sell personal data. Recipients are: the host that runs the server; Cloudflare, which fronts the site; the email provider that sends sign-in codes and, when configured, the order notice; our payment provider, as an independent controller for the payment; and a public authority when the law requires it. A linked forum account is matched by email on our side. We do not give the forum the hardware fingerprint or the installed-application list.

5. International transfers

We and our providers may process data in the countries where we and those providers operate. Our payment provider may process payment data in its own country, and cryptocurrency payments run on infrastructure we control. Cloudflare and the email provider may process data in more than one country. Where a transfer out of the EEA or the UK needs a safeguard, the provider's own mechanism (such as standard contractual clauses) applies to that provider's processing. We do not claim a specific data-center location.

6. Cookies and similar storage

  • dari_account_session: signs you in, HttpOnly, about 12 hours.
  • The payment provider's checkout may set its own cookies.
  • Cloudflare may set a cookie necessary to route or protect the site.

We do not use advertising or analytics cookies.

7. Automated locking

A tamper or device-mismatch signal can lock the account without a person looking at it first. That decision significantly affects access. Email the reference code to [email protected] and a person will review it. You can object to the processing. If we cannot provide the Service without the security checks, the result of a successful objection may be that the license ends, not that the checks are turned off for one account.

8. Your rights

You may ask whether we process your data, request information, correction, deletion, or restriction, and object. We answer within 30 days. Email [email protected] from the account address so we can tell the request is yours. If the GDPR applies to you, you have the rights it gives, including the right to complain to the supervisory authority where you live. Payment data held by the payment provider must be requested from that provider. We cannot delete a record we still need for a live dispute or a legal claim, and we will tell you if that is why a deletion request is refused in part.

9. Children

The Service is not for anyone under 18. If we learn that an account belongs to a child, we will close it and delete the data we are not required to keep.

10. Security

Sign-in codes are stored as hashes. Sessions are HttpOnly. Card data never reaches us. No method of storage is perfect. Email [email protected] if you believe an account is being used without you.

11. Changes

Material changes are published on this page with a new version date. The version in force when you accepted checkout applies to the data collected for that order.