Lawful notice and consent before you collect
A family should know what you are collecting and what it will be used for at the moment they hand it over, in language they can read, and should be agreeing to that rather than to a buried paragraph.
Blog · Compliance
The Digital Personal Data Protection Act is India’s law on how organisations handle personal data, and an admission office handles a great deal of it: names, phone numbers, marksheets, bank details and information about children. In practice it asks you to be clear with families about what you collect and why, to collect only what you need, to keep it safe and to delete it once the reason for holding it has passed.
Please note: this is general information to help you prepare, not legal advice, and institutions should confirm specifics with their own legal adviser or data protection officer.
Principles
Strip away the vocabulary and the law is a short list of reasonable expectations about other people’s information. An admission office already meets some of them out of habit. The ones that usually need work are deletion, access control and being able to show what a family agreed to.
These are durable principles rather than procedure. Treat them as the questions to ask of your own process, then use the checklist below to turn the answers into something your team can actually do during an admission season.
If the broader software picture is new to you, our guide to what an education CRM is explains where admission data usually lives and why it tends to get copied across several places.
A family should know what you are collecting and what it will be used for at the moment they hand it over, in language they can read, and should be agreeing to that rather than to a buried paragraph.
Every extra field on an enquiry form is data you then have to protect, justify and eventually delete. If a question does not change what you do next, it does not belong on the form.
Data given for an admission enquiry is for admission. Using the same numbers for an unrelated campaign, or passing them to another institution, goes beyond what the family agreed to.
Wrong data causes real harm, from a fee notice sent to the wrong parent to a certificate issued with a misspelled name. One authoritative record is easier to keep correct than four copies.
Reasonable safeguards, which in an admission office usually means ending shared logins and files on personal phones, encrypting what is stored and limiting who can open a student’s documents.
Holding every enquiry forever is the most common gap. Once the purpose has passed and no accounting or regulatory requirement applies, the data should go rather than sit in an old sheet.
A family can ask what you hold about them, ask you to fix it and ask you to remove it. You need a route for that request and a way to act on it across every place the data sits.
For a minor, consent comes from a parent or lawful guardian and you should be able to show that it did. Tracking children or targeting advertising at them is out of bounds.
The Checklist
Work down the list in order. The first three change what families see, the next three change what your team can do, and the last two cover the parts that are easiest to forget.
Put a clear consent step on the website form, the walk-in register and the phone script, so agreement is recorded at the moment the data arrives rather than reconstructed later. Store what the family agreed to, and when, against their record.
A short paragraph beside the form naming what you collect, why you collect it, how long you keep it and who to contact about it. Offer it in the languages your families use, because a notice nobody can read is not notice.
Write down what each kind of data is for, then check your actual practice against it once a season. If marketing wants to use last year’s enquiry list for something new, that is a fresh purpose and needs fresh agreement.
A counsellor, the accounts desk and the transport office each need a different slice of a student record, not all of it. End shared logins, give every staff member their own, and remove access on the day somebody leaves.
Agree how long you keep an unconverted enquiry, an application that was not accepted and the records you must retain for accounting or audit. A retention rule nobody acts on is worse than none, so put the deletion in somebody’s calendar.
Where the applicant is a child, the consent you record should be the parent’s or lawful guardian’s, with enough detail to show whose it was. Keep photo, media and trip permissions separate from the consent to process admission data.
Give families one named contact point for questions about their data, on the website and in the notice. Log what arrives there, answer it within a stated time and keep a note of what you did, so a request is never lost in a general inbox.
Your software, messaging gateway, payment provider and any agency running campaigns all handle family data on your behalf. Ask each one where data is stored, what they may do with it, how they delete it and what happens at the end of the contract.
One Record
Most of the difficulty in the checklist comes from the same source: the same family exists in an enquiry sheet, a fee sheet, an email inbox and somebody’s phone. Answering a deletion request then means finding four copies, and proving what a parent agreed to means finding the right version of a form. Keeping one record per student removes that search.
To be plain about what software can and cannot do: the points below describe what CampusFlow gives you to work with. They do not make an institution compliant on their own, because the decisions in the checklist, what you collect, what you say, who may see it and how long you keep it, stay with you.
Consent capture, records, withdrawal and retention rules are built into the product, so agreement is recorded where the enquiry arrives rather than added afterwards, and consent trails export for audit.
Enquiries, counselling notes, documents, consents, fee instalments and messages sit on the same record, so a request to see or erase data has one place to go instead of four.
Teachers, accounts and transport each see only the files their role needs, sharing outside the institution needs approval, and every view and download is logged.
Files carry versions, expiry dates and access rules, and parent consents go out as one link and are signed in a tap. The detail is in document and consent management.
Every grant, change and withdrawal of consent is logged with the time and device against the student record, which is what turns a data request from an argument into a lookup.
Instalments, receipts and scholarship records are part of the same record rather than a separate sheet, which matters because financial data usually carries its own retention period. See fees, payments and scholarships.
To walk through the eight items on your own enquiry form and document checklist, book a 30-minute demo.
FAQs
The Digital Personal Data Protection Act is India’s law on how organisations collect, use, store and share personal data about identifiable people. For an admission office the practical shape of it is this: tell families clearly what you are collecting and why, collect only what you need for that purpose, keep it accurate and secure, delete it once the purpose has passed and be able to act on a request to see, correct or erase it.
It applies to organisations that handle personal data about identifiable people, and a school, college, university or coaching institute handles a great deal of it, including data about children. Being small does not exempt you. A single campus has the same duties of notice, purpose limitation, security and deletion as a large group, even though the scale of the work is smaller.
If a family filled in your enquiry form in order to hear from you about admission, that is the purpose they handed over the data for, and calling them about admission is consistent with it. What matters is that the notice beside the form said so plainly, that you do not then use the same number for something unrelated, and that you stop when the family asks you to. A bought or scraped list is a different matter, because nobody gave you a purpose.
For as long as the purpose you collected it for still applies, and no longer. There is no single number that fits every field. An enquiry that never converted does not need to sit in your system for years, while admission and fee records are usually held to meet accounting, audit and regulatory requirements that carry their own periods. The practical step is to write down a retention period for each category of data, then delete on that schedule instead of keeping everything by default.
Data about a child is treated more carefully and needs verifiable consent from a parent or lawful guardian rather than from the child. You should also avoid tracking children, avoid targeting advertising at them and avoid processing that could harm them. For an institution this mostly means routing consent to the parent, recording who gave it and when, and keeping photo and media permissions separate from the consent to process admission data.
It is a named route for a family to raise a concern about their data and actually get an answer, and families do need a way to reach you. Publish a contact point, make sure requests arriving there are logged and answered rather than lost in a general inbox, and keep a record of what was asked and what you did about it. How formal the arrangement needs to be scales with the size and sensitivity of what you handle.
No, and no software can promise that. Compliance is a set of decisions and habits: what you collect, what you tell families, who may see it, how long you keep it and how you answer a request. Good software makes those decisions easier to carry out and easier to evidence, by capturing consent where the data is collected, keeping one record per student, restricting access by role and logging what was done. The decisions themselves stay with the institution.
Bring your enquiry form and your current document checklist to the demo. We will show you where consent gets captured, who would see which part of a student record and how a deletion request is answered.