What you are buying

Offboarding & Data Handover

DKT Digital, St Peter Port, Guernsey GY1 · [email protected]

Draft

DRAFT — pending legal review, not binding. This document has not been reviewed by a solicitor. It is published so you can read our terms before you talk to us, and so we can be held to what it says — but it is a working draft, not a vetted contract, and nothing here is legal advice. A binding version will be issued for signature only once it has been through legal review. If you are relying on any part of it, ask us and we will tell you where it stands.

How you leave, what you get when you do, and in what format. Published for the same reason the rest is: a provider who will not tell you how to leave before you join is telling you something.

Last updated: 2026-08-01. Owner: Daniel Thomas, DKT Digital (Guernsey).

1. Principle: your data is yours, and you can leave

You are never locked in. At any time — and automatically when you offboard — you can take a complete, usable copy of your data in standard formats and move to another provider or run it yourself. "You can leave anytime but your workflows stay with us" is a red flag we deliberately do not have.

2. Notice period

Either side may end the retainer with 30 days' written notice (proposal — confirm with solicitor), unless a fixed term was agreed in writing.
The final month is served normally: automations keep running, support continues.
No lock-in, no exit fee. (Founding-client testimonial commitments are a separate, non-technical matter — see Scope & Inclusions.)

3. What you receive, in what format, and when

Within 10 working days of the end of the notice period (target — usually much sooner, the export itself is automated and takes minutes), you receive a handover bundle containing:

Item	Format	Notes
Your data export	JSON + CSV (both)	Every table of your data — see the rehearsed contents in §6 — one CSV per data type plus a single combined JSON. Opens in Excel/Sheets or any system.
Your automations	Written description + the workflow definitions (JSON)	What each automation did, its triggers, and its logic, so another developer can rebuild or import it.
Your credentials/connections	List + instructions to revoke/transfer	We do not hand over secret keys in the clear; we tell you exactly what was connected (e.g. your Xero, your GoCardless) so you reconnect them elsewhere and revoke our access.
A plain-English handover note	PDF/Markdown	What you have, how to read it, what to do next, what we deleted and when.

Delivery is by a secure, access-controlled link (not an unencrypted email attachment).

4. Who does what

Step	Owner	Client
Trigger the export, assemble the bundle	DKT Digital	—
Verify the bundle is complete and usable	DKT Digital (against this checklist)	—
Deliver the secure link	DKT Digital	—
Confirm receipt	—	Client
Revoke third-party access (Xero, bank, GoCardless, etc.)	DKT Digital revokes from our side	Client confirms/rotates on their side
Delete client data from live systems + future backups	DKT Digital	—
Confirm deletion in writing	DKT Digital	—

5. What we delete, and when

After you confirm receipt of the handover bundle (or after 30 days if you do not respond):

Your records are deleted from the live operational database.
Your encrypted OAuth tokens (Xero/bank) are deleted and our access revoked.
Backups already taken age out under the normal backup-retention window (the off-site copies are encrypted; see Security Overview §5 for exactly which copy is and is not encrypted); they are not restored or used after offboarding except where law requires retention (e.g. financial records kept for the statutory period).
We confirm the deletion to you in writing, with the date.

Financial records we are legally required to keep (invoices, payments) are retained for the statutory period and then deleted; this is stated in Security Overview §6.

6. Rehearsal record — what the bundle actually contains

*This section is filled from a real run of the export against a seeded test client, then the test data was deleted. It is proof the handover works, not a description of what it should do.*

Rehearsed 2026-07-21 against a seeded test client (OFFBOARD Rehearsal Ltd, [email protected]) with rows across several tables, then the seed was deleted. The export ran through the live Client Data Export (per-client) automation (admin-authorised via the verified access header; a request without the header, or with a non-owner header, is refused).

The bundle produced (a real directory, ~24 KB, opens with no DKT software):

HANDOVER-NOTE.md         ← plain-English "what this is / what to do next"
data.json                ← everything in one machine-readable file (11 data sets)
csv/
  client.csv             ← the client record
  leads.csv              invoices.csv        meetings.csv
  reports.csv            roi.csv             savings.csv
  payments.csv           tasks.csv           invoice_chases.csv
  feedback.csv

Formats: one combined data.json and one CSV per data type — every CSV opened and parsed cleanly (headers + rows), so a client can use Excel/Sheets or any system with no dependency on us.
Coverage (11 data sets): client profile, leads, invoices, meetings, reports, ROI, savings, payments, tasks, invoice chases, and feedback.
Gap found and fixed during the rehearsal: the export originally omitted the client's feedback (it predated the feedback feature). Because "your data is yours" includes feedback, feedback was added to the export so the bundle is now complete. The updated automation was re-run and the bundle re-verified.
Not in the bundle by design: secret keys/tokens are never exported in the clear; the handover note tells the client what was connected (e.g. their Xero, GoCardless) so they reconnect elsewhere and we revoke from our side.

Seed data deleted after the rehearsal.

The full set