FeedBot Chrome extension Privacy Policy

Effective date: October 11, 2026

This Privacy Policy explains how FeedBack Software LTD ("FeedBot", "we", "us", or "our") collects, handles, stores, and shares information through the FeedBot: WhatsApp Bulk Messaging Chrome extension (the "Extension") and related FeedBot services.

1. Summary

The Extension works inside WhatsApp Web (web.whatsapp.com) and helps users perform actions such as bulk messaging, scheduled messages, contact export, chatbot replies, labels, opt-out management, and API-based message sending.

To provide these features, the Extension accesses certain information from WhatsApp Web and from the user's browser.

Most WhatsApp-related information is processed locally in the user's browser and is not sent to FeedBot.

Some information is sent to and stored on FeedBot servers where this is necessary to provide account, licensing, API, chatbot, label, opt-out, or support functionality.

We do not sell or rent personal data. We do not use personal data for advertising, marketing profiles, creditworthiness, or unrelated purposes.

2. Information the Extension accesses

The Extension runs on WhatsApp Web and may access information that WhatsApp Web has already loaded in the browser, including:

  • WhatsApp contacts and phone numbers;

  • contact and group names;

  • group participants;

  • chat identifiers;

  • incoming and outgoing message content;

  • profile-picture links;

  • WhatsApp language and display preferences.

The Extension also uses Chrome browser functionality, including:

  • Google Sign-In through Chrome Identity;

  • Chrome extension storage;

  • Chrome Sync storage;

  • browser IndexedDB storage;

  • the Tabs API to locate and focus the WhatsApp Web tab.

Tab URLs are checked only to identify WhatsApp Web and are not stored or transmitted to FeedBot.

3. Data processed locally on your device

The following information is primarily processed locally in your browser:

WhatsApp contacts and groups

The Extension may read:

  • contact names;

  • WhatsApp display names;

  • phone numbers;

  • group names;

  • group participants.

This information is used for recipient selection, bulk messaging, group functionality, and contact or participant export.

Contact information is normally kept temporarily in browser memory. If you export information to Excel, the resulting file is saved by your browser to your device.

FeedBot does not upload your full WhatsApp contact list or group list to its servers.

Incoming WhatsApp messages

Incoming messages may be read locally in order to:

  • match chatbot rules;

  • detect an opt-out keyword;

  • determine whether an automated reply should be sent.

Incoming message text is not uploaded to FeedBot for chatbot matching.

If a chatbot response is sent, a local activity log may contain the sender's phone number, incoming message text, reply text, and timestamp.

Bulk messages and attachments

Bulk-message content may come from:

  • text entered by the user;

  • CSV or Excel files;

  • pasted phone lists;

  • contacts or groups;

  • files attached by the user.

This information may be temporarily stored in browser IndexedDB while the sending process is active.

Bulk-message content and attachments are sent to WhatsApp through the user's active WhatsApp Web session. They are not uploaded to FeedBot's servers as part of the regular bulk-send feature.

Message templates and activity logs

The Extension may locally store:

  • message templates;

  • sending activity;

  • recipient information;

  • message content;

  • delivery results;

  • last-sent timestamps.

These records are stored in browser IndexedDB and may remain there until the user clears the relevant browser site data.

Scheduled messages

Scheduled messages may include:

  • recipient name or identifier;

  • phone number or chat ID;

  • message content;

  • scheduled time;

  • image link;

  • send status.

Scheduled messages are stored using Chrome's extension sync storage.

If Chrome Sync is enabled, Google may sync this data through the user's Google account. FeedBot does not receive this Chrome Sync data.

4. Information sent to FeedBot servers

Certain features require information to be transmitted to FeedBot's backend services.

Account information

When you sign in with Google, FeedBot may receive:

  • your Google account email address;

  • email verification status;

  • your Google profile name.

This information is used to identify your account, verify your subscription or license, and provide account-related functionality.

Google OAuth access token

A short-lived Google OAuth access token is used to verify your Google identity.

The token may be transmitted to FeedBot's backend for verification.

FeedBot does not store the Google OAuth access token on its servers.

Your WhatsApp phone number

The Extension may obtain your own WhatsApp phone number from WhatsApp Web.

It may be sent to FeedBot in order to associate the WhatsApp account with your FeedBot account and enforce plan or account limits.

Labels and recipient lists

If you use FeedBot labels, FeedBot may store:

  • label names;

  • recipient phone numbers;

  • WhatsApp group IDs.

This allows saved recipient lists to be reused.

Opt-out lists

FeedBot may store phone numbers of recipients who should no longer receive messages.

A number may be added to an opt-out list:

  • manually;

  • from the current chat;

  • automatically when an enabled opt-out keyword is received.

The opt-out list is used to prevent future messages to those recipients.

Chatbot configuration

If you use chatbot features, FeedBot may store:

  • chatbot trigger phrases;

  • reply text;

  • match settings;

  • operating settings;

  • opt-out keywords.

Incoming WhatsApp message text is processed locally for matching and is not uploaded to FeedBot as part of normal chatbot matching.

API-mode messages

If you use FeedBot API mode, your own systems may submit messages to FeedBot's servers.

This may include:

  • message ID;

  • recipient phone number;

  • message text;

  • image link;

  • expiration time;

  • delivery status.

The Extension retrieves those messages, sends them through WhatsApp Web, and reports whether each message was successfully sent or failed.

If WhatsApp Web is closed or reloaded before all pending API messages are sent, unsent API messages may be returned to FeedBot's servers for later processing.

Usage and error information

FeedBot may receive:

  • last activity timestamps;

  • message delivery status for API-mode messages;

  • technical error messages;

  • stack traces;

  • file names;

  • browser user-agent information;

  • timestamps.

This information is used for service operation, support, diagnostics, and error resolution.

5. How we use information

We use information only for purposes necessary to operate and support FeedBot, including:

  • account authentication;

  • license and subscription validation;

  • linking authorized WhatsApp accounts;

  • sending messages requested by users;

  • managing labels and recipient lists;

  • honoring opt-out requests;

  • operating chatbot features;

  • processing API-mode messages;

  • maintaining service reliability;

  • diagnosing technical problems;

  • providing customer support.

We do not use personal data for unrelated advertising or profiling.

6. Google user data

The Extension uses Google Sign-In and requests Google profile information needed for authentication.

FeedBot uses Google user information only for the purposes described in this Privacy Policy.

FeedBot's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including Limited Use requirements.

7. Sharing and service providers

We do not sell, rent, or trade personal information.

Information may be processed by the following service providers where necessary:

Google Cloud

FeedBot's backend services are hosted on Google Cloud, including Cloud Run / Cloud Functions.

FeedBot uses Google Cloud Firestore to store server-side application data described in this Privacy Policy.

Google Identity

Google provides authentication services used for Google Sign-In.

Google Chrome Sync

If Chrome Sync is enabled, Chrome may sync extension settings and scheduled-message information through the user's Google account.

FeedBot does not receive data stored solely through Chrome Sync.

WhatsApp / Meta

Messages and attachments are delivered through the user's own WhatsApp Web session.

WhatsApp may also receive phone numbers when the user asks FeedBot to validate whether a number is registered on WhatsApp.

Profile-picture requests are also handled through WhatsApp.

Image hosting providers

If a user provides an image URL, the Extension may request that image directly from the website hosting it.

That website may receive standard network information such as the user's IP address and browser user-agent.

Legal requirements

We may disclose information if required to do so by applicable law, court order, or lawful government request.

8. Data storage and retention

Data stored locally

Some information is stored in Chrome extension storage or browser IndexedDB.

Chrome extension storage is normally removed when the Extension is uninstalled.

Certain data stored in WhatsApp Web's IndexedDB may remain after the Extension is uninstalled because it is stored within the browser storage associated with web.whatsapp.com.

This may include:

  • activity logs;

  • chatbot logs;

  • last-sent records;

  • message templates;

  • temporary bulk-message data.

Users may remove this information by clearing site data for web.whatsapp.com. Clearing this data may also sign the user out of WhatsApp Web.

Data stored on FeedBot servers

FeedBot stores server-side information for as long as it is necessary to provide the applicable FeedBot service or account functionality.

This may include:

  • account information;

  • WhatsApp account identifiers;

  • labels;

  • opt-out lists;

  • chatbot settings;

  • API-mode messages;

  • activity information;

  • error reports.

Users may request deletion of their server-side personal data by contacting FeedBot.

When a valid deletion request is received, FeedBot will delete the user's personal data, subject to any information that must be retained to comply with legal obligations.

9. IP addresses

FeedBot does not intentionally store users' IP addresses as part of its application data.

Standard infrastructure providers may temporarily process network information as necessary to deliver internet services.

10. Security

FeedBot uses reasonable technical measures designed to protect information.

These measures include:

  • HTTPS/TLS encryption for communication with FeedBot servers;

  • authenticated backend requests;

  • Google identity verification;

  • limiting server-side data use to FeedBot functionality.

No system of electronic transmission or storage can be guaranteed to be completely secure.

11. User choices and deletion

Users may manage or delete certain information directly through the Extension, including:

  • scheduled messages;

  • chatbot rules;

  • labels;

  • label recipients;

  • opt-out entries.

Users may revoke FeedBot's Google access through their Google Account settings.

Users may remove extension storage by uninstalling the Extension.

Users may remove FeedBot-related IndexedDB data stored under WhatsApp Web by clearing the site data for web.whatsapp.com.

Users may request:

  • access to their server-side personal data;

  • correction of their data;

  • deletion of their data.

Requests can be sent to:

*[email protected]

12. Information about other people

FeedBot users may process information relating to other people, including:

  • contact names;

  • phone numbers;

  • group membership;

  • message recipients.

Users are responsible for ensuring that they have an appropriate legal basis to contact recipients and for complying with applicable privacy, marketing, anti-spam, and communications laws.

Users are also responsible for honoring opt-out requests.

13. Children

FeedBot is not intended for use by children under the age of 16.

14. International processing

FeedBot's infrastructure is hosted using Google Cloud services in the United States.

Information may therefore be processed outside the user's country of residence.

15. No affiliation with WhatsApp

FeedBot is an independent product and is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta.

16. Changes to this policy

We may update this Privacy Policy from time to time.

When we do, we will publish the updated version on this page and update the effective date.

17. Contact

For privacy questions or data-deletion requests:

FeedBack Software LTD
Email: [email protected]