Privacy
A plain description of how the product handles data. It is not a substitute for the data-processing terms in a signed agreement, which is where the binding version lives.
This website
No analytics, no advertising pixels, no cookies and no third-party requests on any page of this site. The typeface is served from our own origin. Nothing here sets client-side storage, so there is no consent banner, because there is nothing to consent to.
We hold that email in order to reply to it, and for no other purpose.
The product
Vessel and voyage records, the daily reports filed from the bridge, certificates, invoices and requisitions, inspection findings, crew certificate and rest-hour records, and the seats of the people in your office who use it. Crew records are personal data and are treated as such.
Your own organisation only. Each customer’s fleet is scoped separately and that scoping is enforced on the server for every request. Hiding a screen is layout; the server refuses the record. Within your organisation, what a seat can read is set by its role. A Master reaches his own vessel and nothing else.
Changes to people, roles and scopes are recorded with who made them and when, and so is a seat reaching for a record it is not entitled to. That trail is yours and is visible to your administrators.
On Cloudflare’s platform. Sign-in is through your own identity provider; we never hold a password of yours. Mail sent on your behalf goes through a transactional mail provider.
If you have found something wrong with how this works, write to security@neptane.io. You get a reply from a person within one business day and an account of what we did about it. We do not ask anyone to sign something before reporting, and we do not threaten people who do.
Contact
Write to privacy@neptane.io for access, correction, export or deletion, or for the current sub-processor list. A pilot customer’s data is deleted on request at the end of a pilot, and we confirm when it is done.