Legal
Privacy Policy
MacOn is a remote control for your own Mac, so it handles some of the most private data there is: your screen, your keystrokes, your files. Here is exactly where all of it goes, which is mostly nowhere.
Last updated 28 August 2026
The short version
There is no MacOn account and no MacOn server. You never give us an email address, and there is nothing for you to sign into.
Your phone talks to your Mac directly. Screen frames, keystrokes, cursor moves, clipboard contents, files, terminal output and build logs travel between your two devices and stop there. They never reach us, because there is no "us" in the middle to reach.
The app contains no analytics, no crash reporting, no advertising and no tracking SDK of any kind. Not a disabled one, not a "we only collect anonymous usage" one. None.
The only outside parties involved are Apple and RevenueCat, for handling the purchase, plus whichever optional services you switch on yourself.
Contents
1. What we collect
Nothing, on any server we operate, because we do not operate one. To be specific, MacOn never sends us your name, your email address, your phone number, your location, your contacts, your photos, your device identifier, or a log of what you did in the app. There is no sign up step because there is no account.
The one exception is the purchase, and even that is anonymous. When you buy MacOn Pro, our payments provider RevenueCat records that an anonymous customer bought a product. We use it to check whether the app should unlock, and to see how many people bought which plan. It carries no name and no email from us. Details in section 7.
MacOn is designed this way for a practical reason, not just a principled one. A remote control for your Mac is a terrible thing to trust to somebody else's server, so we built it not to need one. It also means we cannot leak, sell, or be subpoenaed for data we never had.
2. Where each thing lives
Every piece of data MacOn touches, and who can actually see it:
| Data | Where it lives | Who can see it |
|---|---|---|
| Screen frames, cursor, keystrokes, clipboard | In flight between your phone and your Mac only. Never written to a server, never stored by us | You only |
| Files you browse, edit and save | On your Mac, where they already were | You only |
| Terminal input and output | In flight between the two devices | You only |
| Build logs and pipeline config | Your Mac, and your own repository | You only |
| Pairing code, device token | Keychain on your phone, config file on your Mac | You only |
| Repository credentials, AI keys, push key | Keychain on your Mac | You only |
| Settings, themes, Deck, Flows, the daily meter count | On the device, in standard app storage | You only |
| Reach beacon: tunnel URL, LAN address, port, status, power state | Your own private iCloud database, and only if you turn iCloud on | You, through your Apple ID |
| Push device token | Your phone, then your Mac, then Apple's push service | You and Apple |
| AI prompts, and agent screenshots | Your Mac if the model is local. Otherwise the provider you chose | You, and that provider |
| Purchase record and anonymous customer id | Apple, and RevenueCat | Apple, RevenueCat, and us as a total |
3. The connection to your Mac
On your own network, the companion connects straight to the Mac app over your local Wi-Fi. Nothing leaves your home or office, and no third party is involved at any point.
From outside your network, MacOn's built in option is a Cloudflare quick tunnel: your Mac asks Cloudflare for a temporary public address, and your phone reaches the Mac through it over TLS. That means your traffic passes through Cloudflare's network in transit, and Cloudflare's privacy policy applies to that leg. We do not run the tunnel, we cannot read it, and we never see the address.
The address alone grants nothing. Pairing requires a one time code shown on the Mac, and every request after that requires a device token. Tokens are stored in the Keychain and you can revoke a device from the Mac at any time.
If you would rather not involve Cloudflare, you do not have to. Point the companion at any address your Mac is reachable on, such as a VPN, Tailscale, or a port you forward yourself, and the tunnel feature stays off.
4. iCloud, if you turn it on
Off by default. When you switch it on, the Mac publishes a small beacon record to your own private iCloud database in the container iCloud.com.karar.MacON. The beacon says how to reach the Mac (its current tunnel URL, its local address and port), plus a compact status and whether the Mac is awake. A paired device signed into the same Apple ID reads it and re points itself, which is what lets your phone find the Mac again after a tunnel address rotates. The device can also write a small command record, which is how wake and unlock can arrive over iCloud instead of over the local network.
This is a private CloudKit database belonging to your Apple ID. We have no access to it. That is Apple's architecture rather than a promise we are making about our own conduct, which is the strongest kind. Turning the toggle off stops the publishing, and the records go away with the container if you delete the app's iCloud data in your Apple ID settings.
5. Notifications
Build notifications are unusual in that your own Mac is the push provider. There is no notification server of ours in the middle, because you supply your own Apple push key and the Mac app talks to Apple directly.
Your phone gets a push token from Apple and registers it with your Mac. Your Mac keeps that token locally and uses it to send alerts through Apple's Push Notification service when a build starts, passes or fails. The token never reaches us. The notification content is a build name and a status.
6. AI, and what leaves your Mac
This is the section to read if you use the AI features on a Mac with anything sensitive on screen.
- Local models, through Ollama. The model runs on your Mac. Your prompts, your code and your screen never leave the machine. This is the default and the private option.
- Cloud models, with your own key. If you add a key for Anthropic, OpenAI, Google, or any OpenAI compatible endpoint, the call is made from your Mac straight to that provider. Your key is stored in your Mac's Keychain and never sent to us. What you send is covered by that provider's privacy policy, not this one, and we have no visibility into it.
- The agent that drives your Mac works by looking at the screen. That means screenshots of your Mac, whatever happens to be on it, are sent to the model you selected. If your screen has client data, credentials or anything else you would not paste into a chat box, use a local model for the agent.
- Voice. Speech to text and the spoken replies use on device or local components, and the same rule applies to whatever model handles the conversation.
7. Purchases
Payment is handled entirely by Apple when you buy in the app. We never see, receive or store a card number or a billing address.
We use RevenueCat to check what you bought and whether it is still valid, which is what makes Restore Purchases work across your devices. RevenueCat records a purchase against an anonymous customer id that the app generates, together with the receipt from Apple and basic technical facts such as country, app version and platform. It does not receive your name or email address from us. Their policy is at revenuecat.com/privacy.
If you buy on this website instead, Paddle acts as the merchant of record. They collect what a seller has to collect to take a payment and issue an invoice, including your email and billing country, under their privacy policy. The receipt carries a link code, which is the anonymous customer id, and pasting it into the app is what moves the entitlement onto your device. The code identifies a purchase, not a person.
We can see totals: how many trials started, how many people are on the yearly plan, how much came in this month. We cannot see who you are.
8. Tracking and analytics
None. There is no analytics SDK, no crash reporter, no advertising framework and no attribution framework in the app. We do not build a profile of you, we do not track you across apps or websites, we have nothing to share with data brokers, and MacOn never asks for permission to track because it has no use for it.
The App Store privacy label reflects this: purchase history and an anonymous identifier, used only to make the app work, and no data used to track you.
9. This website
The site is static files served by GitHub Pages. We set no cookies and run no analytics. There is no CDN request either: the 3D world's Three.js library is committed into this repository rather than loaded from someone else's server, and the type is your own system font, so visiting a page does not tell any third party you were here.
The only thing the site stores in your browser is your light or dark preference, under the key macon-theme in localStorage. Clear your site data and it is gone. GitHub, as the host, processes server request logs including IP addresses under their privacy statement.
If web checkout is live, the checkout page loads Paddle's script so it can take a payment. That page is the only place on this site where a third party script runs, and it is only there because a card form has to be.
10. Children
MacOn is a developer tool. It is not directed at children, and we do not knowingly collect anything from anyone, of any age, because we do not collect anything at all.
11. Your rights
Depending on where you live you may have the right to see, correct, export or delete the personal data a company holds about you, and to object to its processing. This is where our answer is unusual: we hold nothing that identifies you, so in almost every case there is nothing to hand over and nothing to delete.
The exceptions, and what to do about them:
- Everything on your devices is yours already. Delete the app, or delete its data, and it is gone. Revoke a paired device from the Mac to cut its access.
- The iCloud beacon is in your own iCloud account. Turn the feature off, or remove the app's iCloud data from your Apple ID settings.
- The RevenueCat purchase record. Email us the link code from the app and we will ask RevenueCat to delete it. Be aware this is the record that proves you paid, so deleting it means Restore Purchases will no longer bring Pro back to a new device.
- Apple's and Paddle's records of the transaction are theirs, kept for tax and accounting reasons, and you would need to ask them.
No request costs anything and we do not need to verify your identity, since we have no identity on file to verify against.
12. Changes
If this policy changes, the new version goes up on this page with a new date at the top, and a change that materially affects you will be called out in the app's release notes. If we ever did add something that collects data, it would be described here first, and it would be off until you turned it on.
13. Contact
MacOn is made by Ali Haidar, an independent developer, who is the data controller for the little that exists.
- Email: musawahaidar123@gmail.com
- GitHub: github.com/alimusawa313/MaconKit/issues
- LinkedIn: Ali Haidar