A practical privacy programme for schools and universities

Start with a student journey

An admissions form is a useful place to begin. Follow the information from the applicant through enrolment, administration and communications. Write down which team receives it, which application stores it and which outside provider helps process it. This gives staff a shared picture of the work before they try to improve it.

Keep the first exercise small. Name, email and phone number may be enough to explain the journey. Avoid collecting extra information simply because an old form asks for it. Expand the map when a real service needs additional fields.

Separate the purposes

Managing a student account and sending promotional messages are different activities. Describe them separately so families can understand what each activity involves. A clear purpose includes the reason for processing and the information used. General wording such as improving services makes it harder to explain a specific decision later.

Let the institution assess the appropriate processing basis before collection. Where a purpose uses consent, provide a clear selection. Where a reviewed basis uses a notice instead, do not record that notice as an affirmative consent decision. A software label alone does not establish a legal basis.

Make the privacy centre useful

Students should be able to see the purposes linked to their account and find a straightforward route to raise a request. Keep their original user ID consistent across applications. If the same email field serves several purposes, show it once in a correction form rather than asking the student to interpret several duplicate entries.

Plan a separate guardian journey for children and confirm applicable requirements with an adviser. Staff need to know whose identity was checked and who acted for the student. A shared family email address does not, by itself, explain that relationship.

Give staff a complete working loop

Assign requests to a responsible team, show its contact and set a realistic internal target. A correction request should reach the administrator who can change the student record. That person performs the change in the university application, then reports completion with a short explanation in the rights dashboard.

Test the loop with a new account, a marketing permission, a withdrawal and a correction. Check both the student view and the staff view. Review the evidence together rather than relying on a successful form submission as proof that every connected system has changed.