About / Governance
What a regulated buyer can inspect, with the documents attached
People Tech Revolution builds into hospitals, councils, schools, justice services and enterprises. This page gathers what a procurement, clinical governance, security or legal reviewer asks us for, and links the document behind each answer.
Where the answers come from
The site keeps a claims register in its own repository: a figure gets an entry naming the source it came from, and the entry travels with the wording. The legal documents are versioned and carry an effective date and a checksum of their text. The register of who processes what names a region class for each category of provider, including the ones where the running configuration establishes no region at all.
The bands below are that position in detail, and each one links the document behind it.
The questions a regulated buyer asks
The questions that arrive in a due-diligence pack
These come up in a procurement questionnaire, a clinical governance meeting or a security review. Each answer points at the document it comes from.
Who is behind People Tech Revolution?
People Tech Revolution Pty Ltd, ABN 66 646 534 858, ACN 646 534 858, at 27/65 Manooka Drive, Cannonvale, Queensland. Those identifiers sit in the structured data of every page of this site, and the Australian Business Register entry is public. The founders are Leonie Sanderson and Simon Lowe, and the story page says how the company started.
Where is our information processed?
The Subprocessors and Data Locations register answers this category by category. It records cloud infrastructure and application hosting as deployed in an Australian region, and the managed application database the same way. It records the web caching edge as operated outside Australia. Several categories it lists as not established, meaning the running configuration was checked and it pins no region, and the register says so instead of supplying a likely answer.
Who are the third-party processors?
The same register lists them as categories of service rather than company names, and it explains why in its own opening: a list of names would go stale faster than it could be republished, so what is held out instead is the function performed, the information involved, whether the category touches customer content, and the location or region class. Each row carries the date it was last checked against the production configuration. The register's contact section is where to write for the identity of the providers engaged for a particular product.
How long is information kept?
The Privacy Policy holds retention to as long as is reasonably required for the applicable service, security, business records, disputes or law, and points at the product supplement for product-specific retention and deletion behaviour. Rights of access, correction, deletion, restriction, objection and export follow applicable law, and the policy names the Office of the Australian Information Commissioner as the escalation path for an unresolved complaint.
What does a participant consent to, and what happens to a recording?
A conversational twin operates with consent and with ongoing oversight of what it says on the person's behalf, which is the line the digital twins page draws between a twin PTR will build and one it will not. Consent, copyright and ethical governance around a real person's likeness or voice are settled before the build, a point the explainer takes from UNESCO's global recommendation on AI ethics.
For a live twin call, the subprocessors register is explicit about what travels: the consented reference photograph, live microphone audio and camera video from the participant's browser, the persona prompt, the transcript, and any recording. It records that category as processing outside Australia, because the provider publishes no region split for it.
How does a session leave a record an assessor can inspect?
In a hospital, the answer is the training register. NSQHS Action 1.20 asks a health service organisation to implement a mandatory training program and to monitor the workforce's participation in it, and the standards page quotes the action in the Commission's own words.
What PTR supplies against it is a program that goes from a pilot into something the hospital runs itself: at Mater Education, delivery reached staff across Brisbane and regional campuses face to face, and Mater's own facilitators were trained to run the technology, with the evaluation published under Mater's name, which is how it happened at Mater Education. Outside health the shape is the same: a safety or people lead holds a record of what was rehearsed, by whom, and how often they came back to it, which is the answer the workplace page gives. Action 5.34 is the other standard the healthcare work is built around.
What about accessibility and participant safety in a headset session?
The library experiences are built for limited controller use, simple trigger pulls for people with mobility issues, limited movement inside a scene, and short scenarios that reduce eye strain. Motion sickness affects people differently, tends to reduce with repeated use, and is less common in seated or slower-paced experiences than in fast first-person movement. Glasses can usually stay on, made easier by the spacer that usually comes with the headset. The FAQ answers each of these in the words they get asked in.
Who runs the debrief?
A trained facilitator, in the room, after the headset comes off. The debrief is a facilitated group discussion where participants reflect on what they saw, connect it to real situations and talk through how they might respond differently. It is run by a person rather than delivered inside the headset, and that is a design decision the immersive training page is built around.
What about psychosocial safety at work?
In Queensland, where PTR is based, a business has a duty to manage psychosocial risks. Section 55D instructs nobody to run a course. It says that in determining control measures a business must have regard to all relevant matters, and among the matters it lists are workplace interactions or behaviours, and the information, training, instruction and supervision provided to workers.
Redesigning the work comes first, and the workplace page says so in those words. Job demands, staffing, systems of work and layout are all named ahead of training and they do more. Rehearsal is for what is left once the work has been redesigned: the manager who still has to raise the concern, and the person who still has to hear it.
How does a first build get funded and contracted?
Out of money already committed to something else. A state grant plus a hospital's own innovation funding, a regulator-funded pilot that a partner already held, or an access and inclusion strategy with an owner and a budget: the funding page names the precedent behind each one and what the funder received back.
Contracting sits under the Terms of Service where no separate negotiated agreement applies, with product supplements for specific products, and enterprise terms, order forms or signed agreements controlling where they conflict. Both documents are versioned at the legal site below.
What you can inspect
The material behind the answers, all of it open
Every band above rests on something a reviewer can open and read in their own time. Here is where each of those things lives.
And the legal library, versioned like code
Each published PTR legal document carries a document identifier, a version, a status, an effective date and a SHA-256 of its own text, and a new version replaces the old one at the same address. A machine-readable registry of every document and version sits alongside them, which is what lets a reviewer pin the exact text they assessed.
Subprocessors and Data Locations
Every category of service provider PTR relies on, each with its purpose, the information it processes, its processing location or region class, whether it touches customer content, the products it applies to, and the date the row was last checked against the running production configuration.
Privacy Policy and Terms of Service
Collection, use, customer-organisation responsibilities, device permissions, artificial-intelligence providers, service providers and international processing, disclosure, retention, security, rights, children, cookies and the complaints path. The Terms cover eligibility, permitted use, accounts, customer content, purchases and Australian Consumer Law.
Clinical Governance Standard, Action 1.20
The health service organisation uses its training systems to assess the competency and training needs of its workforce, implement a mandatory training program to meet its requirements arising from these standards, provide access to training to meet its safety and quality training needs, and monitor the workforce's participation in training.
Enterprise delivery
From a pilot to something the organisation runs itself
PTR builds toward a program the customer's own people run, with a record their own assessors read.
The handover is the deliverable
At Mater Education the pilot became a program the hospital took across its Brisbane and regional campuses, and Mater's own facilitators were trained to run the technology themselves. The evaluation went out under Mater's name. The case study and the pilot write-up both describe that handover.
With XRHealth Australia the structure came the other way round: the funder and the pilot existed first, and PTR was brought in to build the part of it that needed building, for a WorkSafe Victoria-funded program on workplace mental health and recovery in the transport industry.
The rollout is rarely the headset
The same conversation runs typed at a desk, or spoken out loud before the one to one, on the laptop the work is already on. The headset is the deepest version of the practice rather than the way a whole workforce reaches it, which is how the workplace page and the roleplay page both scope a rollout.
That matters to an IT reviewer. A program whose common path is a browser on an existing laptop asks less of a device fleet than one that needs a managed headset on every floor.
What an IT or security reviewer opens with
Devices, networks and how an integration reaches us. Each answer here is the one the delivery pages already give, and each is settled per project rather than by a house standard that would be wrong somewhere.
What a reviewer should ask us for next
The subprocessors register names the address to write to for the provider information a procurement or regulatory assessment needs, and for the contractual position on a particular provider. The product supplement that governs a build comes with the agreement for it. Say which product and which reviewer is asking, and the answer goes back to them directly.
