Sendify (Dify Sender) — Privacy Policy

Last Updated: 2025-08-31

This Privacy Policy explains how the Chrome extension "Sendify (Dify Sender)" ("the Extension") handles information and data.

About the Extension

The Extension lets you send text you enter in the popup, the current page text, selected text, or visible form values to a Dify app endpoint that you configure. When possible, the Extension extracts response text and shows it in the popup (and you can view Raw JSON if extraction fails).

1. Data We Process

All data handled by the Extension comes from explicit user actions. It does not continuously or automatically collect data.

Content you choose to send

  • Text you type in the popup
  • The current tab's page text (on user action)
  • The current tab's selected text (on user action)
  • Visible form input values on the page (password, hidden, and disabled fields are skipped)
  • Metadata such as the page URL and the source of the send (page/selection/etc.)

Settings you provide

  • Dify endpoint URL, API Key, optional App ID, display name(s)
2. When and How Data Is Collected
  • Only when you click popup buttons like "Page Text", "Selection", "Form", or "Send". We use activeTab together with scripting to read the minimal necessary text from the current tab.
  • There is no background monitoring or automatic harvesting.
  • Long inputs are truncated to a safe length to prevent oversized posts.
3. Where Data Is Sent and Shared
  • Data is sent only to the Dify endpoint you configure.
  • We do not send or share your data with any servers operated by the developer of this Extension.
  • Responses are parsed for display in the popup only; they are never executed as code.
4. Storage and Retention
  • The only data the Extension stores in your browser is configuration (endpoint, API Key, App ID, language, etc.), using chrome.storage.sync.
  • The content you send (page/selection/form/input text) is handled transiently for sending and UI display and is not persistently stored by the Extension.
  • Data in chrome.storage.sync may sync with your Google account. Sync behavior and encryption follow Google's policies.
5. Purpose of Permissions

storage

Save configuration such as endpoint and API Key

activeTab

Temporary access to the current tab's content on user action

scripting

Execute small functions to read page/selection/form text

notifications

Show success/error notifications

6. Security
  • Your API Key is stored via chrome.storage.sync and is only accessed by the Extension. Use secure devices/accounts and avoid sharing devices or accounts with others.
  • Configure only endpoints you control or trust. Security, retention, and processing at the destination are governed by the destination operator's policies.
7. Your Choices and Data Management
  • You can view, edit, and delete configuration (profiles) from the Options page.
  • Uninstalling the Extension removes locally stored configuration from your browser.
  • Data already sent to your configured destination cannot be deleted through the Extension. Contact the destination service's administrator/operator if you need deletion or corrections.
8. Children's Privacy

The Extension is not directed to children. If you are a minor, use it with parental/guardian consent and supervision.

9. Changes to This Policy

We may update this Policy as features or behavior change. The latest version is kept in this repository.

End of Policy

This Privacy Policy is effective as of 2025-08-31.

Built with v0