Legal agreements
The platform runs on clickwrap agreements: checkboxes and affirmative clicks that are binding electronic signatures (you consent to exactly that in the Terms of Service). This page maps every document, every gate, and what gets recorded.
The documents
Section titled “The documents”| Document | Current version | Who it binds | Where to read it |
|---|---|---|---|
| Platform Terms of Service | 1.1 | Every user, with role-specific schedules | /terms (public, and in-app for every role) |
| Privacy Policy | 1.1 | Every user | /privacy (public, and in-app) |
| Mobile App EULA | 1.0 | Anyone using the iOS/Android app | Presented in-app on first native launch |
| Master Client Services Agreement (MCSA) | 1.1 | Client organizations | /mcsa (clients only) |
| Placement Order Terms | 1.1 | One per booked placement | /placement-order (clients only) |
Some roles have additional per-engagement documents; they are presented in-app at the moment they apply and are covered in that role’s own guide.
All documents are served fresh from the platform, so the text you read is always exactly the version your acceptance would record.
When each acceptance happens
Section titled “When each acceptance happens”At account creation (everyone)
Section titled “At account creation (everyone)”Registration and invite-acceptance both require two checkboxes:
- “I have read and agree to the Terms of Service, and my clicks in this platform are binding electronic signatures.”
- “I have read and agree to the Privacy Policy.”
The server refuses account creation without them (“You must accept the Terms of Service” / “You must accept the Privacy Policy”).
When terms change (everyone)
Section titled “When terms change (everyone)”If L3 publishes a new version of the Terms or Privacy Policy, the next time you use the app you’ll meet the re-acceptance gate: “Please review and accept to continue” (eyebrow UPDATED LEGAL TERMS) — “We’ve updated the documents below. You’ll need to accept the current version before using the platform.” Tick each updated document (the title opens the full text) and click “Accept and continue”. The gate is computed server-side on every session, in the web and mobile apps alike — material changes take effect by re-acceptance, not by continued use.
At first booking (clients)
Section titled “At first booking (clients)”The first time a client account accepts a proposal line, the confirmation includes: “I have authority to bind my company and accept the Master Client Services Agreement.” Once your MCSA acceptance is on file, it isn’t asked again (until the MCSA version changes).
At every booking (clients)
Section titled “At every booking (clients)”Every accepted proposal line requires: “I accept the Placement Order terms for this booking at the day rate shown.” Each acceptance creates a Placement Order for that specific booking — the deal’s numbers (candidate, rate, start, cadence) live in the accepted line itself.
Your copy of each Placement Order names the contractor and shows your all-in day rate.
On first mobile launch (native app users)
Section titled “On first mobile launch (native app users)”The mobile app presents the Mobile App EULA once per device: “I have read and agree to the Mobile App EULA, including delivery of app updates over the air.” → “Agree and continue”. See The mobile app.
The audit trail
Section titled “The audit trail”Every acceptance writes a permanent, immutable record: who (user + role), what (document + version + a SHA-256 fingerprint of the exact text served), when (UTC timestamp), from where (IP address — the Privacy Policy discloses this narrow retention), and for deal-scoped documents, which placement. Records are never updated or deleted; the first acceptance instant is the legally meaningful one. These records are the platform’s proof of contract formation.