Privacy Policy — Bulk SMS Sender

In short: your messages, contacts and the lists you import are handled on your phone and are never uploaded to our servers. The app sends Google's Firebase services a small amount of usage and crash data, and an anonymous ID with your purchases so we can confirm them. There are no ads and no account to create, and we don't sell any data.

Who we are

The app is published on Google Play by Mediant Technologies, the trading name of Janesh Kumar, an individual developer based in New Delhi, India (“we”, “us”). You can reach us at medianttechnologies@gmail.com.

Data that stays on your phone

To work as an SMS app, the app needs access to some personal data on your device. This data is processed on your phone, kept in Android's own message store or in the app's private database, and is not uploaded to us or to any third party.

Data	What the app does with it
Text messages (SMS and MMS)	Shows, sends, receives, searches and organizes your messages. Bulk sends go out one by one through your own SIM. Deleted messages wait in the in-app Recycle Bin until you restore them or empty it.
Contacts	Shows contact names and photos next to conversations and notifications, lists contacts so you can start a chat or pick recipients, and creates contact groups when you ask it to (saved in your phone's contacts).
Phone and SIM information	Lists your SIM cards and their numbers so you can choose which SIM sends a message, and rotate between SIMs on a bulk send.
Files you import (CSV, Excel)	Reads the names, numbers and other columns you choose, only when you pick a file. The file itself is not changed or copied anywhere.
Import from computer	Your phone briefly runs a small upload page on your local Wi-Fi. The file goes straight from your computer's browser to your phone over that network, protected by a one-time 6-digit PIN. The page accepts a single file and shuts down as soon as it arrives, when you cancel, or when it times out. The link uses a sslip.io address, a free public DNS service that simply points back to your phone's local IP address, so your computer's DNS provider sees that local address but not your file.
Settings, drafts and scheduled sends	Stored in the app's private storage on your phone.

The app's own database is excluded from Android cloud backup. Your messages themselves live in Android's system message store, so they follow whatever SMS backup your phone or carrier provides. Uninstalling the app removes its private database; your messages stay in Android's message store, as they do with any SMS app.

Data the app sends to service providers

The app uses the following Google services. None of them receives the content of your messages, your contact list or the files you import.

Service	What is sent	Why
Firebase Analytics (Google)	Which screens you open, whether a purchase was completed (the product type only), when a notification is opened, and whether the app is your default SMS app, together with the standard data the SDK collects: an app-instance ID, device model, Android version, app version, language, approximate country and usage times. Screen names are stripped of any phone numbers or conversation IDs before they are logged.	To understand which features are used and improve the app.
Firebase Crashlytics (Google)	Crash and error reports: the technical error, device model, Android version, app version and an installation ID.	To find and fix crashes.
Firebase Authentication (Google)	A random anonymous user ID created on your device. No name, email or phone number.	To link your purchases to your copy of the app without an account.
Cloud Firestore and Cloud Functions (Google), run by us	When you buy something: the purchase token and product ID from Google Play, linked to the anonymous ID. We store which plans and items you own and when your subscription renews.	To verify purchases with Google Play and unlock what you paid for.
Google Play Integrity	A one-time integrity token from Google Play.	To check that purchases come from a genuine copy of the app. The result is not stored.
Firebase Cloud Messaging (Google)	A push token held by Google. The app subscribes to general announcement topics; we don't store your token.	To send occasional app announcements.
Google Play Billing, In-App Review and In-App Updates	Handled by Google Play under your Google account.	Payments, ratings prompts and app updates. We never see your payment details.

These providers process data on our behalf under Google's terms, see Google's Privacy Policy and Privacy and Security in Firebase. Their servers may be outside India.

What we don't do

We don't upload, read or store the content of your messages or your contact list.
We don't show ads or use advertising identifiers.
We don't sell or rent personal data, and we don't share it with anyone except the service providers above.
The app doesn't ask you to create an account.

Messages sent on the Free plan

On the free plan of Business Mode, each bulk message ends with a short line naming the app (“: via tiny.cc/BulkSender”). The line is added to the message text before it is sent, so your recipients see it. Plus and Max plans don't add it.

Permissions

Permission	Used for
SMS and MMS (send, receive, read, write)	The default SMS app role: showing, sending and managing your messages.
Contacts (read, write)	Names and photos for conversations, picking recipients, and creating contact groups.
Phone state and phone numbers	Dual-SIM: choosing and rotating the sending SIM.
Notifications	New message alerts, with reply and mark-as-read actions.
Exact alarms and foreground service	Sending scheduled batches on time and keeping a bulk send running.
Internet and network state	The Google services above, MMS, and the local Wi-Fi import page.

How long we keep data

Purchase records (anonymous ID, products owned, purchase tokens): for as long as we need them to give you what you bought and handle restores and refunds. We delete them when you ask.
Analytics data: kept by Google Analytics for Firebase for the retention period set in our project (never more than 14 months), then deleted automatically.
Crash reports: kept by Crashlytics for 90 days.

Your choices and rights

You can stop all data collection by uninstalling the app. To ask for a copy of the data we hold, or to have it deleted, follow the steps on Delete your data or email us. We reply within 30 days. Deleting purchase records may mean you have to restore your purchases from Google Play again.

Children

The app is not directed at children under 13, and we don't knowingly collect personal data from them.

Security

Data sent to Google services is encrypted in transit. Purchase records can only be written by our server code and read by the copy of the app that owns them.

Changes to this policy

If we change this policy, we'll post the new version here and update the date at the top. For significant changes we'll also tell you in the app.

Contact

Questions or requests: medianttechnologies@gmail.com, Mediant Technologies, New Delhi, India.