Salesforce data privacy is the work of keeping personal data in your org lawful, minimal, secure and traceable under laws such as the GDPR, the CCPA and Australia's Privacy Act. Salesforce provides the controls, including field-level security, encryption, audit trails and consent records; your team decides how they are configured and who is accountable.
This checklist is for the developers and admins who make those decisions. It sets out what each law asks for, using the official texts, and maps each duty to the Salesforce feature that covers it.
Which privacy laws affect a Salesforce org?
Most orgs hold data on people in more than one jurisdiction. The three laws below are a common starting point for orgs serving Europe, the US and Australia.
| Law | Who it covers | What it means for your org |
|---|---|---|
| GDPR (EU) | Processing of personal data of people in the EU | Seven principles (Article 5), privacy by design (Article 25), impact assessments for high-risk processing (Article 35) and the right to erasure (Article 17). Fines for breaching the principles can reach EUR 20 million or 4% of worldwide annual turnover, whichever is higher (Article 83(5)). |
| CCPA (California) | Businesses handling personal information of California residents | Rights to know, delete, correct, opt out of sale or sharing, limit use of sensitive personal information, and non-discrimination. The rights to correct and to limit came in with the CPRA amendments from 1 January 2023. |
| Privacy Act 1988 (Australia) | Australian Government agencies, organizations with annual turnover over $3 million and some others | The 13 Australian Privacy Principles, which govern how APP entities handle personal information. |
Sector rules for health, education or financial data can add to these. Check them with your legal team before you design the data model.
What are the seven GDPR principles?
Article 5 of the GDPR is the clearest summary of what a privacy-ready org looks like. Each principle has a direct Salesforce consequence:
- Lawfulness, fairness and transparency: record the lawful basis and the consent behind each use of the data.
- Purpose limitation: do not reuse data for a purpose incompatible with the one it was collected for.
- Data minimization: only create the fields you need for that purpose.
- Accuracy: use validation rules and duplicate management so wrong data is corrected or erased.
- Storage limitation: set retention periods and delete or anonymize records when they expire.
- Integrity and confidentiality: restrict access and encrypt sensitive fields.
- Accountability: be able to prove all of the above, which is what audit trails and documentation are for.
What are the GDPR Article 5 principles?
- LawfulnessFair and transparent
- Purpose limitationNo incompatible reuse
- Data minimizationOnly needed fields
- AccuracyValidate, deduplicate
- Storage limitationSet retention periods
- IntegrityRestrict and encrypt
The Salesforce data privacy checklist
Work through these eight steps for every new project, integration or AI feature that touches personal data.
| Step | Check | Salesforce control |
|---|---|---|
| 1. Assess | Have you run a data protection impact assessment for high-risk processing? | A documented DPIA before build (GDPR Article 35) |
| 2. Design | Does each personal data field have a stated purpose? | Data model review; fewer fields |
| 3. Restrict | Can only the right users view or edit each sensitive field? | Field-level security, permission sets, sharing rules |
| 4. Encrypt | Are sensitive fields encrypted at rest? | Shield Platform Encryption |
| 5. Mask | Is real personal data kept out of sandboxes? | Data Mask & Seed |
| 6. Consent | Is consent captured and respected before marketing use? | Consent records and preference management |
| 7. Respond | Can you find, export, correct and delete one person's data on request? | Privacy Center, reports and a documented deletion process |
| 8. Prove | Can you show who accessed or changed personal data? | Event Monitoring, Field Audit Trail |
Why does field-level security matter most?
Field-level security is the control that most orgs get wrong. Salesforce's help page on controlling user access to fields says that fields hidden on a page layout can still be seen through reports, search results, list views and the API, and tells admins not to use page layouts to secure data. Field-level security restricts view and edit access across all of those, and overrides less restrictive page layout settings.
For developers, apply the same discipline in code: check object and field access in any Apex class, flow or integration that returns personal data to a user or another system.
Which Salesforce tools cover encryption, masking and audit?
Salesforce says Shield is a paid add-on with four tools: Platform Encryption, Event Monitoring, Field Audit Trail and Data Detect. It lists Data Mask & Seed, for developing safely with sensitive data protected in sandboxes, and Privacy Center, which it says simplifies data management to reduce compliance costs, as related products.
One date to note: Salesforce's active retirements list, updated 16 October 2026, shows end of support for the Data Mask managed package on 31 December 2026. If your sandboxes rely on that package, plan the move to Data Mask & Seed now.
For the platform's own certifications, Salesforce publishes its certifications and attestations on its compliance site. Check the ones that cover the specific services you use, rather than assuming one certificate covers every product.
How do you keep an org compliant over time?
- Re-run the checklist when you add a data source, integration, managed package or AI agent.
- Review permission sets and sharing rules at least once a quarter, and remove access people no longer need.
- Make citizen developers follow the same rules. A flow built by a business user can expose data just as easily as code; see when no-code is enough and when you need a developer.
- Keep the DPIAs, retention decisions and access reviews in one place, so you can prove accountability when asked.
Techila's Salesforce development services team builds these controls into new projects and audits existing orgs against them.
Frequently asked questions
What are the 7 main principles of GDPR?
Article 5 of the GDPR sets out seven principles: lawfulness, fairness and transparency; purpose limitation; data minimization; accuracy; storage limitation; integrity and confidentiality; and accountability. The first six describe how personal data must be processed, and accountability means the controller must be able to demonstrate compliance with them.
What does FLS mean in Salesforce?
FLS stands for field-level security. It controls whether a user can view or edit each field on an object, and Salesforce applies it across record pages, reports, search results, list views and the API. Salesforce warns that hiding a field on a page layout does not secure it, so use field-level security to restrict access to personal data.
Is Salesforce GDPR compliant?
Salesforce publishes its compliance certifications and attestations on its compliance site, and it provides controls such as field-level security, encryption and audit trails. Compliance with the GDPR, though, depends on how your organization collects, uses, secures and deletes personal data in its own org, so the responsibility stays with you as the controller.
When is a data protection impact assessment required?
Article 35 of the GDPR requires the controller to carry out a data protection impact assessment before processing that is likely to result in a high risk to people's rights and freedoms, in particular when using new technologies. Run one before you add a new data source, integration or AI feature that handles personal data in Salesforce.
Does Australia's Privacy Act apply to my business?
The OAIC says the Privacy Act 1988 covers Australian Government agencies and organizations with an annual turnover of more than $3 million, plus some other organizations. Those entities must follow the 13 Australian Privacy Principles. Check the OAIC's guidance if your business is under the threshold, because some smaller organizations are still covered.
Talk to a Salesforce architect
Share your org, data sources and the regulations you work under to get a privacy review.
Talk to our Salesforce development team. We reply within 1 business day.
