CodeFootprint Privacy Policy
输入“/”快速插入内容
CodeFootprint Privacy Policy
CodeFootprint Privacy Policy
用户7268用户72685月11日修改
CodeFootprint Privacy Policy
Effective: May 11, 2026
No Data Collected
CodeFootprint does not collect, transmit, or share personal data with servers or third parties. All project data generated by the app remains on your device unless you export it or open an external link yourself.
1.
Overview
CodeFootprint ("the App") is a native macOS application that monitors file changes in user-selected source code directories and generates a local, persistent history of those changes. The App operates entirely on-device, requires no user account, and does not upload project data or personal data to any server or third party.
2.
Data Collection
CodeFootprint does not collect data from users for transmission, profiling, analytics, advertising, tracking, or sale. It does not require an account and does not collect personal information, device identifiers, location data, browsing history, usage analytics, crash data, payment information, contact information, credentials, media, health data, or other sensitive information for off-device processing.
The App does not send project data, source code, diffs, hashes, metadata, or user content to servers, third-party services, analytics platforms, advertising networks, or any other remote endpoint operated by us or by third parties.
3.
Local Data Storage
While the App does not collect data externally, it does generate and store data locally on your Mac for its core functionality. This local storage is part of the product’s behavior and is not transmitted off-device by the App.
Data Type: Unified Diff Records
Description: Textual differences between file versions, stored in standard unified diff format
Purpose: Core feature — enables browsing and reviewing code changes
Data Type: Local Content Snapshots
Description: In some records, local file content snapshots needed to preserve created/deleted traces or to reconstruct and display certain modified records
Purpose: History integrity — preserves readable trace history when diffs alone are insufficient
Data Type: SHA-256 File Hashes
Description: Cryptographic hashes of monitored file contents
Purpose: Change detection — determines whether a file has been modified
Data Type: File Metadata
Description: File paths, modification timestamps, and change status (added / modified / deleted)
Purpose: Change tracking — organizes and presents file change history chronologically
Data Type: Project Configuration
Description: Monitored directory paths, optional custom storage path, and Security-Scoped Bookmarks
Purpose: App configuration — remembers which projects to monitor across sessions
Data Type: Local Notification Content
Description: Optional local notification titles and bodies generated for events such as monitoring start or file deletion
Purpose: User alerts — delivers optional on-device notifications when you allow them
Key privacy design decisions:
•
All App-generated data is stored locally using SQLite databases located within each monitored project’s .codetrace/ directory, or in the user’s designated storage location.
•
The App may store local file content snapshots for created and deleted records, and for certain modified records when needed to preserve readable and reconstructable history. These snapshots stay on your device unless you export them yourself.
•
The App accesses only directories and storage locations that you explicitly choose. It uses macOS Security-Scoped Bookmarks to restore access to those same user-selected locations across launches.