Legal

Privacy Policy

Last updated 17 November 2026 · See also the terms and conditions

You can use the map, search, vessel pages and port pages without an account. If you create one we store your email address, a hashed password, and what you set up: your fleet, alert rules, areas and webhooks.

Payments are handled by Stripe and we never see your card. We do not sell personal information. You can download everything we hold about your account, or delete the account, yourself on the Privacy & data page.

1.Who we are

VesselTrack is operated by RB Alliance (NZ) Limited, a company registered in New Zealand. We decide how the information described here is used (in GDPR terms, we are the controller). This policy covers the VesselTrack website and API. The terms and conditions cover how the service may be used.

We are bound by New Zealand’s Privacy Act 2020 wherever you are. If you are in the European Union or the United Kingdom, the GDPR or UK GDPR may also apply to how we handle your information. We have not appointed a data protection officer or a representative in the EU or the UK; write to support@vesseltrack.net about anything in this policy.

2.What we store and for how long

This is everything the service stores that is tied to you or your account.

Account
Your email address, your first and last name if you give them, your email alert settings, and your password. The password is stored only as a bcrypt hash; we cannot read it.
Kept for:Until you delete the account
Sign-in links
A hash of the link we email you to confirm your address or reset your password. The link itself is not stored.
Kept for:Confirmation links expire after 48 hours, reset links after 1 hour
Pending sign-ups
If an address is signed up for again before it has been confirmed, that sign-up’s password (as a bcrypt hash) and a hash of its own confirmation link are kept separately, up to 5 per address. The link that is opened decides which password the account gets.
Kept for:Until the address is confirmed, the password is reset or the account is deleted; otherwise removed by the clean-up job once the link has expired (48 hours)
Sign-in attempts
Each failed sign-in, each registration, each request for a reset or confirmation email, each “account already exists” notice, each wrong current password and each data download is recorded with the email address, the account number or the IP address it came from, so that guessing and email flooding can be limited. For IPv6 the record holds the network’s /64 prefix rather than the full address. A sign-in that succeeds removes its own record.
Kept for:Counted for up to 24 hours. Removed once out of its window when the same email, account or address is checked again, or by the clean-up job once 25 hours old
Activity log
A record of account events: registration, sign-in, email confirmation, password and API key changes, fleet additions and removals, webhook changes, billing events, unsubscribing, and changes an administrator makes to your account. Each record holds your email address and the time, and most also hold the IP address the request came from. Your sign-in records from the last 30 days are also used to recognise networks you have signed in from before, so that someone guessing at your password from elsewhere cannot lock you out.
Kept for:180 days (see the note below)
Subscription
Your Stripe customer and subscription identifiers, the subscription status, the price it is on, when the current period ends, whether it is set to cancel, the latest invoice identifier, and any payment grace period. We do not receive or store card details: you enter them on Stripe’s own checkout page.
Kept for:Until the account is deleted. Stripe keeps the payment records themselves for us for 7 years (section 9)
API key
A SHA-256 hash of your key and its first few characters, so you can recognise it. The key itself is shown once and not stored.
Kept for:Until you replace it or the account is deleted
API requests
For each request made with your API key: the method, the path, a hash of the query string, the response status and size, the time, and the first characters of the key. The IP address is not recorded. Requests made by the website in your browser are not recorded per person.
Kept for:30 days
Fleet and alerts
The vessels you follow with your labels, groups, notes and alert rules; your alert areas; your email alert preferences; and the alerts generated for you.
Kept for:Alerts for 90 days (see the note below). Everything else until you remove it or the account is deleted
Webhooks
The addresses you ask us to send alerts to, with their description, filters and signing secret (stored encrypted). For each delivery we keep the event type, time, HTTP status, duration and a short error code. We do not store what was sent or what your server replied.
Kept for:Delivery records for 7 days. Endpoints until you delete them
Emails we send you
Our email provider keeps a record of each message sent to you (address, subject, delivery status) on its own schedule.
Kept for:Set by the provider (section 6)

A note on deletion. Pending sign-ups, sign-in attempts, activity-log entries, API request records and alerts are deleted by a scheduled clean-up job that runs every 10 minutes (at least every 6 hours while the live AIS feed is down); the last three also by the collector that receives AIS data, while it is running. A record can therefore outlive its period until the next run. The job deletes a bounded number of records per run, so after a long backlog it can take several runs to catch up. Webhook delivery records are deleted by the webhook delivery job.

If you email us, we keep that correspondence in our mailbox. Authorised VesselTrack administrators can view account records, including the activity log, to run the service and to help you when you ask.

3.Why we use it, and on what basis

We use this information to provide VesselTrack, keep accounts and the API secure, take payment, send the emails below, keep the records the law requires, and understand how the site is used. Where the GDPR or UK GDPR applies, these are the legal bases we rely on:

Running your account
Sign-in, your fleet, alerts, alert areas, webhooks, API key, the alert emails you switch on, data downloads and deletion.
Legal basis:Contract: needed to provide the service you signed up for
Billing
Subscription status, payment events, invoices and refunds, and keeping payment records.
Legal basis:Contract, and legal obligation (tax records, 7 years)
Security and abuse prevention
Sign-in attempt records, the activity log, IP addresses, rate limits, the site access cookie.
Legal basis:Legitimate interests: keeping accounts and the service safe
Service emails
Confirmation, password reset, billing notices, security notices, the deletion confirmation.
Legal basis:Contract and legitimate interests
Measuring use of the site
Google Analytics (when switched on) and Vercel Web Analytics.
Legal basis:Consent where the law requires it (EEA, UK, Switzerland); otherwise legitimate interests, and you can turn it off
Advertising to visitors without Pro
Google AdSense (when switched on).
Legal basis:Consent where the law requires it, collected by Google’s consent message; otherwise legitimate interests
Showing vessel data
AIS broadcasts, which can concern a person when a small vessel is run by its owner (section 7).
Legal basis:Legitimate interests: maritime awareness from openly broadcast safety data

Where we rely on legitimate interests you can object (section 8). Where we rely on consent you can withdraw it at any time, as easily as you gave it. We do not make decisions about you by automated means that have legal or similarly significant effects; automatic rate limits and fraud checks only slow or refuse requests.

The emails we send are:

  • a link to confirm your email address, and a welcome message once you have;
  • a password-reset link when one is requested for your address;
  • a notice if someone tries to register an address that already has an account;
  • a notice when a subscription payment fails or succeeds;
  • a notice to your previous address if an administrator changes the email address on your account;
  • a notice if one of your webhook endpoints is switched off automatically;
  • a confirmation when your account is deleted;
  • if you have Pro and have turned email alerts on, a digest of your new alerts (every 10 minutes) from the last 7 days. Every digest has an unsubscribe link that works without signing in, and you can turn it off on the email alerts page.

These are the only emails the service sends. We do not send marketing email.

4.Cookies and browser storage

These are the cookies and browser storage the site uses. The ones marked strictly necessary are needed for the pages you open to work and are not used for advertising or analytics; the functional ones only remember your own settings in your browser.

__vt_a (cookie)
Set by VesselTrack on your first page view. A random value signed by our server: it lets the pages you load call our API, rate limits visitors, and counts how many rows the vessel listings and how much fleet replay history have been read by this browser (counts kept in server memory only). Not linked to an account.
How long:30 days. Strictly necessary
Session cookie
__Secure-next-auth.session-token, set when you sign in so you stay signed in. It holds your account number, email address, role and plan in an encrypted token.
How long:30 days, renewed while you use the site. Strictly necessary
Sign-in helper cookies
Two cookies set by the sign-in system for every visitor: one protects the sign-in form against forged requests, the other remembers which page to return you to.
How long:Until you close the browser. Strictly necessary
Local storage
Preferences kept in your browser and never sent to us: theme (vt-theme), map layers and position, legend state and recent searches (vt-map-layers, vt-map-view, vt-map-legend, vt-recent-searches), the page to return to after signing in (vt-return-to), whether this browser belongs to a Pro account so empty ad space can be hidden (vt-ads), and your analytics choice (vt-consent).
How long:Until you clear site data; the analytics choice is asked again after 395 days. Functional
Session storage
While you are confirming a new account, the address you registered with (vt-pending-email), for that tab only.
How long:Until the tab closes. Functional
Google cookies
Google Analytics (_ga, _ga_<id>) and Google’s advertising and consent cookies, when we have switched these services on. See section 5.
How long:Set by Google; up to about 2 years. Not set in the EEA, UK and Switzerland unless you agree

Vercel Web Analytics and Speed Insights set no cookies and store nothing in your browser. Web Analytics recognises a visit by a hash of the request that Vercel discards after 24 hours.

Your choices. Clearing your browser’s site data removes all of the above. You can switch analytics off here:

5.Analytics and advertising

  • Vercel Web Analytics is on every page and reports page views (the address, referrer, browser, device type and approximate location) to Vercel, our host, without cookies. Vercel Speed Insights reports how fast each page loads and responds (performance measurements, the page and the element a measurement refers to, device and connection type), also without cookies.
  • Google Analytics is loaded only when we have switched it on. It never runs on password-reset, email-confirmation, admin and development pages (some carry a one-time link in their address); moving to one of them from another page loads it afresh, so Google Analytics is not running there.
  • Google AdSense is loaded only when we have switched ads on, and never for visitors with Pro or administrators. Ad spaces are on these pages only: vessel page, port page, port directory, guides, home and live map; and only where the page has enough content of its own. An ad space that Google does not fill shows VesselTrack’s own content instead. AdSense never runs on sign-in, registration, forgotten-password, password-reset, email-confirmation, account, fleet, admin and development pages; moving to one of them loads the page afresh. Third parties, including Google, may place and read cookies in your browser, or use web beacons and your IP address, to show and measure ads, including ads based on your earlier visits to this and other sites.

Visitors in the EEA, the UK and Switzerland. Until you make a choice, Google’s tags run with advertising and analytics consent switched off: they set no advertising or analytics cookies, send only cookieless measurements, and ads are limited and not personalised. Where we have switched on Google’s consent message, it asks for your choice, and its “Privacy and cookie settings” link lets you change it later. Google decides from your IP address whether you are in one of these regions.

How Google uses this information is explained at How Google uses information from sites or apps that use our services. You can turn off personalised ads in Google’s ad settings, and switch analytics off in section 4. The site does not change its behaviour in response to a browser’s “Do Not Track” signal; use those choices instead.

6.Who else receives data, and where

We do not sell personal information. We share it only with the service providers below, which help us run VesselTrack, or where the law requires it.

Vercel
Hosts the website and API (US-based; our functions run in its regions in the United States, Australia and Germany). Every request passes through it, so it processes your IP address, browser details and the pages or API paths you request, and keeps request logs for a short time. It also provides Web Analytics and Speed Insights (page performance), on every page.
When:Always
Neon
Hosts the database that holds everything in section 2, in Sydney, Australia, with backups for a short rolling window.
When:Always
Railway
Runs the collector that receives AIS data. To generate alerts it reads fleet entries, alert areas and whether the account that owns them has Pro. It does not read your email address or password.
When:While the collector is running
Stripe
Takes payment. We send Stripe your email address and your VesselTrack account number; you give Stripe your card and billing details directly. Stripe tells us when a payment succeeds, fails, is refunded or is disputed. Stripe also uses payment data for its own purposes, such as fraud prevention and its legal duties, under its own privacy policy.
When:When you subscribe or open billing
Resend
Sends our email (US). It receives your email address and the content of each message: confirmation and password-reset links, billing notices, and the alert digest, which names the vessels and areas in your alerts.
When:When we email you
Google
Google Analytics and Google AdSense, only when we have switched them on. Google uses the data it collects through them for its own purposes too. See section 5.
When:Only when enabled
Map and photo hosts
Your browser downloads map tiles straight from OpenFreeMap (Hungary), and from EOX (Austria) and OpenSeaMap (Germany) when you turn on the satellite or seamark layers. Vessel photos load from Wikimedia Commons (US). Each of these hosts sees your IP address and which tiles or image you asked for, which shows roughly where on the map you are looking.
When:When you view the map or a vessel photo
Your webhook endpoints
If you set up a webhook, we send alert and vessel data to the address you gave us.
When:When you configure one
Authorities
Where the law requires us to, for example a lawful request from a New Zealand authority.
When:Only when required

Where your data goes. We are in New Zealand, our database is in Australia, and most of our providers are in the United States; the map and photo hosts are where shown above. When data leaves New Zealand, the European Union or the United Kingdom, we rely on: the European Commission’s and the UK’s adequacy findings for New Zealand; for providers in the United States, their certification under the EU-US Data Privacy Framework where they hold one, or the standard contractual clauses in their data processing terms; and, for New Zealand law, providers that act as our agents or are bound to protect the information comparably. Ask us for details of the safeguards for a particular provider.

7.Vessel data from AIS

Ships broadcast their identity, position, course, speed and destination over AIS, an open radio system they use for safety. We receive those broadcasts from AISstream, which relays them from receiving stations, and show them as received: the vessel’s MMSI, name, call sign, IMO number, type, dimensions, position, speed, course, heading, navigational status, destination and ETA. They are shown to every visitor and returned by our API. We keep the latest report for each vessel, its track for 30 days, and port calls and events for 90 days.

For fleet replay we also keep a snapshot of the whole map: where each vessel heard in the previous hour was, with its speed, course, heading, ship type and navigational status, but not its name. Snapshots are recorded every 15 minutes and thinned as they age: every snapshot is kept for 30 days, then one an hour for 2 years, then one every six hours, which we keep without a set end date. This is a longer-lived record of vessel positions than the track history above. To limit load, replay requests are counted in server memory, per account or per browser and IP address; those counts are not stored.

We receive only the Class A equipment that larger and commercial vessels must carry, not the Class B sets on most yachts and small craft. Even so, a vessel such as a fishing boat can be run by its owner, and then its position can say where that person is. If you are the owner or operator of a vessel, you can ask us what we hold about it, ask us to correct it, or ask us to remove or limit what we show and keep; email support@vesseltrack.net with the vessel’s MMSI or IMO number. We do not combine vessel data with information about account holders.

8.Your rights and choices

You can, yourself, at any time:

  • Get a copy of your data: Privacy & data → Download my data gives you one JSON file with everything in section 2 that is tied to your account.
  • Delete your account on the same page (section 9).
  • Correct your name on the account page, and change your password there.
  • Stop alert emails on the email alerts page or with the unsubscribe link in any digest.
  • Remove vessels, alert areas and webhooks in your fleet and webhook settings; replace your API key on the API page.
  • Cancel your subscription or change your card from Account → Subscription, in the Stripe billing portal.
  • Turn analytics off, or change your advertising consent, with the privacy choices (sections 4 and 5).

You can also ask us, by email to support@vesseltrack.net, to change your email address, to correct anything else, to stop or limit a particular use of your information, to tell you what we hold about you that the download does not contain, or to explain how we handle it. We answer within 20 working days (New Zealand law) and in any case within one month (GDPR), and tell you if we need longer and why. We may ask you to confirm the request from the address on the account. There is no charge.

9.Deleting your account

Delete your account on Privacy & data. You confirm with your password, and it happens at once; there is no waiting period and it cannot be undone. If you have a subscription, we cancel it with Stripe first; if Stripe does not confirm the cancellation, nothing is deleted and you are told. We send a confirmation to your email address afterwards.

Deleted straight away:

  • Your account: email address, name, password, API key and email settings.
  • Your fleet, with labels, groups, notes and alert rules.
  • Your alert areas and every alert raised for you.
  • Your webhook endpoints, their signing secrets and delivery records.
  • Your API request log and your sign-in and account history.
  • Pending sign-up links and rate-limit records tied to your address.

Kept, and why:

  • Payment records held by Stripe (invoices, payments, refunds, disputes). New Zealand tax law requires business records to be kept; kept for 7 years.
  • Log entries about payments, and about actions an administrator took on your account, with your email and IP address removed. To answer refunds, chargebacks and security questions; kept for 180 days from when each entry was written.
  • Database backups held by our database host. Backups cannot be edited; they are replaced on a rolling schedule; kept until the backup window rolls over.

Administrator accounts cannot be deleted from the account page; email us. You can also ask us by email to delete your account, and we do the same.

10.Complaints

If you are unhappy with how we have handled your information, tell us first at support@vesseltrack.net. We acknowledge a complaint within 30 days and tell you what we will do. You can also complain to a data protection authority:

11.Security and breaches

Passwords and API keys are stored only as hashes, webhook signing secrets are encrypted, all traffic uses HTTPS, and administrator access is limited by role and logged. If a breach of your information is likely to cause you serious harm, we will tell you and the New Zealand Privacy Commissioner as soon as we can, and other regulators where their law requires it.

12.Children

VesselTrack is not directed at children and accounts are for people aged 16 and over. If you believe a child has given us personal information, email us and we will delete it.

13.Changes to this policy

When this policy changes, the date at the top changes. If a change affects how we use information we already hold about you, we will email account holders before it takes effect.

14.Contact

Questions or requests about your information: support@vesseltrack.net. RB Alliance (NZ) Limited, New Zealand.