Privacy

ClockGuard collects nothing.

Not a diluted version of nothing — no analytics, no accounts, no crash reporting, no identifiers, no network calls at all. This page exists to say exactly that, and to be specific about the little ClockGuard does keep, which never leaves your Mac.

Last updated: 2 August 2026 · applies to ClockGuard 1.0 for macOS

No data is collected

ClockGuard gathers no personal data, no usage data and no diagnostics. There is no analytics SDK, no advertising SDK and no third-party code of any kind inside the app. Nothing is linked to you, and nothing is used to track you across apps or websites.

No network use

The app makes no network requests. It has no server, no account system and no update channel of its own — updates arrive through the Mac App Store like any other app. Because nothing is sent anywhere, there is nothing for anyone to intercept, store or subpoena.

No access to your audio, ever

ClockGuard never captures audio and never asks for microphone permission. Through CoreAudio it only reads and sets device properties — chiefly the nominal sample rate — and observes which processes are doing audio input or output, so it can name the app that likely changed a rate. It cannot hear anything, because it never opens an audio stream.

The app is sandboxed, and the only entitlement it requests is the App Sandbox itself.

What is stored, and where

Three things, all written only to ClockGuard's own sandbox container on your Mac:

  • Device profiles — for each interface you watch: its CoreAudio unique identifier, the target sample rate and the mode you chose.
  • Your allowlist — the name and bundle identifier of each app you allowed to change the rate.
  • The Event Log — the most recent 300 events: when a rate changed, on which device, the likely writer, and what ClockGuard did.

They live in ~/Library/Containers/br.com.maurolopes.ClockGuard/. Deleting the app deletes them. You can also empty the log yourself at any time with Clear Log in the Event Log window.

About this website

Separate from the app, and stated here so the two are not confused: wptrat.com measures its own traffic with Matomo, running on a server the maker owns rather than a third-party analytics service. It records ordinary page-visit information. No advertising networks, no cross-site trackers, and nothing that connects a visit here to anything you do inside ClockGuard — the app cannot reach the network, so it has nothing to report.

Questions, or a correction

If anything on this page turns out not to match what the app does, that is a bug in the app or in this page, and I want to know. Write to me through the contact page.

ClockGuard is made by WPTRAT — Mauro Lopes, Rio de Janeiro, Brazil.