Privacy Policy
Last Updated: November 12, 2026 · Compliant with Indian DPDP Act 2023 & Global GDPR Standards · Corporate Headquarters: Chennai, Tamil Nadu, India.
Strict PostgreSQL schema isolation prevents merchant data bleed.
Bank-grade encryption in transit and AES-256 encryption at rest.
We never sell, rent, or broker your transaction or customer data.
Full compliance with India's Digital Personal Data Protection Act.
1. Introduction & Scope
Billpoz Technologies (“Billpoz”, “we”, “us”, or “our”), registered and operating from Chennai, Tamil Nadu, India, is committed to safeguarding the privacy and integrity of your corporate and personal information.
This Privacy Policy outlines how we collect, process, store, and protect information when you utilize our cloud software, desktop POS (Electron), mobile POS applications (Android and iOS), and associated APIs.
2. Data We Collect & Classification
We differentiate between Merchant Account Data (which you provide to maintain your account) and Customer Transaction Data (which you process on behalf of your end consumers):
- Contact details: Legal business name, authorized representative name, phone number, and verified email address.
- Business & Tax Identifiers: GSTIN, PAN, ZATCA TRN, business address, and industry vertical.
- Authentication: Encrypted passwords, OTP tokens, and role-based access privileges.
- Invoicing records: Invoice numbers, itemized line items, bill amounts, applied tax rates, discounts, and payment methods (Cash, Card, UPI, Wallet).
- Customer phone numbers or emails collected solely for thermal/digital bill delivery and loyalty points.
- Cardholder Data: We do not store raw credit/debit card numbers or CVV codes; all digital card transactions are tokenized through RBI/PCI-DSS certified payment aggregators (e.g., Razorpay, Stripe, Paytm).
3. Multi-Tenant Database Isolation
Unlike basic multi-tenant billing apps that rely solely on row-level tenant IDs, Billpoz enforces Schema-Per-Tenant Isolation in PostgreSQL:
Every merchant store has its own dedicated schema (tenant_<your_tenant_code>). Your customers, products, inventory movements, shifts, and financial ledgers reside exclusively in your isolated schema. This architectural boundary makes cross-tenant data leakage technically impossible.
For desktop and mobile offline billing, the local SQLite database is encrypted on the device with a hardware-backed cryptographic key and synchronized securely over TLS 1.3 WebSockets.
4. Compliance with Indian DPDP Act 2023 & Global Regulations
In strict adherence to the Digital Personal Data Protection Act, 2023 (DPDP Act, India), the Information Technology Act, 2000, and the GDPR:
- Purpose Limitation: We process data solely for delivering billing operations, generating statutory tax reports (GST/ZATCA), and synchronizing hardware.
- Right to Erasure & Export: Merchants can export all inventory, sales, and customer ledgers in standardized formats (CSV, JSON, Excel) or request permanent schema purging upon subscription termination.
- Zero Secondary Monetization: We do not sell, rent, commercialize, or share your transaction records with data brokers or advertisers.
5. Data Storage, Localization & Security
Primary production databases and API gateways are hosted in secure enterprise-grade tier-IV data centers compliant with ISO 27001, SOC 2, and Indian data localization guidelines. All data in transit is encrypted using TLS 1.3, and data at rest is secured via AES-256 bit encryption.
6. Grievance Redressal & Jurisdiction (Chennai, India)
In accordance with the Information Technology Act, 2000 and DPDP Act, 2023 rules, the details of our designated Data Protection & Grievance Officer are:
Any dispute regarding this Privacy Policy or data processing shall be subject to the exclusive jurisdiction of the competent courts in Chennai, Tamil Nadu, India.