Legal

Privacy Policy

Last updated: November 12, 2026

1. Introduction

Welcome to Reply.BD ("we", "our", or "us"), a product of Tarun Soft Pvt Limited, a company registered in Bangladesh with its registered office at 47, West Shewrapara, Mirpur, Dhaka-1216, Bangladesh.

We are committed to protecting your personal information and your right to privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform at reply.bd.

Please read this policy carefully. If you disagree with its terms, please discontinue use of our service.

2. Information We Collect

Connecting a WhatsApp Business number is not available yet. Where this policy mentions WhatsApp, it describes what will apply once we offer it.

2.1 Information You Provide

  • Account information: name, email address, phone number and password when you register. Your phone number also receives our service alerts by SMS (verification codes, new-lead and hand-off alerts, your daily summary).
  • Meta access tokens: when you connect your Facebook Page, its linked Instagram professional account or an ad account (and, once we offer it, a WhatsApp Business number), we store the access tokens Meta issues for them, and the token of the Facebook login you connect with (used to list your Pages and the businesses they belong to). They are encrypted at rest. We use them to send and receive messages on your behalf and to run the features you switch on.
  • Domain registration: if you buy a domain through us, the registrant's name, national ID (NID) number (encrypted at rest), phone number, e-mail and address, and the identity or trade-licence document you upload, which are passed to the domain registrar.
  • Product catalog: product names, descriptions, prices, and images you upload.
  • Settings: your bot's instructions, the facts and answers you teach it, and your reply preferences.

2.2 Information Collected Automatically

  • Conversations: messages exchanged between your business and your customers on Facebook Messenger, Instagram Direct and, once you can connect a number, WhatsApp, including a copy of the photos they send and the text of their voice notes (turned into text, not kept as audio), and the sent, delivered and read statuses Meta reports, are stored to power AI replies and your inbox.
  • Checkout details: what a shopper types on a business's website checkout before placing an order (name, phone number, e-mail, address), kept so the business can follow up, and used for one reminder SMS if the business switches that on.
  • A business's website: the orders its shoppers place (name, phone number, e-mail, address, and the shopper's IP address and browser), the accounts shoppers open there, the reviews they write (with their phone number and photo) and any customer list the business imports. To protect the business from fake orders, the website keeps a random device id in the shopper's browser, and each order stores it with a one-way hash of the device's screen and settings and the shopper's network address.
  • Payment SMS: if a business switches on automatic advance-payment checks, the bKash, Nagad or Rocket money-received text messages its phone forwards to us (with the payer's wallet number, the amount and the transaction id), kept to match payments to orders.
  • Customer identifiers: the ids Meta gives each customer (on Messenger a page-scoped id, on Instagram an Instagram-scoped id and username, on WhatsApp the customer's phone number, WhatsApp id and business-scoped user id), and the name and profile picture Meta shares, so that each customer's messages stay in one conversation.
  • Comments and lead forms: while comment automation is on, the ids, times and outcome of the comments on your posts (we do not keep the comment text); and the ids of submissions to your Facebook lead forms and, when you switch lead forms on, the answers people submit, which become leads in your dashboard.
  • Usage data: log data such as IP address, browser type, and pages visited for security and analytics purposes.
  • Conversion events: if a business adds its own Meta pixel, an event is sent from our servers to that pixel through Meta's Conversions API when a customer first messages the business, leaves their details or places an order (in a chat or on the business's website), for the business's own ad measurement. Names, phone numbers, e-mail addresses and city are hashed with SHA-256; the customer's Messenger or Instagram id, and for an order on the business's website the shopper's IP address and browser, are sent as they are. We do not send these events to any pixel of our own.

2.3 Information From Meta

When you connect a Facebook Page, we receive your Facebook user ID, page IDs, page names, and page-level access tokens via the Facebook Graph API, and the Instagram professional account linked to the Page. Once we offer WhatsApp, connecting a WhatsApp Business number will give us its phone number ID, the WhatsApp Business account it belongs to and an access token for it. We do not access your personal Facebook profile beyond what is required to list your Pages, your ad accounts and the businesses they belong to, and to connect them.

2.4 WhatsApp and Instagram

A business can connect an Instagram professional account today; connecting a WhatsApp Business number is not available yet, and the points below will apply to it once it is. When a business connects one to Reply.BD:

  • What we store: the messages and media exchanged with its customers; the customer's WhatsApp phone number and the ids Meta gives them (WhatsApp id and business-scoped user id, or Instagram-scoped id and username); the sent, delivered and read statuses Meta reports for each message; and the access token for the number or account, encrypted at rest.
  • Why: to write the business's automated AI replies and to show its conversations in its inbox, where the business's own people can answer; and for what the business switches on: saving the leads and orders a customer gives in the chat, with the messages that go with them (a text message to the customer, alerts to the business and to a dealer it lists), follow-up messages and order updates. We also use conversations to test and improve the quality of the bot's replies.
  • Payment to Meta: the business pays Meta directly for WhatsApp messaging, under its own WhatsApp Business account. We are not a party to that payment and we do not resell WhatsApp messaging.
  • Deletion: when the business disconnects the WhatsApp number, or the Facebook Page (which also removes its Instagram account's conversations), or asks us to delete its data, these messages, media, customer ids, statuses and tokens are deleted within 7 days (see Section 5). Orders and leads the business recorded from those chats, and the record of text messages sent about them (which can hold the customer's name, phone number and the Messenger or Instagram id they wrote from), are its own records: a disconnect leaves them in its account until it asks us to delete them or its account.
  • If you are a customer of a business: to have your messages deleted, ask that business, or write to us at [email protected] naming the business and the number or account you wrote from. We act on it within 7 days.

3. How We Use Your Information

  • To operate, maintain, and improve the Reply.BD platform.
  • To send automated AI replies to your customers via Facebook Messenger, Instagram Direct and, once we offer it, WhatsApp.
  • To display your conversation history and analytics in the dashboard.
  • To authenticate you and keep your account secure.
  • To communicate with you about service updates, billing, and support.
  • To send conversion events to a business's own Meta pixel, when it adds one, for its ad measurement (see Section 2.2).
  • To comply with legal obligations.

4. Sharing Your Information

We do not sell, trade, or rent your personal information. We may share data with:

  • AI service providers: the message context needed for a reply is sent to the AI service providers we use to write replies and to turn voice notes and photos into text.
  • Meta (Facebook, Instagram, WhatsApp): replies are sent back to customers through Meta's Messenger and Instagram APIs (and its WhatsApp API once we offer WhatsApp). Conversion events go to a business's own Meta pixel when it adds one (see Section 2.2). If a business connects an ad account and builds an audience from its own customers, their phone numbers are sent to that ad account hashed with SHA-256. All of this is subject to Meta's Privacy Policy.
  • SMS providers (Bangladesh): the customer's phone number and the text of each message (which can include the customer's name, the order number, the amount and the product) are sent to our SMS gateway to deliver the text messages the service sends for the business (a one-time verification code, a note that an inquiry was received, the order and lead updates the business turns on, a reminder about an unfinished checkout if the business switches that on) and the codes a shopper asks for on the business's website. Our alerts to the business about a new lead also carry the customer's name and phone number and what they asked for.
  • E-mail delivery provider: delivers the e-mails the service sends, including order and lead alerts to the business (with the customer's name, phone number and address) and lead e-mails to its dealers.
  • A business's dealers: if a business lists its dealers and switches lead e-mails on, the details of a lead (with the customer's name and phone number) are e-mailed to the dealer nearest the customer.
  • Courier companies: the customer's name, phone number and address when the business books a delivery with them, and the customer's phone number to check its delivery history with the couriers when an order is placed.
  • Payment gateways the business connects: the customer's name, phone number, e-mail address and delivery address for an online payment, and for some gateways the shopper's IP address.
  • Systems the business connects (such as its ERP): the orders it chooses to send there.
  • Domain registrar: when you register a domain through us, the registrant details and documents in Section 2.1 go to the .bd domain registrar we use, to register and verify the domain.
  • Cloudflare: our network provider. Traffic to our dashboard and API, and to businesses' websites (which Cloudflare hosts), passes through Cloudflare; it stores uploaded images (products, logos, media) on its R2 object storage under our data-processing agreement, and, where we switch it on, checks our forms for bots (Turnstile).
  • Hosting provider: the data centre in Bangladesh that hosts our servers, which processes data solely on our behalf.
  • Legal requirements: if required by law, court order, or governmental authority.

5. Data Retention

We retain your data for as long as your account is active or as needed to provide our services. You may request deletion of your account and associated data at any time (see Section 7). A Page's conversations belong to the business that connected it: conversations, media, customer ids and phone numbers, message statuses and access tokens from Facebook, Instagram and WhatsApp are deleted within 7 days of the business's valid data-deletion request, and those of a disconnected Page (with its Instagram account) or WhatsApp number within 7 days of the disconnect. A request made by removing Reply.BD from a Facebook account covers that person's Facebook user id and the tokens issued through their login, and those are deleted within 7 days (a token Facebook still honours stays with the business that uses it, for its Page or its ad account, until the business reconnects or disconnects it). All other personal data a request covers is removed within 30 days. Copies of any of this data in our backups are gone within 39 days. Orders and leads a business recorded, and the record of text messages sent about them (which can hold the customer's name, phone number and the Messenger or Instagram id they wrote from), stay in its account after a disconnect until it asks us to delete them or its account.

6. Security

We implement industry-standard security measures including:

  • Encryption at rest (AES-256) of the access tokens we receive when you connect a Facebook Page, an Instagram account, an ad account or your Facebook login (and a WhatsApp number, once we offer it).
  • HTTPS (TLS) for all data in transit.
  • HMAC-SHA256 signature verification for all Meta webhook payloads.
  • Hashed passwords (bcrypt) for user accounts.

No method of transmission over the internet is 100% secure. We strive to use commercially acceptable means to protect your data but cannot guarantee absolute security.

7. Your Rights & Data Deletion

You have the right to:

  • Access the personal data we hold about you.
  • Correct inaccurate data.
  • Delete your data — submit a request via our Data Deletion page or by emailing us.
  • Restrict or object to processing.
  • Port your data in a machine-readable format.

Facebook users may also request deletion by removing the Reply.BD app from their Facebook account settings: Facebook sends us the request, and we delete your Facebook user id and the tokens issued through your login within the times in Section 5. A token Facebook still honours stays with the business that uses it, for its Page or its ad account, until the business reconnects or disconnects it. The conversations of a Page you connected belong to the business: they are deleted when it disconnects the Page or asks us to delete its data.

If you messaged a business that uses Reply.BD (on Messenger, Instagram or WhatsApp), ask that business to delete your messages, or write to us at [email protected] naming the business and the number or account you wrote from. We act on it within 7 days.

8. Cookies & Tracking

Our dashboard uses a session cookie and a CSRF cookie to keep you logged in and protect your forms, and a device cookie (kept for up to a year) to recognise your devices and protect your account.

Our public pages (the homepage, the blog and these legal pages) may load Google Tag Manager, Google Analytics and the Meta Pixel, which set analytics and advertising cookies (such as _ga and _fbp) to measure visits and our own advertising. You can block them in your browser's settings or with a tracker blocker.

Separately from cookies, conversion events may be sent from our servers to a business's own Meta pixel through the Conversions API, as Section 2.2 describes. A business's website keeps a random device id in its visitors' browsers (a first-party cookie, rbd_dev, kept for up to two years, and browser storage) to protect the business from fake orders (see Section 2.2). It may also load, in its visitors' browsers, that business's own Meta Pixel, its Google Tag Manager container and any other code the business adds to its site.

9. International Data Transfer

Our servers are located in data centres operated by our hosting providers. Data submitted by EU/UK residents may be transferred outside the European Economic Area. Where such transfers occur, we rely on standard contractual clauses or other lawful mechanisms to protect your data.

10. Third-Party Links

Our platform may link to third-party sites. We are not responsible for the privacy practices of those sites and encourage you to review their policies.

11. Children's Privacy

Reply.BD is not directed to individuals under the age of 16. We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal data, please contact us and we will remove it.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new policy on this page with an updated date. Continued use of the service after changes constitutes acceptance.

13. Contact Us

If you have questions about this Privacy Policy or wish to exercise your rights, please contact us at: