Last updated 17 August 2026
Ventus does not collect anything about you. That is not a policy position, it is a property of the code: it makes exactly one network request, and that request says nothing about you or your machine.
Ventus reads sensors, controls fans, and stores your profiles and curves locally on your Mac. It has no analytics, no crash reporting and no user accounts. It never transmits your telemetry, your settings or anything else about you.
The one request it makes is the update check: a plain GET of
iventus.app/version.json, a small static file listing the current version. It carries
no identifier, no serial number and no query parameters — it is the same request any browser would
make for that file, and our server sees only what serving any file reveals: an IP address, a user
agent and a timestamp. It runs at most once every six hours, and you can turn it off, after which
Ventus makes no network requests at all.
The check only notices. It never downloads or installs anything, and it can only ever point at iventus.app.
Separately, when you click a link — the tip button, a support link — Ventus hands that URL to your default browser. The app itself is not making that request.
You do not have to take our word for it. Ventus is source-available: read
the source and check for yourself. Search it
for network calls and you will find exactly one — UpdateChecker.swift — and you can
read precisely what it sends.
This site is static. There is no advertising pixel, no tag manager, no cookie set by us, and nothing that can follow you to another site.
We do count page views, using Cloudflare Web Analytics. It records that a page was loaded and where the visit came from; it does not use cookies, does not fingerprint your browser, and has no way to recognise you on a second visit or on anyone else’s website. We chose it over the usual options precisely because it cannot build a profile of you — we want to know whether an article sent ten people or a thousand, not who they are.
One thing is stored in your browser, and it is worth describing exactly. If you arrive from a
link that carries campaign tags, or from another site, the page keeps a short label of that origin
— something like s-github__m-referral — in sessionStorage.
When you click through to buy, that label is attached to the checkout so we can tell which link
actually led to a sale. It holds no identifier and nothing about you, it is discarded the moment
you close the tab, and it is never sent anywhere except to Stripe as part of a checkout you chose
to start.
Between that counter and the page’s own assets, this page contacts a few services we do not control. Each necessarily sees your IP address and user agent:
static.cloudflareinsights.com for the
script, cloudflareinsights.com for the measurement it sends) — the page-view
counter described above.None of these are analytics and none of them are asked to identify you, but they are third parties and you deserve to know they are there. We intend to self-host the fonts and the runtime so that fewer of them are needed at all.
When buying Ventus, payment is processed by Stripe. Your card details are handled by Stripe and are never seen by or sent to us; we receive only what is needed to deliver your purchase and provide support, such as your email address and the fact that a payment succeeded. Stripe's own privacy policy governs the data they hold.
For anything touching a purchase — a question about your order, or a request to delete what we hold about it — reply to your Stripe receipt. That reaches us privately, and it is the right channel precisely because it should not be public: a GitHub issue would publish your email address and your purchase for anyone to read.
For bugs and questions that involve no personal detail, the issue tracker is the better place — other people with the same Mac benefit from the answer.