This page sets out how we build, deploy, and hand over AI systems for the businesses we work with, who is accountable, what we will not build, and how anyone can raise a concern.
It is a trust artefact, written for the directors, owners, and operators who carry the risk of the systems we install. It is not a marketing page. If a claim here does not hold up to a direct question, we have written it wrong and want to hear about it.
They show up in our scoping conversations, our service agreements, and our handover packs.
Every tool, credential, account, dataset, and workflow we build sits under the client's own infrastructure. If Roovolt stops tomorrow, nothing breaks and nothing walks out the door.
No workflow sends externally, commits funds, or takes an irreversible action without a person in the loop. We design for meaningful human control, not for autonomy.
We build the specific system the business needs. We do not deploy unbounded autonomous agents in production, and we do not recommend them.
Every engagement ends with documentation, training, and a 30-day stabilisation period with the client team, so the people who have to run the system after us actually can.
Every engagement ships with a written Security Considerations section covering the specific tools deployed, their data residency, their retention settings, and their known limitations.
We are a small Australian consultancy, not a certified AI assurance provider. Where a framework calls for a formal artefact we do not yet produce, we say so and point to how we close the gap.
Douglas Reyes Corrin is the accountable person on the Roovolt side for every AI system we build, deploy, or hand over. He is the point of contact for Roovolt clients, and for any director or accountable officer reviewing a Roovolt engagement, on any question, concern, or incident relating to our work.
Email doug@roovolt.com.au. Phone 0468 031 661 (Roovolt AI Assistant line, routes to Doug).
For every active engagement, a named escalation path on the client side is agreed during scoping, so that issues have a clear route on both sides.
The single strongest claim we can make about our work is that meaningful human oversight is the operating default, not an optional extra. This is consistent with Guardrail 5 of the Commonwealth Voluntary AI Safety Standard (2024).
In practical terms:
If a proposed build sits in a grey area, we say so in writing during scoping. If we cannot find a way to meet the principle above and deliver the business outcome, we decline the work.
If you are a Roovolt client, or a director or accountable officer reviewing a Roovolt engagement: email doug@roovolt.com.au or call 0468 031 661. Include the engagement reference and a description of what happened. We respond as quickly as we can.
If you are an end user, a customer of a Roovolt client, or another third party interacting with a system we have built: the contest and complaint path sits with the client that owns and operates the system. Your first contact should be their nominated accountable officer within that business. This is how the frameworks intend contestability to work: with the deployer of the system, not with the supplier that built it.
If your concern relates to a live incident (harmful output, data exposure, unauthorised action) and the client is not responding, you can contact us directly at the details above. We will prioritise it and move to notify the client's accountable officer without delay.
If you are not satisfied with the response and your concern relates to personal information, the Office of the Australian Information Commissioner (oaic.gov.au) is the relevant external avenue.
Our delivery approach is informed by, and consistent with the core guardrails of, the following Australian frameworks:
The 8 Elements of Safe and Responsible AI. We reference this Guide when scoping engagements and structuring handover documentation, and we are progressively formalising our practice against the elements we currently satisfy only in part.
The 10 Guardrails published by the Department of Industry, Science and Resources. Our human-oversight default and client-ownership model directly implement Guardrail 5. Formal documentation against all 10 guardrails is in progress.
The evolution of the 10 guardrails into 6 essential practices for organisations adopting AI. We track this guidance alongside the standard above.
The principles our acceptable-use rules are anchored in.
We do not claim full alignment with any of the above. We claim our operating model is consistent with their core guardrails and that we are honest about the gaps. Directors who want to see how we assess and monitor AI systems internally can email hello@roovolt.com.au and we will share the templates we currently use.
This page will be updated as our practice formalises against the frameworks above. Material changes are noted here.
Version 1.0, 14 April 2026. Initial publication.