Last updated: 28 October 2026. This Privacy Policy explains how Data Sailors Private Limited (“Data Sailors”, “we”) collects, uses, shares, keeps and deletes personal information when people use the Open Analytics app on iPhone (App Store) and Android (Google Play), the Open Analytics web dashboard, and the related monitoring services. Where we describe what the iPhone app does, we mean Open Analytics for iPhone version 1.3.0 and later.
Open Analytics is a business platform from Data Sailors Private Limited, India, for utilities, campuses and industrial sites that monitor electrical and water systems. This policy covers the Open Analytics app on iPhone and Android, the web dashboard and the servers behind them. We provide Open Analytics to organisations (“your organisation”) under a contract. Your organisation decides who gets an account and how long its operational records are kept; we run the service and are responsible for the apps and for the processing described here.
We collect only what Open Analytics needs to work. We get it from your organisation’s administrator (your account profile), from your sign-up request if you made one, from what you enter in the apps and the dashboard, and automatically when you use them. Everything below is linked to your account and used only to provide Open Analytics’ features (“app functionality”); none of it is used for tracking or advertising. The first five categories are the ones we declare in the App Store privacy details for the iPhone app.
The rest of your profile. Your profile can also hold your organisation, department, designation, role and site assignments, and a profile picture if you uploaded one in the web dashboard. The iPhone app shows these but cannot change them.
Security records. To keep accounts secure, our servers keep a record of your sign-in sessions (when you signed in, a description of the device or browser, its IP address and when the session was last used) and server logs. The logs contain IP addresses and the addresses of the requests made, and for some events, such as a sign-up, a password-reset request or an email we send you, your email address. Alert history entries can also keep the IP address and the app or browser description recorded when an action was taken. Your notification preferences and alert subscriptions are stored with your account.
On your phone. The app keeps recent data, your profile details and your preferences in its own storage so it can work offline. In the iPhone app this data is removed when you sign out; only device-level settings, such as light or dark mode, stay. To remove everything, sign out before you delete the app. When you export a report, the app creates the file and hands it to the system share sheet; where you save or send it is up to you. To tell whether it is connected, the iPhone app checks the connection against our own server: its network library sends a small request to our own API address, through Cloudflare like all the traffic between the app and our servers (section 8). Our servers and Cloudflare see your phone’s IP address, as with any request the app makes, and the app sends this check to no other company. Separately, your phone’s operating system may run its own connectivity checks, which we do not control and which are governed by Apple’s or Google’s terms. On Android, the app does not send its own check; it uses the result of Android’s built-in internet check, which Android carries out itself and which may contact Google. If your profile has a picture uploaded in the web dashboard, the app loads it from Google Firebase Storage, which also sees your phone’s IP address.
Earlier Android versions. Android versions that do not yet show Delete my account may keep the following on the phone after you sign out, until you uninstall the app or clear its storage: your app preferences (such as refresh and display settings), the list of meters you viewed recently, generator start times, the time of the last push alert, photos you took or picked for a leak report and the app’s record of them, and report files you exported.
In the apps. The apps include the crash-reporting library of Sentry (Functional Software, Inc.). Open Analytics 1.3.0 is built without a crash-reporting key, so it sends nothing to Sentry. If we switch crash reporting on in a later version, Sentry may receive crash and error reports (the error, where in the app it happened and the app version), app-hang reports when the app stops responding, release-health data (whether an app session ended normally or in a crash), performance data, the device model, operating-system version and free memory and storage, a short trail of recent app events (“breadcrumbs”, such as the addresses and status codes of requests the app made, console messages and the buttons you tapped), and your user ID. Before a report is sent, the app keeps only your user ID in the report’s user details, drops the details of the request, and masks email addresses and values named like passwords, tokens or cookies in the report’s extra data and breadcrumbs. Other parts of a report, such as error messages, are not filtered, so they can contain whatever text the error carried. Sentry also sees the IP address a report is sent from.
In the web dashboard. When error reporting is switched on for the dashboard, it sends error reports and a sample of performance data to Sentry, identified by your user ID, role and organisation. It is set up not to collect cookies, request bodies or your IP address as user information.
On our servers. Our servers report their own errors to Sentry, together with warnings that our code logs. Since 28 October 2026 they are set not to attach request bodies (what the app or dashboard sent in a request, such as form fields), cookies, the IP address the request came from, or the values the program held at the time of the error. Before a report leaves our servers they remove that data and mask email addresses and values that look like passwords, tokens or sign-in credentials in its text; if a report cannot be cleaned this way, it is dropped and not sent. Requests our servers refuse as invalid are the exception: the servers log a warning with a shortened copy (up to 1,000 characters) of what was sent and of the reply, and that warning is sent to Sentry. In that copy, email addresses are masked wherever they appear, and so are fields whose names our servers recognise as passwords, tokens or other secrets, or as a few common personal details (such as first and last name, phone number, username, reason and comment). Other fields are copied as sent, and they can include names, phone numbers, notes or comments under other field names, or an organisation, department or designation. File uploads are never copied. What a report holds is technical details of the error: the type and message of the error, the stack trace (the files, functions and lines of code where it happened), the address and method that were requested and the response status, a few ordinary request headers such as the browser or app description, a short trail of recent log lines and other recent events, and which server and software version it came from. The masking works by recognising patterns, so the error message, the log lines and the other recent events in a report can still contain details that our code wrote into them, such as an internal user ID, the IP address a connection came from or a phone number an alert was sent to. Reports sent before 28 October 2026 were collected before these protections were in place. Sentry’s own scrubbing, which was already switched on, masked password, token, session and sign-in fields before those reports were stored, but they can still include your user ID, email address and IP address, other request headers, other contents of the request, and the values the program held when the error happened, which can include other account details. These older reports are deleted automatically by 26 January 2027 at the latest. Our servers send no performance data to Sentry. We use these reports only to find and fix faults. Sentry processes them in the United States and keeps them for up to 90 days, after which they are deleted automatically. They are not erased when you delete your account; they leave Sentry on that schedule.
We do not use your information for advertising, profiling or tracking, and we do not sell it.
We share personal data only with the service providers below, only for the purpose shown, and only as much as that purpose needs. We share personal data only with service providers that process it on our behalf for the purposes in this policy, and we require them to protect it at least as well as this policy does.
If your organisation turns on Telegram alerts for you, Telegram delivers those alert messages to your Telegram account. Telegram is a channel your organisation chooses, not one of the providers above, and it handles those messages under its own privacy policy.
Open Analytics servers and databases are run by Data Sailors for each customer deployment. For our current deployment they are in India, in the customer organisation’s own data centre. Some of the providers above process data outside India.
Under applicable Indian law, including the Digital Personal Data Protection Act, 2023 as its provisions come into force, you have the right to:
We apply these rights wherever you live. Write to the Grievance Officer below. We may need to confirm your identity, and when a request concerns records your organisation keeps, we will involve its administrator. We aim to reply within 30 days. Your profile is read-only in the iPhone app: to change your name or phone number, ask your organisation’s administrator or write to us. “Change password” in the app sends you a password-reset email.
Where we rely on your consent, you can withdraw it at any time, as easily as you gave it, and withdrawing does not affect what was done before:
We process your account details because your organisation has given you access to Open Analytics under its contract with us, or because you asked for access through a sign-up request. If you no longer want that, you can delete your account or your request (section 11).
For privacy questions, requests and complaints, contact:
Grievance Officer, Data Sailors Private Limited
11, Haripuram Kukra, Muzaffarnagar, Uttar Pradesh 251001, India
Email: ops@datasailors.io (subject “Privacy request”)
Please tell us your name, your organisation and the email address on your account, and what you would like us to do.
We use HTTPS/TLS for all app and dashboard traffic, hashed passwords, secure token storage on the phone, role-based permissions checked on our servers, confirmation on the phone before equipment commands, encrypted offsite backups, and a tamper-evident audit log in which each equipment-command entry is chained to the previous one. No system is perfectly secure, but we apply safeguards suited to industrial monitoring and control.
Open Analytics is a business tool for staff of our customer organisations. It is not directed to children, and we do not knowingly collect personal information from children.
This policy covers both apps. The App Store privacy details describe the iPhone app and the Google Play Data safety section describes the Android app; both are kept consistent with this policy when features or data flows change.
We may update this policy when the apps, the law or our providers change. The new version is published at this address with a new “Last updated” date. For significant changes we will also tell users in the app or through their organisation.
Data Sailors Private Limited, 11, Haripuram Kukra, Muzaffarnagar, Uttar Pradesh 251001, India. Email ops@datasailors.io, call +91 70782 29901, or use the contact options on our support page.