Privacy Policy

Last Updated: January 25, 2026

1. Introduction

At WhatsLink+, your privacy is our highest priority. We believe in a transparent, "local-first" approach to software. This Privacy Policy explains how WhatsLink+ handling your data, why we require specific permissions, and how we protect your information.

The Bottom Line: WhatsLink+ does not collect, sell, or transmit your personal data, phone numbers, or messages to external servers. All operations happen directly on your device.

2. Data Collection and Usage

WhatsLink+ operates as a standalone client-side extension.

A. Personal Information

We do not collect personal identification information (names, email addresses, etc.).

• Phone Numbers: When you enter a phone number to send a message, it is processed locally to generate a WhatsApp link.
• Recent Numbers: To improve your experience, the last 5 numbers you utilized are saved locally on your device using Chrome's Sync Storage. These are never shared with us.

B. Message Content

We do not have access to, read, or store your messages.

• The "Pre-filled Message" feature generates a URL parameter. The actual message sending happens entirely within the official WhatsApp interface (Web or App).

C. Usage Analytics

We do not use third-party analytics software (like Google Analytics or Mixpanel) to track your usage behavior inside the extension.

3. Permissions Explained

To function correctly, WhatsLink+ requires specific browser permissions. Here is a breakdown of why each is necessary:

• Storage: Used to save your preferences (e.g., Default Country, Theme), your configured "Privacy Blur" settings, and your locally stored history of recent numbers.
• Tabs: Required to open the official api.whatsapp.com or web.whatsapp.com links in a new browser tab when you click "Send".
• ActiveTab / Host Permissions: Required for two features:
  1. Context Menu: To read the phone number you highlighted when you right-click on a webpage.
  2. Privacy Functions: To inject the CSS filters that blur content on web.whatsapp.com.
• Context Menus: Adds the "Send to..." option when you right-click selected text on a webpage.
• Notifications: Used to provide system feedback (e.g., "Link copied to clipboard", "Invalid Number") and occasional review reminders.
• Alarms: Used to schedule low-priority background tasks, such as the weekly check for the review reminder, ensuring the extension doesn't consume resources when not in use.

4. Privacy Blur Features

WhatsLink+ includes features to blur sensitive information on WhatsApp Web.

• How it works: This feature uses CSS (Cascading Style Sheets) injection. It strictly modifies the visual presentation of the page locally in your browser.
• Data Safety: The extension cannot read the content beneath the blur. It purely applies a visual filter overlay.

5. Data Storage and Security

All settings and history are stored effectively in chrome.storage.sync or chrome.storage.local.

• Sync: If you are signed into Chrome, your settings (like your default country code) may assume the security of your Google Account to sync across your devices.
• Security: Since we do not maintain external servers, there is no central database of user data that can be breached. Your data stays on your machine.

6. Third-Party Services

WhatsLink+ acts as a bridge to WhatsApp (owned by Meta Platforms, Inc.).

• When you click "Send" or scan a QR Code, you are redirected to WhatsApp.
• Once you leave the extension and enter the WhatsApp platform, you are subject to WhatsApp's Privacy Policy.

7. Compliance

Chrome Web Store User Data Policy

We adhere strictly to the Google Chrome Web Store User Data Policy. We strictly limit our use of permissions to the core functionality of the extension.

GDPR / CCPA

Since we do not collect, process, or store personal data on our servers, WhatsLink+ is privacy-compliant by design. You retain full control and ownership of your data on your device.

8. Changes to This Policy

We may update our Privacy Policy from time to time. We will notify you of any distinct changes by posting the new Privacy Policy on this page and updating the "Last Updated" date.