What does your institution need to know about data privacy today?
Which data privacy laws reach an education institution?
GDPR (General Data Protection Regulation), LGPD (Lei Geral de Proteção de Dados, Brazil's general data protection law) and CCPA (California Consumer Privacy Act), plus the CPRA (California Privacy Rights Act), reach anyone recruiting students in Europe, Brazil and California.
Did the CPRA replace the CCPA in California?
The CPRA did not replace the CCPA. Approved by California voters in November 2020, the CPRA amended the CCPA and added new privacy protections that began on January 1, 2023.
Who can take legal action over a CCPA violation?
For most CCPA violations, only the Attorney General or the California Privacy Protection Agency may take legal action. A consumer can sue directly only in limited cases of data breach.
Does a CRM handle data privacy compliance on its own?
A CRM (Customer Relationship Management) does not handle compliance on its own. The system records consent and restricts access, but internal policy and regular database review stay with the institution.
What will you learn in this article?
In this article, you will understand:
- What changed in California: the CPRA amended the CCPA and brought new rights from January 1, 2023.
- How the laws compare: basis for processing data, data subject rights and who enforces each regime.
- What role the ANPD plays: legitimate interest as a legal basis inside the Brazilian framework.
- What to configure in the CRM: recorded consent, restricted access, anonymization and a retention period.
- Which routines keep compliance alive: periodic audits, team training and a review of every integration.
Managing data privacy during student recruitment is now a routine, not a one off project. Every form submitted, every list imported and every new integration creates a legal obligation for the institution.
The problem is rarely a missing tool. The problem sits in the gap between what the law asks for and what the team actually configured in the system, especially when the operation recruits students in more than one country.
This guide organizes the four rules that affect education institutions the most, shows where they align, where they diverge and what has to be switched on in the CRM to sustain compliance day after day.
- What are GDPR, LGPD, CCPA and CPRA in data privacy?
- What are the similarities and differences between GDPR, LGPD and CCPA?
- Which data privacy principles should every institution follow?
- How does a CRM help with compliance with data privacy laws?
- Which data privacy best practices should you apply in the CRM?
- What are the benefits of complying with data privacy laws?
- Frequently asked questions about data privacy
- Where should you start the data privacy review of your CRM?
What are GDPR, LGPD, CCPA and CPRA in data privacy?
GDPR, LGPD, CCPA and CPRA are the data privacy rules that most often reach education institutions with international recruitment. The first three define how to collect, use and share personal data. The CPRA expanded the California text and added new consumer rights.
GDPR: the European Union data protection regulation
The GDPR protects the personal data of European citizens and has applied since May 2018. The text demands transparency at collection, a declared purpose and security during processing, with heavy fines for anyone who ignores the rule.
Institutions based outside Europe also answer to the GDPR when they recruit candidates inside the bloc. The trigger is the person's data, not the address of the institution's headquarters.
LGPD: the Brazilian data protection law
The LGPD has been in force since September 2020 and organizes the collection, storage and sharing of personal data in Brazil. Enforcement belongs to the ANPD (Autoridade Nacional de Proteção de Dados, the Brazilian national data protection authority), which publishes guidance on the law.
CCPA and CPRA: the California privacy rules
California's law is the California Consumer Privacy Act of 2018, known by the acronym CCPA. The text gives consumers the right to know which data was collected, to request deletion and to refuse the sale of that information to third parties.
The CPRA, approved by California voters in November 2020, amended the CCPA and added new privacy protections that began on January 1, 2023.
Two rights were born at that turn: the right to correct inaccurate personal information and the right to limit the use and disclosure of sensitive personal information, which includes social security number, financial account data and precise geolocation.
For most violations, only the Attorney General or the California Privacy Protection Agency (CPPA, the California privacy regulator) may take legal action. A consumer sues directly only in limited cases of data breach.
Since July 1, 2023, consumers can also file a complaint with the CPPA. The agency opened CPRA rulemaking on July 8, 2022, and the rules became effective on March 29, 2023.
All three jurisdictions ask the same of anyone holding someone else's data: clarity about what was collected, a simple path to correct or erase the record and a fast answer to the data subject's request.
Institutions recruiting in Europe, Brazil and the United States need to track the new privacy and data regulations together rather than one at a time, because the deadlines never line up.
Caption: Data privacy is settled along the path a record travels before it becomes a contact in the CRM.
What are the similarities and differences between GDPR, LGPD and CCPA?
GDPR, LGPD and CCPA start from the same principle: the person controls their own data and the organization answers for how it is used. The difference shows up in the basis that authorizes processing, in the set of data subject rights and in the authority that enforces each regime.
|
Law |
Basis for processing data |
Data subject rights |
Who enforces it |
|
GDPR (European Union) |
Explicit consent and the other grounds set out in the regulation |
More control over personal information, with transparent collection and processing |
Data protection authorities across European Union countries |
|
LGPD (Brazil) |
Consent and the other legal bases, legitimate interest among them |
Control over their own data, with clear rules for collection, storage and sharing |
ANPD, the Brazilian national data protection authority |
|
CCPA and CPRA (California) |
Consumer rights over the collection, use and sale of personal information |
Know, delete, refuse the sale, correct inaccurate data and limit the use of sensitive data |
California Attorney General and the California Privacy Protection Agency |
Table: Comparison of the data privacy laws that reach the contact database of an education institution.
The table shows why a single policy never works. The CRM has to offer data deletion, communication opt out and transparent access to the stored information, with behavior that varies by the contact's region of origin.
Another practical difference sits in what triggers the obligation. The European and Brazilian rules follow the residence of the data subject, while the California framework follows the consumer of that state.
The practical reading of the table is simple: the institution configures one policy per region and documents the basis of each processing activity, instead of applying the strictest rule to everyone and losing reach.
Which data privacy principles should every institution follow?
Transparency, consent, minimization, security and purpose hold up data privacy under any of these rules. The LGPD principles organize that list for Brazil and work as a practical checklist for reviewing forms, imported databases and active integrations.
- Transparency: the person needs to know which data the institution collects and for what purpose, in plain language.
- Consent: permission comes before collection and gets recorded, with date, channel and declared purpose.
- Minimization: the form asks only for the data needed for the stated purpose, and nothing beyond it.
- Security: access control, encryption and monitoring reduce the risk of improper access and of a breach.
- Purpose: processing serves legitimate, specific and informed purposes, with no incompatible later use.
The LGPD and the GDPR both expect a data protection lead, known by the acronym DPO (Data Protection Officer). That professional bridges data subjects, the supervisory authority and the institution itself.
Legitimate interest is the legal basis that allows personal data to be processed for legitimate purposes, as long as it does not harm the fundamental rights and freedoms of the data subject. The ANPD guide on legitimate interest describes the test an institution has to document.
Legitimate interest belongs to the Brazilian and European design of data protection. The necessity test and the data subject expectation test need to be recorded before collection, not after the first campaign goes out.
These principles also cover automated prospecting. An SDR (Sales Development Representative) supported by AI (Artificial Intelligence) can only approach a lead on a recorded legal basis, so it is worth checking whether prospecting leads with AI is safe before scaling volume.
Purpose deserves extra attention during recruitment. A phone number given for an entrance exam reminder cannot migrate into a sales cadence for a different program without a new, clearly stated agreement from that candidate.
A principle without configuration protects nobody. Each item on that list has to become a field, a permission or an automation inside the system that stores the institution's contacts.
How does a CRM help with compliance with data privacy laws?
A CRM helps with compliance because it gathers the data, the source and the consent of every contact in one place. With that history, the institution answers access, correction and deletion requests without hunting for information in scattered spreadsheets.
Before configuring any rule, align the team on what is CRM and on what the system actually stores. Without that agreement, every department creates a new field and the database loses traceability within a few months.
Centralization solves the first compliance problem: knowing which data exists. The second problem is the consent record, with date, accepted text and source channel saved on the contact itself.
HubSpot CRM lets you flag the legal basis by contact and by communication type, which separates people who agreed to receive email from people who only downloaded a content offer.
Access levels form the third layer. Only authorized staff can see sensitive data, and every integration through an API (Application Programming Interface) gets its own permission, reviewable at any time.
Reporting counts as compliance too. Dashboards showing how many contacts carry a recorded legal basis and how many asked for deletion turn the privacy policy into a number the leadership actually follows.
Anonymization and pseudonymization close the set. Both techniques make data unrecognizable or less identifiable without additional information, which lowers risk in analysis, testing and staging environments.
Why a CRM strategy underpins data privacy in daily operations.
Which data privacy best practices should you apply in the CRM?
Data privacy best practices in the CRM fit into three routines: auditing the database on a schedule, training whoever operates the system and deciding how long each record stays stored. All three belong on the operation's calendar.
- Periodic audit: review fields, lists and integrations to find data collected without a declared purpose.
- Permission by role: each user profile sees only what that person needs to do their own job.
- Retention policy: set a disposal deadline by record type and automate the purge once the deadline arrives.
- Request log: keep access, correction and deletion requests with date and outcome, ready for an audit.
Training holds all of it together. Well designed CRM training makes the team understand why the consent field exists, instead of filling it in automatically just to close the task.
Teams running HubSpot CRM find these controls under users, permissions and contact properties, with no custom development needed to start the routine.
The technical setup needs review as well, and the step by step on LGPD in HubSpot shows what to switch on in the tool to sustain the legal basis of every contact.
It is also worth mapping who exports data from the database. A spreadsheet downloaded to a personal computer leaves the system's control and becomes the weakest point of the whole policy.
What are the benefits of complying with data privacy laws?
Complying with data privacy laws lowers the risk of a fine, but the bigger gain is operational. A clean database, recorded consent and controlled retention improve email deliverability, segmentation and the reading of every campaign result.
Trust is the most visible effect. Candidates and students share more information when they understand the purpose of the collection and can review or delete their own record whenever they want.
Compliance also improves commercial results. A digital marketing strategy built on a reliable database avoids sending messages to invalid contacts and concentrates budget on people who actually asked for contact.
The same holds for an inbound marketing strategy, which depends on clear consent to nurture leads, and for an inbound sales strategy, which needs an intact history before every commercial approach.
In practice, an inbound marketing strategy and an inbound sales strategy only scale when the digital marketing strategy respects the legal basis of every contact. Dirty data is expensive in budget and in reputation.
Compliance done well becomes a competitive advantage. An institution that can prove care with personal data negotiates better with partners, vendors and regulators.
Frequently asked questions about data privacy
Where should you start the data privacy review of your CRM?
A data privacy review starts with an inventory: which data lives in the database, where it came from and for what purpose it was collected. Without that list, any internal policy stays a document nobody applies.
Configuration comes next. Consent recorded per contact, permission by role, a defined retention period and an active audit trail cover most of what GDPR, LGPD, CCPA and CPRA ask for.
Institutions that want support designing this process can count on Mkt4edu consulting to structure the contact database and the recruitment operation.




