01Who we are

Wharfa Group Pty Ltd publishes wharfa.com, the Wharfa API and the Wharfa Landside Index, and is the entity responsible for personal information collected through them. Privacy questions go to [email protected] with the subject "PRIVACY".

02What we collect

Four things, and nothing beyond them. Account details: the email address you sign up with, and the organisation name you give us. What you asked us to watch: your saved lanes, meaning the publishers, ports and charge types you follow, plus the monthly container volume and average days-over figures you enter into the calculators if you save them to a lane. Billing records: your plan, billing period, seat count, invoice history and the customer reference Stripe issues you. Usage: API calls counted per key per month, and a record that an alert email was sent to you and whether it arrived.

If you write to us, request a source, or subscribe to the change brief, we hold what you typed: your name, email, company and message for enquiries; the URL, note and email for a source request; your email alone for the brief.

03What we deliberately don't collect

No advertising or analytics of any kind runs on this site: no tracking pixels, no behavioural profiling, no third-party analytics service, and no cookie banner because there is nothing to consent to. We hold no shipment data, no commercial contracts and no customer rate files. Card numbers never reach us; Stripe processes payments and we store only its customer reference. API keys are stored as a one-way hash, so we cannot read your key back, even to help you. Where the Index embed is used on another site we count the referring domain and a daily total, never a visitor.

04Why we hold it, and what we do with it

To run your account, take payment, send the alerts you asked for, enforce API rate limits, and answer you when you write. That is the complete list of purposes. We do not sell personal information, we do not disclose it for anyone else's marketing, and we make no automated decision that produces a legal or similarly significant effect about you.

One disclosure deserves naming on its own, because it is the one our users actually worry about: we never tell a publisher who is watching their schedules. Not in aggregate, not on request, not as part of a commercial arrangement. Our independence depends on it.

05Who else processes it

We use four service providers, each for one job: Supabase hosts the database and handles sign-in; Stripe processes payments and issues invoices; Resend delivers alert and notification email. Each receives only what that job requires. Our extraction pipeline reads publishers' published documents and is not given personal information.

06How long we keep it

Account, lane and usage records are kept while your account is open. Billing records are kept for seven years after the transaction, because Australian tax law requires it. If you close your account we delete the rest.

07Access, correction and deletion

Write to [email protected] and you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete your account and its data. We answer within 30 days and we do not charge for it. Most of it you can also see and change yourself in your account settings. If we ever refuse a request we will tell you why in writing.

08Security

Access to production is limited, logged and protected by MFA; backups are encrypted; subscriber lane data is isolated per account. The fuller account is on our security page. Your sign-in session is stored in your own browser and refreshes itself; signing out clears it.

09Complaints

If you think we have mishandled your personal information, tell us at [email protected] and we will investigate and respond in writing. If our answer does not satisfy you, you can take the complaint to the Office of the Australian Information Commissioner at oaic.gov.au.

10Changes to this policy

If we change this policy we will post the revised version here with a new effective date, and we will email account holders before any change that materially reduces the protection you have now.

Version 1.0. Effective 20 July 2026.