Privacy
What this site does with your information.
There is one form here. It exists so an enquiry can be answered. This page says what that enquiry contains, who reads it, where it is kept, and how to have it removed.
Who is responsible
Made to Ship is responsible for the personal information described on this page. It is an Australian business, registered under ABN 35 910 404 693.
There is no postal address for a privacy request. The route is email: hello@madetoship.com, and a person reads it.
What is collected
The contact form asks for four things: your name, your email address, your company if you give one, and your message. Those four values are the whole of what a visitor can send us. The submission is stored in the site's own database, with the four answers kept together as JSON.
The form also stores one thing you did not type: a hash of the IP address the request came from. It is a SHA-256 hash made with a key held on the server, and it is kept so the form can be rate limited when somebody floods it. The raw IP address is not stored, and the hash cannot be turned back into an address without the key.
That is all of it. This site has no visitor accounts, no client login, no newsletter, no payment page and no card field anywhere. There is no analytics script, no advertising pixel and no third-party embed. The fonts are served from this domain, so opening a page does not call out to a font service.
Staff sign-in
One part of the site is not public: /admin/login, where the people who run the site sign in to edit pages. An operator account holds an email address, a password stored as an Argon2id hash, and a time-based one-time password secret used as a second factor. There is no self-service sign-up, so a visitor cannot create one of these accounts.
Cookies
One cookie is set on this site, and only after a successful staff sign-in: __Secure-sk-sess-madetoship. It carries that session. It is Secure, HttpOnly, SameSite=Strict, and limited to Path=/admin, which means it is not sent to any page a visitor reads. It is strictly necessary — without it an operator cannot stay signed in while editing.
A visitor who is not signed in receives no cookie from us. There is no analytics cookie, no advertising cookie, no preference cookie and no cookie set by another company. Nothing on this site needs a consent banner, because nothing on it follows you across other sites.
Why it is held, and what allows it
- To answer the enquiry and quote the work. The information is the only way to reply.
- To keep a record of what was asked and what was quoted, so a later conversation does not start from nothing.
- To stop the form being flooded, which is what the hashed IP address is for.
- To keep the site itself secure, which is what the operator account is for.
Under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, this is information collected for a purpose you would expect when you fill in a contact form (APP 3 and APP 6), and held no longer than that purpose needs (APP 11). Nothing is collected by stealth: the form says what it wants before you type.
For a visitor in the European Union or the United Kingdom, the bases under the GDPR are: steps taken at your request before entering a contract, for the enquiry and the quote (Article 6(1)(b)); and our legitimate interest in answering business enquiries and keeping the site secure (Article 6(1)(f)). We do not rely on consent for the contact form, and we do not profile anyone.
Who else sees it
Four suppliers are involved in running this site. Each sees a narrow slice of it:
- DreamHost hosts the site on a virtual private server. It stores the database, so the enquiry sits on its disk, and its network answers the request when a page or a form is served.
- Cloudflare is the authoritative DNS provider for the domain. It answers the lookup that turns the name into that address and nothing else. The records are DNS-only, not proxied, so page requests do not pass through Cloudflare and it does not see them.
- Let's Encrypt issues the TLS certificate. It sees the domain name in the certificate, which is published in a public transparency log, and nothing about any visitor.
- Purelymail provides the mailbox at hello@madetoship.com. An enquiry answered by email passes through it, and the correspondence stays there.
Nobody else. We do not sell information, we do not share it with advertisers or data brokers, and we do not send it anywhere it is not needed to answer you. A supplier may disclose it if compelled by law; if that happened and we were allowed to say so, we would tell you.
How long it is kept
- An enquiry is kept while it is being answered, and afterwards for as long as it is needed for the purpose it was collected for: to reply, to quote, and to keep a record of what was asked.
- It is deleted when you ask for it to be deleted, or when it is no longer needed for that purpose.
- There is no separate archive of deleted content. Deleting an enquiry removes the row and the message; backups are rotated, so a copy leaves them as they rotate.
- An operator account is kept while the person has access to the site, and removed when they do not.
- The hashed IP address is kept with the submission it arrived with, not as a separate log.
Your rights
You can ask for a copy of what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to hello@madetoship.com and say which. We answer within 30 days. We may ask one question to confirm the request is yours; the address it came from usually settles it.
Deletion is real: the row is removed from the database and the message from the mailbox. It does not reach into a backup already written: backups are rotated, so a deleted record leaves them as they rotate.
If you are in the EU or the UK you also have the right to restrict processing, to object to it, and to receive your information in a portable form. The same mailbox handles those requests, and you may complain to a supervisory authority in your country at any time.
In Australia, if you think we have breached the Australian Privacy Principles, write to us first so we can fix it. If the answer is not good enough you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au or on 1300 363 992.
Security
Passwords are stored as Argon2id hashes, never as text. Sign-in needs a second factor from a time-based one-time password app. IP addresses are stored only as keyed hashes. Traffic is encrypted with TLS and the certificate renews itself. Access to the server and the database is limited to the people who run the site.
No system is perfect. If something goes wrong and your information is affected, we will tell you, and we will tell the OAIC where the Notifiable Data Breaches scheme requires it.
No automated decisions
Nothing here makes an automated decision about you. No enquiry is scored or ranked, and no software decides whether you are refused or accepted. A person reads the enquiry and replies.
Changes to this policy
If what the site collects changes, this page changes with it and the date below changes too. A material change is described on the page rather than made quietly.
Last updated 13 November 2026.