Export a person’s data
- Enter the person’s email address, for example
alex@example.com. - Select Download ZIP. M.A.R.C.U.S. builds a ZIP file and downloads it.
- Device telemetry isn’t included.
- Secrets are left out. Password hashes, tokens, encrypted values, credentials inside settings and authorisation headers are removed. Webhook and Teams URLs are cut back to the address of the site, such as
https://example.com. - Spreadsheets are kept safe. In the CSV files, any cell that starts with
=,+,-or@gets a'in front, so a spreadsheet won’t run it as a formula. The JSON file holds the exact values. - Deleted accounts are found too. The export uses the audit log to find people whose accounts were deleted earlier.
Erase a person
- Enter the person’s email address and select Preview. You see how many records will change, before anything does.
- If it looks right, type the email address again to confirm, and select Erase.
- The person’s account is deleted.
- Their name, email and other personal values are replaced with a stand-in such as
erased-user-1a2b3c4d. If the account no longer exists, the stand-in is worked out from the email address. - Audit log entries are kept, but anonymised. They now show the stand-in, so the history stays complete without the person.
- Personal dashboards are deleted. Shared dashboards are kept and now show the stand-in as their owner.
What erasure can’t reach
After erasure, an amber list shows the places M.A.R.C.U.S. can’t clean up for you. Deal with these yourself:- Microsoft Entra ID. Remove the person there too. If you don’t, they’re created again the next time they sign in.
- Notification channels that send to the person’s email address. Change the channel’s recipients.
- Room Readiness recipients and the helpdesk email.
- The organisation support contact, if it’s this person.
- Application logs, which are kept for 30 days, and backups, which are kept for 35 days. Both clear themselves on schedule.
Old sign-in tokens
M.A.R.C.U.S. tidies up expired credentials automatically. Password reset, sign-in link and Collector enrolment tokens are deleted 30 days after they expire or are used. API tokens are deleted 90 days after they’re revoked or expire. Active tokens are never deleted.When your organisation leaves
Offboarding a whole organisation is done by the Involve helpdesk, not from the portal. It works like this:
To start offboarding, or to cancel it, contact the Involve helpdesk.
Updated 06 Nov 2026 14:07 · page 4312ed3