Privacy Policy

The short version

MacDotes collects nothing. It has no analytics, no telemetry, no crash reporting, no accounts, no advertising, and no network code of any kind. Nothing you do in MacDotes is sent anywhere, because MacDotes cannot send anything anywhere.

Everything it stores stays on your Mac, inside the app’s own sandbox container, and is deleted when you delete the app.

How that claim was checked

This is not a promise, it is a property of the shipped binary. Anyone can re-run these checks on the copy they installed:

• No network frameworks are linked. otool -L on the binary lists Foundation, AppKit, Carbon, Combine, CoreFoundation, ServiceManagement, SwiftUI and the Swift runtime — no CFNetwork, no Network.framework, no Security.framework.
• No networking symbols are imported. nm -u filtered for URLSession, socket, getaddrinfo, nw_ or CFStream returns zero matches.
• No server addresses are compiled in. strings filtered for http:// or https:// returns zero.
• No analytics SDK is bundled. The app has no Frameworks directory at all — it bundles no third-party code.

MacDotes also declares no networking entitlement. Its entitlements file contains exactly one key, com.apple.security.app-sandbox. Under the App Sandbox an app without com.apple.security.network.client cannot open an outbound connection even if it tried, and that restriction is enforced by macOS, not by us.

What MacDotes stores on your Mac

Two things, both local, both inside the sandbox container at ~/Library/Containers/com.agentgelabs.MacDotes/.

1. Your settings. Whether MacDotes is switched on; which modifier mapping to apply while the game is in front and which to go back to; the detection rules — the app names, bundle identifiers or executable paths it treats as “the game”; the polling interval; and a pending “restore owed” marker, written before MacDotes changes anything so that a crash can be undone on the next launch. No name, no email address, no device identifier, no licence key. MacDotes never asks you for any of those and has nowhere to put them.

2. A local diagnostic log, shown live in the app’s Log tab. It records what the app did and why: when the game started or stopped, when it came to or lost the front, which mapping was applied or restored, and every refusal with its reason.

Please read this part carefully, because it is the one place MacDotes touches information about you. To decide whether the frontmost application is your game, MacDotes reads that application’s name, bundle identifier, process id and executable path from macOS, and it writes those to the log. So the log contains a record of the applications you switched between while MacDotes was running. That log never leaves your Mac, is not transmitted or uploaded, is capped in size, and is deleted with the app. If you would rather not keep it, quit MacDotes and delete the file — nothing depends on it being present.

What MacDotes does not have access to

• It does not read your keystrokes. MacDotes is not a keylogger and contains no event tap. It changes the mapping between two modifier keys through the system’s HID service and never sees, receives or records a single key you press. It requires no Accessibility or Input Monitoring permission, and macOS never prompts you for one — which is itself the proof: macOS requires that permission for any app that can observe keystrokes.
• It does not read your files. The sandbox confines it to its own container. It never opens a file picker and never asks for access to your documents.
• It does not use the camera, the microphone, your location, your contacts or your calendar. None of those frameworks are linked and none of the corresponding usage descriptions appear in its Info.plist, without which macOS would refuse the request.

Third parties

There are none. MacDotes uses no third-party SDK, no analytics provider, no crash reporter and no advertising network. No data is shared with anyone, because none is collected.

Apple may collect its own information about your purchase and about app crashes, under Apple’s privacy policy. That is between you and Apple; MacDotes receives nothing from it. If you opt in to sharing crash reports with developers, Apple may show us anonymised, aggregated crash traces — these contain no personal information and we cannot tie them to you.

Children

MacDotes is not directed at children and collects no data from anyone, of any age.

Deleting your data

Delete the app. Its container goes with it. If you want to remove the data but keep the app, quit MacDotes and delete ~/Library/Containers/com.agentgelabs.MacDotes/. It will start again from its built-in defaults.

Changes to this policy

If a future version of MacDotes ever collects anything, this page will say so before that version ships, and the App Store privacy label will change to match. A version that collects nothing will keep saying exactly that.

Contact

Questions about this policy: aaronaludo@gmail.com.