Privacy Policy

1. Who we are

Quantank ("we", "us") is a marine bunker-survey toolkit operated from Chennai, India. It consists of the website at quantank.org (also reachable at quantank-663bb.web.app) and the Quantank Android app. Both use the same account and the same data described below, so this one policy covers both.

Contact for anything in this policy, including complaints and requests about your data: admin@quantank.org.

2. Data you give us when you use an account

You can use most of the site without an account. If you create one, the following is stored in your account (see section 6 for where):

• Sign-in details — your email address and a password. We never see or store the password itself: it is handled by Firebase Authentication, which stores only a cryptographic hash.
• Profile — whatever you choose to enter in Settings: name, rank, company, date of birth, and an optional profile photo. The photo is resized on your device (max 256 px) before it is saved.
• Survey and fleet data — vessels, tank setups, gauge readings, bunker survey figures and the notes you type into them; an optional company logo used on printed reports (also processed on your device before saving).
• Work records — if you use them while signed in: certificates and their expiry dates, rest-hours records, and contract dates. These also work without an account, in which case they stay on your device only (section 4).
• Housekeeping fields — timestamps, your email address, and whether a change came from the website or the app, which is what makes the two stay in sync.
• Which messages you have read — a single timestamp per account, so the site knows which notices are still new to you.

Everything in this section is content you put in. We add nothing to it, and we do not read it except as needed to operate the service (for example, restoring it when you sign in) or to carry out a setup you have asked us for — see Operator access below.

2a. Operator access

Quantank offers to set your tanks up for you: you send in a calibration table and we enter it into your account so you do not have to. To make that possible, the operator account (admin@quantank.org, and only that account) can:

• See the account list — the name, rank, company, email and last-active time of every account, so we know who has written in;
• Open and edit the fleet data of an individual account — vessels, tank setups, calibration and surveys — in order to perform a setup;
• Send you a message, either an announcement to everyone or a direct message to you alone, which appears under Messages in the site and app.
• See and progress your calibration requests — see the separate heading below.

What the operator cannot reach, enforced by the database security rules rather than by policy alone:

• your password — it is hashed by Firebase and nobody, including us, can read it;
• your private preference records — the certificates, rest-hours, contract and message read-state documents in your account are excluded from operator access;
• your profile — name, rank, company, date of birth, photo and unit preferences. The operator can read these in the account list but the security rules refuse any write to them, so a setup cannot alter who you are;
• anything held only on your device, including the blood-pressure log and reaction-time baseline (section 4). Those are never uploaded, so no amount of access reaches them.

We look at fleet data only to do work you have asked for. If you would rather nobody opened your account, simply do not send a setup request — and if you want confirmation that we have not, or want a setup undone, write to admin@quantank.org.

2b. Calibration-table requests

If you use Bunker → Calibration Tables to ask us to set a vessel up, the request itself is stored and contains only what you type into that form: the vessel name, its IMO number, how many tanks it has, whether it is gauged by sounding or ullage, your notes, and the email address on your account. It also carries a status that we move as the job progresses, which you can see on that page.

Requests are readable by you and by the operator account, and by nobody else — another customer cannot list them. Only the operator can change a status; you cannot alter your own request after sending it, and neither can anyone else.

The calibration table itself reaches us by email, to admin@quantank.org, not through the website — there is no file upload. That means the document travels through ordinary email and is handled under section 6's account of the mail forwarding we use. Do not send anything in that email you would not send by email generally. Once we have typed the table up, it lives in your account as ordinary calibration data, and you can delete it as described in section 9.

Billing is not live. Nothing in the site takes a payment, we store no card or bank details of any kind, and any price is agreed with you by email before work starts.

3. Location

One button in the survey editor — "Use device location" — asks your browser for your position, and only after you approve the browser's own permission prompt. When you use it:

• your coordinates are sent once to Nominatim, a reverse-geocoding service run by the OpenStreetMap Foundation, to turn them into a place name (for example "Singapore");
• the resulting place name and coordinates are written into the survey field you were filling in, and stored with that survey like any other survey content.

Location is never collected in the background, never collected automatically, and not used for anything else. If you never tap that button, no location data exists anywhere in Quantank.

4. Data that never leaves your device

Several tools store their data in your browser's local storage on your device. This data is not transmitted to us or anyone else, does not sync between devices, and is deleted if you clear your browser's site data:

The BMI, hearing-check, colour-vision and other wellbeing tools compute their results on the page and store nothing at all.

If you sign in on the dashboard, the certificates, rest-hours and contract records additionally sync to your account so the app can see them. The blood-pressure log and reaction-time baseline never sync — they exist only on your device.

5. Data collected automatically

• Server logs. Like effectively every website, our hosting provider (Google Firebase Hosting) processes the IP address and request details of each visit in order to deliver the pages and defend against abuse. We do not use these logs to identify or profile visitors.
• Abuse protection. The site initialises Firebase App Check with reCAPTCHA Enterprise, a Google service that estimates whether a request comes from a real browser rather than a bot. To do this, Google processes technical signals from your browser and your IP address. No CAPTCHA puzzles are shown.
• Update check. The page periodically re-fetches its own version number from our own server to offer you a refresh when the site has been updated. This contacts no third party.

We run no analytics (no Google Analytics or similar), no advertising, no social-media buttons, and no tracking pixels. We set no cookies. Signed-in sessions are kept by Firebase in your browser's own storage (IndexedDB), on your device, so you stay signed in between visits.

6. Where your data is stored, and the third parties involved

Quantank has no servers of its own. Account data is stored in Google Firebase (Authentication for sign-in, Cloud Firestore for content, Hosting for the pages), on Google Cloud infrastructure. Access to your content is restricted by per-user security rules: your data is readable and writable only by your signed-in account.

The complete list of third parties your browser may talk to when using Quantank:

That list is exhaustive. Fonts are served from our own domain (not Google Fonts), currency and location requests happen only inside the tools that need them, and no other external service is contacted.

International transfer. Google Cloud infrastructure may store or process data outside your own country. Google participates in the major cross-border data-transfer frameworks; see their policy above.

7. What we use data for — and what we never do

We use your data for exactly one purpose: operating Quantank for you — keeping your account working, storing what you save, syncing it between the site and the app, and producing the reports you generate. Legal bases, where a law asks for one: performance of the service you signed up for (contract), your consent (location), and our legitimate interest in keeping the service secure (server logs, abuse protection).

We never:

• sell your data, or share it with anyone for marketing or advertising;
• profile you, or use your content for anything other than showing it back to you;
• use your data to train AI models, or permit our providers to;
• send marketing email. The only emails you can receive are the ones you trigger yourself (password reset).

We would disclose data if genuinely compelled by law, and we would tell you unless legally forbidden from doing so.

8. How long we keep it

• Account content (profile, vessels, surveys, synced records) — kept until you delete it or ask us to. Deleting a vessel or survey in the site or app deletes it from your account.
• The account itself — kept until you ask for it to be deleted (section 9).
• Device-only data (section 4) — entirely under your control; clear it in the tool itself or through your browser's site-data settings.
• Server logs — retained briefly by Google per their standard schedules; we keep no separate copy.

9. Your rights

Under India's Digital Personal Data Protection Act 2023, the EU/UK GDPR where they apply, and as a matter of how we think this should work regardless of law, you can at any time:

• access a copy of the personal data we hold about you;
• correct it — most of it you can edit yourself in Settings;
• delete it — individual items yourself in the site or app; the whole account by emailing us;
• export your survey data (the report generator produces portable copies; ask us for a fuller export);
• withdraw consent for location at any time — simply don't use the button, and revoke the browser permission;
• complain — first to us, and if unsatisfied, to the Data Protection Board of India or your local supervisory authority.

Send any of these to admin@quantank.org from the email address on the account, and we will respond within 30 days. This mailbox is also our grievance contact for the purposes of the DPDP Act.

10. Security

• All traffic to quantank.org is encrypted (HTTPS, with HSTS so browsers refuse plain HTTP).
• Passwords are hashed by Firebase Authentication; we have no access to them.
• Firestore security rules restrict every account's data to that signed-in account.
• The site sends a strict Content-Security-Policy, which is why it loads nothing from third-party script hosts.

No online service can promise perfect security. If we learn of a breach affecting your data we will inform you, and the authorities where required, without undue delay.

11. Children

Quantank is a professional tool for mariners and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has created an account, email us and we will delete it.

12. Changes to this policy

If we change what data is collected or how it is used, we will update this page, change the effective date at the top, and — for anything material — say so prominently on the site. The current version is always at quantank.org/privacy.html.