Trust and security
Employee data, handled like an operating record.
Relay holds schedules, responsibilities, training and shift history for real people. These are the principles the product is built on, stated plainly and without borrowed credentials.
- Scoped access
Access is scoped to organization, location and role. People see the operating context they work in, not everything the company has ever recorded.
- Attributable actions
Where the product supports it, actions carry a person and a time. That is the point of an operating record — it should be possible to say what happened and who handled it.
- Tenant isolation
Each organization's data sits behind its own authorization boundary. Requests are authorized against the organization and location they claim, on the server.
- Private evidence
Photos, notes and completion evidence are stored as private operating records tied to the shift, reachable through authorized access rather than public links.
- Defined operational purpose
Employee data is handled for defined operational purposes: scheduling, coverage, responsibilities, training and shift history. It is not collected for resale.
- Not covert surveillance
Relay is not designed as covert surveillance software. It records work that the team is asked to do and can see, and employees can see their own record of it.
Relay does not claim SOC 2, ISO or any other certification, and does not claim regulatory compliance on this page. When formal attestations exist, they will be published here with their scope and date.
Operational readiness
What we hold ourselves to.
- Backups
- Regular backups of operating data, with restoration treated as a tested procedure rather than an assumption.
- Monitoring
- Application and infrastructure monitoring so failures are noticed by us before they are noticed during service.
- Incident ownership
- A named owner for security and reliability incidents, with customer notification handled directly.
- Retention and deletion
- Operating history retained for the period agreed with the customer, and deleted on request within a defined window.
Legal surfaces
Documents, as they stand today.
These pages describe how Relay operates. Final contractual terms are prepared with counsel and issued directly as part of a pilot or subscription agreement.
- Privacy
How Relay handles operational and employee data.
Read - Terms
Service terms, issued with your agreement.
Read - Security
The principles and readiness practices on this page.
You are here - Contact
Security questions, data requests, or a technical review.
Get in touch
Bring the shift that keeps biting you.
We’ll walk through the real service, the systems beside it, and where Relay could own one workflow.