Privacy Policy

The Mac app has no analytics or usage tracking. This website uses cookie-free PageHum analytics, alongside the records needed for your waitlist entry, optional X sharing and license.

Effective November 5, 2026. Questions: hello@systune.app.

The app

Systune does its work entirely on your Mac. It has no analytics, no crash reporting and no usage tracking. It does not upload file names, scan results, settings or system information anywhere. Activation and manual license checks require a connection; the Mac tools run locally.

What it writes, it writes locally and you can read: a history log and settings snapshots under ~/Library/Application Support/systune, and preferences in ~/.config/systune. Both are readable only by your account. Deleting those folders removes local Systune records. To delete your waitlist or license email, contact us.

The iPhone companion

The companion talks to one Mac, on your own network, using a pairing code you generate on that Mac. There is no account, no cloud relay and no server in between. The pairing is held in memory on the phone and is gone when the app closes.

Licenses

We can also assign complimentary lifetime licenses to friends and testers. For these we keep the recipient email, Friends or Testing purpose, license code, creation and release date, any revocation date, Mac allowance and activation records. These licenses do not require a waitlist signup and are managed separately from giveaway reservations. Removing a waitlist signup does not remove a separate complimentary license; contact us to manage or delete its data.

The first 100 unique waitlist signups receive a free lifetime license. We provision the codes privately and reserve them in signup order. Codes are on hold and are not sent or activated until we explicitly release them.

We keep a license code, its reservation email, signup position, license type, creation date, release or revocation date and Mac allowance in a private Cloudflare database. An administrator can manage these records using an authenticated website. License management actions are logged with their time and license ID; codes and email addresses are not included in the action log.

The private Mac beta download checks your license code and assigned email without using a Mac activation. Its download page uses one essential, secure, HTTP-only cookie that expires after 15 minutes. It contains a short-lived access ticket, not your email or license code. The page clears entered credentials after a request and does not save them in browser storage. Each download request checks that the license remains active. Downloads are stored privately on Cloudflare; a copied download link still requires valid access.

Signed updates in the direct Mac edition check your license on request and before installation. The app holds update access tickets in memory. You choose when to install and restart; updates preserve your local settings, history and saved license. The App Store and TestFlight editions use Apple's update systems.

When you activate, check or deactivate a license, the app sends the code, its assigned email and a randomly generated installation ID to our Cloudflare license service. It does not send your Mac's name, serial number, file names, scan results or settings. The service stores active installation IDs and activation dates so it can manage the license's Mac allowance. The app keeps your code and last verified license status privately on your Mac.

This website

To investigate blocked inline styles on the homepage, a first-party diagnostic records only a fixed release label, the blocked directive, a source category and numeric line/column. It never sends CSS text, page text, full URLs, email or account details. At most two distinct events are sent per page load to our Cloudflare service, with rate limiting and no cookies; sanitized fields appear in operational logs, separate from waitlist records.

For a reported JavaScript timeout or rejection without a reason on the homepage and three comparison routes, a similar diagnostic sends only a fixed route, error category, event type, source category, release label and numeric line/column. It sends at most two distinct events per page load. Raw error messages, stacks, full URLs, browser storage and account details are not sent. This does not suppress ordinary browser or PageHum reporting.

No advertising or analytics cookies, no tag managers and no fonts loaded from anyone else. The site is hosted by Vercel and the waitlist and license service runs on Cloudflare. These providers process ordinary request information, such as network addresses and security logs, to deliver and protect the service. We do not use it to build advertising profiles. See Vercel's Privacy Policy and Cloudflare's Privacy Policy.

X sign-in uses one essential, secure, HTTP-only cookie on our waitlist service to confirm that the browser returning from X started the login. It lasts up to ten minutes and is cleared when the callback finishes. X may set its own cookies on its own site.

Website analytics and uptime

We use PageHum to measure pageviews, visitors, sessions, referral sources, broad device categories, page performance, interaction and error counts, and broken links. It also checks whether our homepage is available. Page paths are reported without query strings or URL fragments.

The PageHum script sets no cookies and sends no visitor identifier. It keeps dates and simple flags in your browser's local and session storage to count visits and engagement. PageHum receives the request information needed to deliver its script and accept these events.

After the server confirms a waitlist entry through email signup or a private access link (including a return from X), we send a generic success event. We do not add email addresses, X account details, private access credentials, license codes or post text to analytics events. Returning to an already signed-in page does not itself record another success.

The waitlist

If you enter your email address on the waitlist, we store that address and the date you entered it, your signup position and any license reservation. Not your IP address, not your browser, not which page you came from in the signup record. It is kept in a private Cloudflare database with access restricted to service operations and authorized administrators. We do not sell or rent your address, share it for advertising or use it to build an audience elsewhere. Our hosting providers process data to operate the service.

You will get at most two emails: one when the beta opens and one when Systune ships. There is no newsletter and no sequence. Reply to either one and we delete the address outright — we do not keep a suppression list with your name on it. Deleting the address also removes it from its license reservation and revokes that code.

Your browser also remembers locally that you joined, so the form does not ask you again. That is stored on your own device and is never sent anywhere.

Optional X sharing challenge

You can log in with X to join or recover the waitlist entry matching your confirmed X email. We request your account identity, confirmed email, permission to read and publish posts, and offline access for later checks. We store your X account ID and username, encrypted access and refresh tokens, the post ID and verification times. We do not store a copy of your post text.

Publishing requires your explicit confirmation of the full public post. Its personal share link identifies this challenge entry; it never contains your email or private access credential. A verified post earns early-access priority while it remains public and published. We check daily and pause priority after 48 hours without successful confirmation. Removing the post or the required link or disclosure removes the boost. Existing lifetime-license reservations do not change.

Your private waitlist access credential is kept in this browser and sent only to our waitlist service to retrieve your position and manage sharing. Logging out removes it from this browser. Disconnecting X removes stored X tokens and the sharing boost; we also attempt to revoke X access. You can revoke Systune in X's connected-app settings. Deleting your signup removes its X data, saved post ID and private access credential. We never delete your public X post for you.

To stop automated abuse the form counts how many submissions have come from one network address in the past hour. Our application stores a salted one-way hash of that address rather than the address itself. This rate-limit record is never attached to your signup and expires after one hour. Hosting providers separately process requests as described above.

Retention and your choices

We keep waitlist and connected-account records while your entry is active, and license records while needed to manage the entitlement. You can request access, correction or deletion by writing from your signup address to hello@systune.app. We may need to verify ownership before changing a record. Deleting your signup removes its email and X connection; a non-identifying signup position, revoked license record and security audit history can remain so deleted giveaway places are not reused.

You can clear site storage to remove the browser's local joined flag and private access credential. This does not delete your server-side entry. To manage X's own use of your data, see X's Privacy Policy and its connected-app settings. We use these records to provide and secure the service and respond to your requests, not for advertising. If privacy rights apply where you live, contact us to exercise them.

Getting in touch

Questions about any of this: hello@systune.app.