privacy
Privacy policy
What the Diffwright website and app collect, why, for how long, and how to withdraw your consent or have your data deleted.
In short
- The website sets no cookies. It measures its own traffic without storing your IP address: only totals are kept (per day, and per hour for page views), including the country of the visit, derived from the address without keeping it.
- The desktop app sends usage statistics and scrubbed error reports to Diffwright only if you agree: it is optional, asked at first launch or after an update, and you can withdraw at any time in Settings.
- If you write through the form, your message is kept for 90 days in the site’s database, only to reply to you. It is also received in a mailbox, where it stays until it is deleted by hand.
- Downloads are counted in aggregate, with no IP address or user agent stored by the application.
- Like any web server, the server briefly keeps a technical log with a truncated IP address (see “Web server access log”).
Who is responsible?
The data controller is Julien Pierlot, an individual, the publisher of Diffwright.
Contact: contact@diffwright.app
Postal address: Rue de Wathermal 8, 6672 Beho, Belgium
The diffwright.app website
The website sets no cookies and uses no trackers or third-party analytics service. Its fonts are hosted on the site itself: nothing is loaded from a third-party service.
The website counts its own visits, on the server, without cookies and without storing your IP address or your browser identifier (user agent). For each page it serves, the site’s server sends its API the page path, the response code, the render time, the address of the page you came from, the campaign tag if any, the browser language and user agent, and your IP address; the API immediately reduces them to counters and stores only those counters.
Only totals are kept:
- the number of page views, per page and per language, per day, and per hour (UTC) for human visits;
- an approximate number of unique visitors per day, and the country they visit from (country code only, see below);
- the domain name of the site the visit came from (never the full address of the page);
- the kind of device and the operating system and browser family;
- the browser language;
- whether the visit came from a campaign link (the “utm_source” tag);
- the response codes and render times of the pages, to monitor the health of the site.
To estimate unique visitors without tracking them, a fingerprint is computed from a shortened address (IPv4: /24, IPv6: /64) and the browser and operating system family, with a random salt that changes every day. This fingerprint exists in memory only: it is never written to disk, and it is wiped every day at midnight UTC. The user agent is reduced to those families, then forgotten. The country is derived from your IP address at the time of the visit, on the site’s server, using a local database (no third-party service is queried); only the country code (for example “BE”) is added to the totals, at most once per visitor and per day, and the address is neither kept nor logged for this purpose. Countries with few visits are grouped together when the statistics are viewed.
Geolocation data: IP Geolocation by DB-IP (https://db-ip.com), licensed under CC BY 4.0.
Bots (search engines, automated tools) are counted separately and are not included in visits.
The paths of pages that weren’t found (404 errors) are kept as totals per path, sanitized and limited to the 100 most frequent per day, to fix broken links.
These totals are kept for 25 months. Legal basis: legitimate interest (measuring the site’s audience, where it comes from, and the health of the site). Since nothing is stored on or read from your device, no consent banner is needed.
Web server access log
The web server that receives every request (website, downloads, contact form, telemetry) keeps an access log. It records: the truncated IP address (IPv4: /24, IPv6: /48, so never the full address), the date and time, the method, the requested path without URL parameters, the response code and the size. It records no user agent, no referrer and no browser language.
This log rotates in size-limited files: it covers a few days at most and disappears when the server is recreated. It is only used for security and for diagnosing outages or abuse.
The server’s operating system also keeps, for about 4 weeks, its own security logs (SSH, firewall), which contain the full address of the machines trying to connect to the server.
The contact form
The form collects the name, email address and message you enter. This data is only used to reply to you.
The message is stored in the site’s database, then deleted automatically after 90 days. Your IP address is not stored with it.
Submitting the form does, however, briefly appear in the web server access log (truncated IP address, date and time), without the content of the message.
The message is also delivered to a mailbox hosted at OVH, where it stays until the publisher deletes it. The publisher aims to delete it once the conversation is over; this deletion is manual, and there is no automatic erasure for this mailbox. You can ask for it to be deleted at any time.
To limit spam, the form contains an invisible trap field and a cap on messages per visitor. Your IP address is only used, in memory, to count those messages: it isn’t stored in the site’s database.
The form also asks for a proof of work: a small calculation your browser runs while you write, which makes sending in bulk costly for a bot. No external anti-bot service is used, and this calculation isn’t used for any tracking.
Downloads
The download buttons go through a redirect link that increments a counter aggregated by day, platform, architecture and version. The application stores neither the IP address nor the user agent: to avoid counting the same visitor twice on the same day, a salted fingerprint is kept in memory only, and wiped every day at midnight UTC. The request does, however, appear like any other in the access log described above.
The file itself is served by GitHub (the public diffwright-releases repository), which applies its own privacy policy.
The download statistics the publisher looks at also use the public counters GitHub shows for each published file: they are totals, with no personal data.
Hosting and backups
The website and its API run on a virtual private server rented from OVH (France).
Encrypted backups of the database are kept off the server, in a private GitHub repository: daily copies for 8 days, weekly copies for 30 days and monthly copies for up to about 190 days. The encryption keys never leave the publisher. A contact message deleted from the database can therefore remain in those backups, encrypted, for that time, without being used.
Recipients and processors
Your data is neither sold nor handed over. The following technical providers are involved:
- OVH (France, European Union): hosting of the server and the mailbox that receives contact form messages.
- GitHub: storage of the encrypted backups (private repository) and distribution of the download and update files (public repository).
- healthchecks.io: only receives a heartbeat ping, with no personal data.
No advertising trackers or third-party analytics services are used: the measurement described above is done by the site itself.
Transfers outside the European Union
GitHub may process data outside the European Union. The backups entrusted to it are encrypted with keys that GitHub does not hold; the files published in the public download repository contain no personal data. When you download a file from GitHub, it receives your IP address, under its own privacy policy. The other providers listed are hosted in France or receive no personal data.
The desktop app
By default, the app sends no usage data to Diffwright: that only happens if you accept the optional usage statistics described below. The one exception is the terms of use: the app contacts diffwright.app at first launch and from time to time to learn which version is in force, and, when you accept them, it sends a random identifier used only for this purpose (separate from the statistics one), the number and fingerprint of the accepted version, and the language; the server adds the date. No IP address is stored with this acceptance (the address is only used in memory, to limit request rates). Legal basis: legitimate interest (being able to establish which version of the terms was accepted). Each acceptance is kept until 5 years after the accepted version is replaced by a newer version in force. The acceptance ID is shown, read-only, in Settings › Privacy. The app also makes the following kinds of connections.
- With the platforms you connect (Azure DevOps, GitHub, GitLab), directly from your computer and with your token: only the platform concerned receives these exchanges, which don’t go through diffwright.app.
- With GitHub, to look for updates (the public diffwright-releases repository): GitHub then receives your IP address, as with any download.
- If you use the AI, the analyzed content (diff, comments) is sent to the engine you chose: your local Ollama instance (the content then stays on the machine that runs it), the claude CLI or Codex CLI (which send the content to their publisher, Anthropic or OpenAI, under your own account), or, as an option, a pay-per-use API (Anthropic, OpenAI-compatible) with your own key. These services process the content under their own terms; neither Diffwright nor diffwright.app receives it. Repository content is only sent to a paid engine after your explicit consent for that service; keys are stored on your computer.
Optional usage statistics and error reports
The app can send pseudonymous usage statistics and scrubbed error reports. It is optional: nothing is sent until you agree. The app asks once, at first launch or, for an existing installation, after an update. You can decline, and withdraw your consent at any time in Settings › Privacy; an explicit choice is not asked again.
Legal basis: your consent (Article 6(1)(a) GDPR). It is freely given: declining or withdrawing doesn’t prevent you from using the app and has no other consequence.
What is sent if you agree
- A random installation ID, created when you turn sharing on and never derived from your machine, your account or a code platform. It doesn’t identify you directly but stays stable as long as the installation exists on the server: it is a pseudonym, which the publisher treats as personal data. Turning sharing off doesn’t delete it: it stays on your computer so that erasure remains possible, and a new ID is only created after a deletion.
- The app version, the operating system (name and major version), the CPU architecture and the interface language.
- Daily counters of actions from a closed list (for example the number of pull requests opened), with no other content.
- Error reports: error type, message and stack frames, scrubbed as described below.
- When you turn sharing on, the app registers with the server: it performs a small calculation (about one second, a “proof of work”) that limits automated registrations, then receives a secret token. This token stays on your computer, is only used to authenticate this installation’s submissions, and is not kept by the server.
Error reports can be turned off separately in Settings › Privacy. Before anything is sent, their text is scrubbed twice, by the app and then by the server: paths, addresses, URLs, email addresses, identifiers and tokens are removed, and they contain no repository or file names and no content. For failures of AI tools, only the error category is sent.
What is never collected
- Your IP address and user agent are not stored by the application’s database (the address is only used in memory, to limit request rates and count registrations per network, with no geolocation). The web server access log does briefly record the truncated address, as for any request (see above).
- Names of organizations, projects, repositories, pull requests, branches or files.
- Code, diffs, comments and descriptions, file paths, tokens and credentials, email addresses.
To detect forged or oversized submissions, the server applies daily caps per installation and may flag an installation: unusual volume, an impossible system combination, registrations in a burst from the same network. Your network address is never stored: only random group numbers, kept in memory, link installations registered together. The publisher can exclude an installation that behaves abusively, and its submissions are then ignored; data from an unknown version is kept out of the statistics, then deleted within 72 hours. These flags are kept for 90 days.
Retention periods
- Raw events: 30 days.
- Crash reports: 90 days.
- Inactive installations: erased 180 days after their last signal.
- Anonymous daily totals, which aren’t linked to any identifier, are kept.
- Each installation’s activity days (number of submissions per day): 35 days.
In the app, the “Delete my data” button (Settings › Privacy) immediately erases everything linked to your installation ID, then forgets it and turns sharing off. You can also write to the publisher with your installation ID (shown in Settings › Privacy): the data is then erased by hand. The address of the erasure request is not written to the web server access log. The backups described above take at most about 190 days to purge it.
This data is stored on the diffwright.app server. It is not sold, not shared with any third party or analytics tool, and not used for advertising.
Purposes and legal bases
These legal bases are the publisher’s declared choice; they are not legal advice.
| Processing | Purpose | Legal basis |
|---|---|---|
| Website audience measurement | Measure the audience and the health of the site | Legitimate interest; no cookies, only totals are stored (including the country, never the IP address) |
| Contact form | Answering your message | Legitimate interest (answering a request) or pre-contractual steps at your request |
| Optional usage statistics and error reports | Knowing which versions are used, fixing crashes and protecting these statistics from abusive submissions | Consent (Article 6(1)(a) GDPR), which you can withdraw at any time |
| Acceptance of the app’s terms of use | Being able to establish which version of the terms was accepted, and when | Legitimate interest (proof of acceptance, establishing and defending legal claims); no IP address or identifying data stored |
| Web server log and rate limiting | Security, diagnosing outages and abuse | Legitimate interest (security of the service) |
| Download counter | Measuring usage in aggregate | Legitimate interest; no personal data is stored |
| Encrypted backups | Being able to restore the service | Legitimate interest (availability of the service) |
Retention periods
Usage statistics are only sent if you have agreed to them in the app.
| Data | Duration |
|---|---|
| Website traffic totals (per day, page views per hour, country) | 25 months |
| Contact form messages (database) | 90 days, then automatic deletion |
| Messages received in the mailbox | Until the publisher deletes them by hand, aiming for the end of the conversation |
| Raw usage counters (optional statistics) | 30 days |
| Error reports (optional statistics) | 90 days |
| Activity days per installation (optional statistics) | 35 days |
| Abuse flags on installations (optional statistics) | 90 days |
| Inactive installations (optional statistics) | 180 days after the last signal |
| Terms of use acceptances (random ID, version, fingerprint, language, date) | 5 years after the accepted version is replaced by a newer version in force |
| Web server access log | A few days at most (size-based rotation, lost when the server is recreated) |
| System security logs (SSH, firewall) | About 4 weeks |
| Encrypted backups | Daily 8 days, weekly 30 days, monthly up to about 190 days |
Your rights and contact
You have the right to access, rectify, erase, restrict and object to the processing of your data, and the right to data portability where it applies. For usage statistics, you can withdraw your consent at any time in the app, with no effect on using it; withdrawing doesn’t affect what was sent before.
To exercise these rights, write to the address below: the publisher answers within one month. To find a contact message, give the email address you used. For usage statistics, the app’s “Delete my data” button (Settings › Privacy) erases the data linked to your installation ID directly, without an email; otherwise, write and give that ID. For your acceptance of the terms of use, give the acceptance ID shown in Settings › Privacy, by email or through the contact form: the publisher can only find an acceptance with that ID, because no other data links it to you. It can’t be erased before the end of its retention period, since it serves as evidence; “Delete my data” doesn’t affect it.
Address for any request about your data: contact@diffwright.app
You can also lodge a complaint with the Belgian Data Protection Authority (APD/GBA): autoriteprotectiondonnees.be