Trust centre
Security for services that act, approve and prove work.
A Tredy service reads documents, works inside sessions you approved, asks for decisions and produces evidence-backed artefacts. The trust model makes each of those things scoped, visible, reviewable and exportable.
Trust model
The controls travel with the service.
They are not a setting on the platform that someone remembers to switch on. They are attached to the service, so the same limits apply on every run of it.
Data handling
Service inputs, source extracts, browser captures, run traces and output artefacts are scoped by workspace policy.
Browser permissions
Services that work in the browser can be limited by allowed domains, page access, action type, and evidence retention.
Credential boundaries
Tredy works through approved sessions, without exposing passwords or secrets to service prompts.
Approval gates
Sensitive actions such as submit, send, delete, publish, purchase or update can pause for a reviewer.
Audit trace
Every service run can preserve pages visited, data read, decisions made, approvals and the final artefacts.
Evidence exports
Export trace timelines, screenshots, source links and approval history alongside the finished artefact.
Start with one service.
A 30-minute scoping session with your risk owner and your IT contact. We leave with the first service named, the connections listed, and a date.