Privacy Policy
Last updated November 14, 2026
Phan Vu Chau (“we”, “us”) makes Diffacto and is responsible for the personal data described here. Write to andzrev@pm.me with any question about it.
The short version
Diffacto compares your files on your own computer. It has no telemetry, analytics or crash reporting, and it never sends file contents, file names or paths to us. What it does send, it sends only for the reasons listed below.
What the app sends, and when
- Checking for updates. Once a day, the app downloads a small file from downloads.diffacto.com that lists the newest version. The request carries your IP address and the app's name and version, nothing that identifies you or your computer.
- Activating a license. When you activate a paid license, and then at most once a day while you use the app, it sends your license key and a one-way hash (SHA-256) of your computer's hardware ID to store.diffacto.com. The hash lets us count your computers against your plan; it can't be turned back into the ID.
- Buying. Choosing a plan in the app asks store.diffacto.com for a checkout, sending the plan, packs, number of people and a random code the app uses to pick up your key afterwards. Paddle's checkout collects your payment details, which we never see. If you recover a purchase, the app sends the transaction ID and email address from your receipt to the same server.
- Share links you create. The app encrypts the comparison before uploading it to share.diffacto.com. The key stays in the link you hand out, so the server stores only ciphertext, its expiry date and encrypted comments. Shares are deleted when they expire.
- Services you connect. If you open a pull request, a Figma file, cloud storage or a database, the app talks to that service directly with your own credentials. We don't receive those credentials or that data.
- An optional cloud summary. Plain-language summaries run on your computer by default. If you set up a cloud model instead, the comparison is sent to the provider you chose, under its terms.
An administrator can turn off every one of these connections with a policy, and the app then works fully offline.
What we keep about customers
Paddle is the Merchant of Record for our sales and processes your payment under its own privacy policy. Paddle shares with us what we need to run your license: your name and email address, your country, what you bought, and the transaction's reference. We keep that, your license key, and the hashes and last check-in dates of the computers you've activated.
We use this only to issue, recover and check licenses, to answer you, and to tell you about changes that affect your purchase. We don't sell it, and we don't use it for advertising.
We keep license records for as long as your license exists and afterwards for as long as tax and accounting law requires. Deactivating a computer removes its hash.
This website
The website sets no cookies, runs no analytics and loads nothing from other sites, apart from Paddle's checkout when you buy. We don't keep logs of the pages you visit. The only thing we look at is how many times each page was requested in total, a count Cloudflare makes as it serves them, which says nothing about who asked.
Who handles data for us
- Cloudflare serves this website and the downloads, and carries the app's connections to store.diffacto.com and share.diffacto.com. It processes your IP address and those requests to deliver them and to block attacks, under its privacy policy. Share links reach it already encrypted.
- Paddle takes payments as the Merchant of Record, as described above.
Legal bases and transfers
We use your data to provide the license you bought (a contract with you) and to keep the records tax and accounting law requires (a legal obligation). Cloudflare and Paddle may process data outside your country, under their own policies.
Your rights
You can ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it, where the law allows. Write to andzrev@pm.me. If you're in the EU or the UK you can also complain to your data protection authority.
Changes
If we change this policy we'll update the date above, and if a change affects what the app sends, we'll say so in that version's release notes.