Jarvisby TheSEO
EN
Language · same pageNLNederlands/jarvis/vertrouwen/offboarding/ENEnglish (UK)/en/jarvis/trust/offboarding/ESEspañolnot translated yetWe do not remember your choice and never redirect you automatically.
OPS.J02 · working method in force The deadlines are set out in the data processing agreement; the file format per part is not yet
JarvisTrustOffboarding
OPS.J02 · offboarding checklistversion 0.2 · working method in force

Your data comes with you. Access demonstrably gone.

Leaving is a controlled workflow, not an account somebody forgot by hand.

The onboarding checklist →The data processing agreementfive parts come with you, six doors close · the file format is not settled yet
FIG.F01: What comes with you, what goes out, and the field that is still emptyOPS.J02 · exit route

Five parts you take with you, six doors that close, and a format that is not settled yet

The four steps sit on this page as cards, but what actually happens in steps two and three is only there as a list inside the running text. Here it hangs off the step it belongs to. Next to each of the five parts is an empty format field, because this page says itself that the file format per part has not been settled.

~/jarvis/trust/offboarding · export.manifest[note] format open
the route when you leavefour steps, two with content
01Confirmauthorised requester, end date, contract status and the export you want
02Exportfive parts, each with a structure of its ownsourcesformat not settled yetmemoryformat not settled yetagentsformat not settled yetapprovalsformat not settled yetaudit dataformat not settled yet
03Revokesix doors closemembersoffsupportoffconnectorsofftokensoffsessionsoffwebhooksoff
04Deleteproduction data and copies according to the retention table, with confirmation on request
# five parts travel out, six doors close, and those two movements belong together: exporting without revoking leaves a door open. The format field stays empty until it is settled, per part, in which file format you get it delivered
01

Confirm

Authorised requester, end date, contract status and the export you want.

02

Export

Sources, memory, agents, approvals and audit data in agreed formats.

03

Revoke

Switch off members, support, connectors, tokens, sessions and webhooks.

04

Delete

Delete production data and copies according to the retention table, and confirm.

The deadlines are settled. After the agreement ends, a standard export stays available for thirty days, after which we delete or anonymise the production data, and a backup disappears through rotation at the latest thirty five days after that. If you want it confirmed that deletion happened, you can ask for that confirmation.

What is not settled is the file format each part comes in. Sources, memory, agents, approvals and audit data each have their own structure, and we only commit to a format once we have tested it per part. Until then we agree the format with you at the moment you give notice.

This is the working method, not the agreement. The agreement itself sits in the chapter on return, export and erasure in the data processing agreement, and giving notice is covered by the terms that apply to you: consumer or business. Where this explanation differs from those documents, the document applies.

Section · Next stepreachable 24/7
Book a call ↗