Sender Studio

Privacy Policy

Last updated: May 26, 2026

1. Introduction

At Sender Studio, we respect your privacy and aim to be clear about what data we process, why we process it, and where it lives. This policy applies to our website, web app, and Chrome extension.

No affiliation notice

Sender Studio is an independent product. We are not affiliated with, associated with, or endorsed by WhatsApp Inc., Meta Platforms, Inc., or Google LLC.

2. Data we may process

2.1 Account and subscription data

  • Basic account information if you create a Sender Studio account, such as email, name, and internal identifiers.
  • Subscription and billing data related to your plan. Payments are processed by third parties such as Stripe; we do not store your full card number.

2.2 Data processed by the extension

  • Phone numbers that you paste or load into the extension.
  • The message text that you choose to send.
  • Local preferences such as language, templates, sending progress, and sending state.
  • Minimum technical data needed for security and product operation, such as extension version, runtime ID, and a local device identifier.

2.3 What we do not host as a WhatsApp dataset

The extension works on web.whatsapp.com in your own browser. Message content, recipients, and WhatsApp interface state are processed mainly locally to carry out the action you requested. We do not turn your WhatsApp activity into a hosted dataset as part of the quick-send extension flow.

3. How the Chrome extension works

The Sender Studio extension has one main purpose: to allow simple, user-initiated quick text sends from WhatsApp Web and direct users to the web app for advanced workflows.

3.1 Permissions and why they are used

  • tabs: to open the landing page or dashboard when the user asks for it, detect the WhatsApp Web tab, and avoid conflicts caused by duplicate WhatsApp Web tabs.
  • storage: to locally preserve pasted numbers, message content, language, sending progress, technical status, and other preferences so work is not lost when the popup closes.
  • unlimitedStorage: to support large recipient lists and local sending state without truncation.
  • alarms: to refresh technical checks and internal state in the background.
  • Access to web.whatsapp.com: required to read WhatsApp Web state, perform the user-requested send flow, and display sending progress.
  • Access to Supabase: required for extension security validation and Sender Studio backend services.

3.2 What the extension stores locally

The extension uses chrome.storage.local to store working data such as:

  • pasted or loaded phone number lists,
  • message text,
  • quick templates,
  • language, sending progress, and sending state,
  • technical security and compatibility status.

3.3 What is sent to our services

The extension may send minimum technical data to our services for validation and security, such as the extension runtime ID, extension version, and a local device identifier. This helps us validate official builds and reduce unauthorized copies.

3.4 What the extension does not do

  • It does not track browsing activity outside of web.whatsapp.com.
  • It does not inject ads or third-party trackers.
  • It does not sell user data.
  • It does not download or execute remote code within the extension package.

4. How we use information

  • To operate the Sender Studio website and web app.
  • To enable user-initiated quick sending through the extension.
  • To preserve local preferences and avoid losing in-progress work.
  • To validate extension security status and detect technical conflicts.
  • To manage accounts, subscriptions, support, and abuse prevention.
  • To measure advertising campaigns, attribute signups and purchases, and improve our pages.

5. When we share information

We do not sell or rent personal information. We may share information only in these cases:

  • with providers that run product infrastructure, such as Supabase or Stripe,
  • with advertising measurement providers such as Google Analytics, Google Ads, and Meta when enabled,
  • if required by law,
  • or if necessary to protect our rights, users, or service security.

6. Measurement, advertising, and attribution

We may use Google Analytics, Google Ads, Meta Pixel, and the Meta Conversions API to measure visits, signups, plan selections, checkout starts, and confirmed payments. We may also store campaign identifiers such as UTM parameters, gclid, gbraid, wbraid, fbclid, fbp, and fbc to attribute conversions to advertising campaigns.

In European regions where consent is required, we show a notice before loading advertising cookies or pixels. Outside those regions, these tools may load directly when measurement is enabled.

7. Google and authentication

The Sender Studio web app may offer Google sign-in. In that case, we only use standard profile data needed for authentication and account management. The current quick-send extension flow does not require sign-in to send simple text messages.

8. Security

We use reasonable administrative, technical, and organizational safeguards to protect information. We also use remote checks to validate official extension builds and reduce unauthorized copies.

9. Your rights and data deletion

You may request access to, correction of, or deletion of personal data associated with the web app.

Extension-local data can be removed by uninstalling the extension or clearing the browser storage associated with it.

10. Changes to this policy

We may update this policy as the product, infrastructure, or legal requirements change. When that happens, we will update the effective date on this page.

11. Contact

If you have questions about this Privacy Policy, contact us at:

soporte@senderstudio.app