BotMaster Bulk Sender

BotMaster Bulk Sender Privacy Policy

Effective date: 2 November 2026 · Last updated: 17 November 2026

App: BotMaster Bulk Sender for Android (package com.botmaster.plus) · Developer: Youhexa Technologies Pvt. Ltd.

1. Summary

2. Who we are

BotMaster Bulk Sender (the “App”) is developed and published by Youhexa Technologies Pvt. Ltd. (“Youhexa”, “we”, “us”). Our address is 2nd Floor, Apex Tower, Mahatma Gandhi Marg, Hazratganj, Lucknow, Uttar Pradesh 226001, India. We are responsible for the App and for this policy.

Privacy contact: support@botmaster.software · Website: youhexa.com · App website: botmaster.software

The App is a business tool. It helps you send messages that you write to contacts you add, through the WhatsApp or WhatsApp Business app installed on your phone. You can also set up auto-replies.

3. Data stored on your device

You create, import or type the following data yourself. It is kept in the App’s private storage on your phone, protected by Android’s app sandbox, and it is not sent to us:

Contacts, messages, campaigns, and settings stay on your phone. We cannot see or restore them. Android system backup is turned off for this App. That data is copied off the device only if you choose to: by making a Google Drive backup, by saving a backup or export file, or by sharing something. Crash logs, diagnostics and usage analytics in section 9 are the exception: they are sent automatically to Google Firebase (Crashlytics and Analytics; Analytics only after consent where the law requires it).

4. Accessibility Service Prominent disclosure

BotMaster Bulk Sender uses the Android AccessibilityService API. It uses it to open each chat and tap Send in WhatsApp or WhatsApp Business, for messages that you prepared and asked the App to send. This includes campaigns you start, the group sender, scheduled sends, and auto-replies you set up.

What it accesses: only the on-screen content of WhatsApp (com.whatsapp) and WhatsApp Business (com.whatsapp.w4b). The service is limited to these two apps in its configuration and cannot see any other app.

What we do not do: we do not collect, store, upload or share chat content, contacts or screen data obtained through the Accessibility Service. That data is used only for a moment, on the device, to find the message box and the Send button. It is not used for advertising, analytics or profiling, and it is never sold or transferred to anyone.

Your consent: before Android settings open, the App explains this in a disclosure screen and asks you to tap Agree. You can decline. Automatic sending will then not work, but the rest of the App still works.

What the service does

What the service does not do

How to turn it off

Go to Android Settings > Accessibility > Installed (or Downloaded) apps > BotMaster Bulk Sender and switch it off. Uninstalling the App also removes it.

5. Notification access (optional)

Notification access is optional. If you turn it on in Android settings, the App’s notification listener processes notifications from WhatsApp and WhatsApp Business only and ignores all other apps. For each such notification, the App reads the sender name, the latest message text and any phone number the notification provides, on the device, in order to:

Notification content is processed in memory and is not uploaded or shared. The App keeps only the result, such as the opt-out flag. You can turn notification access off at any time in Android Settings > Notifications > Device & app notifications (the name of this menu varies by device).

6. Google Sign-In and Drive backup (optional)

You can link a Google account to back up your App data. When you do, the App uses Google Sign-In and asks for your basic profile (name and email) and the drive.appdata scope. This scope lets the App read and write only its own hidden app folder in your Google Drive. It cannot see your other Drive files.

Google processes your account and Drive data under the Google Privacy Policy. The App’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

7. Permissions and why we need them

Permission / accessWhy the App needs itRequired?
Accessibility ServiceTo open chats and tap Send in WhatsApp / WhatsApp Business for messages you started (see section 4).Needed for automatic sending
Display over other apps (SYSTEM_ALERT_WINDOW)Shows a small bubble with progress and Pause / Skip / Stop controls while a campaign runs. Nothing from the overlay is collected.Needed for campaigns
Notification access (notification listener)STOP opt-out detection and auto-reply (see section 5).Optional
Contacts (READ_CONTACTS)Only when you tap From phone to add campaign recipients: reads names and phone numbers from your address book on the device so you can pick contacts. Only the contacts you select are saved in the App; your address book is not uploaded (see section 3).Optional
Post notifications (POST_NOTIFICATIONS)Shows campaign progress and status notifications, and app announcements sent with Firebase Cloud Messaging (see section 12).Optional
Foreground service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE)Keeps your send queue running while you use WhatsApp, with a visible notification you can stop.Needed for campaigns
Exact alarms (SCHEDULE_EXACT_ALARM)Starts campaigns you schedule for a specific time.Only for scheduled campaigns
Run at startup (RECEIVE_BOOT_COMPLETED)Restores your scheduled campaigns after the phone restarts.Only for scheduled campaigns
Wake lock (WAKE_LOCK)Keeps the phone awake during an active send so that sending is not interrupted.Automatic
Vibrate (VIBRATE)Vibration for the App’s campaign notifications.Automatic
Internet (INTERNET)Google Sign-In and Drive backup, Google Play purchases and the purchase check through RevenueCat, crash reports and usage analytics (Google Firebase), ads on the Free plan (Google AdMob), and opening web links.Automatic
Google Play Billing (com.android.vending.BILLING)Buying and restoring Premium through Google Play.Only for purchases
Advertising ID (com.google.android.gms.permission.AD_ID)Lets Google AdMob use your device’s advertising ID to show and measure ads on the Free plan (see section 10). Not used on Premium. You can reset or delete the advertising ID in Android settings.Automatic (Free plan ads only)
Battery optimisation settingsThe App may open your phone’s battery settings so that you can allow background use. It does not request the battery-exemption permission.Optional

Apart from the optional Contacts permission above, the App does not request access to your SMS, call log, location, camera, microphone or all files. Files are opened only through the Android file picker, one file at a time, when you choose them.

8. Files and sharing that you start

9. Crash reports, diagnostics and usage analytics

Crash reports (Google Firebase Crashlytics)

If the App crashes, it sends crash logs, diagnostics, and a device or Firebase installation id to Google Firebase Crashlytics so we can fix bugs. This includes the device model, operating-system version, a technical stack trace, the current and previous screen names (the route name only), the app version, the Android version, and that installation id. The same crash-log diagnostics also include plan (free or premium), app language, campaign state (idle, sending or paused), channel (WP or WB), whether accessibility and notification permission are on, the last action name, and build type. Google processes this data as our service provider, under the Google Privacy Policy and Firebase privacy information. We do not use it for advertising, and Crashlytics does not receive your advertising ID.

Crashlytics does not receive message text, contact names, phone numbers, email addresses or file names. The App does not set a Crashlytics user id. Custom fields stay inside crash logs and diagnostics: screen names, app version, Android version, plan, language, campaign state, channel, permission flags, last action and build type. There is no in-app screen to copy or share a crash report. Crash files saved by older versions of the App are deleted when you open this version.

Crash reporting is part of how the App runs. It is not a switch you can turn off inside the App.

Usage analytics (Google Analytics for Firebase)

To understand how the App is used and to improve it, the App uses Google Analytics for Firebase. It automatically collects screen views and sessions (for example, when the App is opened and how long it is used), in-app purchase and subscription events (product ID, product name and price), a random app-instance ID, and an approximate location (for example, country or city) that Google derives from your masked IP address. It also records technical details such as device model, Android version, app version and language.

Analytics does not receive message text, contact names, phone numbers, email addresses or file names. The App does not set an Analytics user id and does not send the advertising ID to Analytics. Analytics data is not used for advertising or ad personalisation: the App always sets ad storage, ad user data and ad personalisation consent to “denied” for Analytics.

Your choice. Where consent is required (for example in the EEA, the UK and Switzerland), analytics stays off until you agree in Google’s consent message (User Messaging Platform). You can change your choice at any time from Privacy & ad choices in the App. Elsewhere, analytics is on when you use the App.

Google processes this data as our service provider, under the Google Privacy Policy and Firebase privacy information. It is encrypted in transit.

10. Advertising

On the Free plan, the App uses Google AdMob to show banner and rewarded ads. Google may process advertising ID, device information, approximate location (from your IP address) and ad interactions under the Google Privacy Policy. Where required (including GDPR/EEA and certain US states), we collect consent with Google’s User Messaging Platform (UMP) before requesting ads. Premium users do not see or load ads. The App may still show its own Premium upgrade screens; those are not AdMob. You can open Privacy & ad choices in the App when Google requires a privacy options form.

You can reset or delete your advertising ID, or opt out of personalised ads, in Android Settings > Google > Ads or Settings > Privacy > Ads, depending on your device. Our Google Play Data safety section lists advertising ID and device identifiers shared with Google for AdMob on the Free plan.

11. Purchases and billing

Premium plans, when offered, are sold through Google Play Billing. Google processes your payment under the Google Privacy Policy. We never see or store your card or bank details. The App checks with Google Play whether you have an active purchase, so that it can unlock Premium. Purchases stay with your Google account, and you can restore them with Restore purchases. You can manage or cancel subscriptions in the Google Play Store under Payments & subscriptions.

RevenueCat. To check whether your Premium purchase is active and to restore it, the App uses RevenueCat, Inc. as our service provider. RevenueCat receives: the Google Play purchase details (product ID, purchase token, purchase and expiry dates, price and currency), a random app user ID that RevenueCat creates for this installation, and technical details such as device model, Android version, app version, language and your IP address. It does not receive your name, email address, contacts, phone numbers, messages or card details, and the App does not send your advertising ID to RevenueCat. RevenueCat processes this data on our behalf under the RevenueCat Privacy Policy and does not use it for advertising.

12. Network connections

The App connects to the internet only for:

The App has no BotMaster or Youhexa server that receives your data. Unencrypted (cleartext) network traffic is disabled.

13. Sharing, selling and use of data

14. Retention and deletion

BotMaster Bulk Sender does not create an account on any BotMaster server. All App data is on your phone, plus your optional Drive backup, so you control how long it is kept.

15. Security

Please keep your phone locked and protect exported files. No method of storage or transmission is 100% secure, but we design the App to keep your data on your device.

16. Children

BotMaster Bulk Sender is a business tool for adults. It is not directed at children and is intended only for users aged 18 or older. We do not knowingly collect personal data from children. If you believe a child has sent us personal data (for example by email), contact us and we will delete it.

17. Your rights (GDPR and India DPDP Act 2023)

Depending on where you live, you may have rights under laws such as India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”) or the EU/UK General Data Protection Regulation (“GDPR”). These may include the right to:

Most App data never reaches us, so you can use these rights directly in the App: view and edit it, export it as CSV or a backup file, or delete it (see section 14). For data we do hold, such as support emails, write to support@botmaster.software. We will respond within the time required by law.

Legal basis (GDPR): processing on your device is done to provide the features you ask for, based on our contract with you. Accessibility, notification access and Google Drive backup are based on your consent. Answering support emails is based on our legitimate interest in helping you.

Contacts you message: when you add other people’s details, you decide what is collected and why, and you are responsible for that use (see section 19). The App helps you respect their choices by honouring STOP opt-outs.

18. International users

We are based in India. Because App data stays on your device, it is not transferred to us. If you use Drive backup, your data is stored by Google, which may store it in other countries under its own safeguards. If you email us, your message is handled in India, with appropriate safeguards where the law requires them.

19. Your responsibilities and disclaimer

20. Changes to this policy

We may update this policy when the App changes or when the law requires it. We will post the new version on this page with a new “Last updated” date. For significant changes, such as adding a new ad network, a new analytics or billing provider, or a server, we will update this page and our Google Play Data safety section before the change takes effect.

21. Contact and grievances

Youhexa Technologies Pvt. Ltd.
2nd Floor, Apex Tower, Mahatma Gandhi Marg, Hazratganj,
Lucknow, Uttar Pradesh 226001, India
Email (privacy, data requests and grievances): support@botmaster.software
Website: youhexa.com · App: botmaster.software
Hours: Monday–Saturday, 10:00 AM–7:00 PM IST

Appendix: Data summary (Google Play Data safety)

This table matches our Google Play Data safety declaration. “Collected” means the data is sent off your device: to your own Google Drive if you turn on backup, to Google Firebase Crashlytics for crash logs and diagnostics, to Google Analytics for Firebase for usage analytics (after consent where the law requires it), to RevenueCat for purchase checks, and to Google AdMob for ads on the Free plan. “Shared” means transferred to a third party; the only shared data is what Google AdMob uses for ads on the Free plan (advertising ID and device identifiers, approximate location, app and ad interactions, and ad diagnostics). Google processes Crashlytics and Analytics data, and RevenueCat processes purchase data, as our service providers, so that data is not shared. All transfers use encryption in transit.

Data typeCollected?Shared?PurposeOptional?
Name (contact names you add; store name)Yes, only in your optional Drive backupNoApp functionality (backup and restore)Yes
Email address (Google account you link)Yes, used for Google Sign-In for backupNoApp functionality, account linking for backupYes
Phone numbers (contacts you add)Yes, only in your optional Drive backupNoApp functionality (backup and restore)Yes
Contacts (contacts you add or pick from your phone’s address book; lists, tags, opt-out status you create)Yes, only in your optional Drive backup. Your phone’s address book is read on the device only and is not uploadedNoApp functionality (backup and restore)Yes
Messages: templates and auto-reply text you writeYes, only in your optional Drive backupNoApp functionality (backup and restore)Yes
Other user-generated content (campaign names, send results)Yes, only in your optional Drive backupNoApp functionality (backup and restore)Yes
WhatsApp screen content (Accessibility)No, processed on device for a moment onlyNoTapping Send for your messagesYes (needed for automatic sending)
WhatsApp notification contentNo, processed on device onlyNoSTOP opt-out and auto-replyYes
Crash logsYes, sent to Google Firebase Crashlytics (stack trace, current and previous screen names, app version). No message text, names, phone numbers, emails or file namesNo. Google is a service providerApp functionality and AnalyticsNo
DiagnosticsYes, sent to Google Firebase Crashlytics (device model, OS version, plan, language, campaign state, channel, permission flags, last action, build type). On the Free plan, Google AdMob also collects ad performance diagnosticsYes, with Google AdMob on the Free plan only. For Crashlytics, Google is a service providerApp functionality, Analytics, Advertising or marketingNo
Device or other IDsYes, a Firebase installation id used to group crash reports, and a random Analytics app-instance id, and a random Firebase Cloud Messaging token used to deliver push notifications. The Firebase installation id is also used by Firebase In-App Messaging to pick in-app announcements. The advertising ID is not sent to Crashlytics or Analytics (for AdMob, see the advertising row below)No. Google is a service providerApp functionality and Analytics, Developer communications (push and in-app announcements)No
App interactions (screen views, sessions; on the Free plan also ads shown and taps on ads)Yes, sent to Google Analytics for Firebase and, on the Free plan, to Google AdMob. No message text, names, phone numbers or emailsYes, with Google AdMob on the Free plan only. For Analytics, Google is a service providerAnalytics, Advertising or marketing, Developer communications (choosing in-app announcements)No (consent applies where the law requires it; Premium has no ads)
Approximate locationYes, derived from your IP address (country or city level) by Google Analytics and, on the Free plan, by Google AdMob. Precise location is not collectedYes, with Google AdMob on the Free plan only. For Analytics, Google is a service providerAnalytics, Advertising or marketingNo (consent applies where the law requires it; Premium has no ads)
Purchase historyYes. In-app purchase and subscription events (product ID, product name, price) are sent to Google Analytics for Firebase, and purchase details (product ID, purchase token, dates, price) to RevenueCat to check and restore Premium. Payment details stay with Google PlayNo. Google and RevenueCat are service providersApp functionality (Premium) and AnalyticsNo (analytics consent applies where the law requires it)
User IDs (random app user ID)Yes, a random ID created by RevenueCat for this installation. It is not your name, email or phone numberNo. RevenueCat is a service providerApp functionality (Premium)No
Advertising ID and device identifiers (Free plan only)Yes, by Google AdMob, after consent where the law requires itYes, with Google AdMobAdvertising or marketingYes (Premium has no ads; you can reset or delete the advertising ID)
Precise location, payment info, photos, files, audioNoNoNot used (attachments stay on device)N/A

You can delete this data at any time in the App, or by deleting the hidden app data in Google Drive (see section 14).