MacClue is designed to keep system monitoring on your Mac. We distinguish between local measurements, information necessary for website accounts, and support data you deliberately choose to submit.
1. Scope and who handles your data
This notice covers the MacClue macOS application, macclue.com website and optional support and license services. The publisher is the operator of MacClue. The contracting legal entity and dedicated privacy contact will be identified before commercial checkout is enabled.
The app and website have different data flows. Installing the app does not, by itself, create a website account or consent to upload system measurements.
2. Monitoring that stays on your Mac
MacClue reads CPU, GPU, memory, disk, network, processes, app inventory, service metadata and available hardware sensors to show performance. Some readings are estimated or unavailable depending on hardware and macOS.
The collector runs locally. MacClue does not automatically send process commands, user names, installed-app inventories, network addresses, folder names, file contents or historical performance data to its website. Folder scans inspect metadata and do not read document content.
3. Local storage, recording and deletion
Optional historical samples are stored in a local SQLite database with up to seven days of retained history. Temporary hardware information and interface preferences are stored in application-owned cache and settings. Exact paths are described in the in-app privacy disclosure.
Background recording is disabled by default. If you enable it, a user-level scheduled job records limited measurements on a best-effort basis; you can stop it. Removing the app does not silently remove history or your separately exported files. Follow the documented, confirmed removal steps if you want to erase app-owned local data.
4. Account, sign-in and website data
If you create an account, we process your email address, name, login session, authentication records and security-related request metadata. Email/password credentials are stored as password hashes, not readable passwords. If Google sign-in is enabled, Google authenticates you and provides basic account profile information; MacClue does not receive your Google password.
The website may use essential session cookies, abuse controls and ordinary hosting logs. Download counts are recorded to operate the release service. No advertising tracking SDK is intentionally integrated into the Mac monitoring collector.
5. Payments, licenses and receipts
If and when PayPal purchases are enabled, the payment flow is hosted by PayPal under its own privacy practices. We receive order identifiers, transaction status, amount, currency and the limited buyer/order identifiers required to issue and administer a Pro license. We do not store full card numbers.
License activation may send the entered license key and a randomly generated installation alias to our activation server over HTTPS. The app can retain a cryptographically signed entitlement for offline checking. Paid checkout is unavailable until the merchant and activation flows are independently verified.
Following verified payment, the licence may be emailed to the purchasing account through our configured delivery service. Email is not end-to-end encrypted, so keep this message private. Authenticated account recovery remains available even if sending fails. No licence is emailed to an unauthenticated, user-supplied recipient.
6. Diagnostic reports and customer support
The app stores a small local history of approved error categories and timestamps. When you open its diagnostic screen, it may summarize recent native macOS crash reports for MacClue, such as the exception, termination reason, faulting thread and bounded, path-free frame identifiers. This is not a wholesale upload of Apple crash logs.
Reports are generated and reviewed on-device. Copying or saving is your choice. A support ticket only receives the text and optional validated diagnostic report after you sign in and explicitly consent. Support staff with assigned permissions may access the ticket. Avoid adding personal information to free-text descriptions.
7. Providers, security and international processing
Website infrastructure currently uses Cloudflare for hosting and storage. If enabled, Google handles sign-in, PayPal handles payment and the configured email provider handles transactional messages. Each provider may process data under its own terms and in different jurisdictions.
We use HTTPS where network services are enabled, limit release access by publication status, and restrict administrative support access by role. No service can promise perfect security. Early unsigned beta downloads are not Apple-notarized; verify the file hash and follow official macOS security guidance.
8. Retention and legal obligations
The app retains local history for up to seven days while recording. Support tickets, account data, downloads, authentication records and transaction records follow operational needs, applicable law and provider retention requirements; they do not necessarily share the app-history period.
We will document specific retention periods and an operator contact before paid launch. Legally required financial records may be retained after account closure; other account-linked information should be deleted or de-identified when appropriate.
9. Your choices and privacy requests
You can avoid creating a website account for local monitoring, disable background recording, review diagnostic exports and decide whether to submit support reports. Your browser controls cookies, and you can remove app-owned local files using the documented procedure.
Depending on your location, you may have rights to request access, correction, deletion, portability or restriction of personal data. Use the authenticated support form to submit a privacy request. We may need to verify your identity and retain limited records required by law.
10. Children, changes and contact
MacClue is a general-purpose Mac utility, not a product intentionally directed at children. We may update this notice when the software, service providers or legal obligations change. Material changes will be identified on the website with an updated revision date.
For an account or privacy question, open the Support page and create a private ticket. Before the first paid checkout, we will additionally disclose the legal seller and a durable contact address.
11. Crash information and diagnostic transparency
Apple crash reports can contain thread register values, memory mappings, application paths, machine-specific identifiers and full stacks. MacClue does not copy such raw reports into support tickets. The optional report limits frame evidence to an image name, build UUID and offset, plus a bounded crash reason and app/environment version. This is enough to match private debug symbols in many cases but may not explain every problem.
Any extra evidence, such as your own screenshot or a raw Apple crash report, should be shared only if you decide it is necessary and have reviewed or redacted personal details. We do not request your password, private keys or complete file list for routine troubleshooting.
12. Publishing screenshots responsibly
Marketing images are captured from the actual Mac application, not invented metrics. Before publishing, we review them for visible user names, device names, serial numbers, private paths, network endpoints and activation details and remove such details where present. Displayed performance values are observations from a single session, not a benchmark or a promise for other Macs.