Emba ConsultingDiscreet candidate handling
Registration is reviewed before representation. Candidate details are not sprayed across the market or used as filler for speculative shortlists.
What clients and candidates should expect
Practical trust controls, not theatre.
Emba keeps the public experience simple while maintaining strong internal boundaries around candidate information, commercial context and automation.
Security-aware delivery
Cloudflare protections, security headers, rate limits, Turnstile and access controls protect the public edge. Internal drift checks monitor the stack.
Automation with judgement
Automation helps with triage, reminders, reports and ledgers. External submissions, invoices, pay runs and client-facing commitments stay behind a human gate.
PII minimisation
Public forms ask for enough to start a useful conversation. Sensitive identity, payroll and clearance material is not collected through public webpages.
Government-aware posture
For regulated work, Emba treats client requirements, security expectations and official information handling as part of the operating model, not an afterthought. The Government ICT capability pack summarises this posture for procurement teams.
Evidence over assertion
Health checks watch site availability, edge configuration, mail posture, candidate portal controls and business-system drift so issues are visible early.
What Emba deliberately does not do.
No automatic representation
Candidate registration does not authorise blanket submission. Emba reviews fit and context before any client conversation.
No public secret intake
The website is not a channel for TFNs, bank details, clearance numbers, police checks or identity documents.
No blind outbound automation
Drafting, reminders and operational checks can be automated. Sending, submitting, signing, invoicing and pay-run posting require approval.
No inflated security claims
Emba describes the controls it actually runs. Formal certifications or legal determinations are only claimed when they are real and current.
Security contact.
If you believe you have found a vulnerability affecting Emba systems, contact hello@emba.au. The canonical security contact is published at /.well-known/security.txt.
This page is intentionally plain. It avoids over-claiming and reflects current operating principles rather than a formal certification statement.