Data and Privacy
The Data settings tab is where you run Historical Sync, manage test data, see how much data TrustLens holds, choose whether to share usage data, and decide what happens to TrustLens data on uninstall. This page covers that tab and how TrustLens handles personal data more broadly — hashing, retention, GDPR tools, and what leaves your site.
Location: TrustLens → Settings → Data.
Privacy Architecture #
Before getting into settings, the high-level privacy story:
- Processing is local. Scoring runs on your site. Customer data leaves it only through features you turn on — see What Leaves Your Site.
- Customer identifiers are keyed hashes. Email addresses are converted to HMAC-SHA256 hashes for internal use, keyed with your site’s WordPress authentication salt, so hashes differ from site to site. The customer record also stores the email address itself so you can see who a customer is in the admin.
- Linked-account identifiers are hashed. Shipping and billing addresses, phone numbers, payment tokens, IP addresses, and browser user agents used for linked-account matching are stored only as keyed hashes, and are deleted 365 days after they were last seen.
- Card-testing data is short-lived. Velocity events keep the IP address of each checkout attempt (and the email hash when there is one) for the event-retention window — 48 hours by default.
- GDPR integration. WordPress’s personal-data export and erasure tools include TrustLens data.
The Data Tab #
Historical Data Sync #
Analyzes your existing WooCommerce orders to build customer trust profiles, in the background. Shows the status (Not Started, Running, Complete, Failed, or Skipped) and progress, with Start Historical Sync and Stop Sync buttons.
Test Data (Development) #
Generate Test Data creates 65 sample customers across all segments (optionally with a fixed seed for identical data every run); Remove Test Data deletes them; Check & Clean scans every table for leftover test data and removes it.
Data Statistics #
Counts of customers, events logged, and signals recorded.
Help Improve TrustLens #
Lets you opt in or out of sharing your site’s basic WordPress environment (such as PHP and plugin versions) with Webstepper.
Uninstall Behavior #
Default: Off
“Remove all TrustLens data when plugin is deleted.” If on, deleting the plugin from WordPress’s Plugins page drops every TrustLens table and deletes its settings, transients, user meta, and scheduled actions. If off (default), data persists across reinstalls — useful when troubleshooting. Turn it on before final removal if you want a clean uninstall.
HMAC Key Management #
There is no key setting or regenerate button. The key that hashes emails and linked-account identifiers is your site’s WordPress authentication salt (AUTH_SALT / AUTH_KEY in wp-config.php).
Changing those salts — for example with a security plugin’s “regenerate salts” feature — changes every hash going forward. Existing customer records, linked-account fingerprints, and card-testing history no longer match new activity and become orphaned. Avoid rotating the salts on a store with TrustLens history unless you have to, and be aware that moving to a new environment with different salts has the same effect.
Data Retention #
| Data | Retention |
|---|---|
Customer records and the event log ({prefix}trustlens_events) |
Kept until the customer is deleted or erased; not purged automatically |
| Signals | Rewritten on each recalculation — only the most recent calculation is kept |
| Linked-account fingerprints | Deleted 365 days after they were last seen |
| Card-testing velocity events | 48 hours by default, set from 24 to 168 hours on the Card-Testing Defense page |
| Automation logs (Pro) | 90 days (developers can change it with the trustlens/automation/retention_days filter, 7–365) |
| Webhook delivery log (Pro) | The most recent 1,000 deliveries |
| Dispute worklist records | Not purged automatically |
There is no automatic erasure of inactive customers.
GDPR Privacy Tools Integration #
TrustLens registers with WordPress’s Tools → Export Personal Data and Tools → Erase Personal Data. The integration is always on; there are no settings for it.
Export contributes the customer’s record, events, refund records, refund cases and their history, current signals, category stats, linked-account fingerprints (as hashes), and automation logs.
Erasure deletes all of the above, plus product-risk snapshots.
Not covered by either tool: rows in the dispute worklist table, which stay until TrustLens data is deleted on uninstall, and card-testing velocity events, which expire with the retention window. Card-testing device fingerprints aren’t tied to an email address.
Data Export #
- Customers: the Export CSV button on the TrustLens Customers page
- Card-testing events (Pro): the Export CSV link in the 24-hour intelligence card on the Card-Testing Defense page
- A single customer: WordPress’s Export Personal Data tool
There is no export for disputes or for the full event log.
Data Deletion #
There is no “Delete All TrustLens Data” button. Your options are:
- Individual customers: the Delete bulk action on the Customers page, or WordPress’s Erase Personal Data tool
- Test data: Remove Test Data or Check & Clean on the Data tab
- Everything: turn on Uninstall Behavior and delete the plugin
WooCommerce orders and customers are never touched by TrustLens deletion.
What Leaves Your Site #
| Feature | What is sent | Default |
|---|---|---|
| Dispute report verification (Pro) | A report’s fingerprint, the order number, your site URL, and the report’s risk figures, to webstepper.io — never customer data | On (Chargeback Monitor → Chargeback settings) |
| Store Trust Network (Pro, multi-site) | Risk flags keyed by a group-key hash of the email, to your own linked stores | Off |
| Webhooks and automation webhooks (Pro) | Event payloads to URLs you configure | Off |
| Card-testing alerts (Pro) | Alert details, including the checkout’s IP and email for attack alerts, to the email or Slack URL you set | Not configured |
| Usage data (Freemius) | Your site’s WordPress environment details | Only if you opt in |
Data Mapping for GDPR #
The privacy export bundle structure (when a customer’s data is exported):
| Section | Contents |
|---|---|
| Customer Profile | Trust score, segment, status flags, stat columns |
| Events | This customer’s events |
| Refunds and Refund Cases | This customer’s refund records, refund cases, and case history |
| Signals | Current signal breakdown |
| Category Stats | Per-category order and refund statistics |
| Fingerprints | Linked-account fingerprint hashes, with how often and when they were seen |
| Automation Logs | Automation rule runs for this customer |
The export uses WordPress’s standard format and is delivered via WordPress’s personal-data request mechanism.
Compliance Caveats #
TrustLens is designed for GDPR compatibility but compliance is your responsibility:
- Document TrustLens’s data processing in your privacy policy
- Update terms of service to reflect behavioral scoring
- Honor erasure requests within statutory windows
- If you operate in jurisdictions with stricter requirements (CCPA, others), evaluate accordingly
For specific compliance questions, consult counsel — this documentation is informational, not legal advice.
Updated on October 18, 2026
