Open Analytics Account Deletion

Delete your account in the app

1. Open the Open Analytics app and sign in.
2. Tap More in the tab bar.
3. Scroll down to the About section.
4. Tap Delete my account.
5. Read the explanation and confirm.

Delete my account is in Open Analytics for iPhone, version 1.3.0 and later. It will come to the Android app in an update; until your Android app shows it, use the email route below. If you cannot sign in, also use the email route; “Forgot password” on the sign-in screen can help you get back in.

What happens and when

• Straight away: your request is recorded and your sign-in is revoked on every device: your sign-in tokens stop working, web dashboard sessions end and live connections close. Another device that is in use at that moment loses access within 15 minutes at most.
• Who is told: the request is emailed to Data Sailors, who act on it, and your organisation’s administrators are informed by email, for their information.
• Within 30 days: Data Sailors staff, not your organisation’s administrator, erase your account with our account-erasure tool, on behalf of your organisation. Your account and the personal data listed under “What is deleted” are deleted, and your sign-in is disabled for good.
• Changed your mind? Write to ops@datasailors.io or tell your organisation’s administrator before the deletion is completed.
• Confirmation: if you ask, we will email you when the deletion is complete.

What is deleted

• Your account and sign-in details (email address and password hash), and the records of your sign-in sessions. The stored text of your sign-in tokens is blanked (see “What is kept”).
• Your profile: name, email address, phone number, organisation, department, designation, role, site assignments and profile picture link.
• Your notification preferences, alert subscriptions, the notifications addressed to you, and push notification registrations (Android and web).
• Your email address on scheduled-report recipient lists (Android and web).
• Any earlier deletion request of yours, which is cleared the same way.
• Outside our database, by hand, as part of the same request. Some personal data is held in Google Firebase and in our analytics engine, where our erasure tool cannot delete it. Data Sailors staff delete it by hand, where such data exists for your account, inside the same 30 days:
  • Saved dashboard layout (web): the document under your user ID in Google Cloud Firestore.
  • Older profile copy: the copy of your profile (name, email address, phone number, organisation, role) that the web dashboard and the first app versions saved in Google Cloud Firestore before March 2026. Only older accounts have one.
  • Profile pictures (web): every picture you uploaded, not only the latest, from Google Firebase Storage.
  • Old sign-in record: your email address and the stored form of your old password in Google Firebase Authentication, if your account is from before we moved sign-in to our own servers.
  • AI assistant conversations (Android and web): staff find your conversations in our analytics engine by your user ID and delete them.
  • Report schedules: your email address, if it is on a report schedule held by our analytics engine.
• Support emails linked only to your account, once the retention period below has passed.

In the iPhone app, data saved on your phone is removed when you are signed out; only device-level settings, such as light or dark mode, stay. Earlier Android versions may keep your app preferences, recently viewed meters, generator start times, the time of the last push alert, leak-report photos and exported report files until you uninstall the app. Error reports held by our error-reporting provider, Sentry, are not erased with your account; they are deleted automatically after at most 90 days (see “What is kept”).

What is kept, and why

• Operational and safety records your organisation must keep: alert records (acknowledgements, assignments, resolutions, comments and history), the equipment-command audit log, shift, handover, roster, maintenance and checklist records, leak inspection records, billing records, configuration submissions, and alert contacts and alert logs. They are the operating history of electrical and water systems, so they are kept under your organisation’s retention policy and may keep the name, phone number, email address or user ID recorded at the time. Alert history entries can also keep the IP address and the app or browser description recorded when an action was taken.
• The equipment-command audit log is tamper-evident: each entry is chained to the previous one, so entries are never edited.
• AI assistant ratings, feedback comments and question log (Android and web): our analytics engine has no way to delete these yet, so we cannot erase them with your account and they may stay in the engine. Ratings and comments are stored with a conversation and answer, not with your name or user ID; the log of questions asked is stored with your user ID. We set no fixed deletion date for them. Do not put personal information into feedback comments.
• Error reports in Sentry: reports our servers send about their own errors hold technical details of the error and a partly masked copy of requests they refused (see section 6 of the Privacy Policy), and their messages and log lines can contain your internal user ID and occasionally other details, such as an IP address or a phone number. Since 28 October 2026 our servers are set to keep cookies, email addresses and credentials out of these reports; reports sent before that date can also include your email address, IP address, request headers, request contents and other account details, with password, token, session and sign-in fields masked. We use them only to fix faults. Sentry keeps them (in the United States) for at most 90 days and then deletes them automatically; we do not delete them individually before then. Details are in section 6 of the Privacy Policy.
• Records of changes administrators made to your account, kept in our administration history.
• Sign-in token records, with the token text blanked: an entry stays for each token so that an old token keeps being refused.
• Meter readings, alarms and device history belong to your organisation and are not personal data about you.
• A record of your request: that the deletion was requested and completed, and when. Your email address is kept in it only in hashed form, and the record of what was erased holds counts, not personal data.
• Emails already sent, such as the deletion-request email or bills, reports and alerts sent to you, stay in the mailboxes that received them.
• Server logs and database backups may contain deleted data until they are overwritten in the normal cycle (see the retention periods below).

If you cannot use the app: request deletion by email

1. Email ops@datasailors.io from the email address on your account, with the subject “Open Analytics account deletion request”.
2. Include your full name and your organisation.
3. If you cannot write from that address, tell us why; we will confirm the request with your organisation’s administrator.
4. We will file and complete the request for you.

This route is for anyone who cannot use Delete my account: an Android app that does not have it yet, a sign-up request you made on the web dashboard (approved or not), an account you cannot sign in to, or anyone who simply prefers email.

What we do. We find your account by your email address; if more than one account matches, we ask which one you mean. Once we have confirmed the request, Data Sailors staff file the deletion request for you, and the 30 days start on the day we file it. Data Sailors staff then erase the account as described on this page; once it is erased it no longer works. We will email you when it is done if you ask. Deleting an account removes that account only: if we find other accounts under the same email address, we will ask you whether they should be deleted too.

Retention periods

• Account & profile data — erased within 30 days of your request.
• Server logs — our application log is rotated by size (the current file and at most five older files of up to 100 MB each); other server logs are kept only as long as needed for security and troubleshooting.
• Database backups — 7 nightly backups on the database server, and 5 daily and 4 weekly encrypted copies offsite, so deleted data leaves these backups within about five weeks.
• Error reports in Sentry — not erased with your account; deleted automatically after at most 90 days.
• Support records — may be kept for up to 180 days after the request is closed, for audit and service quality.
• Operational and audit records — kept under your organisation’s retention policy, contract terms and applicable law.

Deleting your account removes your access to dashboards, alerts and saved preferences. If you need access again later, your organisation’s administrator can create a new account. More detail, including your rights and our Grievance Officer, is in our Privacy Policy.