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

Student data privacy: 2027, 2028, 2029, 2030

A year-by-year plan for coaching centres, schools and education platforms handling student and parent data under Bangladesh’s new privacy law.

E
EncryptTechBD · 0 comments
Students in a library with bookshelves
Photo: Josh Felise / StockSnap

Education providers hold some of the most sensitive data in any business: names, ages, guardians, addresses, phone numbers, attendance, exam results, fee status, medical notes and sometimes photographs. A coaching centre may collect all of it on paper, in a spreadsheet and in a messaging group. The data is necessary to run the institution. It is also a privacy obligation.

Bangladesh's Personal Data Protection Act, 2026 changes the baseline. The Act applies to personal data processing, gives data subjects rights and imposes obligations on data controllers and processors. Some provisions have a phased commencement, but the direction is clear: know what you collect, why, where it is stored, who can see it and when it is deleted.

Where things stand in 2026

Most education providers do not have a data map. Student records live in an admission register, a fee ledger, a WhatsApp group, a teacher's phone and a Google Drive. Access is informal. Former staff may still have the spreadsheet. Vendors may hold copies for support. A parent asking "what do you know about my child?" may not get a complete answer.

The first step is not a policy document. It is an inventory. What data is collected, at which point, by whom, for what purpose and how long is it kept? Once the inventory exists, the policy can be written in plain language.

2027: consent, notices and retention

2027 should be the year of lawful basis and clear notices. Review the admission form: does it explain what data is collected, why, who it is shared with and how long it is kept? Separate consent from the service where consent is the basis. Do not bundle marketing consent with admission.

Set retention periods. Admission enquiries that do not convert should not be kept forever. Attendance and results need a defined academic retention period. CCTV, if used, needs a shorter period and a clear purpose. Fee records may need a longer period for accounting and tax.

  • Data map: student, guardian, attendance, results, fees, health, transport.
  • Access roles: teacher, accountant, admin, principal, vendor.
  • Retention: a defined period and a deletion method.
  • Vendor terms: data processing agreement, breach notification, deletion on exit.

2028: residency, breach response and audit

By 2028, the provider and hosting choices matter more. If student data is stored in a third-party learning platform or a cloud region outside Bangladesh, confirm whether the transfer is permitted and what safeguards apply. The PDPA's residency provisions and the vendor's subprocessors are part of the decision.

Write a breach response plan for student data. Who is notified, within what time and with what evidence? A lost laptop, a shared spreadsheet link or a misdirected email are realistic incidents. The plan should be tested with a tabletop, not stored in a drawer.

Audit access. Review who can export student lists, who can change results and who can delete records. Remove former staff immediately. Log administrative actions in the student system where possible.

2029: age-appropriate design and analytics minimisation

2029 is the year to review analytics and AI. Education providers will want dashboards for attendance, retention and performance. That is useful, but it can also create new personal data: predicted dropout risk, behaviour scores, family income indicators. Collect only what the decision requires and explain how it is used.

If the provider uses an AI tutor, chatbot or automated grading tool, ask whether student data is used for model training, where it is stored and how a parent can exercise their rights. Do not send more data than the tool needs.

Parent and student rights should be operational: access, correction, deletion where applicable and a contact point. A rights request should not depend on the director's personal email.

2030: privacy by design and independent assurance

By 2030, privacy should be part of the procurement and design process. New systems should be reviewed before they go live: what data, what purpose, what retention, what access and what vendor. The review should be short and practical, not a 40-page form.

Independent assurance can be proportionate. A small coaching centre may use an internal audit and a vendor checklist. A larger institution may seek ISO/IEC 27701 certification or an external privacy assessment. The point is evidence, not a logo.

The mature position is trust: parents know what is collected, staff know the rules, vendors are contracted and the institution can answer a data request without panic.

What to do in the next 90 days

  1. List every place student and guardian data is stored, including phones and messaging groups.
  2. Write a one-page privacy notice for admission and enrolment.
  3. Set retention periods for enquiries, attendance, results, fees and CCTV.
  4. Review access for current and former staff; remove inactive accounts.
  5. Add data protection, breach notification and deletion terms to vendor contracts.

How to measure progress

  • Data map coverage: the share of systems and files inventoried.
  • Retention compliance: records deleted on schedule.
  • Access reviews: completed quarterly, with inactive accounts removed.
  • Vendor coverage: the share of student-data vendors under contract.
  • Rights requests: response time and completeness.

Student data privacy is not a legal formality. It is part of the trust a parent places in the institution. Treat it with the same care as fee accuracy and exam integrity.

Where this fits in our work

If you want help applying this to your business, start with Education Operations. We publish scope and starting prices on the pricing page. For the next step in this series, read AI governance policy: 2027, 2028, 2029, 2030.

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