Verified people
Agency accounts require email verification. Client reviewers receive a private invitation and verify the named mailbox with a code before seeing the delivery.
SECURITY & ACCESS
A clear handoff.
With clear boundaries.
Client deliveries contain important work. Here is how the current Handoff pilot protects access and preserves the delivery record.
Workspace boundaries
Workspace membership and permissions are checked when requests run. Revoked team access takes effect on the next request; unrelated workspaces cannot read each other’s records.
An exact version
Publishing freezes a delivery snapshot and content hash. Decisions belong to that version. Publishing a revision requires a fresh decision and revokes old review access.
Protected transport and sensitive records
The hosted app uses HTTPS. Sensitive billing values, queued email payloads and receipt objects are encrypted. Browser sessions use secure, HTTP-only cookies.
Private receipt downloads
Receipt downloads require current workspace access and a short-lived signed link. The PDF includes the exact source record as a JSON attachment.
Recovery practices
Daily encrypted backups retain the latest 14 successful archives on the pilot host. The initial database restore rehearsal checked record counts and access rules. Continuous off-server backups are not yet configured.
A focused pilot
Handoff currently runs on a shared server with a single application process. Enterprise SSO, high availability and independent security certification are outside this release.
Ask us about security