Accurate tracking, respectful of your customers.
Server-side tracking is often sold as a privacy workaround. We see it differently: done properly, it is a chance to handle customer data more carefully than a browser pixel ever could. Here is exactly how PrestaSignal treats personal data.
Personal data is hashed before it leaves your server
Email, phone number, first and last name, city and state are normalised and SHA-256 hashed on your PrestaShop server — before anything is sent anywhere. The ad platforms receive only irreversible hashes for matching (exactly what Enhanced Conversions and the Meta Conversions API expect), never raw personal details.
Every field, accounted for.
Nothing identifying ever leaves your server in the clear. Here is exactly what happens to each piece of data.
- #Email address
- #Phone number
- #First name
- #Last name
- #City
- #State / region
- ·Country
- ·Postal code
Non-identifying on their own; required in plain form for geographic matching.
- ✕Raw email or phone
- ✕Your Meta CAPI token
- ✕Anything that identifies a person in the clear
Your secrets never reach the browser
Sensitive credentials — like your Meta Conversions API token — stay strictly server-side. They are never exposed in page source or to any client-side script, which is one more thing a browser-based setup cannot guarantee.
Consent is respected, not bypassed
Server-side does not mean consent-free. PrestaSignal forwards each visitor’s consent choice exactly as they made it — declined is never rewritten as granted — so you stay compliant while still recovering the conversions you are entitled to measure. Country and postal code are sent in the plain form Google requires; everything identifying is hashed.
The cookies we set on your shop
A privacy page should say this plainly. The small connector PrestaSignal places on your store’s own address sets first-party cookies only — nothing third-party. Here is each one: what it does, how long it lives, and what happens when a visitor says no.
Apple’s cookie-deletion rules are published in WebKit’s tracking-prevention policy: webkit.org/tracking-prevention.
Data retention, in plain terms
We keep as little as possible for as long as necessary. The tracking server forwards events to your connected platforms; it is a conduit, not a long-term data store of your customers’ personal information. The platforms you send to — GA4, Google Ads, Meta — apply their own retention policies to the data they receive, which you control from within each platform.
Who processes your data
Your events pass through infrastructure we operate and the ad platforms you choose to connect. We don’t sell or share your customers’ data with anyone else, and we don’t use it for any purpose beyond delivering the tracking you’ve asked for.
Receives events from your store and forwards them to the platforms you connect. We operate it — you host nothing.
GA4, Google Ads and Meta receive only the events and fields needed for measurement.
No data brokers, no resale, no secondary use. Your customer data stays within that chain.
You stay in control
Because personal data is hashed before it leaves your server and consent signals are respected, you remain the controller of your customers’ information. You decide which platforms to connect, what consent gates apply, and you can stop sending at any time by disabling the module.
Privacy — your questions.
Which personal fields are hashed?+
Email, phone, first name, last name, city and state are SHA-256 hashed on your server before transmission. Country and postal code are sent in plain form because Google’s matching requires it; nothing directly identifying is sent in the clear.
Is this GDPR-compliant?+
PrestaSignal is built to respect consent and to minimise what personal data is transmitted, hashing it irreversibly first. Used with a proper consent banner, it supports a compliant setup — but you remain the data controller for your store.
Can the ad platforms reverse the hashes?+
No. SHA-256 is a one-way hash used only for matching. The platforms compare your hashes against their own hashed data; they cannot recover the original email or phone number from what you send.
Where is my Meta CAPI token stored?+
Server-side only. It is never placed in page HTML or any browser script, so it cannot be scraped from your site.
Do you store my customers’ personal data?+
The tracking server acts as a conduit that forwards events to your platforms; it isn’t a marketing database of your customers. Identifying fields are hashed before they’re sent, so what passes through is not readable personal data.
Tracking you can stand behind.
Book a teardown — we’ll walk through exactly what your store would send, and how it’s protected.