At Robotic Partner, information security and merchant privacy are core engineering imperatives. This Privacy Policy details how our automated recharge platform ingests, encrypts, and isolates telecom transaction data, operator telemetry, and credentials.
1. Information We Collect
We collect strictly necessary operational data required to authenticate B2B users and execute recharge automation requests across Indian telecom networks:
- Merchant Identifiers: Unique username (minimum 4 characters), legal full name, verified business email, and verified mobile number.
- Network Target Data: 10-digit Indian recipient mobile numbers, operator code (01 Airtel, 02 Jio, 03 Vi, 04 BSNL), circle ID, and plan denomination.
- Hardware Bridge Telemetry: Lapu device serial numbers, battery health percentages, cellular signal metrics (dBm), and carrier slot indexes.
2. Hardware MPIN & Credential Vault (Rule 07)
Carrier Lapu SIM MPINs are never stored in plaintext. All SIM pins are sealed inside our hardware key vault using authenticated AES-256-GCM encryption with unique Initialization Vectors (IVs) and 128-bit authentication tags. Passwords utilize HMAC-SHA256 peppering with adaptive bcrypt rounds.
3. Mandatory Geolocation & Proximity Binding
During sign in and account onboarding, our security runtime captures browser GPS coordinates and client IP addresses. Geolocation telemetry protects merchant float balances by enforcing session proximity boundaries and detecting credential stuffing from unauthorized regions.
4. Double-Entry Ledgers & Transaction Audits
Recharge requests trigger atomic wallet holds logged with high-resolution microsecond timestamps. Transaction history is stored in an immutable Microsoft SQL Server ledger with dual-entry balancing, ensuring every debit, credit, or automatic timeout reversal has a cryptographic audit trail.
5. Strict Zero Third-Party Sharing (Rule 02)
Robotic Partner does not sell, license, or share user data, merchant client lists, or transaction metrics with external advertising networks, data brokers, or competitor platforms. Transaction payloads are dispatched exclusively to the destination cellular network operator (Airtel, Jio, Vi, BSNL).
6. Regulatory Compliance & Data Retention
Telecom billing records and operator Reference IDs (RP_*) are retained in accordance with applicable Indian financial and statutory regulations. Merchants can request cryptographic deletion of obsolete API keys and session tokens upon written verification.