Privacy Policy

Last updated: August 8, 2026

Note on legal status: This product is operated by an individual who has not yet registered a legal entity. No company name, registered address, or jurisdiction has been established. This privacy policy describes the technical data practices of the tool as it currently operates. When a legal entity is registered, this policy will be updated with the entity name and contact information.

What data we collect

Portpeek does not collect, store, or transmit any personal data. The tool is entirely stateless:

Hostnames and ports that you enter are sent to the server as a single HTTP POST request. The server processes the request, returns the results, and retains nothing.
No accounts exist. There is no registration, no login, no session, and no cookie-based tracking.
No analytics scripts, cookies, or fingerprinting are used.
No logs of individual checks are kept. The server does not write to any persistent storage.

How we handle data

When you submit a port check, the hostname and port numbers are sent to our server, which opens outbound TCP connections to those ports from our infrastructure. The connection attempt is the entire transaction:

The server receives your request, validates it, opens TCP connections, measures timing, and returns the results as JSON.
No record of the hostname, ports, or results is written to disk or database.
No data is shared with third parties.
No data is used for training, analytics, or any purpose beyond fulfilling the immediate request.

Data retained by the platform

The tool runs on Cloudflare Workers. Cloudflare's infrastructure may retain transient network logs for operational purposes (e.g., request counts, error rates). These logs contain IP addresses and request metadata but are not used or accessible by us for any purpose. Cloudflare's privacy policy governs that data.

Your rights

Because we collect no personal data, there is nothing to access, correct, delete, or export. If you have questions about this policy, you may contact the operator through the repository or deployment channel where you found this tool.

Changes to this policy

If the tool's data practices change — for example, if user accounts or saved history are added — this policy will be updated to describe those changes. The "Last updated" date at the top reflects the most recent revision.