Salesforce Data Privacy Quiz: 12 Questions for Admins and Architects

Answer: They are copied as they are, with no masking applied

Salesforce describes a Full sandbox as a replica of production, including all data. Nothing in the copy masks it. If you want masked data, you need a separate step after the copy, such as a masking tool or a post-copy script.

“Full sandboxes are a replica of your production org, including all data, such as object records and attachments, and metadata.”

Answer: User information

Developer and Developer Pro sandboxes copy your configuration (metadata), not your business records. User records are the exception: they come across in every sandbox type. So employee names and email addresses reach even a Developer sandbox. Field history and Chatter are optional extras for Full sandboxes only.

“User information is included in a sandbox copy or refresh for all sandbox types.”

Answer: System email only

New and refreshed sandboxes default to System email only. If someone switches a sandbox to All email for testing, automated email can reach the real addresses copied from production. Sandboxes created before Spring '13 default to All email.

“New and refreshed sandboxes use the System email only setting by default. Sandboxes created before Spring ’13 default to All email.”

Answer: Runs your own post-copy tasks, such as data changes, once the sandbox is created

SandboxPostCopy is the built-in hook for running your own Apex at the end of a sandbox copy. Teams use it for tasks like scrambling personal data. Salesforce runs the class, but you write and maintain the logic yourself.

“To make your sandbox environment business ready, automate data manipulation or business logic tasks. Extend this interface and add methods to perform post-copy tasks, then specify the class during sandbox creation.”

Answer: It encrypts data at rest, and it is not a tool for deciding who can see data

Shield Platform Encryption protects stored data. Salesforce says it is not an authorization tool, and that field-level security and sharing control who sees what. So it does not do the job of masking data in a sandbox.

“Shield Platform Encryption is not a user authentication or authorization tool. To control which users can see which data, use out-of-the-box tools such as field-level security settings, page layout settings, and sharing rules”

Answer: It goes to the Recycle Bin for 15 days and can be restored

A normal delete is not an erasure. The record sits in the Recycle Bin for 15 days, where users can restore it, and then Salesforce schedules it for permanent deletion. Emptying the Recycle Bin deletes it permanently straight away.

“Deleted items remain in the Recycle Bin for 15 days, and during that time users can restore them. After 15 days, Salesforce schedules these items for permanent deletion from the Recycle Bin.”

Answer: Up to 18 months, and up to 24 months through the API

Without Field Audit Trail, field history is kept for up to 18 months, or 24 months through the API. Changes to tracked fields are saved in history objects. So an earlier value of a field, such as an old email address, can outlive the edit that replaced it.

“When Field Audit Trail is turned off, Salesforce retains field history data for up to 18 months, and up to 24 months via the API.”

Answer: Until you delete it

With Field Audit Trail on, Salesforce keeps field history until you delete it. Some older guides quote a fixed 10-year limit, but the current help page does not. For erasure requests, archived history is one more place personal data can remain.

“If Field Audit Trail is turned on, Salesforce retains field history data until you manually delete it.”

Answer: The customer's preference to have their records and personal data deleted

The Individual object stores a customer's data privacy preferences, and ShouldForget is one of them. It records what the customer wants. Finding and deleting the related records is a process you build or buy.

“Preference to delete records and personal data related to this customer.”

Answer: Support ended on 9 July 2026, and it becomes read-only from 31 Dec 2026

Support has already ended: it stopped on 9 July 2026, and Salesforce says issues will not be fixed. The package becomes read-only from 31 Dec 2026. 18 July 2026 is the date its replacement, Data Mask & Seed, became available with Summer '26.

“the Data Mask managed package's support ended on July 9, 2026, and any issues which arise will not be fixed. The managed package's display will become read-only starting December 31, 2026.”

Answer: You create new masking policies to replace them

Salesforce tells customers to create new masking policies to replace existing configurations. Nothing carries over automatically, so plan time to rebuild and test each one. You can run both side by side until the old package becomes read-only.

“To use the new app, simply create new masking policies to replace your existing masking configurations, as new functionality is only available through newly created policies.”

Answer: No. Salesforce lists it at 10% of net spend

Data Mask & Seed needs no installation, but that does not make it free. Salesforce's pricing page lists it at 10% of net spend, and users also need the Data Mask And Seed User permission set licence. Salesforce notes that the pricing page is for information only and subject to change.

“Data Mask & Seed Test securely by protecting sensitive data in Salesforce Sandboxes. Work with realistic, not real data throughout the development process. 10% of net spend”