PixelSpy Privacy Policy
Last Updated: July 18, 2026
This Privacy Policy explains how PixelSpy handles information when you use the PixelSpy macOS application. This Policy applies to PixelSpy with the bundle identifier com.zeroordinal.pixelspy, published by the developer identified on the Apple App Store product page. In this Policy, "PixelSpy," "we," "us," and "our" refer to the application and its developer.
PixelSpy is designed to keep its color picking and color management features local on your Mac. The App does not require an account and does not operate a cloud service for your colors, projects, or notes. PixelSpy does use Firebase Crashlytics to receive crash and diagnostic reports, as described below.
1. Information Processed Locally
PixelSpy processes screen pixels locally to display the magnifier and determine the color selected by you. Screen images, screen recordings, window contents, documents, and sampled pixels are not uploaded by PixelSpy.
PixelSpy stores the following information locally on your Mac as needed to provide its features:
Color history and color values.
Color names, token names, semantic roles, tags, favorites, and project assignments.
Project names and other color organization data.
Notes that you manually add to color records.
Color format, language, hotkey, launch-at-login, window, and other App preferences.
PixelSpy does not automatically determine or save the application, image, document, website, or other source from which a color was selected. You may add a source note manually.
PixelSpy does not provide cloud synchronization or a backend service for this local content. Local content remains on your Mac unless you choose to export or otherwise share it.
2. Screen Recording Permission
PixelSpy requires the macOS Screen Recording permission to read the color of a pixel selected on the screen. Depending on the macOS version, System Settings may describe this permission as access to screen and system audio.
PixelSpy uses this permission only to inspect screen pixels locally. PixelSpy does not record video, record audio, listen to system audio, or transmit screen content to us, Google, or any other third party.
You can revoke this permission at any time in System Settings under Privacy & Security and Screen & System Audio Recording. Revoking the permission prevents PixelSpy from picking colors from the screen until permission is granted again.
3. Clipboard
PixelSpy writes a color value to the macOS clipboard only when you choose to copy a color or related value. PixelSpy does not read, collect, store, or upload your clipboard history.
4. Import and Export
When you import or export a PixelSpy archive or project file, PixelSpy reads or writes only the local file that you explicitly select through the macOS file picker. Imported and exported files are not automatically uploaded.
An exported file may contain the colors, projects, names, tokens, tags, roles, favorites, and notes that you choose to include. You are responsible for deciding where to save or share exported files.
5. Crash Reports and Diagnostics
PixelSpy uses Firebase Crashlytics, a service provided by Google LLC, to identify crashes and improve reliability. Crash reporting is enabled by default.
When a crash occurs, Crashlytics may automatically receive and process:
Crash stack traces and relevant application state.
The crash timestamp and session identifier.
The PixelSpy bundle identifier, version, and build number.
The macOS version.
Device model, CPU architecture, memory, disk space, and related device or operating system information.
Crashlytics installation identifiers and Firebase installation identifiers.
Exception or signal information.
Limited diagnostic logs and custom keys related to App stability, such as the PixelSpy version, build number, bundle identifier, macOS version, or a failed hotkey registration status.
Network and service metadata necessary to transmit and operate the diagnostic service, which may include an IP address and Firebase SDK performance metadata.
PixelSpy does not set a Crashlytics user ID. We do not intentionally attach picked colors, color history, notes, project data, screen images, screen recordings, clipboard contents, imported or exported file contents, your name, or your email address to Crashlytics reports.
Crashlytics information is used only to investigate crashes, measure the impact of stability issues, maintain the diagnostic service, and improve PixelSpy. It is not used by PixelSpy for advertising or cross-app tracking.
Google states that Firebase Crashlytics retains crash stack traces and associated identifiers, including Crashlytics installation UUIDs and Firebase installation IDs, for 90 days before beginning removal from live and backup systems. More information is available at:
https://firebase.google.com/support/privacy
6. Information We Do Not Collect for PixelSpy Features
Except for the diagnostic information described above and information you voluntarily send when contacting us, PixelSpy does not collect or upload personal information for its color picking and color management features.
PixelSpy does not:
Require or provide a user account.
Collect your name, phone number, address, contacts, or account credentials.
Upload your screen content, color history, projects, notes, or local files.
Collect analytics about how you use individual PixelSpy features.
Use advertising SDKs.
Sell personal information.
Use personal information for targeted advertising or cross-app tracking.
7. Payments and the Apple App Store
PixelSpy is distributed as a paid application through the Apple App Store. Apple handles purchases, receipts, refunds, taxes, App Store account information, and payment details. We do not receive or store your payment card information.
Apple processes App Store information under its own privacy policy:
https://www.apple.com/legal/privacy/
8. Contacting Us
If you contact us by email, we receive your email address and any information that you choose to include in your message. We use this information only to respond to your request, provide support, protect the App and its users, or comply with legal obligations.
Support correspondence is retained only as long as reasonably necessary to handle the request, maintain appropriate support records, resolve disputes, or comply with applicable law. You may request deletion of support correspondence by using the contact address at the end of this Policy.
9. Third-Party Processing
The third parties relevant to PixelSpy are:
Google LLC, through Firebase Crashlytics, for crash reporting and diagnostic processing.
Apple, through the Apple App Store and macOS, for distribution, payments, updates, system permissions, and related platform services.
Your email provider and our email provider when you contact us.
These providers process information under their own terms and privacy policies. Where they process information on our behalf, we require them to use it only for the purposes described in this Policy and to provide privacy and security protections consistent with applicable law.
PixelSpy does not allow third parties to use your local color history, screen content, notes, or project data for their own advertising purposes.
10. Data Retention and Deletion
Local PixelSpy data remains on your Mac until you delete it, replace it through an import operation, clear it using PixelSpy, or remove the relevant App support or container data from macOS.
Deleting the App may not automatically delete every local preference or support file retained by macOS. You can clear color records from PixelSpy before uninstalling or remove PixelSpy support and container data using macOS.
Firebase Crashlytics retention is described in Section 5. Because PixelSpy does not create user accounts or set a Crashlytics user ID, we may not be able to associate a particular Crashlytics report with you. You may still contact us with a deletion or privacy request, and we will take reasonable steps based on the information available to us and the tools provided by Google.
Stopping use of or uninstalling PixelSpy prevents the App from generating and sending future crash reports. Screen Recording permission can be withdrawn separately through System Settings.
11. Legal Bases and Privacy Rights
Where applicable law requires a legal basis for processing, diagnostic information is processed for our legitimate interests in maintaining the security, reliability, and quality of PixelSpy, or on another lawful basis available under applicable law. Information that you send to us is processed to respond to your request and provide support.
Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal information, or to withdraw consent where processing is based on consent. You may also have the right to complain to your local data protection authority.
Because PixelSpy has no user accounts and does not assign a Crashlytics user ID, we may need additional information to determine whether we can identify data related to your request. We will not ask for more information than reasonably necessary.
12. International Data Transfers
Google and Apple may process information in countries other than the country where you live. Their privacy notices and data processing terms describe the safeguards they use for international data transfers. Firebase privacy and data processing information is available at:
https://firebase.google.com/support/privacy
https://firebase.google.com/terms/data-processing-terms
13. Data Security
PixelSpy minimizes data transmission by keeping screen sampling, color history, projects, and notes on your Mac. We use established platform and third-party services for the limited processing described in this Policy.
No storage or transmission method can be guaranteed to be completely secure. We take reasonable measures appropriate to the nature of the information and the limited purposes for which it is processed.
14. Children's Privacy
PixelSpy is a professional utility and is not directed to children under 13 or the equivalent minimum age in the applicable jurisdiction. We do not knowingly collect personal information from children. If you believe that a child has provided personal information to us, please contact us.
15. Changes to This Policy
We may update this Privacy Policy when PixelSpy features, third-party services, legal requirements, or data practices change. The revised Policy will be posted on the same public page with an updated date. Material changes will apply from the date stated in the revised Policy.
16. Contact Us
For privacy questions or requests, contact:
zeroordinal@gmail.com