Privacy Policy
GDPR, CCPA & Data Minimization Commitment
1. Introduction & Privacy Philosophy
At AdShield Pro, we believe security tools should respect user privacy. Unlike cloud analytics platforms that aggregate and sell visitor behavioral datasets, AdShield Pro is built on a Local-First, Zero-Cloud Data Leak model.
2. What Data is Collected by the WordPress Plugin
All traffic analytics, ad click logs, and IP quarantine tables remain 100% inside your own WordPress MySQL database. AdShield Pro's central licensing server never receives your visitors' personally identifiable information (PII).
- Visitor IP Addresses: Stored locally in your WordPress database to compute click frequencies and enforce penalties. IPs older than 30 days are automatically purged.
- Referral Strings: Cleaned and aggregated (e.g. Google, Facebook, YouTube, Direct) without retaining sensitive query params.
- Geo-Location: Derived in-memory from Cloudflare edge headers without calling third-party tracking beacons.
3. What Data is Collected by the Central SaaS Store
When you register for a trial or purchase a license, our central store collects:
- Customer Name & Email Address: Used solely to issue license keys, payment receipts, and security updates.
- Root Domain: Kept to enforce our 1-trial-per-domain anti-abuse policy and validate your Pro activation status.
- Payment Reference ID: Binance Pay or Payoneer transaction hashes. We never store credit card or bank account numbers.
4. GDPR & CCPA Compliance
Publishers have full sovereignty over their visitor records. With 1-click inside the AdShield Pro WordPress dashboard, site administrators can purge logs, unblock IPs, or export their traffic summaries.