Readyline
Security & Data Handling
Last updated June 9, 2026
This page describes Readyline’s security posture and intentions during early deployments. It is written to be honest about what exists today versus what is planned — it does not claim certifications Readyline does not yet hold.
Readyline is a readiness layer that sits between utility work planning and contractor field execution. Because two organizations collaborate on the same work package, access control and data handling are designed in from the start rather than bolted on.
1. Access & tenancy
Access is organization-scoped: users only see work packages their organization is a party to. Permissions are role-based, and every request is checked against the acting user’s organization and role — there is no shared, unscoped view of all data.
2. What we store
We store the account and work-package information you and your counterparties enter: references, scopes, requirement values, requests for information, attachments (metadata and, where enabled, files), and the resulting readiness and activity records. Notes can be kept private to your organization where collaboration does not require sharing them.
3. Auditability
State changes are recorded to an activity and audit history. Readiness is computed transparently and is re-runnable, so a score can always be traced back to the underlying requirements — there is no opaque, unexplained decision.
4. Assistive intelligence
Where Readyline uses assistive intelligence — for example, to help identify missing context, summarize blockers, or draft an RFI — it is assistive, not autonomous. Readiness decisions remain transparent, auditable, and under operator control.
5. Export controls
Data export is available to authorized users within an organization (for example, CSV export of work packages). Customer work-package content is not shared publicly and is not sold.
6. Pilot data handling
During a pilot, we work with a limited, agreed sample of active or historical work packets. Pilot data handling terms are agreed in writing before any data is shared, and access is limited to what is needed to run the pilot.
7. Compliance posture
Readyline is built with enterprise controls in mind. SOC 2 readiness is planned as deployments mature and enterprise demand validates it. We will not represent that we hold a certification before we actually do.
8. Reporting a concern
If you have a security question or want to report a concern, contact us at info@ready-line.com.