Last Updated: May 2026
Privacy Policy
At PrintLabX (operated under PrintLabX Automation Platforms Private Limited), we consider the privacy of our everyday users ("Consumers") and retail operators ("Sellers") to be absolute and foundational.
Unlike traditional cloud storage or internet infrastructure networks, PrintLabX is engineered as an ephemeral data conduit. We do not harvest, monetize, or permanently retain your digital file content. This Privacy Policy outlines exactly how we handle data transiting through our software layers (Automate), micro-hardware nodes (Pi), and automated self-service terminals (Kiosk).
1. The Zero-Retention Ephemeral Data Principle
Our core architecture enforces a strict data lifecycle policy to protect your personal documentation:
- In-Transit Encryption: When a User scans a localized PrintLabX QR code and uploads a file via their smartphone web browser, the payload is protected using industry-standard Secure Socket Layer (SSL/TLS) bank-grade encryption protocols.
- Insulated Caching: Documents are held in highly restricted, isolated temporary RAM or system cache locations on our cloud infrastructure purely for the duration of the rendering and print queue sequence.
- The Millisecond Purge Rule: The exact millisecond the local physical printing device spooler flashes a hardware confirmation handshake indicating successful physical output onto paper, our software executes an automatic, unrecoverable bitwise deletion command across the cache sector.
- No Retention: PrintLabX does not keep backup copies, historical archives, or recovery trails of your uploaded file contents. Once it prints, it is gone from our systems forever.
2. Information We Explicitly Collect
Because we do not require everyday users to create formal profiles or download applications, data capture is categorized into two clean streams:
A. Everyday Users (Print Customers)
We do not collect names, phone numbers, or email addresses for basic print jobs unless you explicitly fill out a manual customer care form. We capture only transient transactional metadata required to validate your order:
- System Session Metadata: Timestamp of the upload, file size, target page count, and your chosen print configurations (e.g., Color vs. Black & White, layout scaling factors).
- Location Mapping: The unique physical Station ID or QR code ID identifying the partner printer node executing your request.
- Payment Metadata: Gateway-generated Transaction IDs used to confirm successful digital wallet, card, or UPI settlements. We never see, store, or log your credit card numbers, CVVs, or UPI PINs.
B. Registered Sellers & Business Partners
To maintain business relationships and manage digital payouts, we securely archive:
- Merchant Credentials: Full name, registered corporate name, physical shop or corporate office addresses, and verified email or mobile contact points.
- Financial Settlement Profiles: Verified bank account configurations, IFSC codes, and associated tax indicators required to route automatic weekly financial earnings.
- Telemetry Logging: Continuous hardware operational states (online status, printer driver notifications, localized ink levels, and cumulative transaction counts) to display performance grids inside your encrypted Seller Dashboard.
3. How We Utilize Your Data
We process the limited metadata collected strictly for operational maintenance:
- To authenticate, calculate, and route precise consumer payment values through digital gateway processors directly to local seller bank nodes.
- To trigger automatic system health monitoring matrices, enabling our engineering team to detect localized printer jams, disconnected Pi modules, or offline Kiosk software hooks.
- To process and verify legitimate, time-bounded user support tickets or refund requests initiated within our 24-hour dispute window.
4. Third-Party Data Processing and Subprocessors
PrintLabX will never sell, lease, or distribute your operational information to marketing tracking agencies. Data is safely transited only through our vetted technical infrastructure partners:
- Payment Infrastructure Providers: Regulated third-party payment gateways (such as Razorpay or native UPI merchant switches) manage payment execution loops independently under strict compliance guidelines.
- Cloud Hosting Architectures: Encrypted cloud computing layers house our secure central websocket orchestrator nodes, operating under high-security server compliance models.
- Statutory Compliance Exceptions: PrintLabX may disclose metadata strings if explicitly requested to do so by formal legal warrants, courts of law, or regional regulatory enforcement bodies to satisfy overriding systemic security protocols.
5. Localized Caching and Token Management
- No Consumer Tracking Cookies: Our public mobile web application does not implement tracking cookies or cross-site behavior analytics tools.
- Transient Storage Tokens: We utilize minimal, isolated local storage tokens or active browser session values purely to preserve your active print file configuration choices while you navigate through our dynamic digital payment gateway window. These items disappear entirely when the browser session terminates.
6. Security Architecture Hardening
Our infrastructure teams maintain defensive measures designed to protect partner telemetry profiles and transient customer file blocks:
- Encapsulated software code barriers designed to isolate local Windows system printing buffers from unauthorized inspection loops.
- Cryptographic hardware-level profile locks deployed on our external PrintLabX Pi and PrintLabX Kiosk nodes to prevent unauthorized physical firmware extraction or remote code injection attacks.
7. Data Subject Rights & The Erasure Caveat
Under regional data protection frameworks, users generally maintain structural rights regarding access, deletion, and auditing profiles. However, due to PrintLabX's deliberate zero-retention infrastructure, a unique technical constraint applies:
Because customer document files are wiped automatically at the moment of physical printing, PrintLabX cannot process access requests, content audits, or manual deletion requests for your uploaded print content. We cannot delete or show you what we no longer possess.
For long-term stored information—such as a registered Seller's banking details or old support ticket metadata logs—partners can request corrections, account summaries, or permanent profile closures directly via the unified Enterprise Support interface.
8. Updates to this Policy
PrintLabX reserves the right to amend, update, or patch this Privacy Policy to mirror engineering optimization shifts or new legal mandates. Updates become binding the moment they are refreshed publicly on this portal. Users and partners are encouraged to routinely verify this page to monitor operational tracking rules.