WADeck Private Policy
Last updated: July 3, 2025
WADeck (“we”, “our”, or “us”) is committed to protecting your privacy. This Privacy Policy explains what data we collect from users of the WADeck Chrome Extension, how we use and protect that data, and with whom we share it.
1. What Data We Collect
We collect data only as needed to provide core functionality of the extension. Here is a detailed breakdown:
| Data Type | How It’s Collected | Purpose | Shared With |
| WhatsApp contact names and message metadata (e.g. timestamps) | When user enables the Profile feature | Display contact details and activity log in UI | No one |
| Extension usage logs (e.g. feature usage frequency, anonymous error logs) | Automatically | Improve product stability and detect incompatibilities with WhatsApp updates | No one |
| Google identity (OAuth token) | When user connects Google Calendar | Synchronize scheduled messages and reminders | Google APIs only |
| Browser language and timezone | From browser settings | Used to localize UI and align with user's local time for scheduled messages | No one |
Cookies (via Chrome cookies API) |
On login status check | Detect WADeck login status in real time | No one |
| Images or message attachments (if sending media) | User upload only | Temporarily stored for quick image sending | No one |
2. Permissions and Justification
The WADeck extension uses the following Chrome permissions:
| Permission | Why It’s Needed |
activeTab |
Open a new tab for WhatsApp Web (https://web.whatsapp.com/) |
storage |
Save user preferences and settings locally |
unlimitedStorage |
Store large media (e.g., images over 5MB) for faster access |
cookies |
Monitor login status on WADeck via cookies |
scripting |
Inject code for page reload or UI injection |
alarms |
Schedule periodic tasks (e.g., auto-syncing tags or sending messages) |
identity |
Authenticate user for Google Calendar integration |
host_permissions |
Access to web.whatsapp.com to interact with WhatsApp Web |
3. How We Use the Data
We only collect and process data that is necessary to deliver the following functionality:
- Displaying WhatsApp contact data within the extension UI (Profile feature)
- Scheduling and managing messages via Google Calendar
- Localizing content and providing time-based features (e.g., message send delay)
- Diagnosing issues with the extension caused by updates to WhatsApp Web
4. Data Storage and Security
- Data such as extension settings and preferences are stored locally using Chrome’s
chrome.storage.localAPI. - Media attachments (if applicable) are temporarily stored and purged after delivery or expiration.
- All communication between the extension and remote servers (if applicable) is secured via HTTPS/TLS.
- Access to any cloud-stored data is strictly limited to authorized personnel only, and access is logged and audited.
- We conduct periodic security audits and vulnerability scanning.
- The cloud server stores the data that users need to use for a long time for each function. For example: The message content of quick reply includes text and attachments, the relationship between Tab and WhatsApp chat, etc.
5. Data Sharing Policy
We do NOT sell, rent, or share user data with any third parties for advertising or analytics.
Only in the following cases may data be accessed:
- By authorized WADeck 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)
Since we use Alibaba Cloud services, all our data is stored on Alibaba Cloud-related cloud servers, such as OSS, ECS, MySQL and other services. Alibaba Cloud itself has no right to view our data.
6. User Control and Data Deletion
Users have full control over their data:
- All data stored locally by the extension can be cleared via Chrome settings or by uninstalling the extension.
- Users can contact us at [email protected] to request deletion of server-stored data (if any).
- We retain only the minimal data necessary to provide the service and delete stale or inactive user data routinely.
7. Google User Data Disclosure
Scopes we request
-
https://www.googleapis.com/auth/userinfo.email– access to your Google Account’s primary email address. -
https://www.googleapis.com/auth/calendar.events– view and edit events on calendars you can access.
What we access and how we use it
- Email address: to authenticate you, display which account is signed in, link your account across devices/workspaces, avoid duplicate accounts, and send user-requested notifications related to your own calendar activity.
- Calendar events: to let you manage events inside our extension—create, edit, delete, move events between calendars you already have access to, and keep your changes in sync. We do not modify calendar ownership, sharing (ACLs), or calendar-level settings with this scope.
What we don’t do
We do not sell Google user data or use it for advertising. We don’t share it with third parties except subprocessors acting on our behalf under confidentiality to operate the service, or where required by law. No human accesses your data unless you ask for support, we must for security/compliance, or to comply with law. Our use and transfer of Google data adheres to the Google API Services User Data Policy (including Limited Use).
Retention and deletion
We retain Google user data only as long as needed to provide the features you request and meet legal obligations. If you disconnect Google or delete your account, we revoke OAuth tokens and routinely purge cached Google data. You can also request deletion via in-app controls or by contacting support at [your email].
Your control
You can revoke our access anytime in your Google Account (Security → Third-party access). Revoking access stops our app from accessing Google data going forward.
Security
Data is encrypted in transit and at rest, access is restricted by least privilege, and actions are logged for audit.
8. Children’s Privacy
Our extension is not intended for use by children under the age of 13. We do not knowingly collect personal information from children.
9. Changes to This Policy
We may update this policy as necessary to comply with regulations or reflect product changes. The updated policy will be posted on this page with a revision date.
10. Contact Us
If you have questions or concerns regarding this policy or your data, contact us at: 📧 [email protected]