Data Protection & Sovereignty
Privacy & Data Processing Policy
Data governance, end-to-end encrypted Cloudflare R2 storage, Stripe payment isolation, and operational privacy protocols governing WPSmooth LLC.
Entity: WPSmooth LLC
Effective: September 2026
Scope: PII, Telemetry & Backups
Storage: Cloudflare R2 & Stripe Isolated
đź”’
Zero-Knowledge Storage & Data Isolation
WPSmooth LLC operates on strict zero-knowledge principles. Customer payment credentials never touch our origin servers, and daily automated backup archives are encrypted end-to-end and streamed directly to Cloudflare R2 under an autonomous 30-day rolling purge cycle.
01
Information Collection & Use
-
•Lead Capture & PII: When you submit your website URL and email address for a vulnerability audit or service inquiry, this personally identifiable information (PII) is securely routed to and stored within Google Workspace and our proprietary, self-hosted client management dashboard.
-
•Scheduling Data: Fit call booking information is processed via our custom website calendar integration and synchronized directly with Google Calendar without third-party data broker exposure.
-
•Website Analytics: We utilize Google Analytics to track visitor interactions, micro-conversions, and overall site performance. This involves standard tracking cookies deployed on frontend interactions to monitor speed and user experience metrics.
02
Payment Processing Infrastructure
-
✓Third-Party Gateway: All financial transactions, recurring monthly retainers, and Custom Remediation Agreements are processed exclusively through Stripe, an accredited PCI-DSS Level 1 service provider.
-
✓Data Isolation: WPSmooth LLC does not process, transmit, or store raw payment data (such as complete credit card numbers or CVV codes) on our own DigitalOcean droplet or database infrastructure. All checkout sessions interface directly via Stripe’s secure API tokens.
03
Managed Service Data Storage & Retention
-
•Backup Cadence: Daily API-triggered backups are streamed directly to Cloudflare R2 object storage infrastructure, preventing local server disk bloat and origin storage exhaustion.
-
•Retention Period: Backup archives are maintained on a strict 30-day rolling retention lifecycle. Upon exceeding the 30-day threshold, older archives are autonomously and permanently purged from the storage bucket.
-
•Internal Client Management: Client configurations and service statuses are managed on an isolated, self-hosted management hub to ensure strict separation of operational data from public-facing assets, without exposing the underlying infrastructure framework.
04
Infrastructure & Data Sovereignty
-
•Global Distribution: Cloudflare R2 storage buckets are distributed across Cloudflare's high-speed edge network, ensuring high availability, fault tolerance, and geo-resilience without single-point-of-failure constraints.
-
•Zero Egress Footprint: The architecture leverages Cloudflare R2 to maintain an ultra-lightweight operational footprint with zero egress penalties during rollback actions.
05
Encryption & Security
-
✓End-to-End Encryption: All backup payloads—including sensitive database contents, WooCommerce customer transactions, and end-user PII—are encrypted end-to-end at rest within Cloudflare R2.
-
✓Data Obfuscation: Automated Antigravity Python scripts and API connections strictly orchestrate the transit and storage of these encrypted payloads without decrypting, reading, or processing the underlying application data.
06
User Rights & Data Control
-
•Access and Erasure: Users maintain the right to request access to, or deletion of, their personal data stored within our marketing or client management systems.
-
•Asynchronous Requests: In alignment with our operational communication protocols, all data requests must be submitted asynchronously via our official support channels. Requests are verified and processed within statutory timelines.
Questions regarding our privacy framework or compliance?
Our technical team is available to review data isolation and encryption specifications.