The compliance flight recorder for
automated decisions
Australia's Privacy Act now requires you to track and disclose every algorithm, score, filter and macro that affects a person's rights. ADM Guard records every automated decision the microsecond it executes - immutable, tamper-evident, and with privacy-focused controls designed to block personal data.
# Compliant in an afternoon, not a two-week sprint
from admguard import record_decision
record_decision(
system_key="resume_screener",
subject_token="cand_88192_x", # your anonymous token - never a name
decision_type="reject",
factors={"score": 41, "threshold": 65},
)- < 30 minto first logged decision
- PII controlsingestion validation + rejection paths
- 100%Australian data residency
Why now
The December 2026 enforcement cliff is real
The Privacy and Other Legislation Amendment Act 2024 introduces mandatory transparency obligations for Automated Decision-Making under Australian Privacy Principles 1.7–1.9. If a computer program materially affects a person's rights or finances - a credit score, a resume filter, a tenancy ranking - you must be able to identify it, describe it, and evidence it.
- Jun 2026OAIC closes Issues Paper consultation
- Sep 2026OAIC releases final regulatory guidance
- Oct 2026Budgets unlock - the compliance rush begins
- 10 Dec 2026Hard enforcement. Penalties active.
The old answers don't work
- Law firms ($20k-$50k): a static policy PDF that's out of date the moment your engineers ship code.
- Manual AI registers: a spreadsheet-with-a-UI that relies on humans remembering to type updates.
- Build it yourself: two senior engineers, a dedicated sprint, about $15,000 of salary - for undifferentiated plumbing.
ADM Guard operates at the code layer
- Systems auto-register the microsecond they execute in production - the register can't drift.
- Every decision is cryptographically chained and anchored to WORM storage.
- One API call per decision, idempotency-key retries built in. Engineers stay on roadmap.
Pricing
Simple pay-as-you-go pricing
Start with pay-as-you-go pricing based on your decision volume. No fixed tier commitments while you're validating rollout.
FAQ
Common questions
Do you ever see our customers' personal information?
No. You send client-generated anonymous tokens (e.g. cand_88192_x) - never names, emails or phone numbers. Our API applies validation controls and rejects payloads that match configured PII patterns before persistence. You keep the identifier mapping in your own systems.
How long does integration take?
Our target is under 30 minutes from your first API call to first decision visible in your dashboard. A full production rollout across several decision points typically fits in one afternoon.
Where is our data stored?
Exclusively in Azure's Australia East region, enforced by cloud policy. Archived audit batches are held on write-once (WORM) storage with locked retention - they cannot be altered or deleted, even by us.
Does ADM Guard make us legally compliant?
ADM Guard provides the technical evidence layer - the immutable record of what your automated systems actually did, plus the live register and disclosure-ready reports the obligations anticipate. Legal compliance also involves your privacy policy and processes; we integrate cleanly with the advice of your privacy counsel. ADM Guard does not provide legal advice.
Be ready before the December cliff
Get in touch and we'll map your decision points, estimate volumes, and show you a live tamper-evidence verification - on your data shape.
Why teams choose us
Built for compliance evidence at software speed
Zero-PII by design
Payloads containing personal information are rejected at the boundary before persistence.
Cryptographic integrity
SHA-256 chains and immutable storage make post-hoc tampering detectable and provable.
Fast integration
One API call per decision path. Engineers instrument once and stay focused on product delivery.