Privacy Policy
Last updated: September 2026. Learn how MuchLogin protects operator telemetry, isolates browser profile sandboxes, and guarantees GDPR/CCPA data sovereignty.
1. Sandbox Isolation & Zero Cross-Contamination
Every browser profile runs in a hardware-isolated sandbox with dedicated storage directories, process pools, and canvas render pipelines. We enforce zero data cross-contamination between profiles. Local credentials, session tokens, and noise seeds are encrypted on your local system using AES-256 before disk persistence.
2. Cookie Storage & Session Data Management
Cookies, local storage caches, and IndexedDB state remain strictly segregated per profile sandbox. Automated cookie warming and identity aging robots execute client-side without transmitting browsing history or page payloads to central servers. Operators maintain complete ownership and control of all session cookies.
3. GDPR & CCPA Alignment (Data Subject Rights)
In compliance with the General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA), MuchLogin never sells, rents, or monetizes operator data. You maintain unilateral rights to access, rectify, export in JSON format, or request irreversible deletion of your account and profile records at any time.
4. Payment Processing & Merchant of Record
All financial transactions are handled exclusively by our trusted Merchant of Record, Paddle (Paddle.com Market Ltd). MuchLogin does not ingest, process, or store credit card numbers, CVVs, or sensitive billing details on internal infrastructure. Billing records comply with PCI-DSS Level 1 standards.
5. Data Retention & Erasure Procedure
Telemetry logs are limited to high-level system health metrics and license verification pings, retained for a rolling 30-day window. Profile erasure requests submitted through the operator dashboard or to privacy@muchlogin.com trigger immediate and permanent cryptographic wiping of metadata.