TextBlasts.app — Privacy Policy

Decentralized Bulk Texting (SMS · RCS · MMS) · Chrome & Edge Extension

1. What This Service Does

TextBlasts.app is software that runs locally inside your browser (via the Blasts extension) and lets you compose, pace, and send bulk text-message campaigns. Every message is sent directly through your own messaging accounts — your own Twilio or Telnyx account (and, as rich messaging rolls out, your own RCS/MMS-enabled sender). We provide the control interface; the texts leave from your provider account, under your phone number, billed to your provider.

This software is decentralized. Your contact lists, message content, and provider API keys are kept locally on your own device and are never sent to our servers.

2. Data We Access

We do not collect, store, or monitor your recipient lists or message content on our servers. Importing a CSV, filling merge fields such as {{first_name}}, de-duplicating numbers, checking line types, counting segments, and building campaign reports all happen locally inside your browser.

Recipient phone numbers you upload are stored only in your browser's local database on your device. We never receive them, sell them, or use them for our own purposes.

3. How Texting Works (Bring-Your-Own Account)

Your own provider. You paste your own Twilio or Telnyx API credentials. Texts are sent by API call from your browser straight to your provider — nothing routes through us.
Encrypted at rest. Provider API keys are stored in chrome.storage.local and encrypted if you set an Encryption Passphrase in the extension.
You are the sender of record. Because messages originate from your account and your number, you are the party responsible for consent and compliance for the numbers you text (see our Terms of Service).

4. Opt-Outs, STOP Handling & the Do-Not-Text List

Honoring opt-outs is built in. When a recipient replies STOP, UNSUBSCRIBE, QUIT, END, or CANCEL, that number is added to your local do-not-text list and is skipped on every future campaign.

Optionally, you can connect an inbound webhook so STOP replies are captured automatically. To attribute an opt-out to your account, the webhook records only the opted-out phone number and the time, keyed to your registered account. No message content or other personal data is stored. The extension syncs these opt-outs back down into your local do-not-text list. Provider-level opt-out signals (for example Twilio error 21610 or Telnyx code 40300) also add the number to your do-not-text list automatically.

5. Line-Type & Capability Lookups

If you use Line Type Check (to skip landlines that can't receive texts) or, for rich messaging, a capability check, the phone number is sent to your chosen provider's lookup API using your credentials, and the result (mobile / landline / VoIP, or RCS-capable) is cached locally so each number is only looked up once. Results are not shared with us.

6. Data Storage & Encryption

Stored locally. Lists, message drafts, campaign status, the do-not-text list, and cached lookups live in your browser's local storage / on-device database.
Secrets encrypted. Provider API keys are encrypted at rest when you set an Encryption Passphrase.
Prepaid credits. Your credit balance and a minimal billing ledger are verified via secure transactions with our serverless billing endpoint. This records the count of message segments sent for service-fee metering — never your recipients or message content. One prepaid pool is shared with your other Blasts services.

7. What We Never Do

We never read, store, or sell your contact lists or message content.
We never send messages ourselves — your provider does, from your account.
We never use your data for advertising, profiling, or creditworthiness.
We never share your data with third parties except the providers you connect (to deliver the feature you enabled) or as required by law.

8. Compliance

You are responsible for using the Service in accordance with the Telephone Consumer Protection Act (TCPA), the CTIA Messaging Principles & Best Practices, carrier A2P 10DLC (and, for rich messaging, RCS/Google) registration requirements, and all applicable laws in your jurisdiction, including obtaining prior express consent before texting recipients. See our Terms of Service.

9. Contact

For privacy questions, contact support@cockpit.bot

Website: TextBlasts.app

Publisher: Tips Marketing Services, Corp — a New Jersey corporation.

Last updated: July 6, 2026