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

Data minimisation in web applications: a buying guide

How to buy data minimisation work for web applications: scope, requirements, vendor scorecard, pricing questions, pilot checks and exit terms.

E
EncryptTechBD · 0 comments
Hands signing a document beside a folder
Photo: Matt Moloney / StockSnap

Most web applications collect more data than they need. A contact form asks for a date of birth, a checkout asks for a national ID number, and an analytics script records every click because the setting was left at its default. Each extra field creates a storage cost, a security exposure and a question the business must answer when a customer asks what is held about them.

Data minimisation is the discipline of collecting only what a stated purpose requires, keeping it only as long as necessary and limiting who can use it. Buying that discipline is different from buying a security product. You are buying changes to forms, APIs, retention jobs, vendor connections and internal habits.

What you are actually buying

A credible engagement should cover six areas:

  • Data mapping: where personal data enters the web application, which fields are mandatory, and where the data is copied or exported.
  • Purpose and field review: a written reason for each field, linked to a business process and a retention period.
  • Collection changes: removing or making optional unnecessary fields, adjusting validation and updating privacy notices.
  • Retention and deletion: scheduled deletion, archival rules, backup retention and deletion propagation to exports and third-party tools.
  • Third-party review: analytics, chat, marketing pixels, payment and delivery providers that receive data.
  • Evidence: before-and-after field inventories, deletion test results and a maintainable register.

Be careful with the word "compliance". A vendor can help you document decisions, but the business remains accountable for its legal position. In Bangladesh, the personal data protection framework has been evolving, and sector rules may apply alongside it. Ask the vendor to separate technical advice from legal advice.

Requirements to put in the brief

  1. Application inventory: every public site, customer portal, internal dashboard and API that handles personal data.
  2. Field-level justification: a table or register listing field name, purpose, mandatory status, retention and access role.
  3. Data flow: entry point, storage location, copies, exports and recipients, including overseas service providers.
  4. Retention schedule: what is deleted, when, by what job and who can override it.
  5. Deletion evidence: a test showing that a deletion request removes the record from the primary store, search index, cache and downstream tools within an agreed period.
  6. Access control: role-based access to personal data, with logging for exports and bulk views.
  7. Change control: a review step that stops a new form field from being added without a purpose and retention note.
  8. Documentation: enough detail for another team to operate the process without the original vendor.

Vendor scorecard

Score each vendor from one to five against these criteria, and ask for evidence rather than a verbal claim:

  • Method: a documented discovery process, not a questionnaire alone.
  • Application experience: examples of work on forms, APIs, databases and third-party tags in the same technology stack.
  • Deletion competence: a realistic plan for backups, caches, logs and analytics exports, which are the places deletion usually fails.
  • Security practice: least-privilege access to production data, test data handling and confidential handling of findings.
  • Communication: clear writing for both technical and business readers.
  • Knowledge transfer: training and a register the internal team can maintain.
  • Exit: no proprietary tool required to read the documentation or run the deletion jobs.

Pricing questions that reveal the real cost

Do not accept a single lump sum without a breakdown. Ask how the vendor charges for discovery, field and form changes, API work, data migration, deletion jobs, third-party tag cleanup, testing and ongoing support. Ask whether the price assumes a fixed number of forms, applications, languages or environments. Ask what happens when a new form is added after the project, and whether the vendor charges per change or under a retainer.

A useful cost model has four lines: one-time discovery, one-time remediation, recurring operations and change requests. The recurring line should include deletion job monitoring, register maintenance and periodic review. If the vendor cannot separate these, the business cannot compare proposals or budget for year two.

Pilot before full rollout

Choose one customer journey, such as account registration or a checkout, and one internal process, such as a support export. Run the pilot for four to six weeks. Test with a real deletion request, a data export and a new field request. The pilot should prove that the process works when someone is in a hurry, not only when the consultant is in the room.

Exit and ownership

The business should own the data inventory, the retention schedule and the deletion runbooks. Source code, database scripts and configuration should be handed over in a readable form. If the vendor hosts a privacy tool, agree at the start how the register is exported and how deletion jobs continue if the contract ends. An exit plan written after a dispute is usually a list of problems, not a plan.

Metrics to track

Count the number of personal data fields by purpose, the percentage with a documented retention rule, the number of third-party tags receiving data, the time to complete a deletion request and the number of new fields added without review. These numbers are more useful than a one-time audit report because they show whether the habit survived the project.

Where this fits in our work

Data minimisation sits between application development, security and privacy operations. If you need help reviewing a web application and its data flows, start with Managed Technology & Cybersecurity and review the scope options on our pricing page. For the retention side of the same problem, read the data retention and deletion workflow 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