Legal
Data retention schedule
Enquiries are deleted after 24 months. Client project data is deleted within 30 days of final handover, apart from correspondence and invoices kept for six years for tax purposes. Nothing is kept indefinitely, and you can ask for deletion sooner.
- Last updated
- Effective from
- Applies to
- Anas Bin Masud
- Clauses
- 7
Most privacy policies say data is kept "as long as necessary", which tells you nothing. This is the actual schedule, published as a table so it can be checked rather than trusted.
It supplements the privacy policy and the Data Processing Agreement rather than replacing either.
1. The schedule
| What | Kept for | Why | Then what |
|---|---|---|---|
| Enquiry form submissions | 24 months | Enquiries often revive months later, and the context matters | Deleted |
| Email correspondence with clients | 6 years from project end | Tax record-keeping and contract evidence | Deleted |
| Invoices and payment records | 6 years | Statutory record-keeping | Deleted |
| Signed scopes and contracts | 6 years from project end | Contract evidence | Deleted |
| Client production data during a build | Duration of the project | Required to do the work | Deleted within 30 days of handover |
| Client credentials I was given | Duration of the project | Required to do the work | Access requested to be revoked at handover |
| Source code of client projects | Indefinitely, in the client’s own repository | It is the client’s asset | Under client control, not mine |
| Backups on a maintenance retainer | 30 days rolling | Recovery | Overwritten automatically |
| Complaint records | 6 years | Legal record and learning from them | Deleted |
| Failed-delivery enquiry log | 90 days | Fallback so an enquiry is never silently lost | Deleted |
| Server access logs | Per host default, typically 30 days | Security and diagnostics | Rotated by the host |
| Website analytics | None currently collected | No analytics is installed | Not applicable |
2. The principle behind it
Collect less, keep it for a stated period, then delete it. The cheapest data to protect is the data you decided not to store, and the second cheapest is the data you deleted on schedule.
That is why this site sets no cookies, runs no analytics by default, and has no mailing list — each of those would have created a retention obligation in exchange for information nobody here needs.
3. Asking for earlier deletion
Email anasrajpoot766@gmail.com and ask. Anything not required for a statutory purpose is deleted, and you get written confirmation of what was removed.
The exception is genuinely narrow: invoices and the correspondence that evidences a contract have to be retained for tax purposes, and that obligation is not mine to waive.
4. Client data during a project
Where a build can be done against anonymised or sample data, it is. Production access is requested only where genuinely required, and revocation at handover is part of the handover checklist rather than an afterthought.
This is the cheapest possible way to handle a cross-border transfer: make less of one.
5. Sub-processors
Where a sub-processor holds data, its retention is governed by its own terms as well as this schedule. Every sub-processor is named on the sub-processor page, with what it is used for.
6. Deletion method
Deletion means removal from live systems and from any backup on its next rotation. Where a backup cannot be selectively edited, the data is removed when that backup expires — within 30 days on retainer backups.
7. If the practice ceases trading
Client-held assets are unaffected: code is in your repository, domains and hosting are in your name, and credentials are already yours. That is the practical value of the ownership position taken throughout these terms.
Data held by me would be deleted apart from statutory records, and clients would be notified.
Who this document is from
| Trading name | Anas Bin Masud |
|---|---|
| Also known as | Anas Rajpoot — the name on the linked GitHub, LinkedIn and email accounts |
| Legal form | Sole trader / individual supplier. Not an incorporated company |
| Principal place of business | Islamabad, Islamabad Capital Territory, Pakistan |
| Contact email | anasrajpoot766@gmail.com |
| Telephone | +92 346 5348466 |
| Website | anas-portfolio.it.nf |
| VAT / sales tax registration | Not registered for UK VAT or EU VAT |
Not legal advice
This document is written in plain English by the person it binds. It has not been reviewed by a solicitor, and it is not legal advice to you.
Before relying on it in a dispute, or before signing with an enterprise or public-sector client, have it reviewed by a qualified professional in your jurisdiction. That instruction is on the page rather than in a footnote because it is genuinely meant.
Questions about this document
Email anasrajpoot766@gmail.com, or use any route on the contact page. There is no legal department; the reply comes from me.
Anything here that needs changing before you can work with me?
If your procurement process needs a clause added, an NDA signed, or a term adjusted, say so with the brief. It is a conversation rather than a refusal.
- Response
- Replies within 1 business day
- Hours
- Mon–Fri, 09:00–18:00 PKT — overlaps 05:00–14:00 UK, 00:00–09:00 US Eastern
- Booking
- Booking projects from October 2026