Official Legal Policy · Effective & Compliant

Privacy Policy & Data Protection Terms

How BizBot collects, processes, protects, and handles customer orders, chat transcripts, payment settlements, and analytics across WhatsApp, Telegram, and Web Storefronts.

Last Updated: October 2026 • Jurisdiction: Republic of Ghana (Act 843) & Global Standards (GDPR) • Platform: WhatsApp Cloud API & Telegram Bot API

1 Scope & Defined Legal Roles

This Privacy Policy sets forth the terms under which BizBot (operating at bizzbot.tech, hereinafter referred to as "BizBot", "we", "our", or "the Platform") processes personal, commercial, and telemetry data.

Depending on your relationship with the Platform, our legal classification under data protection laws (including the Ghana Data Protection Act, 2012 (Act 843) and the EU General Data Protection Regulation (GDPR)) is as follows:

  • For Merchants / Store Owners: BizBot operates as a Data Controller with respect to your merchant account details, subscription payment records, and administrative dashboard access.
  • For Shoppers / End-Customers: The respective Merchant is the independent Data Controller of buyer personal data (customer name, delivery address, phone number, order preferences). BizBot operates as a Data Processor (Service Provider) acting strictly on the merchant's instructions to automate customer ordering, calculate cart subtotals, route payment requests, and dispatch order status notifications.

2 Specific Information We Collect

We collect and process only the minimum information necessary to execute commerce transactions across our supported channels:

A. Customer / Shopper Data

  • Phone Number (MSISDN): WhatsApp sender phone number in international E.164 format (e.g. +23324XXXXXXX) or alternate contact number provided during checkout.
  • Telegram Identifiers: Telegram numeric user ID, chat ID, and Telegram username where applicable.
  • Name & Profile Information: Customer name supplied during checkout or public profile display name from WhatsApp/Telegram.
  • Delivery Details & GPS Pins: Physical street addresses, landmark descriptions, delivery notes, and GPS latitude/longitude coordinates when the customer shares a WhatsApp location pin for fulfillment.
  • Order Data: Selected items, product variants, order notes, total amounts, currency (e.g., GHS), and fulfillment preferences (Delivery vs. Store Pickup).
  • Chat Transcripts: Inbound and outbound message text exchanged with the store bot to maintain conversational session context and track cart changes.

B. Merchant / Business Owner Data

  • Account Identity: Business name, unique store slug, category/vertical, owner full name, official email address, and account phone number.
  • Payout & Financial Settings: Mobile Money payout phone number (MTN MoMo, Telecel Cash, AT Money) and payment gateway subaccount codes for automated split settlements.
  • Product Catalog: Product names, descriptions, images, variant dimensions, pricing tiers, and inventory stock counts.
  • Credentials: Cryptographically hashed passwords (using bcrypt with work factor 12). Raw passwords are never visible or stored in plain text.

C. Telemetry, Usage & Technical Logs

  • Meta WhatsApp Telemetry: Meta message IDs (`wamid`), webhook delivery timestamps, delivery status receipts (`DELIVERED`, `READ`), and conversation categories (`SERVICE` vs. `MARKETING`).
  • System Logs: IP addresses, HTTP headers, browser user agents, and session cookies for web storefront visits to detect fraud and prevent denial-of-service abuse.

3 How We Use Data & Analytics (Strict Boundaries)

To protect both our merchants and their shoppers, BizBot operates under strict, legally binding data usage parameters:

1. Individual Merchant Store Analytics

We process order volume, transaction totals, and stock consumption solely to provide the merchant with their own sales metrics, inventory alerts, and order management dashboard. A merchant can only view their own store’s metrics.

2. Aggregated & Anonymized Platform Benchmarking

We may compute high-level, statistical platform insights (such as average order values across retail categories, peak ordering hours in Accra, or messaging latency averages). This data is completely stripped of all Personal Identifiable Information (PII) and cannot be reverse-engineered to identify any individual shopper or business.

3. Absolute Prohibition on Data Selling & Advertising

BizBot DOES NOT sell, license, rent, trade, or transfer shopper phone numbers, purchase histories, or personal data to third-party advertisers, data brokers, or marketing networks. We do not inject third-party advertising into WhatsApp or Telegram bot chats.

4. Multi-Tenant Database Isolation

Every merchant's catalog, orders, and customer records are isolated using database foreign keys and software tenant boundaries. Merchants cannot query or inspect the customers or revenue of competing stores.

4 Lawful Bases for Data Processing

Under Section 18 of the Ghana Data Protection Act (Act 843) and Article 6 of the GDPR, BizBot processes personal data under the following legitimate grounds:

  • Performance of a Contract: Necessary to register merchant accounts, display store catalogs, process items in carts, calculate delivery fees, generate Mobile Money payment authorization links, and deliver order receipts.
  • Legitimate Interests: Necessary to ensure platform uptime, prevent duplicate webhook replays via Redis caching, detect payment fraud, and protect against malicious cyberattacks.
  • Legal & Statutory Compliance: Retaining records of financial payments, settlement logs, and billing invoices to satisfy accounting, audit, and tax authorities (e.g. Ghana Revenue Authority).
  • Consent: When merchants broadcast marketing updates or promotional campaigns to opt-in customer lists via WhatsApp Cloud API.

5 Third-Party Infrastructure & Sub-Processors

BizBot partners with industry-standard, security-certified technology providers to execute platform operations:

Meta Platforms, Inc. Provides the official WhatsApp Cloud API infrastructure. Inbound and outbound WhatsApp messages pass through Meta servers in accordance with Meta's Data Policy.
Telegram FZ-LLC Provides the Telegram Bot API infrastructure. Inbound updates and bot messages travel over Telegram's encrypted bot network.
Paystack Payments Limited PCI-DSS Level 1 certified payment gateway. Processes Mobile Money and Card transactions. BizBot never stores debit card numbers, CVVs, or bank PINs.
Flutterwave Inc. PCI-DSS compliant secondary payment processor for alternative Mobile Money routes and merchant subscription settlements.

6 WhatsApp & Meta Policy Compliance

BizBot strictly implements the Meta WhatsApp Business Messaging Policy and Commerce Policy:

  • Customer Service Window: Inbound conversations initiate a standard 24-hour service conversation window during which the store bot assists with product queries, cart building, and order checkout.
  • Opt-In Consent for Marketing: Merchants using BizBot broadcast features represent and warrant that all targeted recipients have explicitly provided opt-in consent to receive promotional messages from the merchant's business.
  • Spam Prohibition: Merchants are strictly forbidden from uploading scraped, purchased, or unauthorized phone number lists. Accounts flagged by Meta for spam or excessive user blocking will be suspended immediately.
  • Prohibited Products: The platform may NOT be used to sell prohibited goods, including firearms, tobacco, illegal drugs, prescription medications without authorization, or counterfeit goods.

7 Data Security & Safeguards

We deploy robust enterprise security safeguards to prevent accidental loss, unauthorized access, alteration, or disclosure of personal data:

  • Encryption in Transit: All HTTP traffic to and from BizBot web storefronts, APIs, and webhooks is strictly enforced over HTTPS using TLS 1.3 encryption.
  • Cryptographic Webhook Signatures: Inbound Meta webhooks are cryptographically authenticated via HMAC-SHA256 signature checks (`X-Hub-Signature-256`) against our private app secret to prevent spoofed payloads.
  • Encrypted Database Secrets: Sensitive merchant access tokens, webhook verify tokens, and payment API keys are encrypted at rest using Laravel's AES-256-CBC envelope encryption.
  • Idempotency & Replay Protection: Message IDs are validated against a 48-hour deduplication cache window to eliminate replay attacks and duplicate order charges.

8 Data Retention & Deletion Policy

We retain personal information only for as long as required to fulfill the purposes for which it was gathered, in accordance with the Ghana Data Protection Act (Act 843):

  • Cart Sessions & Temporary Drafts: Unfinalized cart draft sessions are retained for active browsing and automatically purged after 30 days of inactivity. Shoppers can erase active carts and delivery addresses instantly by replying DELETE MY DATA or CLEAR CART in chat.
  • Order Records & Statutory Financial Retention: Order records, transaction references, invoices, and fulfillment logs are retained in encrypted storage for statutory audit compliance (up to 6 years) as mandated by financial regulations and tax laws.
  • Merchant Account & Store Closure: When a merchant closes their store via Settings > Danger Zone, product catalogs, categories, API credentials, and webhooks are permanently purged immediately. If the user account is closed, personal profiles are completely erased.
Detailed Deletion Instructions: For full, step-by-step instructions for Meta WhatsApp, Telegram, and Merchant account deletion, visit our public User Data Deletion Instructions Page.

9 Data Subject Rights (Your Rights)

Under applicable data protection laws, individuals enjoy statutory rights concerning their personal data:

  • Right of Access: You may request confirmation of what personal data is held about you and receive a readable copy.
  • Right to Rectification: You may correct inaccurate or incomplete phone numbers, addresses, or profile details.
  • Right to Erasure (Right to be Forgotten): You may request the deletion of your personal contact records, subject to statutory retention requirements for financial auditing.
  • Right to Withdraw Consent: Customers may opt out of promotional messages from a merchant at any time by replying *STOP* or contacting the merchant.

Shoppers seeking to exercise rights regarding a specific merchant order should contact that merchant directly as the Data Controller, or reach our Data Protection team at privacy@bizzbot.tech.

10 Liability Limitations & Merchant Warranties

⚠️ Crucial Legal Disclaimer:

BizBot is a software infrastructure provider, not a seller of goods. We do not manufacture, package, inspect, store, or physically dispatch products sold by merchants.

The merchant is solely responsible for fulfilling customer orders, resolving product defects, handling returns, collecting sales taxes, and ensuring truth in advertising. BizBot disclaims all liability for merchant-customer disputes regarding product quality, delayed delivery, or inaccurate catalog pricing.

Merchant Indemnification: Each merchant agrees to indemnify, defend, and hold harmless BizBot and its operators from any claims, regulatory penalties, or legal fees resulting from the merchant’s violation of consumer protection laws, spamming, or data privacy breaches.

11 Contact & Data Protection Officer

If you have questions, inquiries, or complaints regarding this Privacy Policy or our data processing practices, please contact our Data Protection Officer:

Entity: BizBot Commerce Platform

Data Protection Officer: Legal & Compliance Team

Email: privacy@bizzbot.tech / legal@bizzbot.tech

Physical Address: Accra, Greater Accra Region, Republic of Ghana

Regulatory Body: Data Protection Commission of Ghana (Act 843)