Explore modules
All modules
Shop all PrestaShop Modules by Fred
PH Customer Data Privacy – Secure Staging & Sandbox Testing images
PrestaHeroes / Built for your shop
Get technical help. Keep customer details private.
PH Customer Data Privacy encrypts selected sensitive customer fields on a staging copy while preserving the shop’s database structure for testing and troubleshooting.
Create staging. Protect the data. Then share access.
Restore original values with your saved privacy key.
For PrestaShop 1.7, 8 & 9.
PH CUSTOMER DATA PRIVACY · PRIVACY SAFE
A staging copy can contain real customer names, emails, addresses and phone numbers. Protect selected sensitive fields before you give developers, module vendors or support teams access.
PROTECT THE DETAILS
Encrypt selected customer fields directly in the staging database before sharing technical access.
Illustrative protection overview for selected fields.
KEEP THE WORKING STRUCTURE
Customer, order, address and cart records remain represented, with their relationships available for investigation.
PROTECT FIRST. SHARE ACCESS SECOND.
Start with a working copy of your production PrestaShop store for debugging, development or testing. Run Privacy Safe on that staging copy.
Protect sensitive fields in the copy while keeping customers, orders, addresses and related records represented. Save the privacy key securely.
Give the developer, agency or support team access to the prepared staging environment so they can investigate the shop with less exposure of readable customer information.
Use the saved privacy key and restore vault to recover the original values when your workflow calls for them.
Keep your privacy key safe. The module does not store it. You need the saved key to restore the original customer data.
BUILT FOR REAL PRESTASHOP SUPPORT WORK
Encrypt selected names, emails, addresses, phone numbers and other supported customer fields so those values are no longer readable in the working copy.
Retain the structure technical teams need to inspect customer records, order history, carts and linked addresses.
Original values are retained for the restoration workflow, with access to restoration controlled by the privacy key.
You retain the key needed to restore original values. Save it securely before anyone starts work on the protected copy.
Prepare the staging database before sharing it with module developers, theme providers, agencies or technical support.
Make data protection part of how you prepare shop copies for development, troubleshooting and technical reviews.
TECHNICAL CONTEXT WITHOUT UNNECESSARY EXPOSURE
Customer and address records remain part of the shop’s structure while selected personal fields are protected.
Order records and their relationships remain available for investigation and review.
Cart records and related data remain represented for examining shop behavior and troubleshooting.
WHEN THE VENDOR NEEDS TO SEE THE ISSUE
A production-derived staging shop can help reproduce a problem that a clean installation cannot. It can also carry the private information of the people who bought from you.
Use Privacy Safe on the staging copy before granting access, so the technical investigation starts with selected sensitive customer fields protected.
RESTORATION STAYS IN YOUR HANDS
The restore vault retains original values for restoration. The module does not retain your privacy key, so keep that key securely under your control.
Restore original customer information when it is required for your workflow. Until then, let outside support work with the protected staging copy.
A BETTER WAY TO PREPARE FOR SUPPORT
Need help preparing a shop copy for technical work? Talk directly to me about your setup. — Fred
