Privacy Policy

Tasify is designed from the ground up to respect your privacy. It runs entirely on your local machine, communicates with no external servers, and collects no data whatsoever. This policy explains how your data is collected, handled, stored, and shared — or in Tasify's case, why none of those happen. Each section is documented below for full transparency.

Data Collection

The developer has disclosed that it will not collect or use your data. Tasify does not collect any personal information, technical metadata, usage statistics, crash reports, or behavioral data. The extension never asks for your name, email, location, or any account credentials because there is no server to send them to.

The @tasify/host process receives Claude Code hook events — such as task start, tool execution, permission request, and error events — solely over a local inter-process communication channel. These events are ephemeral and are not persisted, recorded, or transmitted beyond your local machine. No analytics SDKs, telemetry libraries, or third-party data-collection code are included in any component of Tasify.

Data Handling

Tasify processes hook event data exclusively for one purpose: displaying real-time session status in the extension popup and triggering optional desktop notifications. The handling logic follows strict rules:

• In-memory only: Event data is held in the extension's runtime memory solely for the duration needed to render the user interface. Once an event is displayed and the popup is closed, the in-memory state is naturally released.
• No transformation or enrichment: Hook events are presented as received. No data is enriched, analyzed, profiled, or combined with other sources.
• No logging to disk: The extension does not write event data to any log file, database, or persistent storage. There is no audit trail, history log, or session replay saved anywhere on your machine.
• User-initiated notification only: Desktop notifications are triggered only when explicitly configured by the user, and the notification content is derived directly from the incoming hook event. No notification data is cached or retained after dismissal.

Data Storage

Tasify employs a zero-persistence storage model:

• No local persistence: The extension does not use localStorage, IndexedDB, chrome.storage, or any other browser storage API to store event data or user activity history. No files are written to disk by the extension itself.
• Host process memory: The @tasify/host Native Messaging process holds hook events in memory only for the duration needed to forward them to the extension. Once forwarded, the in-memory copy is released. The host process does not write to any database, log file, or cache directory.
• Configuration state (limited): The only data stored locally is your notification preferences (which event types trigger desktop notifications). This is stored using chrome.storage.sync or chrome.storage.local — Chrome's built-in extension storage — strictly for the purpose of remembering your preferences between sessions. No hook event data or personal information is included in this stored state.
• No cloud storage: There are no remote databases, cloud buckets, or server-side stores of any kind. If chrome.storage.sync is used for preferences, it is synced through Chrome's own encrypted sync infrastructure — Tasify itself has no access to any remote storage layer.

Data Sharing

Tasify does not share any user data with any party for any purpose:

• No third-party sharing: The developer does not sell, license, trade, or otherwise transfer any user data to third parties. There are no data brokers, advertising networks, analytics providers, or marketing partners integrated into Tasify.
• No legal or compliance sharing: Because Tasify collects and stores no user data, there is nothing to disclose in response to legal requests, subpoenas, or data access demands. In the unlikely event such a request is received, there would be no responsive data to produce.
• No transfer for unrelated purposes: Data processed by Tasify is used exclusively for the extension's core functionality — displaying live Claude Code session activity. It is not used or transferred for advertising, machine learning training, research, or any purpose unrelated to that core function.
• No cross-service data flow: Tasify has no network communication layer in the extension or host process. There are no API endpoints, webhook callbacks, or data pipelines that could transmit data to any external service. The local-only architecture makes data sharing architecturally impossible.

This developer declares that your data is:

• Not being sold to third parties, outside of the approved use cases
• Not being used or transferred for purposes that are unrelated to the item's core functionality
• Not being used or transferred to determine creditworthiness or for lending purposes

Changes to This Policy

If this privacy policy changes, the updated version will be published at this URL. Given Tasify's local-only architecture, any future changes will maintain the same strict no-data-collection standard. Users will be notified of material changes through the extension's update notes on the Chrome Web Store.

Back to Home | All Projects