Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 5 min read

Data minimisation checklist for web applications

A field-level checklist for reducing what a web application collects, keeps and shares, with owners, evidence and a deletion test that proves the process works.

E
EncryptTechBD · 0 comments
Person writing notes beside a smartphone
Photo: Wilfred Iven / StockSnap

Data minimisation is usually written as a principle and implemented as an afterthought. A form asks for a date of birth because the template had a field. A campaign page stores a phone number in three systems. An old export sits in a shared folder because deleting it requires someone to decide.

The principle is simple: collect what the purpose requires, keep it only as long as the purpose requires, and let only the people who need it reach it. The work is in the specifics. This checklist turns the principle into controls a web team can own, evidence a reviewer can inspect, and a test that shows whether deletion actually happens.

Start with a field inventory

Before changing any form, list every personal field the application handles. Include fields collected by embedded tools, support widgets and analytics, not only the main signup form.

FieldWhy it is collectedRequired or optionalWhere it is storedRetention
Example: mobile numberOrder updates and delivery coordinationRequired for deliveryApplication database, SMS providerUntil order closure plus the agreed support period
Example: date of birthAge eligibility for a regulated productRequired only for that productApplication databaseRemove when eligibility is verified

If a field has no stated purpose, remove it. If the purpose is "might be useful later", that is a reason to defer collection, not a reason to store it.

The working checklist

AreaControlOwnerEvidence
CollectionEvery field has a documented purpose and a required justificationProduct ownerField inventory with reviewer sign-off
CollectionOptional fields are genuinely optional and do not block checkoutUX leadForm test and screenshot
CollectionNo sensitive field is collected unless the purpose requires itProduct ownerData protection review note
FormsPrivacy notice names the purpose, retention and sharing for each field groupLegal or privacy leadPublished notice and version date
StoragePersonal data is not copied into analytics, logs or test fixturesEngineering leadCode review and log sample
StorageBackups follow the same retention policy as live dataInfrastructure leadBackup policy and restore test
UseEach system has a documented role and a data-sharing agreementVendor managerContract register
UseAccess is role-based, with a current list of who can exportApplication ownerAccess review record
SharingThird-party scripts are limited to those with a named purposeMarketing leadScript inventory
SharingExports are approved, logged and given an expiry dateData ownerExport log
RetentionEach data class has a retention period and a deletion methodRecords ownerRetention schedule
RetentionDormant accounts are reviewed on a fixed cycleOperations leadDormancy report
DeletionA verified request removes live data, backups and derived copies within the stated windowPrivacy leadDeletion record and test result
AccessAdministrative accounts use unique identities and strong authenticationSecurity leadAccount inventory
LoggingLogs exclude personal data unless the purpose requires itEngineering leadLog schema and sample
ChangeA new field cannot ship without a purpose and retention entryProduct ownerDefinition of done in the ticket
VendorsEvery processor is listed with its data category and review dateVendor managerProcessor register

Retention is a decision, not a default

Most applications do not have a retention problem because someone chose to keep data forever. They have it because nobody chose anything. The signup table grows, the export folder grows, and the backup schedule copies all of it. A retention schedule fixes that by naming a period and a method for each data class, then assigning the job of enforcing both.

Start with the classes that carry the most risk: identity documents, payment references, support conversations and marketing consent. For each, ask three questions. What purpose does this data still serve? What is the consequence of deleting it now? Who is allowed to approve an exception? The answers become the schedule.

Deletion also needs a method. A status flag is not deletion. Removing a row from the live table is not deletion if the same record remains in an export, a cache or a vendor system. Write down every place the record can exist, then test the path end to end.

How to verify the checklist

  1. Form audit. Open the five highest-traffic forms and map every field to the inventory. Any unmapped field is a finding.
  2. Database sample. Inspect a sample record and list every table that contains the same person. Copies that nobody owns are candidates for removal.
  3. Deletion request. Submit a test deletion and trace it through the application, backups, exports and vendor systems. Record the elapsed time.
  4. Export review. Ask for the last three exports and check who approved them, where they were stored and whether they were deleted.
  5. Permission test. Sign in as a support user and attempt to reach records outside the role. The expected result is a refusal, logged.

Run the deletion test at least twice a year. A process that worked during the project may not survive a change of staff or vendor.

Common mistakes

  • Treating the privacy policy as the control. The policy describes intent; the form and the database determine the outcome.
  • Minimising the signup form but leaving the support widget collecting everything.
  • Deleting the live record and leaving the archive, export and CRM copy untouched.
  • Letting analytics tools capture form contents through session recording or event tracking.
  • Giving every engineer a production export permission because it is convenient.
  • Setting a retention period with no job, calendar reminder or owner to enforce it.

Metrics worth reporting

  • Number of personal fields without a documented purpose.
  • Systems holding a copy of customer data, compared with the processor register.
  • Median time to complete a verified deletion request.
  • Dormant accounts past the retention threshold.
  • New fields shipped without a retention entry, which should trend to zero.

Where our team fits

We review forms, data flows and access patterns, and implement retention and deletion routines under Managed Technology & Cybersecurity. Scope and starting points are on the pricing page. For the procurement side of the same subject, read data minimisation in web applications: a buying guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes