Legal

Privacy policy

The iKnowMyMac app watches your Mac so you don't have to, and what it sees stays on your Mac. This page lists every request the app makes and everything this website collects.

Last updated 8 November 2026

On this page

In short
Who we are
The app: what stays on your Mac
The app: every network request
The website
Email me the link and the waitlist
Analytics and cookies
Campaign tags
Purchases and licenses
Support email
Feature requests and problem reports
Service providers
How long we keep data
Your rights
Children
Changes to this policy
Contact

In short

The app has no account, no analytics and no telemetry. Your usage history, app list and diagnoses stay on your Mac.
On its own, the app makes only these requests: update check, license check, app update feeds, homebrew app list and our update sources, app store lookup, daily status check, package list, public database's package list, runtime list. Only when you ask: license activation, license deactivation, internet check, update downloads, coverage request, feature requests, votes and comments, similar requests and help articles, problem reports, my requests. Off until you turn them on: public ip watch, verify with github, background fetch, traffic name look-ups, blocklist updates, location databases, dns health checks, app inspector, crash reports. All 29 are listed below.
Some requests never leave your Mac or your local network: status requests to local model servers on 127.0.0.1. They're listed below too.
Git features that reach your Git host are off by default: one SSH handshake per key with your Git host, to learn which account it belongs to and git fetch to your repos' own remotes every 30 minutes. They use your own keys and credentials, contact only your Git host or your repos' remotes, and send nothing to us. See below.
This website does use analytics: Microsoft Clarity, which in the EEA, the UK and Switzerland sets cookies only after you allow it. See Analytics and cookies.
Dodo Payments sells the license as our Merchant of Record. They handle your payment details; we never see your card number.
If you arrive from one of our ads or links that carries a campaign tag, this website keeps the tag until you close the tab and, if you buy, attaches it to your order so we know which ad led to a sale. The tag names the ad, not you. See Campaign tags.
We don't sell personal data, and we don't share it with advertisers or ad platforms.

Who we are

iKnowMyMac is made by iDevelopApps (“we”, “us”). This policy covers the iKnowMyMac app for Mac and the website at iknowmymac.com. For anything about your privacy, write to support@iknowmymac.com.

The app: what stays on your Mac

iKnowMyMac reads activity figures from macOS (CPU, memory, GPU, disk, network, battery, temperatures, sleep and wake events, running processes, open ports and developer tools) and keeps them on your Mac. None of it is sent to us or anyone else.

What the app stores on your Mac
What	Where	How long
Usage history (per-app and system figures)	`~/Library/Application Support/iKnowMyMac/history.sqlite`	30 days. 10-second detail for the last day, 1-minute detail to 7 days, 5-minute detail to 30 days; older rows are deleted automatically.
Battery health samples	`~/Library/Application Support/iKnowMyMac/battery-health.json`	One sample a day, kept to show the trend.
Your license key and this Mac's license instance ID	Your macOS Keychain, as “iKnowMyMac license”	Until you move the license to another Mac or delete the item.
Settings, alert rules, the date of the last license check	The app's preferences on your Mac	Until you delete them.
The file search index: the names, sizes and dates of your files and folders, never what's inside them. It is never uploaded, synced or included in diagnostics.	`~/Library/Application Support/iKnowMyMac/search/`	Until you turn Search off, which deletes it.
The app's own log: notes iKnowMyMac writes about itself, such as when it started. It leaves your Mac only inside a problem report, if you tick Include diagnostics, after you've read it.	`~/Library/Application Support/iKnowMyMac/diagnostics.json`	The most recent 400 lines.
The package inventory: the name and version of each npm, Python and Maven package found in your projects, global installs and caches, where it is and when it appeared, with the downloaded list of known-bad versions it is matched against. It is never uploaded, and diagnostics carry counts only.	`~/Library/Application Support/iKnowMyMac/packages/`	Kept current as your projects change, until you delete the folder.
The runtime list, which says which Node.js, PHP, Go and Java versions have security fixes, and the version Laravel Herd's PHP gave when asked, since Herd keeps no version on disk. The Node.js, PHP, Go and Java copies and the certificate bundles found on your Mac are matched there and never uploaded.	`~/Library/Application Support/iKnowMyMac/packages/`	Until a newer list replaces it, or you delete the folder.
Disks that disappeared or couldn't be ejected: the time, the disk's name, and the few system log lines that explain it, which can include device product names. They are read on your Mac at that moment and are not in diagnostics.	With the USB log, in the app's folder on your Mac	The newest 200 events, for up to a year.
Agent Undo's copies: what is inside the files in project folders where a coding agent has worked, and in folders you add in Settings, with each later version the app sees, so that a file can be put back. Nothing else in this table holds the contents of your files. Not copied: the .git folder, folders that can be rebuilt such as node_modules, and files over 200 MB. The copies are never uploaded, synced or included in diagnostics, Search and Spotlight leave them out, and the folder is marked to be left out of Time Machine. They are on the same disk as the originals, so this is not a backup.	`~/Library/Application Support/iKnowMyMac/undo/`, which only your account can open	A version that was replaced, or whose file was deleted: 14 days, or less once together they reach the smaller of 10 GB and 10% of your free space. The current version of each file: until you delete the copies in Settings → Agent Undo.
While Always-on mode (Beta) is on: your original sleep and power settings	/Library/Application Support/iKnowMyMac/PowerComponent, readable only by the system	Until they're put back, then deleted.
Traffic's log, only after you turn Traffic on: for each connection your Mac made or accepted, the time, the program and the processes that started it, the project and agent session it belongs to, the address, port and host name, how much data it moved and whether it was allowed, blocked or held. Never what a connection carries. It is never synced, sent anywhere, or added to feedback or diagnostics, and Traffic blocks nothing unless you turn on Blocking.	`~/Library/Application Support/iKnowMyMac/traffic/`, readable by you only	30 days, or the 7 or 90 you choose in Settings → Traffic, until you delete it there.
Traffic Control's data, only after you turn Traffic on: your Blocking rules and trusted networks, your answers to held connections and the Decide later list, how often each rule and blocklist matched, the blocklists you subscribe to, the location databases (country and network, and the city database once you open Map), daily totals for 12 months, your encrypted DNS choices and the results of its checks, Explain's answers and your own entries in its domain list, and the programs you allowed to use `ikmm` commands that change rules. None of it is synced, sent anywhere, or added to feedback or diagnostics.	The `traffic`, `blocklists`, `geo` and `explain` folders in `~/Library/Application Support/iKnowMyMac/`, and Explain's answers in `~/Library/Caches/com.gs.iknowmymac/explain/`	Rules until you delete them, temporary ones until they end; hit counts 8 days; daily totals 12 months; Explain's answers 24 hours; the newest 500 on the Decide later list. Settings → Traffic → Turn Off… → Delete everything now removes all of it.
Inspected requests, only for a project you inspect: the URLs, headers, bodies (up to 1 MB each) and timing of the requests its tools sent through Inspect's proxy. While auth headers are hidden, as they are by default, their values are not stored. The project's certificate key stays in your keychain, and the certificate is never added to your trust settings.	`~/Library/Application Support/iKnowMyMac/inspect/`	1, 7 or 30 days, as you choose for the project, until you delete its setup.
App Inspector's sessions, only while you have it on: the requests, responses and log messages that your own apps with the Pulse SDK send it, one store per device and app. Sign-in headers are hidden on screen and in exports. Never synced, backed up by Time Machine or added to feedback.	`~/Library/Application Support/iKnowMyMac/devices/`	1, 7 or 30 days, as you choose in Settings → App Inspector.

Deleting the app and these files removes everything; our uninstall guide lists the steps. The optional helper (see what it does) reads more of the same kind of figures for the app; it can't use the network.

On macOS 26 and later, the diagnosis summary is phrased by an Apple model that runs on your Mac. The diagnosis is not sent anywhere. Explain, in Traffic, uses the same kind of model: it puts its question together and answers it on your Mac, sends nothing about a connection to us or to anyone else, and keeps its answers for 24 hours. Without Apple Intelligence it answers from a list of domains built into the app.

Location (Wi-Fi name). Used only to read the name of your Wi-Fi network: for trusted networks in Blocking (asked the first time you trust a Wi-Fi network) and for the Wi-Fi card’s name (when you click Show network name). Where you are is never read, kept or sent.

The app: every network request

These are the only requests the iKnowMyMac app makes: 29 in all, last checked against the shipped app on 2026-10-25. Links you open from the app (Buy, help pages, this page) open in your browser.

Every network request the app makes
Request	When	What it sends
Update check `iknowmymac.com/appcast.xml` Automatic	Once a day while “Check for updates automatically” is on (it is by default), or when you choose Check for Updates…. Settings then General then Check for updates automatically	A standard web request whose header names the app, its version and the Sparkle version. Sparkle's system profile is off, so nothing about your Mac's hardware or setup is included. If you install an update, it downloads from iknowmymac.com/downloads/.
License activation `live.dodopayments.com` When you ask	When you activate a key.	Your license key and your Mac's name (as set in System Settings → General → Sharing). Dodo replies with a random instance ID for this Mac.
License check `live.dodopayments.com` Automatic	When the app opens and then every 7 days, or when you choose Validate Now.	Your license key and the instance ID.
License deactivation `live.dodopayments.com` When you ask	When you choose Move License to Another Mac….	Your license key and the instance ID.
Internet check `captive.apple.com` and Apple's network test servers When you ask	Only when you press Check.	One request to Apple's captive portal check, the same one macOS makes when you join Wi‑Fi, then macOS's built‑in network test (networkQuality), which measures speed with Apple's servers. Nothing about you or your Mac is added. Checking that your router answers stays on your local network.
Public IP watch `iknowmymac.com/api/ip` Off by default	Only if you turn on Public IP address changes. Off by default. Then every 5 minutes. Settings then Alerts then Public IP address changes	An empty request. The reply is your public IP address. The endpoint stores nothing.
App update feeds `api.github.com` and each app's own update feed Automatic	Only while the Updates tab is on: each check, one request per app it covers.	The same request the app itself makes to its developer's feed, or GitHub's public release list for apps published there. Nothing about your other apps is added.
Homebrew app list and our update sources `formulae.brew.sh`, `iknowmymac.com/updates/catalog.json` Automatic	Only while the Updates tab is on: Homebrew's list at most every 6 hours, ours once a day.	Nothing. Each is one public file, downloaded whole.
App Store lookup `itunes.apple.com` Automatic	Only while the Updates tab is on: each check, one request for all App Store apps.	The App Store IDs of your App Store apps and your store's country, to read their latest versions.
Update downloads the developer's own server When you ask	When you install an update, or automatic installs are on.	A standard download from the developer's own server. It's checked before anything is replaced.
Coverage request `iknowmymac.com/api/coverage` When you ask	Only when you press Request coverage on an app we don't cover yet.	The app's name, bundle ID and version, shown to you first. We store those three fields and nothing else.
Local model servers `127.0.0.1` on this Mac only: Ollama, LM Studio, llama-server and similar On this Mac	While a model runtime is running on your Mac, as part of normal sampling.	Status requests only, such as Ollama's list of loaded models, to read which models are loaded and the memory they hold. They go to your own Mac and never leave it. Prompts and model outputs are never read.
Verify with GitHub your Git host over SSH, such as github.com Off by default	Only if you turn on Verify with GitHub. Off by default. Then one check for each SSH key. Settings then Git then Verify keys with GitHub	An SSH handshake with that key, the same one ssh -T git@github.com makes. The host replies with the name of the account the key belongs to. No API token is used, and nothing is sent to us.
Background fetch `git fetch` to each repo's own remotes Off by default	Only if you turn on Background fetch. Off by default. Then every 30 minutes for the repos iKnowMyMac knows. Settings then Git then Background fetch	A normal git fetch with your own Git credentials, to each repo's own remotes and nowhere else, so ahead and behind counts stay current. Nothing is sent to us.
Feature requests, votes and comments `iknowmymac.com/api/feedback` When you ask	Only when you press Send or Vote. Send shows the list of what will go first.	The title and details you wrote, the name of the screen it's about, a picture of the iKnowMyMac window if you attached one, your email if you typed one, the app version, and a licence check: a one-way code made from your key, never the key.
Similar requests and help articles `iknowmymac.com/api/feedback` When you ask	While you type in a request or report sheet you opened, a moment after each pause.	The words typed so far in the title, and the screen's name, to find matching requests and help articles. Nothing else is sent, and nothing after the sheet closes.
Problem reports `iknowmymac.com/api/feedback` When you ask	Only when you press Send. Send shows the list of what will go first.	What you wrote, your email if you typed one, the licence check and the app version. If you tick Include diagnostics: the app version, the macOS version, this Mac's model and memory, and up to 200 lines of iKnowMyMac's own log with your home folder shown as ~. You can remove any of it first.
My requests `iknowmymac.com/api/feedback` When you ask	When you open My requests, or a thread in it.	The licence check, to fetch your own requests, votes and replies. Opening a thread tells the website you've read it.
Daily status check `iknowmymac.com/api/feedback` Automatic	Once a day, and only after you've posted or voted. It can be turned off. Settings then Feedback	The licence check and the time of the last check, to ask whether one of your requests changed status.
Package list `iknowmymac.com/lists/` which redirects to deepaks612.github.io, the host that stores the file Automatic	Every hour while “Check for a newer list every hour” is on (it is by default), and when you press Check now. An unchanged list costs one “not modified” reply. Settings then Package Watch then Check for a newer list every hour	A plain download of the list of known-bad package versions and its signature: the same two files for every user. The request names no package, version, project or path and says nothing about your Mac or what is installed on it; at most it repeats the tag the server gave for the copy you already have. The list is matched against your packages on your Mac.
Public database's package list `osv-vulnerabilities.storage.googleapis.com` Automatic	Only when the list from iknowmymac.com could not be fetched or verified for a day. Then at most once a day, and never on a connection macOS marks as metered or Low Data.	A plain download of the public OSV database's npm and PyPI exports, about 254 MB the first time: the same files anyone can download. The request names no package and says nothing about your Mac. The list is built from them, and matched, on your Mac.
Runtime list `iknowmymac.com/lists/runtimes-v1.json` which redirects to deepaks612.github.io, like the package list Automatic	Only while the runtimes check is on (it is by default), with the package list's hourly check and when you press Check now. An unchanged list costs one “not modified” reply. Settings then Package Watch then Check Node.js, PHP, Go and Java versions and certificate bundles	A small signed file of Node.js, PHP, Go and Java security releases and certificate incidents, and its signature: the same two files for every user. Nothing about your runtimes, projects or paths is sent; at most the request repeats the tag the server gave for the copy you already have. The matching happens on your Mac.
Traffic name look-ups the DNS server your Mac uses Off by default	Only while Traffic is recording with “Look up names for addresses” on. Traffic is off until you turn it on. Never for this Mac or your local network. Settings then Traffic then Look up names for addresses	For an address your Mac already contacted, it asks that server for the address's name. That server learns which addresses were asked about. What Traffic records about your connections is never sent anywhere.
Blocklist updates `raw.githubusercontent.com`, `easylist.to` or the address of a list you added Off by default	Only for the blocklists you subscribe to, including the two that Turn on Blocking ticks (HaGeZi Threat Intelligence Feeds and EasyPrivacy) unless you untick them: each is downloaded once when you subscribe, then checked once a day, and when you press Update Now. Never on a metered or Low Data network. Settings then Traffic then Blocklists then Update subscribed lists daily	One request to each list's own address, asking only whether the list changed; an unchanged list costs a few hundred bytes. Nothing about your Mac or its traffic is sent: the lists are matched against your connections on your Mac.
Location databases `download.db-ip.com` Off by default	Only while Traffic is on. The country and network databases once a month, when a newer one may be out; the city database for Map once, when you first open Map (about 60 MB), then monthly. Each has its own switch, on by default. Settings then Traffic then Update location databases monthly	A plain download of DB-IP Lite's public files, the same for everyone; an unchanged file costs one “not modified” reply. No address your Mac contacted is sent: connections are located on your Mac.
DNS health checks the encrypted DNS resolvers you chose, such as Quad9 and Cloudflare Off by default	Only while Encrypted DNS is on in Traffic › DNS and the checks are on (they are by default): every 5 minutes and when the network changes.	One lookup of example.com to each resolver you chose, over DoH or DoT. Nothing about your own lookups is sent.
Inspect's local proxy `127.0.0.1` on this Mac only, for one project at a time On this Mac	Only while you inspect a project, for the tools in its inspected terminal or in a shell you set up with ikmm inspect env.	The proxy passes each request those tools make on to where it was going, and keeps what it saw on your Mac. Its certificate is made for that project and never added to your trust settings, so browsers and other apps never use it.
App Inspector Bonjour on your local network, then the apps that connect Off by default	Only while App Inspector is on. Off by default, and nothing listens while it is off. macOS may ask for Local Network permission when you turn it on. Settings then App Inspector	It announces this Mac on your local network so your apps that include the Pulse SDK can find it, receives the requests those apps report, and sends back the mock responses you turn on. Requests travel over your local network without encryption unless you set a passcode. Nothing goes through our servers or the internet, and what arrives stays on your Mac.
Crash reports Off by default	Only if you turn on Send crash reports. Off by default. Settings then Privacy then Send crash reports	The current app sends no crash reports, even with the switch on. Before that changes, we'll update this page to name the service and what a report contains, with personal information removed first.

License requests carry no cookies and only four headers: the content type, the accepted type, the language (“en”) and a user agent that says “iKnowMyMac”. Like any request on the internet, each one shows the receiving server your IP address. Dodo Payments handles license requests under its own privacy policy.

From version 1.6.0, the feedback requests above also carry one header with the language iKnowMyMac is shown in, such as de or pt-BR, so our emails to you can be in that language. Nothing else about your Mac's settings is sent.

Nothing about what you run

No request includes your app list, usage figures, history, diagnoses, file names, ports or projects. The app has no analytics or tracking code. The optional Git features above talk only to your own Git host and your repos' remotes, with your own keys and credentials. The package list is the same download for everyone: no request names a package, a version, a project or a path, and the list is matched against what is installed on your Mac, on your Mac. Credential files are checked for presence only and are never opened. So is the runtime list: no request names a runtime, a version, a certificate or a path, and the Node.js, PHP, Go and Java copies and certificate bundles on your Mac are found and matched on your Mac. Agent Undo makes no request at all: the copies it keeps of your files stay on your Mac. Traffic records what your Mac sends and receives on your Mac only; the one request it makes itself is the name look-up above, while that option is on. Inspect and App Inspector work on this Mac and your local network only, and only while you have them on. Traffic Control's three requests download public data or check the resolvers you chose: a blocklist update names no site you visited, the location databases are the same files for everyone, and a DNS health check asks only for example.com. Locations are looked up on your Mac, and Explain sends nothing.

The website

The website is hosted by Vercel. Like any web host, Vercel receives technical information with each request (your IP address, browser and device type, the page requested and the time) and keeps logs of it to run and protect the site. Vercel also tells our site which country a visit comes from, which we use only to decide whether to ask for analytics consent.

The homepage shows Product Hunt's launch badge, an image loaded from Product Hunt's servers so it can show the current vote count. Like any image host, Product Hunt receives your IP address, browser type and our site's address when your browser loads it, and your browser may send Product Hunt's own cookies with that request, depending on its settings. The badge runs no script on this site.

We don't use advertising or social media trackers: this site loads no ad platform's pixel or script. We don't sell personal data or share it with advertisers. We do advertise, and we count which ads lead to a sale ourselves, as described under Campaign tags.

Before iKnowMyDisplay comes out, the homepage has an “I'm waiting for it” button. Tapping it stores a one-way hash of your IP address for that day in our database hosted by Supabase, made with a key that stays on our server. It's used only to count each visitor once; the address itself isn't stored. We delete the hashes after iKnowMyDisplay's launch and keep only the number.

Email me the link and the waitlist

Visitors who aren't on a Mac see one of two small forms on the homepage. Apart from buying, they're the only places this site asks for an email address.

On your phone? Send yourself the link for your Mac. (on phones and tablets): we use your address to send one email with the link to this site, the pricing link and the current price, and we don't keep it: it isn't stored in our database or written to our logs. So that nobody can use the form to fill someone else's inbox, it sends at most three emails an hour to one address and ten from one network. To count them, we keep a one-way hash of the address and of your IP address, made with a key that stays on our server, only for the hour it counts; the next use of the form after that hour deletes it. Nobody can work out the address or the IP address from the hash. If you tick “Also tell me about updates”, we store the address so we can tell you about new versions, until you unsubscribe.
Windows or Linux? Join the waitlist (on Windows and Linux computers): we store your address and the platform you chose, and send one confirmation email. The number of signups helps us decide whether to make a Windows or Linux version. We email you only about that, and delete your address when you leave the waitlist or once we've told you what we decided.

For a stored address we keep the address, which list it's on, the platform for the waitlist, the date and a random token for its unsubscribe link, in our database hosted by Supabase. We don't store your IP address or browser details with it; your IP address is only held briefly in memory to stop abuse of the forms. The one exception is the link form's counter, described above.

These emails are sent by Resend, which keeps a delivery log of each email, including the recipient's address, for a limited time under its own privacy policy.

Every email we send from these forms has a link that deletes your address straight away. You can also write to support@iknowmymac.com and we'll delete it.

Analytics and cookies

We use Microsoft Clarity to understand which pages help people and where they get stuck. Clarity records how visitors use the site: pages viewed, clicks, scrolling and mouse movement, which it can replay as a session recording or heatmap, along with browser, device type and approximate location.

In the EEA, the UK and Switzerland, we ask first. Until you choose Allow, Clarity sets no cookies, so it can't recognise you from one page or visit to the next. Choosing Decline keeps it that way.
Elsewhere, Clarity runs with its cookies from your first visit. You can block them with your browser's cookie settings or a content blocker, and the site works the same.
Fields where you enter or see a license key or an email address are marked for masking, so Clarity doesn't record what they contain.
The home page's line about what this page can see of your Mac, and the “This page loaded in” figure, are worked out in your browser and masked too, so they aren't part of any recording.
We also send Clarity a few named events, such as opening the menu bar preview, finishing the demo or clicking Buy, with the button's location. Never what you type.

Cookies and similar storage this site uses:

Cookies and browser storage
Name	Set by	Purpose
`ikm_consent_region` (cookie, 30 days)	This site	Remembers whether your region needs an analytics consent choice. It stores “1” or “0”, nothing else.
`ikm_consent` (browser storage)	This site	Remembers your Allow or Decline choice. To change it, clear this site's data in your browser and the question appears again.
`ikm-menubar-hint-seen` (browser storage)	This site	Remembers that you've seen the “Click me” hint on the menu bar, so it shows only once.
`ikm-ikmd-waiting` (browser storage)	This site	Set only if you tap “I'm waiting for it”: remembers the tap and your place in line, so the button can say, for example, “You're #7 in line”. It stores “1” and that number, nothing else.
`ikm-buybar-closed` (browser storage, this tab only)	This site	Remembers that you closed the buy bar at the bottom of the page, until you close the tab.
`ikm-utm` (browser storage, this tab only)	This site	Set only if you arrived through a link with a campaign tag. Keeps the tag's three values until you close the tab. See Campaign tags.
`ikm.feedback.hash` (browser storage)	This site	Set only if you paste a licence key on the feedback board: the one-way hash of the key, so you stay recognised. Removed when you choose Change. See Feature requests and problem reports.
`sb-…-auth-token` (cookie)	This site	Set only if you sign in to the feedback board by email: keeps you signed in.
`ikm_ticket_…` (cookie, 1 year)	This site	Set only when you open the link to a support conversation: holds that conversation's key so its private page opens again. Scripts can't read it.
Clarity cookies (such as `_clck` and `_clsk`)	Microsoft Clarity	Link page views into a visit and recognise returning visitors. Set only as described above.

Microsoft processes Clarity data under the Microsoft Privacy Statement.

Campaign tags

Some links to this site, such as our ads on X, end with a campaign tag: utm_source, utm_medium and utm_campaign in the page address, for example utm_campaign=usb_cable_kw. A tag names the ad or link you followed. It doesn't identify you.

While you browse: if the address you arrive on has a tag, this site keeps those three values in your browser's storage for that tab, as ikm-utm. It isn't a cookie, and it's removed when you close the tab. The site doesn't send the stored tag anywhere unless you start a purchase.
If you start a purchase: the tag goes to our server with the checkout request and is attached to your order at Dodo Payments. After you pay, Dodo Payments includes it in the order details it sends us. That ties the sale to the ad or link, which is all we use it for.
What the ad platform gets: nothing from us. We don't send X or any other ad platform anything about you, your visit or your purchase.
No tag, nothing stored: if the address has no campaign tag, this site stores no tag and attaches none to an order.

The address you arrive on, tag included, is also part of the page request itself, so it appears in our host's logs and in Clarity's record of pages viewed, as described under The website and Analytics and cookies. The iKnowMyMac app is not part of any of this: it has no analytics and no telemetry, and it never sees a campaign tag.

Purchases and licenses

Dodo Payments is our Merchant of Record. When you buy iKnowMyMac, Dodo Payments sells you the license: their checkout collects your name, email address, billing country and payment details, handles tax, and emails your receipt and license key. We never see or store your full card details. Dodo Payments processes this under its own privacy policy, available at dodopayments.com.

After a purchase, Dodo Payments sends us the order details: order and payment identifiers, the product and number of Macs, the amount, the date and your email address. We store them in a database hosted by Supabase so we can count launch sales, confirm licenses, help you with support and handle refunds and chargebacks.

Now and then, when there's something worth knowing, such as a new app from us, we email customers about it. Every one of these news emails has a link to stop them, and one click is enough. We keep only a one-way hash of the addresses that unsubscribed and of the addresses each email went to, so that nobody gets the same email twice.

If your visit carried a campaign tag, Dodo Payments keeps it with the payment and includes it in those order details. We note it in our server log next to the payment identifier. We don't add it to the order database.

When you use Get your download link, your key is sent to our server and checked with Dodo Payments so we can show the download. If you make a claim through the post-for-refund program, we store your email address, order details, the link to your post and our review notes in the same database.

Support email

When you write to support@iknowmymac.com, we keep your message and our replies so we can help you and refer back to earlier conversations. We use what you send only to answer you.

Feature requests and problem reports

The feedback board is where people ask for features and vote on them. There are no accounts. Nothing is sent until you press a button that says so.

Who you are to it

A licence key: the key is turned into a one-way hash on your own device (in the app, or in your browser when you paste it on the website) and only that hash is sent. We compare it with a hash we keep for each purchase to show a Buyer badge. The key itself never reaches the feedback system. On the website, your browser remembers the hash in its local storage until you choose Change.
An email address, if you have no key: we send a one-time sign-in code through Supabase, which keeps the address as a sign-in record and sets a sign-in cookie in your browser.
An email address you type into a request, a report or “Get updates” is stored with your identity and used only to reply to you and to tell you when your requests change. It is never shown publicly.
The support form on the help centre needs no key and no sign-in: the email address you type is who you are to that conversation, and we keep it for as long as the conversation exists.

What is public and what is not

Public: a request's title and details, comments, vote counts, its status, and beside each post either a Buyer badge or nothing, with an anonymous tag such as “User 3fa9”. Don't put personal details in a title, details or a comment.
Only we see: screenshots, files, diagnostics, the name of the app screen a request came from, the app version, your email address and your licence hash. Problem reports and messages from the support form are private from start to finish: only you and Deepak can read them.
You can take a request of yours off the board (Make private): you and Deepak still see it, nobody else does.
A new post may wait for review before it appears, for example when it contains a link. Anyone signed in can report a post.

What the app sends

From version 1.3.5, the app can send feature requests and problem reports. Each one goes to iknowmymac.com only when you press Send, after a preview of exactly what will leave your Mac.

A request, vote, comment or report: the text you wrote, the name of the screen you were on, a screenshot of the iKnowMyMac window if you attached one, your licence hash, the app version, and your email address if you typed it.
Diagnostics, only if you tick the box and after you've seen and edited them: the app version, your macOS version, your Mac's model and memory, and the last 200 lines of the app's own log, with paths in your home folder shortened to ~.
Similar requests and help articles: while a request or report sheet is open, the words you have typed so far are sent to find matching requests and help articles. Nothing else is sent, and nothing after the sheet closes.
My requests: when you open it, the app fetches your own requests, reports and replies using your licence hash.
One check a day for status changes on requests you created or voted on. You can turn it off in Settings → Feedback.
Your app language: from version 1.6.0, each of these also carries the language iKnowMyMac is shown in, such as de or pt-BR. We keep it with your identity so that emails to you are in that language. Nothing else about your Mac's settings is sent.

Never sent: your search queries, file names or paths from the search index, the index itself, process lists, the USB log or anything from Pulse.

The support form

We store what you write (what went wrong, what you expected), your email address and, if you attach one, a file: a PNG or JPEG image or a text log, up to 10 MB. Images have their metadata (such as EXIF) removed. Files are kept in private storage; only you and Deepak can download them, through this site.
We email you a private link to the conversation. Opening it sets one cookie in your browser, ikm_ticket_…, which holds that conversation's key for a year so the page opens again. Scripts can't read it, and it is used for nothing else. Anyone who has the link can open the conversation, so keep it to yourself.

Emails we send

The link to a support conversation you started, and Deepak's replies in it.
Updates on requests you created, voted on or followed, if we have an address for you: when one becomes Planned, In progress or Shipped, and when Deepak replies on it. Everything waiting for you goes into one email, and we send at most one of these a day.
They are plain emails: no tracking pixels, and every link goes straight to iknowmymac.com. They are sent by Resend, which keeps a delivery log of each email, including the address.
Every email has links that stop the emails about that request or conversation, or all of them, with one click and no sign-in. To keep that promise we store a one-way hash of the address, not the address. We also keep a log of what was sent to which hash, for 90 days; it is what limits update emails to one a day.
Once a week Deepak gets a summary in his own inbox: new requests, vote counts, and the first line of problem reports that have waited more than two working days.

See, download or delete your data

Your feedback shows what is stored for the licence key or email sign-in you use, and lets you:

download all of it as one file (JSON), including the diagnostics you sent;
delete a request. If other people voted or commented on it, it stays on the board as “Deleted request” with their votes and comments, and your title, details, screenshot and authorship are removed;
make a request private, stop the emails, or remove a vote;
delete everything: your identity, your email address, your requests, comments and votes, and your problem reports with their files. If you signed in by email, the sign-in record at Supabase is deleted too.

A message sent from the support form belongs to the address you typed. You can delete it from the conversation's own page, or sign in to Your feedback with that address by email to see and delete all of them.

Abuse protection

To limit abuse (5 requests and 60 votes a day per person, for example) we count actions per identity, and per IP address using a shortened hash of the address that is deleted within two days. Your IP address is not stored with your requests.
Posting from the website runs Cloudflare Turnstile, a check that you are a person. Cloudflare receives your IP address and browser signals for that check, under its own privacy policy.
The support form runs the same check, and counts messages per email address.
Screenshots have their metadata (such as EXIF) removed before they are stored.

How long we keep it

Requests, comments and votes stay until you or we delete them.
Problem reports and support conversations, with their messages, diagnostics, screenshots and files, are deleted two years after the last message. A check runs every day.
The address typed into the support form is deleted with the last conversation that used it.
An unsubscribe (the hash of your address) stays until you turn emails back on or delete everything.
For anything you can't do yourself, such as deleting a single comment, write to support@iknowmymac.com.

This data is stored in our database and private file storage hosted by Supabase.

Service providers

We share personal data only with the providers that run parts of the service for us:

Service providers
Provider	What they do
Dodo Payments	Merchant of Record: checkout, payments, tax, receipts, license keys and license checks.
Vercel	Hosts the website, the downloads and the update feed.
Supabase	Hosts the database of orders, post-for-refund claims and email signups, and of feature requests and problem reports with their private files; sends the sign-in code for the feedback board.
Resend	Sends the emails from the “Email me the link” and waitlist forms, and the feedback emails: links to support conversations, replies and status updates.
Microsoft Clarity	Website analytics, as described above.
Cloudflare	Turnstile, the check that a person is posting on the feedback board.

These providers may process data outside your country. We may also disclose information when the law requires it.

How long we keep data

Data the app stores stays on your Mac and is yours to delete; history older than 30 days is deleted automatically.
We keep order records for as long as your license exists and as long as tax and accounting rules require.
We keep post-for-refund claims and support emails for as long as we need them to help you and handle follow-ups.
Hosting logs and Clarity data are kept for the periods set by Vercel and Microsoft.
A campaign tag stays in your browser until you close the tab. Attached to an order, it's kept with the payment at Dodo Payments and in our server logs for the period Vercel sets.
The hashes behind the “I'm waiting for it” count are deleted after iKnowMyDisplay's launch; only the number is kept.

Your rights

You can ask us for a copy of the personal data we hold about you, to correct it, to delete it, or to stop using it. Write to support@iknowmymac.com from the email address you used with us, and we'll reply within 30 days.

If we delete your order record, we can no longer help with that license, and Dodo Payments keeps its own records of the sale as the law requires. Data the app keeps on your Mac never reaches us, so you delete it yourself (see the uninstall guide).

Where the law asks us to name a legal basis: we process order data to provide what you bought (our contract with you), analytics in consent regions only with your consent, hosting logs in our legitimate interest in keeping the site running and free of abuse, and campaign tags in our legitimate interest in knowing which ads lead to a sale. If you're unhappy with how we handle your data, you can also complain to your local data protection authority.