Make My Plan Ltd, trading as PlanProve
Version 1.3. Last updated: 21 October 2026
This policy sets out how long PlanProve retains different categories of data, what happens to that data when an account is closed or a subscription ends, and how a professional or practice can export their data. It applies to all data processed through the PlanProve platform, whether entered directly by a professional, uploaded as a document, or generated by the platform (such as AI-extracted deadlines or site constraint data).
This policy is written to reflect the storage limitation principle under UK GDPR Article 5(1)(e): personal data must be kept for no longer than is necessary for the purpose it was collected for. Where PlanProve acts as a data processor on behalf of a professional or practice (the data controller), retention of client and third-party data within case files follows the controller's instructions, not a period set unilaterally by PlanProve.
For data relating to a professional's own account (login details, billing, usage of the platform), PlanProve (Make My Plan Ltd) is the data controller.
For client and case data entered by a professional (client details, project correspondence, objector or neighbour personal data included in case files, documents uploaded to a site), the professional or practice is the data controller and PlanProve acts as data processor. Retention decisions for this category rest with the controller; PlanProve's role is to retain, delete, or export this data on their instruction, consistent with the periods set out below unless the controller specifies otherwise in our Data Processing Agreement, which you accept online.
What we keep, and for how long. This is the same schedule as in our Privacy Notice.
| What | How long we keep it | Why |
|---|---|---|
| Your account, profile, sites, projects, documents and case notes | For as long as the account is open. | Needed to provide the service (UK GDPR Art. 6(1)(b), contract). |
| Personal data of a professional's clients and other people in their case files (for example objectors, neighbours and consultees) | For as long as the professional's account keeps the related record. The professional or practice decides, as the controller. | We process this data for the professional or practice, on their instructions. |
| Client accounts, after a deletion request | Deleted automatically 30 days after the request. The request can be withdrawn until then. | A short window to change your mind, then deletion. |
| Professional and practice accounts, after a deletion request | Deleted by us on request, within 30 days of the request. | These accounts can be linked to a practice, invoices and case files, which we settle before deleting. |
| Invoices you create | Until we close your account, then deleted on your instruction. Export them first, including as a CSV for Xero. | They are your own financial records, and you keep them for as long as the law requires. |
| Our billing records for your subscription | As long as tax law requires. | Our own legal obligation for business records. |
| Search history | Your user id is removed after 90 days, and the record is deleted after 365 days. | Only useful for a short time, then kept only as anonymous totals. |
| Sign-in protection records (the email address and IP address of sign-in, sign-up and password reset attempts) | 24 hours. | Protecting accounts from password guessing. |
| Draft projects with no activity | Archived, not deleted, after 90 days without activity. | Keeps your project lists tidy. Archived drafts stay in your account. |
| AI assistant usage records | Until the account is deleted. These record when the assistant was used, not what you asked it. We do not store your conversations with the assistant. | Fair use limits and keeping the assistant working well. |
| Analytics events | Sent to PostHog (EU) only after you accept analytics cookies. They contain a user id and page address, not names or emails. | Understanding how the platform is used, with your consent. |
| Records of actions our administrators take on an account | Kept, with no fixed period. They are unlinked from the account when it is deleted. | Accountability for administrative actions. |
| All other records | Until the account is deleted. | Needed to provide the service. |
| Database backups | Overwritten within 7 days. | Our database provider's standard backups. A deleted record can stay in a backup for up to 7 days. |
| File backups | A document you delete has its file removed from storage straight away. The files of a condition, stage or site you delete, or of an account when we complete its deletion, are removed from storage within 30 days. A removed file's backup copy is kept for 30 days, then deleted. | Uploaded files are backed up separately, because database backups do not include files. |
If a professional or practice chooses not to continue after a trial or free period ends, their account and data are not deleted automatically. Data remains in place unless and until a deletion request is made, as described in 4.2.
A Client can request deletion from their account settings; the request is recorded and the account is deleted automatically after a 30-day grace period.
A professional can also request deletion from their account settings, and the request is recorded immediately, but completion of a professional or practice deletion is currently handled manually rather than automatically. We will complete it within 30 days of the request, consistent with UK GDPR erasure expectations, and you can withdraw the request at any time before then. You can also request deletion by email at info@planprove.com.
Completion is manual because a professional's account may be linked to a practice, to invoices, and to case files for which the professional is the data controller, each of which has to be settled before the account itself can be removed. Invoices you create are your own financial records. Export them first, including as a CSV for Xero, and we delete them on your instruction when we close your account. We keep our own billing records for your subscription for as long as tax law requires.
Database backups are managed by Supabase under their standard platform terms, with a 7-day rolling window; deleted database records may persist in one for up to 7 days after removal from the live system.
Uploaded documents and files are backed up separately and daily to Cloudflare R2 (EU jurisdiction), independent of the primary database infrastructure. A document you delete has its file removed from storage straight away. The files of a condition, stage or site you delete, or of an account when we complete its deletion, are removed from storage within 30 days. Once a file is removed from storage, its backup copy is kept for 30 days and then deleted.
Backups are encrypted at rest, are not shared with any party outside the sub-processors listed in Section 6, and are used only for disaster recovery.
You can export your data at any time, whether the account is active or scheduled for deletion, using the Download My Data button in your account settings. The export is generated immediately; there is no need to request one.
export.json (all records in structured JSON) and a documents/ folder holding the original uploaded files._omitted-files.txt inside the archive, and can be downloaded individually from the project it belongs to or requested at info@planprove.com. An export is never silently truncated.Where data is held by a sub-processor rather than directly within PlanProve's own database, that sub-processor's own retention behaviour also applies. Current sub-processors and their role:
| Sub-processor | Purpose | Location | Transfer mechanism |
|---|---|---|---|
| Supabase Inc. | Database and file storage | Ireland, EU-west-1 | Adequacy |
| Anthropic PBC | AI Planning Assistant and document extraction (in-product features); and AI-assisted development, debugging, and administrative support tooling. | USA | UK Addendum to EU SCCs |
| Stripe Inc. | Payment processing for invoices that clients pay to the professional's own connected Stripe account (Stripe Connect). PlanProve does not store card details. | USA | UK Addendum to EU SCCs/DPF |
| Resend Inc. | Transactional email delivery | USA | UK Addendum to EU SCCs/DPF |
| Vercel Inc. | Application hosting. Application functions run in the UK and EU (London eu-west-2, Dublin eu-west-1, Paris eu-west-3). Request routing runs on Vercel's global edge network. | UK/EU for functions, global for edge routing | UK Addendum to EU SCCs/DPF |
| PostHog Inc. | Product analytics | EU (Frankfurt eu-central-1) | Adequacy |
| Cloudflare Inc. | Storage backup (R2) | EU | Adequacy |
This is Annex A of our Data Processing Agreement, also published on our sub-processors page. Application functions run in London, Dublin and Paris, and some request routing runs on Vercel's global edge network, which processes sign-in session data in transit but does not store it.
Supabase, Cloudflare and PostHog process data within the European Union, which the UK recognises as adequate, so no Article 46 transfer safeguard is required for those transfers.
Anthropic, Stripe, Resend and Vercel are based in or process data via the USA. Each incorporates the UK Addendum to the EU Standard Contractual Clauses into their standard commercial terms, confirmed directly from each vendor's published Data Processing Addendum, so this applies automatically as a customer on their normal terms. Stripe, Resend and Vercel are additionally certified under the UK Extension to the EU-US Data Privacy Framework; Anthropic relies on the UK Addendum alone.
This policy should be reviewed whenever the underlying technical implementation changes (for example, if account deletion behaviour is rebuilt, or if AI processing is moved to an EU-pinned provider), and at minimum annually.