SELECT FIELDS
Identify
Choose what needs to be protected.Contact · Name · ID · Email · Phone
Salesforce native / data protection
Realistic data for testing. Sensitive data out of harm's way.
shuffle2.me protects sensitive information in Salesforce sandboxes so your team can build, validate and evolve faster — without giving up governance.
Configurable maskingLGPD and GDPR in focus
CONTACT / RECORD 00321SOURCE / PRODUCTION
NameMaria SantosSENSITIVE VALUE
ID417.298.250-09SENSITIVE VALUE
Phone+55 11 4118-6883SENSITIVE VALUE
Email[email protected]SENSITIVE VALUE
MASK
CONTACT / RECORD 00321OUTPUT / SANDBOX
NameAna FerreiraFIELD MASKED
ID052.318.947-66FIELD MASKED
Phone+55 11 9284-7731FIELD MASKED
Email[email protected]FIELD MASKED
FIELD MASKED
When real data reaches a sandbox
Development should not mean exposure.
Test environments need context. But real data carries IDs, emails, phones, addresses and a responsibility that cannot be ignored.
Keep the useful structure. Change the sensitive value.
Understand the protectionA protection layer in your flow
Protection in the flow. Context stays intact.
4 RULES ACTIVE
Configure
Define masking rules for your organization context.Contact.Name → MASK · Contact.ID → MASK · Contact.Email → MASK · Contact.Phone → MASK
SAFE TO TEST
Test
Keep data useful for development and testing without exposing original sensitive values.Structure preserved · values protected
IDENTIFY → CONFIGURE → TESTNative Salesforce / governance by design
Security that keeps pace
What changes when data stays protected.
When security stops being an extra step, development gains clarity, testing gains realism and the business gains confidence.
FIELD MASKED
Security by design
The original value appears only as source context and is transformed before reaching the test environment.
STRUCTURE PRESERVED
Realism for testing
The record structure remains similar; sensitive values are what change.
RULE UPDATED
Rules without delay
Support internal data protection and governance policies with rules that follow your scenario.
Animated product demo
The value changes. Context stays intact.
A visual reading of the flow: original record, masking rules and protected sandbox output.
CONTACT / RECORD 00321SOURCE / PRODUCTION
NameMaria SantosSENSITIVE VALUE
ID417.298.250-09SENSITIVE VALUE
Phone+55 11 4118-6883SENSITIVE VALUE
Email[email protected]SENSITIVE VALUE
MASKING RULES
Contact
Contact.Name → MASK
Contact.ID → MASK
Contact.Email → MASK
Contact.Phone → MASK
4 RULES ACTIVECONTACT / RECORD 00321OUTPUT / SANDBOX
NameAna FerreiraFIELD MASKED
ID052.318.947-66FIELD MASKED
Phone+55 11 9284-7731FIELD MASKED
Email[email protected]FIELD MASKED
SAFE TO TEST
Pause to read
Sensitive data needs context
For teams that test without giving up responsibility.
ADMIN / GOVERN
Salesforce Admins
Prepare and manage test environments with more control over the data used.
DEV / BUILD
Development
Build and validate features without depending on exposure of original values.
QA / VALIDATE
QA / UAT
Test flows, rules and scenarios with data that keeps the environment useful.
SECURITY / PROTECT
Security / Governance
Reduce unnecessary exposure of sensitive information outside production.
Frequently asked questions
Clear protection, a simple next step.
Does shuffle2.me alter production data?
No. Masking happens in sandbox environments, preserving production operations.
Can I choose which fields are masked?
Yes. Rules are configurable by field and can be adjusted to your organization context.
Is shuffle2.me for the Salesforce ecosystem?
Yes. It was designed for Salesforce development and testing flows.
Does data remain useful after masking?
Yes. The goal is to preserve the context and structure needed to validate flows without exposing original values.
Can I adapt rules to my scenario?
Talk to Soublox about your scenario and the rules you need to evaluate.
Next step
Your sandbox can be safer today.
Tell us about your Salesforce scenario. Soublox can show how shuffle2.me fits your development and testing flow.