Effective Date: October 12, 2026 • Governed by DPDPA 2023 & IT Act 2000
Official Privacy Statement & Regulatory Disclosures:
This document outlines the privacy commitments and data protection protocols of Conbova (Sole Proprietorship) ("Conbova", "Platform", "We", "Us"). It sets forth the handling, storage, and processing standards for merchant account credentials and storefront visitor telemetry.
Conbova is a multi-tenant cloud-hosted Software-as-a-Service (SaaS) platform that enables registered users ("Merchants") to create, host, and operate e-commerce storefronts and lead generation websites.
Under the Information Technology Act, 2000, and the Digital Personal Data Protection Act, 2023 ("DPDPA"):
A. Information Provided by Merchants:
Account creation data (Full name, business email, mobile phone number, store name, custom domain configurations, product catalogs, and service descriptions).
B. Information Captured via Merchant Websites (Lead Gen & E-Commerce):
When prospective buyers or clients submit quotes, inquiries, or purchase orders on a merchant storefront, the platform captures contact details (Name, WhatsApp number, Email, Service/Product interested, Delivery address) solely for transmission to the Merchant's authenticated CRM dashboard.
C. Technical & Edge Telemetry:
IP addresses (anonymized for geographic node display on the live radar), browser type, device resolution, and referrers for server uptime and Edge CDN caching.
Conbova enforces a strict 0% platform commission policy. Conbova does not hold, escrow, or intermediate end-customer funds. Payments processed on Merchant stores execute directly via the Merchant's own payment credentials (or Cash on Delivery / Direct WhatsApp UPI), settling straight into the Merchant's bank account.
All network communication between visitors, merchants, and Conbova servers is encrypted in transit using industry-standard 256-bit SSL/TLS protocols. Database records are strictly partitioned and isolated across our multi-tenant cloud architecture, ensuring complete merchant data segregation and preventing unauthorized cross-tenant access. Sensitive credentials, payment tokens, and webhook secrets are encrypted at rest using high-grade authenticated encryption.
In accordance with Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, and the Digital Personal Data Protection Act, 2023, designated contact details are provided below:
Contact Person: Vishal
Designation: Founder & Sole Proprietor
Official Email: [email protected]
Business Entity: Conbova (Sole Proprietorship)
Operational Region: Gonda, Uttar Pradesh, Republic of India
Acknowledgment Time: Within 24 to 48 hours of receipt
Resolution SLA: Within 15 to 30 business days, in compliance with statutory intermediary guidelines
Merchants operating stores on Conbova act as independent Data Controllers for their end-customers. Conbova provides pure cloud infrastructure and does not own, process, or assume liability for customer records, order fulfillment, payments, or commercial disputes handled by individual merchants. Any dispute or grievance regarding merchant store conduct or goods sold must be addressed directly to that respective merchant.
Operational Authority: The Sole Proprietor (Vishal) reserves the unilateral right to suspend, discontinue, or retire the platform and cloud server infrastructure in accordance with business or technical requirements.
Storefront Deactivation: In the event of service discontinuation or permanent platform retirement, hosted merchant websites, subdomains, and customer portals cease operation.
Subscription Fees & 24-Hour Refund Policy: All paid plans include a 24-Hour Customer Satisfaction Policy. Subscribers dissatisfied with the service who request a refund within 24 hours of purchase receive a 100% full refund (reverting to the Free tier). After 24 hours from purchase or in the event of subsequent platform retirement, subscription fees remain strictly non-refundable, as detailed in our Cancellation & Refund Policy.
Data Sanitization: Upon permanent service retirement, merchant and operational records are purged in accordance with standard cloud database decommissioning protocols.