Trace by Reliable Group
Trace deployment guide
For the IT, security and department owners preparing a deployment: prerequisites, machines, updates, removal, data retention and the setup script.
Trace is not standalone software; it runs inside a Reliable Group engagement.
Guide last reviewed November 2026.
See it running
Functional
Briefings and skills being generated
What a department owner and an individual see once Trace is running: briefings, and a skill produced from a repeated workflow.
Technical
The deployment and what it needs
The setup into your Azure or Google Cloud account, the temporary role it creates and removes, and the access controls your IT owner sets.
Before setup
Prerequisites
Your IT and security teams review the setup script before it runs. Setup creates a temporary role in your account, installs the capture and analysis stack, then removes the role. A manual install is available where your policy requires it.
Prerequisites as of November 2026.
- An Azure or Google Cloud account with rights to create a temporary role
- A named IT owner
- The applications in scope
- The machines you designate, checked against the endpoint fact sheet
- The written team-member notice
- Compliance sign-off
- A BAA where PHI is in scope
Running it
Machines, updates and removal
Supported machines
Trace runs only on the machines you designate. The endpoint fact sheet in the technical review package sets out the supported operating systems and versions; your IT owner confirms each machine against it before capture starts.
Updates
Reliable Group compiles and signs its own build and can show its provenance on request. How updates reach your machines and your cloud account, and who approves them, is set in the scope agreement with your IT owner.
Removal
Trace sits on the machines you designate and in your own cloud account, so removal happens there, under your controls: the capture software comes off the machines and the stack comes out of your account. We provide the steps.
Data retention
Who is responsible for what
- Retention schedule
- Your privacy officer sets how long the capture record, screenshots, briefings and skills are kept. We apply the schedule you define.
- Where records live and are deleted
- Your cloud account, under your access controls. Nothing is copied to a Reliable Group environment.
- Who can read the record
- Your IT owner sets departments and visibility. Our named analysts read through the Trace admin console, and every read is logged.
- Skills run in Claude or ChatGPT
- Under your own agreements with those providers, including their retention terms.
- BAA
- Where a department handles protected health information, we execute a business associate agreement before Trace is installed or any data is accessed.
- Notice
- We deploy Trace only after your organization has given team members the written notice required in your state; we provide the notice template.
The setup script
Requesting the setup script
The setup script is not published. It is shared privately with your named IT owner for review before it runs, together with the technical review package: the architecture overview, the endpoint fact sheet and the scope agreement. To request it, contact us with your organization and the name of your IT owner.
Next step
Questions before you run it?
Your IT and security teams get the architecture overview, the endpoint fact sheet and the scope agreement, then a joint session that closes any open items.