Privacy and GDPR FAQ
6 min read
- View as Markdown Open this page as plain Markdown (opens in a new tab)
- Open in ChatGPT Ask questions about this page (opens in a new tab)
- Open in Claude Ask questions about this page (opens in a new tab)
- Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)
TrustLens is designed for GDPR compatibility. This FAQ covers the most common privacy questions: what data is processed, where it goes, how customer rights are honored, and what your responsibilities are as the data controller.
What customer data does TrustLens process? #
TrustLens processes data your WooCommerce store already collects:
- Email addresses (hashed as the customer key, with the plain email kept on the customer record)
- Order history, refunds, disputes
- Coupon usage
- Shipping and billing addresses (hashed for linked-accounts detection)
- Phone numbers (hashed)
- IP addresses (hashed for linked-account detection; a blocked checkout attempt also logs the email and IP in that event’s details)
- Payment method fingerprints (saved payment token, Stripe card fingerprint and card last-4, combined and hashed)
- Device fingerprints (browser user-agent and browser/screen characteristics, hashed)
It derives:
- Trust scores per customer
- Behavioral signal records
- Linked-account records
- Card-testing velocity events
Where does the data go? #
Nowhere outside your WordPress install by default. The plugin developer (Webstepper) does not receive customer data. The one default outbound call is Pro’s dispute-report verification: when a Dispute Evidence Report is generated, a one-way fingerprint of the report, the order number, its risk figures and your site URL are registered with the TrustLens verification service — no names, emails, addresses, IPs or hashes — and it can be switched off on the Chargeback Monitor page.
External delivery happens only if you explicitly configure:
- Webhook actions (automation rules sending to your endpoints)
- Email notifications (sending to email addresses you configure)
- Slack alerts (sending to Slack webhooks you configure)
How is data pseudonymized? #
Customer identifiers — email, address, phone, IP, payment method, device — are hashed using keyed HMAC-SHA256. The key is your site’s own WordPress auth secret key (from wp-config.php); TrustLens doesn’t generate or store a separate key, and because every site’s key differs, hashes can’t be matched across sites.
Why keyed: a plain SHA-256 hash of an email is reversible via rainbow tables (the email space is small enough). A keyed HMAC hash isn’t — without the key, you can’t compute the hash or reverse-engineer it.
Effect: even if a TrustLens fingerprint table is leaked, the hashed identifiers in it cannot be reversed back to raw addresses, phones or IPs without also having the secret key. (The customer record itself also holds the plain email — see below.)
Are raw email addresses ever stored? #
Yes — the customer_email column on the customers table stores the email in plaintext alongside the hash. This is necessary so the admin can see who they’re acting on. On a GDPR erasure request the whole customer record — email included — is deleted.
Does TrustLens integrate with WordPress’s privacy tools? #
Yes. TrustLens registers with WordPress’s standard privacy export and erasure tools.
Export #
When a customer requests their data via Tools → Export Personal Data, the export includes:
- Customer trust profile (score, segment, order and refund counts, return rate, blocked/allowlisted/flagged status, first and last order dates)
- Current signal breakdown
- Event timeline for that customer (the latest 100 events)
- Refund ledger entries and any refund cases with their audit trail
- Per-category order and refund stats
- Linked-account fingerprint records (hashes only, not other customers’ data)
- Automation log entries (Pro)
Dispute records and admin notes are not part of the export.
Erasure #
When erasure is requested, TrustLens deletes the customer’s record and associated data:
- The row in
trustlens_customers(including admin notes and tags) - All their signals
- All their events
- Their refund ledger entries, refund cases and product/category stats
- All their fingerprint hashes (which also removes their linked-account matches)
- Their automation log entries
Not erased: dispute records in the disputes table, card-testing velocity events (removed by their own retention window, 48 hours by default), and the TrustLens markers stored on WooCommerce orders.
The exporter and eraser are always registered with WordPress’s privacy tools; there is no setting to turn them off.
Can I anonymize a customer without erasing them? #
Set the customer’s customer_email to NULL in the database (the REST API can’t change it). The hash remains for internal references but the plaintext email is gone. This is a “pseudonymize” operation — the customer’s trust profile and history persist, but the personally-identifying email isn’t accessible.
Full erasure removes the profile entirely.
How long is data retained? #
Default retention:
- Customer trust profiles: indefinite (until erased)
- Event log: indefinite (until erased)
- Linked-account fingerprints: 365 days after the identifier was last used
- Daily score snapshots (trend chart): 400 days
- Card-testing velocity events: 48 hours (adjustable from 24 to 168 hours on the Card-Testing Defense page)
- Automation log: 90 days
There is no automatic purge of inactive customers; use WordPress’s erasure tool for individual customers, or the uninstall option to remove everything.
What is the legal basis for processing under GDPR? #
Most TrustLens processing relies on legitimate interest — protecting your store from fraud and abuse is a recognized legitimate interest under GDPR. Customers can object to processing via the standard rights mechanisms.
For specific compliance questions, consult counsel. TrustLens documentation is informational, not legal advice.
Do I need to update my privacy policy? #
Yes. Your privacy policy should disclose:
- That you analyze customer behavior for fraud prevention
- What behaviors are analyzed (orders, refunds, etc.)
- That trust scores are computed and used for moderation decisions
- That data is processed locally (not shared with third parties unless you configure otherwise)
- How customers can exercise their rights
WordPress’s privacy policy template includes a section for “Plugin data.” TrustLens’s data processing should be added there.
Can customers see their own trust score? #
By default, no. Trust scores are admin-only. They’re shown on the customer profile in admin but not exposed to the customer’s My Account or any customer-facing surface.
If a customer makes a data access request, the score appears in their export. That’s GDPR-required disclosure, not customer-facing display.
How does TrustLens handle minors / children? #
TrustLens has no special handling for minors — it processes customer data the same regardless. If your store operates in a jurisdiction with specific protections for minors (e.g. COPPA in the US), your existing WooCommerce minor-handling applies; TrustLens inherits that posture.
What about CCPA / California-specific requirements? #
CCPA’s “right to know” and “right to delete” map cleanly onto WordPress’s export and erasure mechanisms — TrustLens responds to both. The “right to opt out of sale” doesn’t apply because TrustLens doesn’t sell data.
For CCPA-specific disclosures, ensure your privacy policy includes TrustLens’s processing.
What about other jurisdictions (LGPD, PIPEDA, etc.)? #
Most modern privacy laws share core concepts with GDPR — rights to access, deletion, and information. TrustLens’s GDPR-aligned design generally satisfies these laws’ technical requirements. Disclosure and consent requirements vary; consult local counsel.
Can I export TrustLens data for backup or migration? #
Yes, for customers: Export CSV on the TrustLens → Customers page exports the customer list (following the current segment and search filters, up to 10,000 rows). There’s no built-in CSV export for disputes or events; the data lives in your own database tables, so you can back it up with your normal database backups.
If I uninstall TrustLens, is data deleted? #
By default, no — to allow reactivation without data loss. To wipe on uninstall, turn on “Remove all TrustLens data when plugin is deleted” (Uninstall Behavior) in Settings → Data before uninstalling.
How does TrustLens handle the HMAC secret if compromised? #
TrustLens has no secret of its own — it uses your WordPress auth secret key. If you suspect that key is compromised:
- Regenerate your WordPress secret keys (in
wp-config.phpor with a security plugin’s “regenerate keys” tool) - All existing hashes become invalid (they were keyed with the old secret)
- Run Historical Sync so TrustLens rebuilds customer records and fingerprints with the new key
- Re-apply any blocks and allowlists you set by hand — those don’t come back from the sync
Until the sync finishes, returning customers aren’t matched to their existing profiles and linked-account detection starts over. Use only if necessary.
Does TrustLens process card data? #
No PAN (full card numbers). For linked-account matching, TrustLens hashes the payment token details the gateway provides (saved token ID, Stripe card fingerprint, card last-4); it also notes the card brand on the order for chargeback ratios. It never sees the full card number. Full card data never reaches TrustLens — it’s handled by your payment gateway exclusively.
PCI-DSS scope: TrustLens does not process or store PAN, so it’s outside PCI scope on its own. (Your overall PCI posture depends on your payment gateway integration.)
Updated on October 18, 2026