GDPR Compliance
Complete GDPR Compliance Guide
Comprehensive guide to using Customer History in compliance with GDPR and other privacy regulations.
GDPR Overview
The General Data Protection Regulation (GDPR) is EU law that governs data protection and privacy. Key principles:
- Lawfulness, fairness, transparency: Clear about data collection
- Purpose limitation: Only collect what you need
- Data minimization: Collect minimum necessary data
- Accuracy: Keep data accurate and up to date
- Storage limitation: Don’t keep data forever
- Integrity and confidentiality: Keep data secure
- Accountability: You’re responsible for compliance
Customer History & GDPR
Customer History includes all technical features needed to help you comply with GDPR. However, compliance also requires proper policies and procedures on your part.
Legal Basis for Processing
GDPR requires a legal basis for processing personal data. Options:
1. Legitimate Interest (Most Common)
- Use case: Analytics, fraud prevention, site improvement
- Requirements: Balance your interests against user rights
- Customer History: Analytics and business optimization qualify
- Documentation: Must document legitimate interest assessment
2. Consent
- Use case: Marketing emails, non-essential tracking
- Requirements: Must be freely given, specific, informed, unambiguous
- Customer History: Built-in consent management
- Withdrawing: Users must be able to revoke easily
3. Contract
- Use case: Processing necessary to fulfill orders
- Requirements: Must be necessary for contract
- Customer History: Order tracking qualifies
4. Legal Obligation
- Use case: Tax records, legal requirements
- Requirements: Required by law
Implementing Consent Management
If you choose consent as legal basis:
Cookie Consent Banner
- Install cookie consent plugin:
- CookieYes
- Complianz
- Cookie Notice
- Configure banner to include analytics cookies
- Customer History respects consent decision
- Tracking disabled until consent given
Customer History Settings
- Go to Settings → Privacy → Consent
- Enable Require Consent
- Choose consent method:
- Cookie plugin integration
- Built-in consent banner
- Custom JavaScript
- Customize consent message
- Save settings
Consent Documentation
- Customer History logs when consent was given
- Stores consent timestamp
- Records consent version
- Tracks consent withdrawals
Privacy Policy Requirements
Your privacy policy must disclose:
What Data You Collect
- Browsing behavior
- Product views
- Search queries
- Device information
- Location data (if collected)
- Purchase history
Why You Collect It
- Improve customer experience
- Personalize recommendations
- Optimize store performance
- Fulfill orders
- Send relevant communications
How Long You Keep It
- Session data retention period
- Customer profile retention
- Analytics data retention
Who Has Access
- Store administrators
- Shop managers
- No third-party sharing (data stays on your server)
User Rights
- Right to access their data
- Right to rectification
- Right to erasure
- Right to data portability
- Right to object
Sample Privacy Policy Text
Customer Analytics
We use Customer History for WooCommerce to analyze browsing behavior and improve your shopping experience. This includes tracking page views, product interests, and purchase history.
Legal basis: Legitimate interest in operating and improving our store.
Data retention: Session data is kept for [90] days, customer profiles maintained indefinitely unless deletion requested.
Your rights: You can request access to, correction of, or deletion of your data by contacting [email].
IP Anonymization
Reduce data collection by anonymizing IP addresses:
Configuration
- Go to Settings → Privacy → IP Anonymization
- Choose level:
- None: Store full IP (192.168.1.100)
- Partial: Mask last octet (192.168.1.XXX)
- Full: Don’t store IP at all
- Save settings
Recommendation
- EU customers: Use partial or full anonymization
- Fraud prevention: Partial anonymization maintains some usefulness
- Maximum privacy: Full anonymization
Data Subject Rights
How to handle GDPR data requests:
Right of Access (Article 15)
Request: “Show me what data you have about me”
How to comply:
- Find customer in Customer History
- Click Export Customer Data
- Download complete data package
- Send to customer within 30 days
Right to Rectification (Article 16)
Request: “My data is incorrect, please fix it”
How to comply:
- Open customer profile
- Edit customer information
- Update incorrect data
- Save changes
- Confirm correction with customer
Right to Erasure (Article 17)
Request: “Delete all my data”
How to comply:
- Open customer profile
- Click Delete Customer Data
- Select what to delete:
- Sessions only
- All tracking data
- Complete removal
- Confirm deletion
- Note: WooCommerce order data handled separately
Right to Data Portability (Article 20)
Request: “Give me my data in a format I can use elsewhere”
How to comply:
- Export customer data
- Choose machine-readable format (JSON or XML)
- Provide to customer
Right to Object (Article 21)
Request: “Stop tracking me”
How to comply:
- Add customer to exclusion list
- Settings → Privacy → Excluded Users
- Enter customer email or user ID
- Save
- No future tracking for this customer
Data Retention Settings
Comply with storage limitation principle:
Configure Retention
- Go to Settings → Data Management
- Set retention periods:
- Session data: 30, 60, 90 days, or custom
- Search history: 90, 180, 365 days
- Analytics data: Archive after 1 year
- Enable automatic cleanup
- Save settings
Recommended Periods
- Session data: 90 days (covers return visitors)
- Customer profiles: Retain until deletion requested
- Analytics: Aggregate after 1 year, delete raw data
WordPress Privacy Tools Integration
Customer History integrates with WordPress privacy features:
Personal Data Export
- Go to Tools → Export Personal Data
- Enter customer email
- Click Send Request
- WordPress emails customer with download link
- Export includes Customer History data
Personal Data Erasure
- Go to Tools → Erase Personal Data
- Enter customer email
- Click Send Request
- Confirm erasure after customer approval
- Customer History data deleted
Audit Logs
Maintain compliance records:
- Customer History logs all data access
- Records export requests
- Logs deletion requests
- Tracks consent changes
- View in Settings → Privacy → Audit Log
Data Processing Agreement
Customer History stores all data on YOUR server. We (PureDevs) never process or access your customer data. Therefore, no Data Processing Agreement is required between you and us. You are the data controller.
Security Measures
Protecting data (Article 32):
- Access control: Only admins and shop managers
- Database security: Uses WordPress security
- No external transmission: Data stays on your server
- Regular updates: Security patches provided
- Your responsibility: Keep WordPress, plugins, and server secure
GDPR Compliance Checklist
- ☐ Update privacy policy to mention tracking
- ☐ Determine legal basis for processing
- ☐ Implement consent banner (if using consent)
- ☐ Enable IP anonymization (recommended)
- ☐ Set data retention periods
- ☐ Test data export functionality
- ☐ Test data deletion functionality
- ☐ Document legitimate interest assessment (if applicable)
- ☐ Train staff on handling data requests
- ☐ Create process for responding to requests within 30 days
- ☐ Review and update annually
Other Privacy Laws
Customer History helps with:
CCPA (California)
- Right to know what data collected
- Right to deletion
- Right to opt-out
- Same tools as GDPR apply
LGPD (Brazil)
- Similar to GDPR
- Same compliance features work
PIPEDA (Canada)
- Consent and access rights
- Tools provided for compliance
Getting Legal Advice
This guide provides technical information on GDPR compliance features. It is NOT legal advice. Consult a qualified attorney to ensure your specific implementation meets all legal requirements. PureDevs is not a law firm and cannot provide legal advice.
Was this article helpful?
Help us improve our documentation by providing feedback