Correspondence · encrypted paths
Start a factual, auditable conversation
Messages stay within the informational scope outlined across this site: scheduling explainers, drink-plan templates, environmental cue documentation, refunds, or privacy clarification. We route procurement leads toward written estimates; we decline bespoke medical interpretation, biometric surveillance hooks, or marketing list rentals. Multilingual teams may request glossaries ahead of calls so te reo salutations and English operational bullet points align without rushed improvisation.
Postal, voice, and digital routing without shadow inboxes
We publish a single street address, one published telephone line, and one operational mailbox so audit trails stay legible. If your organisation routes procurement through vendor portals, mention that inside the message body—we still reply from the addresses below to preserve chain-of-custody notes referenced inside our privacy materials.
Secure message form
Mandatory fields mirror GDPR expectations: accurate contact data and explicit acknowledgement before transmission. Field-level errors appear inline; successful validation navigates to a brief thank-you page without storing card data because we never collect it here.
How quickly should we expect human replies?
May we attach classroom photographs?
Who reads messages if someone is on leave?
Processing posture after you press send
Expect acknowledgement within typical business timelines. We summarise retention inside privacy notices and encrypt messages in transit where hosting providers cooperate. Threads about cookies or analytics tagging should cite which browser experiments you ran—we answer methodically rather than speculate about compliance outcomes we have not audited.
Prefer analogue prep before submitting?
Teams sometimes mail printed workshop drafts to the Queen Street address with cover letters referencing prior email threads—either path works as long as identifiers stay consistent for our coordinators.