SMDeck WhatsApp Sender
Privacy policy
Last updated:
This policy covers SMDeck WhatsApp Sender, listed as WARocket Sender:Rocket Sender - WAPI Sender in the Chrome Web Store, extension ID onohcnjmnndegfjgbfdfaeooceefedji, and its workspace on smdeck.com. SMDeck is an independent project maintained by Earnest Hamingo, not affiliated with WhatsApp or Meta. Sender is completely free, with no paid plan, subscription or paid feature unlocks.
1. Data used by extension features
Depending on the feature you select, Sender reads contacts and group members, chat identifiers and profile information, messages and media selected for backup or status download, and numbers or files you import. Account detection checks the supplied numbers through WhatsApp. Auto-reply processes incoming messages to apply your rules. Privacy controls blur content on your screen; blurring is not encryption or deletion.
We do not ask for your WhatsApp password or take custody of your account. WhatsApp controls its login session and messaging service under the WhatsApp Privacy Policy.
2. Local storage and exports
| Data | Location and purpose |
|---|---|
| Spreadsheets, recipients and templates | Read locally. Saved campaigns and tasks use extension storage or IndexedDB for editing, resuming and reviewing. |
| Attachments | Read by the browser and transferred locally to the extension for storage. Your WhatsApp session uploads them to WhatsApp when you send. |
| Progress and results | Extension storage and the website's browser storage retain local records. A successful local send call does not prove delivery or reading. |
| Unfinished website drafts | Browser IndexedDB retains drafts for recovery. Closing a tab does not necessarily delete them. |
| Preferences | Extension local/sync storage and website local storage. Chrome or Edge may sync preferences through your browser account when sync is enabled. |
| Exports and backups | Downloaded to your selected destination. These files remain on your device until you remove them. |
Recipient lists, message text, attachment contents and backups are not sent to SMDeck's GA or Clarity integrations. We do not sell this content. Local storage is not a cloud backup: clearing browser data, uninstalling or changing profiles can remove it.
3. Browser permissions
- WhatsApp host access, activeTab and scripting: connect to WhatsApp Web and run the sending, privacy and download features you select.
- smdeck.com and www.smdeck.com access: connect the website workspace through a local browser bridge and download privacy stylesheet updates. These requests are not an upload of your contacts or message content.
- storage and unlimitedStorage: retain settings, campaigns, attachments and results locally; these permissions do not expose unrelated files on your device.
- alarms: wake scheduled tasks. Sending still requires the browser, WhatsApp connection and session to be available.
- Optional host access: the package declares optional access to other sites. This is not access already granted. Review browser permission prompts and extension site-access settings.
4. Network requests and remote updates
Sender communicates with WhatsApp to perform your selected actions. It retrieves remote product configuration from cdn2.waplus.io. Starting with version 1.0.41, privacy stylesheet updates use smdeck.com/config/whatsapp-sender/privacy/; older releases used the legacy CDN. When privacy is enabled, an online, visible WhatsApp page checks a small version manifest about once per minute. The extension downloads CSS only when its content changes, verifies its SHA-256 hash and compatibility, and caches the last valid version locally. Failed checks retain that version; bundled CSS is the fallback when no valid remote version is available. Checks pause for hidden or offline pages and retry with a delay after failures.
These update requests do not include imported spreadsheets, recipient lists, templates, attachments or chat content. They retrieve CSS and JSON, not remote executable scripts. Hosting providers receive ordinary connection information such as IP addresses and request headers. A stylesheet update changes screen protection rules; it does not change your saved privacy switches.
Installation opens the Sender guide and WhatsApp Web. Uninstallation opens the optional feedback page. Visits to SMDeck pages use the website analytics described below. Sender version 1.0.42 and later include basic usage statistics enabled by default, without an in-extension switch. It reports an actual first installation, a task beginning to send, the first successful local send call and a task's final status with aggregate success, failure and unknown-result counts. Updates do not count as new installations; creating a scheduled task does not count as starting to send; local success does not prove delivery or reading.
The extension sends only a random analytics client/event identifier, event time, Chrome/Edge family, extension version, source category, attachment presence and bounded summary counts directly to Google Analytics at www.google-analytics.com, using Measurement Protocol. These usage events do not pass through an SMDeck backend. It does not include phone numbers, contact or group names, task names, message text, spreadsheet cells, file names, attachment contents or free-text errors. Google receives ordinary connection information, such as the sending IP address and request headers. Network failures use a bounded local retry queue; unsent events expire after 48 hours. Uninstalling the extension removes this local queue but does not delete events already sent to Analytics.
Private sending-error diagnostics in production 1.0.44
Separately from the usage events above, Sender automatically reports sending errors, interruptions and related task outcomes to smdeck-sender-diagnostics.hamingoearnest.workers.dev, hosted by Cloudflare. Reports can include a random installation identifier, task and attempt identifiers, extension/build and WhatsApp versions, error codes and sanitized technical traces, timing, task status and summary counts, message length and attachment type/size metadata. The full phone number of the recipient involved in a failed or unknown attempt can be included in an explicit diagnostic field. This is not an upload of your complete recipient list; successful recipients' numbers, contact names, message text, original spreadsheet and attachment contents are excluded.
The developer uses these reports to diagnose and follow up on failures. The Cloudflare R2 diagnostic bucket is private, with public reading disabled and a one-day expiry rule configured for diagnostic objects; expiry is not a promise of immediate deletion at an exact second. Cloudflare also processes ordinary request connection information. These diagnostics are enabled automatically in the production build. Deleting a local draft or uninstalling does not recall a report already received. For a privacy or deletion request, contact hamingoearnest@gmail.com.
5. Website analytics and hosting
Google Analytics measures website visits, sources, extension-store link clicks and successful feedback submissions. A store click does not confirm installation. We save the first observed source in browser local storage, checking utm_source, then an external referring hostname, then direct traffic. The saved first_source and first_ai accompany website analytics; later visits do not overwrite them. This attribution excludes referrer paths, recipients, message text and attachment contents.
On the Sender page, a local extension bridge shares the website's random GA client/session identifiers and first source with Sender so installation and sending stages in the same browser can be connected to the earlier visit. It does not use your WhatsApp number as an identifier. If that bridge or website analytics is unavailable, the extension uses a separate random identifier and an unknown first source; complete attribution is then unavailable. Different devices or browser profiles are not joined. These extension events request no advertising personalization and do not add a WhatsApp session replay.
Microsoft Clarity provides website interaction analytics, heatmaps and session replays. We explicitly mask the messaging workspace, attachment previews and feedback area. Masking does not mean that no usage data is processed. These website integrations do not record WhatsApp chats or the extension popup. Providers may process browser identifiers, cookies, device information and connection data; see Google's Privacy Policy and the Microsoft Privacy Statement.
Cloudflare processes requests and technical data to host and protect the site. The website also loads Google-provided fonts and advertising scripts, independently of the extension. Browser privacy controls and content blockers can limit third-party requests. Clearing smdeck.com site data resets saved attribution. See also our website privacy policy.
6. Optional feedback and support
Feedback submissions send us your selected product, contact email, description and any attachment or recording link you provide. They are stored in our Cloudflare-hosted feedback service. Descriptions, links and issue status can appear publicly; the email is masked publicly and available in full to the developer for support. Cloudflare Turnstile provides anti-abuse verification.
Remove private messages, contact names, phone numbers and credentials from recordings before sharing. A linked file host has its own sharing and privacy rules. For private support or a removal request, email hamingoearnest@gmail.com.
7. Retention and deletion
- Use campaign and record deletion controls to remove individual items. Website history and extension records are separate local copies.
- For a full local reset, clear smdeck.com site data and remove the extension. Synced preferences follow your browser's sync settings.
- Delete exported files and backups separately from your download folders. Removing local data does not recall WhatsApp messages.
- Cleanup depends on the feature and stored references. Closing a page does not immediately erase all drafts, records or attachments.
- Feedback is retained while needed to investigate and track an issue, unless removed. Contact us to request access, correction or deletion. Website analytics retention follows the service and project settings.
Sender has no built-in unsubscribe feature. Remove contacts who ask you to stop from your own lists before sending again. Being free does not change WhatsApp's message handling or account restrictions.
8. Contact and changes
Contact Earnest Hamingo at hamingoearnest@gmail.com for privacy questions. We revise this policy when data practices change and show the actual revision date above.