Privacy Policy

Last Updated: June 2026

1. Framework Overview

At WA Cloud Worker, we protect your operational footprint and client database structures with strict technical data limits. This Privacy Policy describes how data packages are processed, tracked, and isolated when you interact with our local desktop extension and server-side background daemons (the "Service").

2. Data We Process

Because our background architecture loops asynchronously to execute tasks over the air, our servers process only the vital parameters required for system functionality:

Account Identity: Your business verification email, user token, and transaction logs.
Pipeline Queues: Target phone numbers, scheduled timestamps, text strings, and raw asset files submitted directly to your outbound broadcast grids.
Zero Messaging Storage: We do not permanently read, store, or aggregate your raw customer conversation histories, personal contact books, or chat logs. Data packets pass through our secure pipelines strictly to facilitate delivery to the target recipient.

3. Third-Party Financial Routing

Payment processing is entirely managed off-site by our Merchant of Record Partner, Paddle.com.

When initializing a transaction layout, your financial metrics (including credit card data, bank information, and billing routing tokens) bypass our server databases completely. Paddle collects, securely stores, and legalizes this data under absolute PCI-DSS compliance standards to fulfill tax handling and checkout fraud checks.

4. How Data is Handled & Isolated

We process your operational queue data parameters strictly to perform the service parameters you authorize:

To track due task timestamps and trigger background cron dispatches.
To read and structure media file streams into raw un-prefixed Base64 text blocks matching WhatsApp API requirements.
To clear active sequences immediately upon catching an inbound user response flag (via our Interruption Shield).

5. Local Browser Storage

Our desktop extension stores local script tokens, UI layout settings, and session cache states directly within your browser's isolated environment using standard local storage parameters (`chrome.storage`). This data stays bound to your device and can be cleared instantly by resetting your extension profile.

6. Retention and Security Tunnels

All data parameters transmitting between your extension framework, our Next.js API infrastructure proxies, and our PostgreSQL data arrays are locked using secure TLS end-to-end encryption tunnels. Active sequence variables are permanently deleted from our runtime tables the moment delivery confirmation clears successfully.

7. Your Data Rights

You maintain absolute sovereignty over your operational workspace records. At any time, you can query, update, or completely erase your active account logs or phone number lines by transmitting an infrastructure payload request directly to our mail port.

8. Privacy Contact Port

For compliance reviews, specific privacy inquiries, or deep system data erasure operations, please email our administration layer directly at: support@wacloudworker.com.

WA Cloud Worker Privacy Blueprint // Secure SSL/TLS Tunnels Active.