Privacy Policy
Last updated: 19 September 2026
The short version: our apps do their work on your Mac and send nothing about you or your files anywhere. To run your subscription we keep your email address, your activation key, what you paid, and an anonymous hash of each Mac you activate. That is all.
What the apps collect
Nothing about you or your data. SecureMacApps apps have no account system, no analytics, no telemetry, no advertising or attribution SDKs and no crash-reporting service. They do not send file names, file contents, scan results, settings, or information about how or when you use them.
Your licence, activation key and settings are stored on your Mac. Where several SecureMacApps apps are installed, they share one licence file on the Mac so that a single activation unlocks all of them.
Every network request an app makes
- ActivateKey / hash only
securemacapps.com/api /v1 /activate - RenewKey / hash only
securemacapps.com/api /v1 /refresh - Free trialKey / hash only
securemacapps.com/api /v1 /trial - Update checkSends nothing
securemacapps.com/api /v1 /apps /<app> /latest.json - PriceSends nothing
securemacapps.com/api /v1 /prices
The machine hash is a SHA-256 digest of your Mac’s platform UUID and model identifier. The UUID itself never leaves your Mac and the hash cannot be reversed back into it. We store the hash to bind your licence to that Mac and to let you see and free your Macs on the account page. We do not record which of our apps made a request.
What we store to run your subscription
- Your email address — to send your activation key and receipts, and to let you manage the subscription.
- Your activation key, plan, number of Macs, paid-through date and subscription status.
- The payment provider’s identifiers for your subscription and payments, and the amounts paid.
- The machine hash of each Mac you activate, and when.
- If you start a free trial: the machine hash of that Mac and the trial’s start and end dates — nothing else. No email or other detail is asked for or stored.
- If you used a creator’s code, which code — so that creator can be paid. Creators see only a masked email (a***@example.com), the date, and the amount.
- A log of the emails we sent you (to whom, which template, whether it was delivered).
We do not store your IP address, your name, your postal address or any payment card or bank details.
Payments
Payments are processed by Razorpay. You enter your card or UPI details in Razorpay’s checkout, which runs on its own servers and is governed by Razorpay’s privacy policy. We never see full card numbers or bank credentials. Razorpay’s checkout script is loaded only on the checkout page, and only when you start a payment.
This website
This website runs no analytics, no advertising tags, no tracking pixels and no third-party fonts, and sets no cookies for visitors. Pages are served through Cloudflare, which processes requests (including your IP address) to deliver and protect the site and keeps standard security logs under its own policy. The creator and admin sign-in pages, and the key-recovery form, use Cloudflare Turnstile to block bots; it sets no cookies. Those two portals set a session cookie only after you sign in.
We send transactional email only: your key, receipts, renewal problems and replies to your messages. No newsletters or marketing unless you ask for them. Email is delivered through our email provider, which processes the message to deliver it.
How long we keep it
Subscription records are kept while your subscription is active and afterwards for as long as tax and accounting law requires. You can ask us to delete your record sooner; we will keep only what the law obliges us to.
Your rights
You can ask what we hold about you, ask for it to be corrected, exported or deleted, or object to how it is used. Because we hold so little, most requests take minutes. Write to privacy@securemacapps.com. Deleting your record means we can no longer look up or resend your key.
Changes
If an app ever needs to send something new, it will be listed on this page and on the security page before the release that sends it, and the date above will change.