Privacy policy
This policy explains what personal data the Barquecon IoT Platform at
platform-iot.barquecontech.com and the Barquecon mobile apps that sign in to it collect,
why, where it is kept, for how long, and what you can do about it. The platform is run by
Barquecon Technologies Pvt Ltd, Kharadi, Pune, Maharashtra, India
(“Barquecon”, “we”). Questions: info@barquecontech.com.
The platform is used by organisations (“tenants”) to monitor their own devices. Your organisation decides which devices are connected and who gets an account. For the device data, Barquecon acts on your organisation's behalf.
What we collect, and why
| Data | What exactly | Why |
|---|---|---|
| Your account | Name, email address, role, the organisation (tenant) you belong to, the time the account was created. Your password is never stored, only an argon2id hash of it. | To sign you in and show you only your organisation's data. |
| Sign-in sessions | A session record per sign-in (an id, a hash of the refresh token, when it was created, rotated, revoked and when it expires). | To keep you signed in and to sign you out everywhere when needed. |
| Your organisation | Organisation name, edition, licence and plan, the number of active users and devices, and optional branding (display name, logo address, two colours). | To run and license the service. |
| Device telemetry | The readings your organisation's devices send (for example temperature, humidity, air quality, water level, energy), with the device id, the time, firmware version and any device event or alert. | This is the service: dashboards, history, alerts and reports. |
| Location | Only from GPS asset trackers that an organisation connects: the tracker's position is part of that tracker's telemetry. The apps do not collect your phone's location. | To show where a tracked asset is. |
| Alerts and notifications | Alert history, and a log of each notification sent: the recipient addresses your organisation configured for alerts and scheduled reports, the subject and text, the time, whether it was delivered, and who acknowledged an alert (their email address). | To tell the right people about an alert and to show that it was sent. |
| Audit trail and e-signatures | A tamper-evident (hash-chained) record of changes to accounts and settings, naming who made each change by user id and email address at that time; electronic signatures (signer name, meaning, reason, time). | Security, and the record-keeping that regulated customers (for example pharma cold-chain) require. |
| Security data | IP addresses: in short-lived sign-in attempt counters (15-minute windows) and in the web server's access log. | To stop password guessing and investigate abuse. |
| Adding a device (Barquecon device) | The device's serial number and setup code, read from the QR code on its label with the camera, or typed. The serial becomes the device's id in your account. The setup code is checked against a fingerprint kept from the factory and is not stored by us. Also the name and site you give the device. | To add the device to your organisation's account and to let you remove it again. |
| Adding a LoRaWAN sensor | The sensor's DevEUI, JoinEUI and AppKey (from its maker's key sheet or label), its model, and the name and site you give it, sent to the platform when you tap Add sensor. The AppKey is the secret that lets the sensor join a LoRaWAN network; the app does not store or show it again after sending it. The platform does not store, log or show the AppKey: it passes it once to Barquecon's LoRaWAN network server, which keeps it so the sensor can join the network. (LoRaWAN sensors are not yet available on the live platform.) | To register the sensor so its readings reach your organisation's account. |
| Push tokens | Not collected today. If a later app version switches on push notifications, it will store your phone's push token to deliver alerts, and delete it when you sign out or delete your account. | Alert delivery to your phone. |
| Crash data | Not collected by Barquecon today. If crash reporting is added later, this policy will name the provider and what it receives before that app version is released. (On Android, Google's code-scanner library sends its own diagnostics to Google; see “The camera, location and local network” below.) | Fixing faults. |
We do not use advertising or analytics tools in the platform, its web pages or the apps, and we do not sell personal data. The one third-party library in the apps that sends data to its maker is Google ML Kit in the Android app, described below. WhatsApp and SMS alerts are not switched on.
The camera, location and local network (Add a device)
These permissions are asked for only when you add or re-connect a device, never at start-up.
- Camera. Used only to read the QR code on a device's label (or a LoRaWAN sensor's QR code). The picture is decoded on your phone; no photo is taken, saved or sent by the app.
- Location (Android). Android allows an app to join another Wi-Fi network, here the device's own setup network, only if the app holds the location permission. The app does not read, store or send your phone's location. On iPhone the app asks for location while using it, to confirm the name of the Wi-Fi network the phone has joined is the device's.
- Local network (iPhone). Used to talk to the device on its own setup network while you set up its Wi-Fi.
- Your Wi-Fi password. When you set a device's Wi-Fi, the network name and password you type go only to your own device, over the encrypted setup session on the device's own network. They are not sent to Barquecon's platform. The device keeps them so that it can join your network.
- Google ML Kit (Android only). The Android app reads QR codes with Google's ML Kit code scanner. Google states that ML Kit sends Google device information (such as manufacturer, model and OS version), the app's package name and version, per-installation identifiers that are not intended to uniquely identify a user, performance metrics, API configuration and error codes, for diagnostics and usage analytics (Google, “ML Kit Data Disclosure”, last updated 15 July 2026, read 30 October 2026). This goes from your phone to Google, not through Barquecon, and is governed by Google's own terms. The iPhone app uses Apple's own scanning frameworks and an open-source decoder and has no ML Kit.
Where it is kept, and who processes it
| Processor | What it handles | Location |
|---|---|---|
| Virtual private server (VPS) provider | Runs the whole platform: the database, the services and the web server. All platform data stays on this one server. | India |
| Cloudflare R2 (Cloudflare, Inc.) | Off-site backups: one full copy of the databases each night, encrypted at rest by Cloudflare. Each copy is deleted automatically 90 days after it is uploaded. | Bucket location hint Asia-Pacific; Cloudflare chooses the data centre |
Barquecon's mail server, mail.barquecontech.com | Will send alert and account emails (SMTP); not used yet, as email is switched off on the live platform. | United States (our web-hosting provider's network) |
| Google (ML Kit, Android app only) | Receives the diagnostics listed above from the Android app's QR scanner. Barquecon does not receive them. | Google's |
| Apple App Store, Google Play | Distribute the apps under their own privacy policies; we receive only their aggregate download and rating figures. | Their own |
How long we keep it
| Data | Kept |
|---|---|
| Account | While the account exists. When you delete it, it is disabled at once and your name, email address and password hash are removed 7 days later (how). |
| Device telemetry and alerts | Until your organisation deletes the device or its account with us, or sets a retention period. There is no automatic deletion by default, because cold-chain and other regulated customers must keep records for years. |
| Audit trail and e-signatures | For the life of your organisation's account. These entries are part of a tamper-evident chain and are not changed when a user account is deleted. |
| Alert acknowledgements, alert and report recipients | With your organisation's alert history and settings, until your organisation removes them; deleting a user account does not change them. |
| Backups | On the server: the 7 most recent nightly copies. Off-site (Cloudflare R2): 90 days per copy. Deleted data therefore disappears from backups within 90 days. |
| Sign-in attempt counters | 15 minutes (a lockout, when triggered, also lasts 15 minutes). |
| Web server and service logs | Web server access log: rotated daily, 14 days kept (the server's standard setting). Service logs: at most 50 MB per service, overwritten as they fill. |
Security
All traffic to the platform and from devices is encrypted (HTTPS, MQTT over TLS). Each device has its own secret and may only publish under its own address. The database is not reachable from the internet. Passwords are hashed with argon2id. Sign-in attempts are rate-limited.
Your rights
You can ask us to tell you what personal data we hold about you, to correct it, to delete it, or to stop processing it, and you can complain to us about how it is handled, including under India's Digital Personal Data Protection Act, 2023. You can delete your own account in the app or by email (how). Write to info@barquecontech.com from the email address on your account; we will reply within 30 days. Because device data belongs to your organisation, we may pass a request about it to your organisation's administrator.
Children
The platform and the apps are business tools and are not meant for anyone under 18.
Changes
We will post any change here with a new date, and tell account holders by email before a change that collects new kinds of data takes effect.
Contact
Barquecon Technologies Pvt Ltd, Kharadi, Pune, Maharashtra, India · info@barquecontech.com