Privacy Policy - Zero-Log Network Diagnostic Engine
Transparent, GDPR and CCPA compliant disclosure of our zero-log ephemeral socket probing engine, transient RAM buffering, and client-side history storage.
onmyport.com is architected from the ground up as a stateless network utility. We do not maintain databases of visitor IP addresses, we do not log destination targets or probed port numbers, and we never sell, monetize, or share network telemetry with third-party data brokers.
1. The Technical Reality of Ephemeral Socket Probing
When you submit a single-port or multi-port reachability test, our edge servers open an ephemeral raw TCP socket connection using Node.js's low-level node:net socket API directly to the target IP address and designated port number.
- The destination IP address and port number reside strictly in volatile system memory (RAM).
- The probe executes a standard TCP 3-way handshake (
SYN→SYN-ACKorRST) with a strict 2000ms timeout. - Once the handshake concludes or times out, the socket is immediately terminated with
socket.destroy()and purged by memory garbage collection. - No record of the destination host, IP, or scan result is ever written to server disk or database storage.
2. Client-Side Scan History (Browser LocalStorage)
The “Recent Scans” history drawer displayed on the scanner interface operates exclusively within your personal browser using the HTML5 localStorage API.
- Zero Server Synchronization: Recent scan records are never transmitted, synchronized, or visible to onmyport.com backend infrastructure.
- User Sovereignty: You can permanently purge your scan history at any time by clicking the “Clear All History” button or wiping your browser cookies and site data.
- Automatic Storage Cap: History storage is capped at 30 items with automatic FIFO (First-In, First-Out) pruning to prevent browser quota bloat.
3. Automated IP Detection & Transient Rate Limiting
When your browser requests onmyport.com, our server receives standard HTTP transport headers provided by reverse proxies and CDNs (specifically cf-connecting-ip, x-real-ip, and x-forwarded-for). We process this incoming IP address strictly for two essential functional purposes:
- Form Pre-Population: Pre-filling the “Remote Target” input field during Server-Side Rendering (SSR) so you can verify your own network with a single click without layout shift.
- Sliding-Window Anti-Abuse Bucketing: Tracking request frequency inside transient, in-memory rate-limiting counters. These counters prevent malicious actors from utilizing our infrastructure to conduct distributed denial-of-service (DDoS) attacks or automated brute-force scans. Buckets automatically reset and expire from volatile RAM within 60 seconds.
4. Edge Infrastructure, Cookies, & CDNs
We deliver onmyport.com through global Content Delivery Networks (including Cloudflare) to ensure sub-second global probe execution, DDoS scrubbing, and TLS/HTTPS transport encryption.
Cookie Policy: onmyport.com does not set third-party tracking cookies, user profiling cookies, or marketing trackers. The only browser-persisted state is a single functional preference token (onmyport-theme: 'light' | 'dark') stored in your browser's localStorage to maintain your theme preference across page visits.
5. User Rights Under GDPR, CCPA, & Global Privacy Frameworks
Under the General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA/CPRA), internet users possess fundamental rights regarding their personal data, including the right to know, access, correct, and request deletion of personal information.
Because onmyport.com operates an immutable zero-log architecture—retaining no database of visitor IPs, no user accounts, and no logging of diagnostic scans—we possess no personal data records or search histories to disclose, rectify, export, or delete. Your activity remains ephemeral and anonymous.
6. Contact & Privacy Inquiries
For privacy questions, compliance requests, or inquiries regarding our data handling practices, please contact our administrative team at: