1. Core Philosophy: Zero-Telemetry Guarantee
In an era where modern desktop applications and operating systems routinely collect diagnostic telemetry, user behavior analytics, and metadata, CP Engine is deliberately designed as a local-first, privacy-preserving utility.
We maintain that file management and copy/paste interactions represent the most sensitive layer of your workstation. CP Engine does not track your identity, does not record which files you copy, does not measure how often you paste, does not profile your hardware configuration, and does not operate any analytics or tracking SDKs (including Google Analytics, Mixpanel, Sentry, or Firebase Analytics).
No tracking code, telemetry daemons, or user identification tokens exist in the binary.
Unbuffered memory buffers and IOCP completion queues operate exclusively in local RAM.
No machine fingerprinting or remote advertising IDs are ever created or queried.
2. Clipboard Inspection Boundaries
Because CP Engine hooks into the Windows clipboard subsystem to intercept paste operations, we maintain mathematically strict boundaries regarding what data our hooks touch:
- Strict Format Filtering: CP Engine exclusively queries the clipboard for the
CF_HDROPformat identifier (Standard Windows File Drop Structure). - Text & Password Immunity: Plaintext strings (
CF_TEXT,CF_UNICODETEXT), password manager credentials, cryptographic tokens, bitmap images (CF_BITMAP), and rich HTML markup copied to the clipboard are completely ignored and bypassed. CP Engine never opens, inspects, or logs non-file clipboard formats. - Immediate Handle Release: As soon as file paths are parsed into an active transfer job, the Win32 clipboard handle is immediately closed (
CloseClipboard()), allowing other desktop software unhindered access.
3. Local Unbuffered File Streaming
When transferring files between folders, drives, or network shares, CP Engine employs unbuffered 4MB IOCP kernel streaming. Here is what happens to your files:
Kernel Direct Memory Access (DMA): Data is read in 4,194,304-byte chunks directly from source disk blocks into locked system RAM pages and transferred to destination disk blocks.
No Cloud Mirroring: At no point are your files, documents, archives, or ISOs uploaded to any server, proxy, or cache. CP Engine possesses zero cloud upload capabilities for user files.
No In-Memory Retention: Memory buffers are zeroed out and reclaimed immediately upon I/O packet completion by the Windows kernel manager.
4. Exhaustive Network Request Audit
For total technical transparency, here is the complete, exhaustive list of every outbound network interaction that the CP Engine desktop client can perform:
| Purpose | Destination Endpoint | Protocol | Payload Transmitted |
|---|---|---|---|
| Dynamic OTA Update Check | gphost.eu.cc / cdn.gauravpatil.site | HTTPS (TLS 1.3) | Client User-Agent header (e.g. CP/0.0.1 (Windows NT 10.0; x64)). Zero identifying parameters. |
| Dynamic Binary Payload Download | gphost.eu.cc/raw/cp-* | HTTPS (TLS 1.3) | Standard HTTP GET request for the signed dynamic update archive. Zero telemetry. |
| User File Transfer Operations | NONE (Local Only) | N/A | 0 Bytes transmitted over network. |
5. Local Storage & File System Footprint
CP Engine stores a minimal set of state configuration files in your Windows user profile under %LOCALAPPDATA%\CP:
config.json: Local UI display preferences (e.g., light/dark theme preference, autostart toggle).pending_paste.flag: A transient marker written only during dynamic update hot-swapping to preserve your clipboard copy operation across the restart cycle. This file is deleted immediately after the paste operation commences.updates/: Staging folder holding downloaded dynamic update archives before cryptographic verification and execution.
6. Dynamic Updates & Edge CDN Logs
When CP Engine checks for updates or downloads dynamic patches from our edge CDN (Cloudflare R2 and GPHost infrastructure), the hosting provider records transient HTTP edge request logs (such as connecting IP address, timestamp, and HTTP status code) in accordance with standard web infrastructure logging practices.
These logs are utilized strictly for DDoS mitigation, edge cache optimization, and bandwidth monitoring. Neither Gaurav Patil nor CP Engine ever matches edge IP addresses to specific desktop users or software installations.
7. Third-Party Edge Infrastructure
Our global distribution layer relies on the following enterprise edge hosting providers:
Provides immutable global asset hosting with zero egress fees and automated edge caching across 300+ worldwide point-of-presence datacenters.
Operates the authoritative update manifest verification endpoints with TLS 1.3 encryption and DNSSEC validation.
8. Global Privacy & Regulatory Compliance
Because CP Engine does not collect, process, store, or transmit personal data:
- European Union GDPR (General Data Protection Regulation): CP Engine does not act as a Data Controller or Data Processor under Article 4 of the GDPR, as no personally identifiable information (PII) is gathered.
- California CCPA / CPRA: CP Engine does not collect or sell consumer personal information.
- Children’s Online Privacy Protection Act (COPPA): CP Engine contains zero behavioral tracking or advertising modules and is safe for educational, personal, and enterprise environments without age gating.
9. Data Retention & Complete Software Removal
You retain 100% control over CP Engine on your system. To remove all traces of CP Engine:
- Right-click the CP icon in your Windows System Tray and choose Exit.
- Open Windows Settings > Apps > Installed apps, locate CP, and select Uninstall.
- Optionally delete the local configuration folder at
%LOCALAPPDATA%\CP.
Since no cloud accounts or remote servers maintain records of your machine, uninstallation permanently and completely eliminates CP Engine from your workstation.
10. Security Disclosure & Inquiries
If you believe you have discovered a security vulnerability, unexpected network transmission, or potential flaw in CP Engine’s clipboard isolation, please submit a responsible disclosure report directly to: