Last updated 30 October 2026
Privacy
The short version: WispOS keeps your projects on your own computer. This website counts visits in totals, with no cookies, ads or tracking. The only personal information we hold is an email address you give us, an invite code we made for you, a bug report you choose to send, or the details Stripe needs if you donate.
The WispOS app
Your projects, your HQ folder and everything Wisper and your helpers write live on your own computer. Nothing in them leaves it unless you ask, apart from what you send to the AI service you chose as Wisper's brain, under that service's own terms.
Your WispOS account. The first time you open WispOS it asks for an email address and a password, and a first name if you like. Our account server on Cloudflare keeps the address, the name, whether you want WispOS news, and the app's version and system; the password is kept only in scrambled form we cannot read back. To check the address is yours, we email you a link through Resend, the service that sends our account and App Store emails. If you leave Send me WispOS news ticked, the app adds your address to our own news list, kept in our database on Cloudflare, noting that you signed up from the app and the words of the box you left ticked. We email you once to confirm, and you are only on the list after you click it. Our news emails are sent through Amazon SES. Each one counts whether it was opened (a tiny image) and which links were pressed (they pass through our own server, campaigns.wisp-os.com), so we know what people read, and each has a one-press unsubscribe link. (Versions of the app before 0.2.68 sent the address to Kit instead; we are closing that account.)
Bug reports. If you press Report a bug, the app shows you exactly what it will send before anything leaves your computer: what you wrote, a way to reach you if you gave one, and, if you leave the box ticked, recent app logs with your name, folders, email and IP addresses and keys scrubbed out. Press Send and it goes to our bug inbox on Cloudflare. We use it only to fix the bug, and we delete it when you ask.
hyprmac
hyprmac runs entirely on your Mac. It has no account system, no analytics, no crash reporting and no update check. It does not send your window titles, your configuration, your layout or anything else anywhere, because it has no code that makes a network request at all.
Its log file lives at ~/Library/Logs/hyprmac.log on your own disk. It is yours;
we never see it unless you attach it to an email yourself.
What this website counts
We want to know which pages people read and which posts brought them here, so we count a little. Everything below is a total. None of it says who you are, and none of it can be joined up into a picture of one person.
Visits. We use Cloudflare Web Analytics, the free tool from the company that hosts this site. A small script on each page tells Cloudflare a page was viewed and gives us totals: how many views each page got, which site linked here, which country visitors were in, what kind of device and browser, and how fast pages loaded. It uses no cookies and nothing stored in your browser, and Cloudflare says it does not fingerprint you or follow you from visit to visit. We see the totals in Cloudflare's dashboard, never a list of visitors.
Our own tallies. On our own server we keep a handful of daily totals:
how many pages were opened from a link with a campaign tag on it (the utm_
part of an address, like utm_source=newsletter), and which tag; how many
addresses joined the mailing list from each signup box; how many times the beta
download link was used, by campaign tag; and how many times each short link
(wisp-os.com/go/…, the ones said out loud on podcasts and streams) was opened. Each line reads like "16 October, newsletter,
3". Nothing else goes with it: no IP address, no browser details, no email, no cookie.
Invite codes. If you are sent a closed-beta invite code, we know who we made it for, because we made it for you. We note when the code is first used, each time it is entered, each build it downloads, any try after we switched it off, and the country Cloudflare saw for each of those (the country only, not your city or IP address), so we can tell whether a code has been passed around. Separately, we count how many codes were accepted and turned down per batch of invites, as totals.
What we do not do: no advertising networks, no Facebook, Google, TikTok or other tracking pixels, no fingerprinting, no selling or sharing of any of this, no profiles.
Cookies
One, and only if you have an invite code: when you type a good code on the closed-beta page, your browser keeps it in a cookie for 90 days so the download page stays open. It holds the code and nothing else. "Use a different code" on that page deletes it. Nobody else gets a cookie, and there is no consent banner because nothing here needs one.
Two things are kept in your browser, not sent to us. If you pick light or dark with the
button in the header, your browser remembers that choice. If you arrived from a link with
a campaign tag, the tab holds the tag until you close it, so a signup can say which post
sent you. The same goes for the name of the website that linked you here (just its name,
like reddit.com, not the page).
Hosting and light or dark
The site is hosted on Cloudflare Pages, which keeps short-lived server logs including IP addresses for security and abuse prevention. That is standard for any web host and we do not query those logs for anything else.
The site switches between light and dark at sunrise and sunset where you are. To know when that is, Cloudflare's rough guess at your city (from your IP address, rounded to about 10 km) is written into the page you are reading, and your browser does the sums. It is not stored, logged or sent anywhere else, and there is no location prompt.
If you join the mailing list
We store the email address you give us, which page you signed up from, and, if the link
that brought you here carried a campaign tag (the utm_ part of an address, like
utm_source=newsletter), that tag, so we know which post sent you. Your browser
holds the tag in the tab until you close it; it is not a cookie. We also keep the sentence
you ticked to agree, and when. If you answer the optional "What will you build?" question
under the box, we keep your answer with your address: which you picked (a game, an app or
something else), the line you wrote, and Mac or Windows. We use it to pick who gets each
wave's invite codes. If you answer the optional "How did you hear about us?" question, we
keep that too: which you picked and the line you wrote. And if another website linked you
here, we keep that website's name (like reddit.com), never the page you were
on. Those two tell us which posts and articles bring people. Nothing else — no name, no company, no profile. A signup on this
website is kept in our own database on Cloudflare, the host this site already runs on; no
mailing-list company holds it.
We use it for what you agreed to: your WispOS closed-beta invite, and WispOS news and offers. We do not sell, rent, share or trade it. Every email has your own unsubscribe link: one press on the page it opens and we stop at once. You can also reply "stop", or write to us. If we later use a service to send those emails, we will name it here first.
If you donate
Payments are handled entirely by Stripe. Your card details never touch this site — you are on Stripe's own page when you enter them, and we never see or store them.
Stripe tells us the amount and the email address it collected for the receipt. We use that only to identify the payment. Donating does not add you to any mailing list. If you want updates, there is a separate signup box on the support page that you have to fill in yourself.
Fonts
The site currently loads its typefaces from Google Fonts, which means your browser requests those files from Google and Google sees your IP address in the process.
Who we share with
That is the complete list. Nobody else receives anything.
| Service | What it gets | When |
|---|---|---|
| Cloudflare | IP address, in ordinary server logs; the page-view totals above; your email address, WispOS account, invite code record or bug report, stored for us | Every page view; the address only if you sign up, the account only if you make one, the code only if we invite you, the report only if you send one |
| Amazon Web Services (Amazon SES) | Your email address and the news email we send you, to deliver it | Only if you leave "Send me WispOS news" ticked when you make your WispOS account: the email asking you to confirm, then each news email |
| Kit | Your email address and that it came from the WispOS app | Only from versions of the WispOS app before 0.2.68, when the news list moved to our own (we are closing our Kit account) |
| Resend | Your email address and the email we send you, to deliver it | When you make a WispOS account (the link to confirm your address), and, if you send an app to the App Store, news about its review and the reviews people leave it |
| Google Fonts | IP address, to serve font files | Every page view |
| Stripe | Payment details and an email for the receipt | Only if you donate |
Your rights
Wherever you live, you can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted. If you are in the UK, EU or EEA, the GDPR gives you those rights explicitly, along with the right to complain to your data protection authority.
The honest practical answer is that the most we are ever likely to hold is your email address, the invite code we made for you and when it was used, or a bug report you sent. Email support@wisp-os.com, or by mail: WispOS, 311 New Bern Ave #24854, Raleigh, NC 27611, and we will delete it and confirm that we have.
We keep mailing list addresses until you unsubscribe or ask us to remove them, and invite code records until the closed beta ends or you ask us to remove yours. The totals hold nothing about you, so there is nothing in them to delete. Stripe keeps payment records for as long as tax and accounting rules require.
Children
WispOS is not meant for children, and we do not knowingly collect anything from anyone under 16.
Changes
If this policy changes in a way that matters, the date at the top changes and — if you are on the mailing list — we will tell you rather than quietly editing the page.
Contact
WispOS is the data controller for the purposes of the GDPR. Questions, requests and complaints all go to support@wisp-os.com.