Effective Date: June 22, 2026

Our Commitment to
Absolute Transparency.

Privacy isn't just legalese—it's a system feature. Explore how the ConvaPDF mobile applications, inkless hardware models, and cloud webhook API channels protect your commercial transactional details.

PRIVACY SANDBOX

Customized Data Collection Consent

Toggle permissions below to simulate how the local mobile device app maps diagnostic payloads. We prioritize local processing over remote cloud retention pipelines.

Bluetooth Diagnostics Metrics

Stores local pairing timestamps and Signal Strength (RSSI) indicators for BLE connectivity troubleshooting.

Single-Bit PDF Caching

Temporarily buffers generated document rasters to high-speed local device storage to prevent packet drops during multiple copies print flows.

Cloud API Webhook Event Logs

Saves anonymous transaction logs inside Cloud Suite to verify successful merchant order execution triggers.

Simulated Sandbox Device Output

                    
Enter query to parse text
01 /

General Scope & Philosophy

ConvaPDF Tech Group designs physical-digital bridges using inkless micro-controllers, standard Android files compilation APIs, and SwiftUI iOS TestFlight pipelines. We maintain an offline-first operational philosophy: the majority of print conversion metrics, vector layouts, and PDF parsing cycles are completed on-device.

We do not run advertising-supported platforms or monetize client transaction histories. Our business model relies purely on professional thermal hardware sales, custom-branded paper supplies, and SaaS Enterprise Cloud Suite parameters.

02 /

Information We Collect

When operating our mobile interfaces or utilizing cloud automation streams, the system monitors distinct categories of operational metadata depending on your active integrations configuration permissions:

  • Account Identifiers: Name, Apple ID or Google email references used to authenticate TestFlight passes, custom cloud API tokens, and purchase orders.
  • Local Document Assets: PDF files or custom image layouts processed for printing. These vector rasters are converted directly on the hardware side and are not transmitted to ConvaPDF corporate repositories.
  • IoT Device Identifiers: Serial numbers, Mac addresses, and battery temperature diagnostics for paired ConvaPrinter 57mm hardware.
03 /

Data Usage & Webhook Framework

If using the ConvaPDF Cloud Suite endpoints, our system ingests parameters from third-party webhook integrations (including Shopify store databases, Stripe billing hooks, and customized developer triggers).

These incoming data pipelines are ingested strictly to construct corresponding layouts for remote print nodes. Incoming payloads are stored with absolute encryption (TLS 1.3 protocol) and automatically purge from diagnostic caches within twenty-four hours of successful print execution.

04 /

Bluetooth BLE & Local Security

Our pocket printers connect over Bluetooth Low Energy (BLE 5.2). To run scanning loops on certain mobile versions, standard OS platforms require access to Fine Location permissions.

  • Location Data Scope: ConvaPDF applications do not process, catalog, or transmit your device's geographical GPS coordinate coordinates. Location permissions are used strictly to scan BLE channels.
  • Handshake Encryption: All direct print queues transmitted between your phone client and the thermal printhead employ automated operational encryption algorithms, preventing adjacent signal tracking.
05 /

Your Privacy Rights (GDPR & CCPA)

Regardless of your geography, ConvaPDF provides equal transparency parameters globally. Under standard protections (including GDPR, CCPA, and Indian Digital Personal Data Protection laws), you hold clear privileges:

Right to Deletion (GDPR)

Purge your registered cloud templates, saved API configurations, and TestFlight boarding tokens entirely.

Right to Access

Download a structured JSON export of any transactional histories associated with your bulk shipping accounts.