Editorial corrections and regulatory updates
Found an error in a formula, citation, or calculator? Want to flag a regulation that has been amended? We treat editorial accuracy as a first-class priority. Email editorial@shipcalculators.com with the page URL, the issue, and a citation to the corrected source where possible. Corrections are usually merged within 48 hours; the page's lastmod field updates accordingly.
Calculator and content requests
Need a calculator we don't yet publish? An IMO MEPC resolution, a class-society circular, an EU article, a flag-administration guidance note, a charter-party clause? Email requests@shipcalculators.com. We prioritise requests with regulatory backing; "back-of-envelope" rules of thumb without a published source are harder to add because we cannot cite them.
Privacy enquiries and data-subject requests
For GDPR / UK DPA 2018 rights (access, rectification, erasure, restriction, portability, objection, consent withdrawal), email privacy@shipcalculators.com. We aim to respond within 30 days. See the Privacy policy for the full procedure.
Advertising and partnerships
For ad-network and direct-buy enquiries, sponsored-content proposals (we do not publish sponsored content disguised as editorial), maritime-software partnerships, training-content collaborations, or licensing of calculator data, email partnerships@shipcalculators.com.
Press and media
Journalists and analysts are welcome. We have published explainers covering EU ETS shipping inclusion, FuelEU Maritime, the IMO Net-Zero Framework, and EEDI / EEXI / CII evolution. For interview requests, factual-confirmation queries, or custom data extracts, email press@shipcalculators.com.
General feedback
For everything else, email hello@shipcalculators.com.
What we do not collect
The Contact route is a mailto: link, which opens your local mail client and composes a draft email. Nothing is sent to our servers until you click Send in your own client. We receive only the email you choose to compose. This is intentional: the Site is fully static, and we do not run forms-handling backends that would store submissions in databases.