Privacy

Your check-ups and report cards. No account, no telemetry, no analytics, no automatic crash reporting. Lunite uploads none of them on its own; a report card leaves only when you press SEND. One catch: if you run it from a folder that OneDrive or a similar service syncs (a OneDrive-backed Desktop, for example), that service copies them like any other file.

Only when you press SEND on the SEND A REPORT screen in SETTINGS; its "See the exact card" link shows the report first.

Your report card lists your PC's parts and models, the Windows settings it checked, and the names of programs it found (startup programs, programs with updates, programs that crashed). It holds:

• your report card, with this PC's name, your Windows user name and your user folder's path left out, and serial numbers that carry a label Lunite recognizes (like Serial Number or S/N) left out — a name or number Lunite doesn't recognize can stay in, so read the whole card first;
• your tag, a six-character code for this PC made one-way from Windows' own ID for this install, so the ID itself never travels (the same each time you send from this PC, so two reports can be matched);
• the app and Windows versions, Lunite's newest crash note if there is one, the time you sent it, and anything you typed.

A Google Apps Script on Lunite's Google account saves it in that account's Google Drive and emails it to luniteapp@gmail.com. It stays there until it is deleted; nothing deletes it automatically.

To have it deleted, email luniteapp@gmail.com with your tag (the SEND A REPORT screen shows it) and roughly when you sent the report. One tag covers every report sent from this PC, and the date helps, because a short code can be shared by two PCs.

Write the tag down before you remove Lunite; reinstalling Windows gives the PC a new one. If you lost it, email anyway and say roughly when you sent the report.

Like any internet connection, each of these calls shows your IP address to the server it reaches. ABOUT in the app lists every one.

• The update check: only when you press CHECK FOR UPDATES in SETTINGS, or once at launch if you tick the box there. It asks Lunite's GitHub release page for the newest version; if there is a newer one, it downloads it and checks it, then asks you before installing anything.
• Name-server (DNS) timing, during every check-up: a handful of public names (such as example.com, microsoft.com and wikipedia.org) are looked up through your own name server and two public ones, Cloudflare (1.1.1.1) and Google (8.8.8.8), to see which answers fastest. As with any lookup, your router or network can see these names.
• The connection load test, only if you tick it: about six to eight seconds of download from Cloudflare's public speed test, plus about twenty pings to 1.1.1.1. It uses roughly 1 MB for every 1 Mbps of your line (close to 1 GB on gigabit), so skip it on metered internet.
• The program-updates listing, during every check-up: Windows' own winget fetches Microsoft's public catalog to see which of your programs have a newer version. Depending on your Windows diagnostic-data setting, winget may also send Microsoft its own usage data.
• About a dozen pings to your own router, during every check-up. They go no further than your router.
• One fix changes where your lookups go: if switching to a faster DNS is one of the suggested fixes, pressing FIX times the name servers again on a few popular sites (such as youtube.com or github.com). If you approve the switch, one test lookup confirms it works, and from then on Cloudflare or Google answers your web-address lookups instead of your current DNS, so that company sees which addresses your PC looks up. Like any fix, it has an undo in WHAT CHANGED, which tells you if your DNS setting has changed since.

No cookies of its own, no analytics scripts, no trackers: the site has no scripts and no forms, and loads nothing from other websites.

Cloudflare delivers the pages: like any web host, it handles your IP address and basic request details to serve and protect the site, under Cloudflare's privacy policy. Depending on its security settings, Cloudflare may set a strictly necessary security cookie, for example after checking that a visitor isn't a bot. Cloudflare also keeps standard traffic counts (such as pages served and visitors' countries) that Lunite can see; they don't name anyone.

The Download buttons hand off to the newest Lunite.exe on Lunite's release page at GitHub, under GitHub's privacy statement. Messages to luniteapp@gmail.com are kept in that Google account.

Payments will be handled by Stripe, and Lunite never sees your full card number. Before the paid version goes on sale, this page will be updated to say what a purchase shares with Lunite and how long it is kept.

If this page changes, the date at the top changes with it. Questions about privacy: luniteapp@gmail.com.