Scope
This notice covers the QuietWatch 1.0.0 app and this website’s QuietWatch product pages. The developer is JINGREN CHEN; contact mlaohu.app@gmail.com. Other products and your chosen AI services have their own data practices.
Process monitoring and rule evaluation happen on your Mac. The app has no developer telemetry, ads, tracking identifiers, cloud sync or automatic log uploads. It contacts your chosen AI service only after you preview and approve an analysis request.
Information read on your Mac
QuietWatch reads accessible processes owned by your current user, including process names, executable paths, launch commands, PIDs, start times, user ownership, CPU time and resident memory. This helps show task origins, identify sustained usage and verify the target of a manual action. macOS may limit access to some information. Full samples and launch commands are used during the current app session; they are not retained as a complete process log.
This information may appear in the local interface. Expanded launch commands can contain paths or sensitive arguments, so review them before taking screenshots or sharing your screen.
Information stored locally
- Event history: a fixed task category, necessary PID, status, timestamps and action results. Up to 500 entries are retained for up to 30 days. Raw commands, file paths, API keys and AI responses are excluded.
- Preferences and muting: monitoring rules, pause state, appearance, onboarding state, and AI address and model are stored in local preferences. Mute settings also retain the PID, process start time and expiry to restore the mute and avoid confusing a reused PID with the original task. Muting lasts at most one hour.
- API keys: stored separately in the macOS Keychain for each service address, with Keychain synchronization disabled and access limited to this device after unlock. Keys are not written to preferences, events, exports or error messages.
Event files are stored in the current user’s Application Support directory and protected by that user’s file permissions. File permissions are not disk encryption. macOS FileVault can provide encryption at rest.
Optional AI and third parties
Before every AI request, QuietWatch displays the destination and the exact summary. The summary contains only a fixed task category, resource readings such as CPU and memory, and runtime and observation durations, together with fixed analysis instructions. It excludes raw launch commands, paths, PIDs, usernames, source code, logs, system boot time and device uptime.
If configured, your API key is sent as authentication to the corresponding service. The provider may associate the request with your service account and sees ordinary connection information, such as your source IP. Its policies govern retention, use and potential training use. QuietWatch cannot guarantee deletion or exclusion from training on its behalf. The request’s store: false setting also depends on server support.
Remote services require HTTPS; local loopback addresses may use HTTP. The app does not follow redirects, preventing authentication from being forwarded to a new address. AI responses cannot execute commands or stop processes automatically. The app includes a macOS privacy manifest declaring no tracking and conservatively treating optional AI performance summaries as potentially linked to a user.
Your controls and deletion
You can use local features without configuring AI, cancel an unsent analysis, remove the current service’s key, clear history, and disable notifications or launch at login. Canceling a sent request cannot recall information already received by the service.
An exported event JSON file contains all retained events, including necessary PIDs, and is saved only to the location you choose. You decide whether to share it. The app does not upload it automatically.
Deleting the app does not automatically remove local preferences, events or Keychain entries. Before uninstalling, clear history, remove keys and disable launch at login in the app. To remove keys for previously configured services, search for app.quietwatch.ai-key in Keychain Access and delete the relevant entries.
Website visits and email
These QuietWatch pages do not integrate visitor analytics or advertising tracking scripts. Visiting a page or downloading an installer still sends requests to hosting and network services. That infrastructure may log IP addresses, access times, requested URLs, browser information and response status to deliver content, troubleshoot issues and protect the service. The app does not upload process information to this website.
The scope and retention of infrastructure logs depend on the relevant service’s configuration and policies. This notice does not promise an unverified provider retention period. The app’s local-data practices do not mean website visits leave no network logs.
If you email us, we receive your email address, message and any attachments you choose to send, and use them to respond and handle your request. Email services such as Gmail transmit and store those messages under their own policies. Please do not send API keys, private keys or full process commands. Your app version, macOS version and reproduction steps are usually enough to begin troubleshooting.
To ask about this notice or request deletion of information you sent by email, contact mlaohu.app@gmail.com. We will review the request and address data within our control. We cannot recall information already received by your AI or email provider on your behalf.