Help

How LeaverProof works, end to end. Email [email protected] for anything else.

Accounts and team

Signing up creates an account (your MSP) and makes you its owner. Owners and admins can invite teammates from Team. A person belongs to exactly one account. Other MSPs cannot see your clients, records or packs, and every page and download is scoped to your account.

Clients

Add each client company once, under Clients. Every leaver record lives under a client, and each client page shows its records and its running total of not-returned equipment value, summed from the values you entered on each leaver's current record version.

Leaver records and the checklist

A record holds a leaver's name, their supervisor at the client, an optional last working day, and the technician assigned. The checklist is fixed in this version: accounts disabled, mailbox disposition, OneDrive / files disposition, groups and distribution lists removed, OAuth / app access removed, license reclaimed, equipment, and the data purge date. Mark each section done, not applicable, or exception with a note. Saving a section stamps who saved it and when.

There is no field for a password or any other credential, anywhere. If a note contains password-shaped text, a warning appears before sealing; the seal records whether the warning was confirmed.

Equipment

Add each item the leaver had and mark it returned or not returned. For a not-returned item, enter its value: the record, the sealed pack and the client page all show the same total, computed from your entries.

Sealing, packs and corrections

A record seals only when every checklist section is recorded and every equipment item is decided; the seal panel names whatever is missing. Sealing freezes the version and generates the evidence pack: a PDF with the checklist, the equipment and values, the purge date, who did the work, the client acknowledgement status, a SHA-256 of the file, the hash of the event chain head, and a public verify URL on every page. The last page of the PDF is an integrity page that prints the SHA-256 of the document body and the exact command to reproduce it.

Sealed versions cannot be edited. If something is wrong, start a correction on the record page: a new draft copied from the sealed version. Sealing it links the new pack to the previous pack's SHA-256, and the original stays viewable and verifiable.

Client acknowledgement and intake links

Each record has an acknowledgement link: send it to the client's supervisor or HR contact. They see the record summary and acknowledge with their name and role, no account needed. Before sealing, the acknowledgement prints on the pack. After sealing, it is issued as a separate addendum PDF linked to the pack's hash, downloadable from the record page.

Each client has an intake link: give it to the client so they can report a leaver the day it happens. The form asks only for the leaver's name, supervisor and last working day, and starts the record for you. Links expire after 180 days, can be replaced or revoked at any time, and never ask anyone for a password.

Data purges

The checklist's purge section sets the date the remaining mailbox and files are scheduled for deletion, and it lands on the record. The purge queue lists every record whose purge date has arrived and is not yet marked purged, plus the upcoming ones. Marking a record purged records who confirmed it and when; it does not delete anything in the client's systems.

Verifying a hash

Go to Verify and paste a hash: an event hash from a pack, the SHA-256 of a pack file, or the body hash printed on its integrity page. The page reports whether it exists, its position in the chain and when it was recorded. No account is needed and nothing about the content is revealed. You can also upload a pack PDF on the same page and have its integrity statement checked.

To compute a file's SHA-256: sha256sum file.pdf on Linux, shasum -a 256 file.pdf on macOS, Get-FileHash file.pdf in PowerShell.

Your data

Every change is an event in your account's hash chain: each event's hash includes the hash of the previous event, so an altered or removed event breaks every later hash. Packs are stored as PDF and JSON and can be downloaded from the record page at any time. To delete your account, email support from the owner's address; hashes already printed on documents keep their meaning as fingerprints but will no longer verify.