How we handle your information.One page. Plain English. Written for an Australian small-business visitor.
Spokedraft runs the contact form on /contact, the lead-magnet waitlist on /guide, and the team inbox at spokedraft@polsia.app. This page describes, in plain English, what each surface collects, where the data lands, how long it stays, and what to do if you want it changed or removed.
What we collect, and where
There are three places on this site where information moves from your side to ours. Each one explains exactly what is collected and what is done with it.
The contact form on /contact collects your name, your email address, and the message body you type. That is the whole submission — nothing else is read from your browser or attached automatically. By hitting send you are asking us to reply to the message; using the form is your acknowledgement that we can contact you back about that enquiry.
The lead-magnet waitlist on /guide collects your email address only. Nothing else — no name, no company, no phone number. By entering your email you are asking us to send you the short guide you signed up for, and to keep you on the list while the guide is being delivered.
A direct email to spokedraft@polsia.app collects whatever your mail program records on the way in — the subject, the body, the signature, and the headers every mail server logs (sender, recipient, timestamp). We treat that the same as a contact-form submission: by emailing us you are asking us to reply to that thread.
How we store it
Everything you send to Spokedraft lives in a small number of well-defined places, accessed only by the in-house team.
Contact-form submissions live in Spokedraft's message store — the place our team reads from when we reply to /contact. The store is accessible only to the small in-house team who scope, build and support installs; no third party reads it and no offshore team is involved.
Waitlist signups from /guide live in the same store, deduplicated on email address so an accidental re-entry never produces two records. The list is used to send the guide and to keep you posted while the guide is being delivered.
Direct email threads are held in Spokedraft's team inbox at spokedraft@polsia.app. Outbound replies from that address go through a managed email proxy that the small team has direct access to.
We do not sell, rent, trade or otherwise pass any of this to anyone else. There is no marketing list being built on the side, no partner-share, no enrichment pipeline.
How long we keep it
A short, committed retention policy — set to be reasonable, not as short as we can technically claim it to be.
Contact messages are kept for as long as the conversation is active, archived once the enquiry is resolved, and deleted shortly after. If you come back to us on the same thread a year later, we can re-open the archive and pick the conversation up — otherwise the record leaves the store.
Waitlist signups are kept until you ask to be removed. Reply to any guidance email and we take you off the list, or email spokedraft@polsia.app directly and we will do it by hand. There is no auto-expiry and no re-marketing rabbit hole.
Direct email threads are held as long as the matter is open, then archived after a period of inactivity. The same archive-then-delete rhythm applies whether the thread started on /contact, came in by waitlist reply, or arrived directly.
In the spirit of the small-business reader this page is written for: the operator's policy is not the bare legal minimum, it is the policy we would want a vendor to hold ours under.
How we use it
The use is the narrow one — to reply to your enquiry or send the guide you asked for. Nothing broader.
We use what you send us to reply to your enquiry or to send the guide you signed up for. That is the use, from first message to last reply.
We keep the conversation running on the surface it started on. A /contact submission is replied to from the contact inbox; a /guide signup is sent the guide from the same inbox; a direct email is replied to by direct email. Threads do not get shunted to other channels mid-conversation.
We do not use anything you send us to add you to a third-party marketing list, to enrich a CRM profile, or to share with a partner. The information is held between us, used to answer the question you asked, and then aged out on the schedule above.
Third-party processors
Two services are involved in moving mail to and from spokedraft@polsia.app and in hosting the site itself. Both are listed below, in plain English.
Polsia-managed email proxy
Used to send and receive mail on spokedraft@polsia.app. The proxy logs only what every mail server logs — sender, recipient, subject and timestamp — so a message can be delivered and replied to. We can see and audit those logs from the operator side; no one outside the operator team does.
Vercel hosting
Used to host the website and to store the data above. Vercel acts as the infrastructure provider for the running app and its database. Personal data submitted through the site therefore sits on Vercel-managed servers for as long as the retention window above is open.
Your choices
You stay in control of what you have sent us. The actions below are all available on request, with no form to fill in.
Ask us to correct anything we hold about you. Email spokedraft@polsia.app with the change and we will make it.
Ask us to delete your contact record, your waitlist entry, or both. We confirm the deletion in writing once it is done.
Unsubscribe from the waitlist by replying to any guidance email or by emailing spokedraft@polsia.app. The reply-to on every guidance message is the same address — one click, off the list.
Ask any privacy question, and we will reply the same way we reply to everything else: inside one business day, from Sydney. There is no separate privacy workflow that takes longer because the message is more sensitive.
Australian context
A short note addressing the audience this page is written for — a small-business reader running on AEST/AEDT.
Spokedraft is the operator's business name. The team works out of Sydney, on Australian Eastern time (AEST in winter, AEDT in summer). Replies come from that timezone, in that timezone's hours.
To the extent the Privacy Act 1988 (Cth) and the Australian Privacy Principles apply, Spokedraft holds itself to them on a small-business footing. We treat your information the way the Act expects a small operator to treat it: collected for a stated purpose, held for a stated period, not shared onward.
If you would rather read this in the framework of your own organisation's privacy policy — because you are signing off on Spokedraft as a vendor — send us the diff and we will tell you what is and is not covered. Most small-business privacy policies line up with this one by design.
If a question isn't covered above, send it to spokedraft@polsia.app. We will reply, and we will update this page if the answer is one a future reader would also want to see.
Still want to know something specific?
If a question above wasn't what you came looking for, send it through and we'll either write back or update this page so the next reader finds it.