Skip to main content

How to handle a student data request

What to do when a student or parent asks for their personal data, and how Teach 'n Go supports data erasure requests.

Written by Abdullah Al-Hussein

When a student or parent submits a data access or erasure request (for example under GDPR or a similar privacy regulation), Teach 'n Go does not have a built-in self-serve data export, anonymisation tool, or automated erasure workflow. This article explains what tools are available and how to handle requests manually.

Responding to a data access request

There is no one-click "export everything about this person" button. To gather a student's data, you can:

  • Export their attendance records from Reports → Attendance reports (filter by student)

  • Export their fee and payment history from the student's Fees and Receipts tabs

  • Copy notes, custom field values, and profile information manually from their profile

  • Export relevant class or gradebook data filtered to that student from the relevant report tabs

All exports produce Excel files. You will need to assemble the data into whatever format you provide to the requester.

Archiving vs. deleting a student

Archive hides the student from active lists and searches but keeps all their data intact. Archiving is not a form of erasure — all records remain in Teach 'n Go and can be unarchived at any time. Use archive to deactivate a student while retaining their history.

Delete is a hard delete and is permanent. However, deletion is blocked if the student has made any payments — Teach 'n Go will not let you delete a student with financial records. In that case, archive is the only option. If you must delete a student with payment history, contact Teach 'n Go support.

Erasure requests

Teach 'n Go has no anonymisation feature. If you need to erase a student's personal data in response to a legal request, the available approach is to delete the student record (if no payment history exists) or to contact Teach 'n Go support for guidance on records that cannot be deleted through the interface.

Exports are the main workaround for data access requests. Deletion removes data but is blocked by payment history. There is no anonymisation, no GDPR-specific workflow, and no self-serve data export for end users.

Did this answer your question?