Security & responsible technology
Careful with information, honest about automation.
Two things are on this page. What this website does today, which you can check. And the working principles behind the systems we build, which are principles rather than certifications: we hold ourselves to them, and we do not claim an audit, a standard or a guarantee we have not earned.
- Effective
- Last reviewed
How this website works today
Each of these is true of the site as built and is checked whenever the site changes.
- 01
No analytics or advertising trackers
The website loads no analytics, no advertising pixels, no tracking scripts and no embedded third-party content, and it sets no cookies.
- 02
Enquiries are not stored by the website
There is no website database. An enquiry is delivered by email and the website keeps no copy.
- 03
Delivery is decided on the server
The address an enquiry is delivered to is chosen by our server from the shape of the submission. Nothing in the request can change it, and the credentials involved never reach the browser.
- 04
Basic abuse limiting
The contact form is rate limited by connection address for a few minutes at a time. The address is not stored or attached to the enquiry.
- 05
Blueprint links carry option identifiers only
A shareable System Blueprint link contains the identifiers of the options you selected and nothing else. There is no field in the configurator that could put personal information into a link.
- 06
The blueprint uses fixed rules
The System Blueprint is deterministic: the same selections always produce the same result, every statement is traceable to the options behind it, and no AI model is involved.
- 07
Human decisions stay visible
Where the blueprint or a system example shows a step that should remain a person's decision, it says so on the page rather than implying everything is automated.
- 08
Concept work is labelled
Every system example is marked as a concept and carries the same disclosure: it is not completed client work, and no results are claimed.
How we approach client systems
Working principles for the systems we design and build. They describe how we work, not a standard we are certified against.
- 01
Collect and keep only what a system needs
We design systems to hold the information their job requires and to let go of what it does not.
- 02
AI for a defined purpose
We use AI where it has a clear job, defined limits and a way to check its work, not simply because it is available.
- 03
Accountable human oversight
Consequential decisions keep a person accountable for them. We design the approval step in rather than adding it afterwards.
- 04
Confidential client information and third-party AI
We do not place confidential client information into third-party AI services without an agreed and appropriate basis for doing so.
- 05
Security in proportion to the risk
The protections around a system are matched to the information it holds and what could go wrong, and are explained rather than assumed.
- 06
Test what matters
Important workflows and their failure states are tested before they are relied on, and monitored where the work calls for it.
- 07
Clear ownership and handover
What we build is documented and handed over so that it can be operated without us. Staying with us is a choice.
- 08
Do not automate what should stay human
Some decisions should remain a person's. Part of our job is saying which ones, even when automating them is possible.
- 09
A way to raise a concern
Privacy or security concerns about this website or about work we have done can be sent to hello@needyahmate.com.au. We read them, and we reply.
Report a security concern
If you believe you have found a security or privacy problem with this website, or with a system we have built, email hello@needyahmate.com.au.
Describe what happened and the page or system affected.
Do not include passwords, credentials or any personal information that is not needed to explain the issue.
We will acknowledge the report and investigate it responsibly. We do not run a reward programme and we do not promise a fixed response or resolution time.
What this page is not
It is not a compliance statement, a security certification, an uptime promise or a warranty. If you need any of those for a project, they belong in the written agreement for that work, where they can be specific.