SuperRemote for WhatsApp Web - Privacy Policy

1. Privacy by Design

We know messaging data is sensitive. The Extension follows “local-first, data minimization, transparency and control” principles: data from web.whatsapp.com is processed locally in your browser; server interactions occur only for essential functions you initiate (e.g., configuration fetch, diagnostics logging).

2. What Data We Collect

We follow a data minimization approach and collect only what is needed to provide core functionality and improve stability. Details below:

Data Type	How It's Collected	Purpose	Shared With
Extension usage logs (e.g., feature usage frequency, anonymous error logs)	Automatically	Improve product stability and detect incompatibilities caused by WhatsApp updates	No one
Browser language and timezone	From browser settings	Localize UI and align with local time (e.g., for scheduled messages)	No one
WhatsApp number	Automatically	When issues arise, allows faster feedback through the corresponding WhatsApp account	No one
List of mobile phone numbers sent by the user (including numbers parsed from attachments and those entered directly)	User upload or input only	Excel parsing results to determine whether there are problems with Excel parsing and whether new parsing rules need to be added Record the user's sending status to determine whether the user's sending is normal.	No one
Install time	Automatically	Measure daily installs to detect potential extension issues (sudden spikes/drops)	No one
Browser info	Automatically	Different browser versions/types may cause different issues; used for troubleshooting	No one
UUID (anonymous unique identifier)	Automatically generated	When users contact support, enables quick retrieval of the last 7 days of logs (stored on Alibaba Cloud) to identify issues	No one

Unless explicitly stated, we do not upload your WhatsApp message content, address book, or media files to our servers; most processing is performed locally in your browser.

3. We Do Not Track Native WhatsApp Surfaces

The Extension does not conduct cross-session tracking of WhatsApp’s native UI. It only reads data on web.whatsapp.com while you use the relevant features, and only for local export or messaging workflows you initiate.

4. Cookies, Local Storage and Similar Technologies

• No cross-site behavioral tracking.
• Preferences and state are stored via chrome.storage.local (and/or chrome.storage.sync where applicable).
• All server communications (if any) are transmitted via HTTPS/TLS.

5. Permissions and Justification

Permission	Why It's Needed
activeTab	Open and interact with the current tab as needed to work with https://web.whatsapp.com/
storage	Save user preferences and settings locally (via chrome.storage.local)
scripting	Load/inject code into permitted pages to render the appropriate UI when options change
host_permissions (*://web.whatsapp.com/*)	Access WhatsApp Web to enable interaction and features

Refer to the Chrome permission prompt and Chrome Web Store listing for the authoritative set of permissions; we do not request more than necessary.

For technical reasons a content script may load on many sites, but it only actively operates on web.whatsapp.com.

6. How We Use the Data

• Diagnose and fix extension issues caused by WhatsApp Web updates.
• Localize content based on browser language and timezone.
• Provide support: when you contact us, use the UUID to quickly locate the last 7 days of error logs.

We do not use data for advertising, profiling, or cross-site tracking.

7. Data Storage and Security

• Local storage: extension settings and preferences are stored locally (chrome.storage.local).
• Encryption in transit: all communication with remote servers (if any) is protected via HTTPS/TLS.
• Access control: any cloud-stored data is restricted to authorized personnel for support/debugging only, with access logged and audited.
• Security governance: we conduct periodic security reviews and vulnerability scanning.
• Log retention: we retain user log data for 7 days to monitor WhatsApp changes and speed up issue resolution, using Alibaba Cloud’s automatic deletion policy.

8. Interactions with Third-Party Services (if applicable)

Service Type	Provider	Purpose	Typical Data
Logging and monitoring	Alicloud Log Service	Event logging, error diagnosis, compliance audit	Event type/time, version, install time, anonymous UUID; where available phone and country/region
Config distribution (CDN)	Static/config delivery (e.g., cdn2.waplus.io)	Fetch remote configuration to improve stability	Request metadata

We do not sell your personal information. Third parties are not permitted to use data for their own purposes.

9. International Data Transfer

We may use service providers outside your country (e.g., Alicloud overseas regions). When transferring data across borders, we implement appropriate safeguards (e.g., standard contractual clauses) consistent with applicable laws to provide equivalent protection.

10. Data Sharing Policy

• We do NOT sell, rent, or share user data with third parties for advertising or analytics.
• Data may be accessed only in the following cases:
  • By authorized personnel for debugging or support (with user consent or on anonymized data).
  • If required by law, such as a subpoena or court order.
  • As part of a business acquisition or asset transfer (users will be notified).

We use Alibaba Cloud services; our data is stored on Alibaba Cloud resources such as OSS, ECS, and RDS/MySQL. Alibaba Cloud itself has no right to view our data.

11. User Control and Data Deletion

• Local data: clear extension data via Chrome settings, or uninstall the extension.
• Server-stored data (if any): contact us at wopzaryikdzw4@gmail.com to request deletion; we follow a minimal-retention policy.
• Data minimization: we retain only what is necessary to provide the service and routinely delete stale/inactive data.

12. Your Choices and Rights

• Depending on applicable law (e.g., GDPR/CCPA), you may have rights to access, rectify, delete, restrict/oppose processing, data portability, and withdraw consent.
• You can refuse or revoke optional permissions in your browser without affecting most basic features.
• Clear local data or uninstall the Extension at any time.

13. Children’s Privacy

The Extension is not intended for children under 13, and we do not knowingly collect personal information from children.

14. Do Not Track

There is no uniform industry standard for DNT signals. The Extension does not perform cross-site behavioral tracking; we will update this Policy if standards change.

15. Changes to This Policy

We may update this policy as needed to comply with regulations or reflect product changes. The updated version will be posted on this page with a revision date.

16. Contact Us

If you have questions or concerns about this policy or your data, contact us at:

📧 Email: wopzaryikdzw4@gmail.com