Privacy Policy

Last updated 10 October 2026

Summary

You can use PacketFlo’s public diagnostic tools without an account. We use the inputs you submit to run those checks, and usage and performance data to understand which tools are useful, fix problems, and make PacketFlo easier and faster to use. Page journey records are separate from accounts and do not contain names, email addresses, or IP addresses.

Connection diagnostics use network information, including IP addresses, to help us understand service reliability. If you choose to sign in, send feedback, or subscribe to an alert, we also process the information needed for that feature. The sections below explain what each feature uses and how long we keep it.

Diagnostic requests

Checks can send a domain, IP address, URL, or other input to PacketFlo and the external systems needed to answer your request, such as DNS resolvers, registries, geolocation providers, and the target server. Some measurements run in your browser. The tools do not provide a saved personal query history, but infrastructure logs, temporary caches, and analytics URLs may contain request information. Please keep secrets and confidential information out of diagnostic inputs and links, and send API keys in the API key header.

Abuse prevention uses your IP address, a session identifier, and usage counters held in memory or an expiring cache, including Upstash when configured. API access also uses key-specific credit counters.

Connection health and reliability

The header connection indicator helps show whether PacketFlo is reachable and how quickly it responds. It periodically contacts PacketFlo so we can identify connection problems and improve reliability. These requests can create database records containing your IP address, approximate location, browser and operating system details, device type, page path, connection status, latency, and observation times. Location can include city or region when supplied by our network provider. Recent observations are grouped by IP address, browser, and operating system so we can review recurring failures in the administrative health dashboard.

Connection checks do not send sign-in cookies. The server still receives the IP address and network information needed to handle the request; IP addresses are stored in connection health records.

Improving navigation

We use page journeys to understand how people move between PacketFlo pages and where navigation could be clearer. When this feature is enabled, PacketFlo records known site page paths, visit order, browser observation times, and server receipt times. A random identifier in session storage groups observations within a browser tab, including reloads; it resets after 30 minutes without an observed page navigation. These records are separate from connection observations and contain no account identifiers, IP addresses, diagnostic inputs, query strings, or fragments. Diagnostic targets in site-down page paths are replaced with a route template.

To understand how people discover PacketFlo, the first recorded page in a session can include a broad traffic-source label, such as Google, Bing, ChatGPT, or another referral. Visits redirected through netsh.io or packetgram.io can also include that former domain as a label. We derive these labels from the browser referrer and recognized source tags, without storing full referring URLs, search terms, or arbitrary campaign values in journey records. When the source is unavailable, it is shown as direct or unknown. These labels are not linked to your account.

Our administrative view shows the pages visited within these randomly identified tab sessions, including the first and most recent page. It does not link a journey to your account or show browsing activity on other websites. Some visits may be missing, and the most recent page does not necessarily indicate where a visit ended.

This feature operates independently of the cookie notice. The collection endpoint receives ordinary request metadata and temporarily uses IP addresses for rate limiting, without adding them to page journey records. Raw visits are eligible for deletion after 30 days; cleanup runs during collection and dashboard access, at most hourly.

Optional feedback and notifications

Result feedback stores the tool name, rating, optional comment, approximate country, and submission time. The feedback record has no account or IP address field, although the request IP is processed to determine country. Do not include personal or confidential information in comments.

Waitlists and SSL expiry alerts store your email address, subscription type, optional domain, signup time, and notification state. We send confirmations, requested product availability notices, and certificate alerts through Resend. Email delivery records store the recipient, message type, and sending time. When an operator notification webhook is configured, signup details are also sent to that destination. Contact us to request removal from a waitlist or alert subscription.

Accounts and API keys

Google sign-in stores your provider account details, name, email, and profile image, along with authentication tokens returned by the provider. Passwordless email sign-in processes your email and verification token. We store login sessions and any display name or profile image you save.

API keys are shown once at creation; the key database stores a SHA-256 hash, identifying prefix, name, owner, and creation, last-use, and revocation times. Revocation disables a key but does not delete its database record. Contact us to request account or associated record deletion.

Cookies and browser storage

PacketFlo currently has no third-party advertising integration. The site uses cookies and browser storage for the following features:

  • Rate limits: The packetflo_sid cookie identifies a tool session and expires 30 days after it is last refreshed. IP-based limits also apply.
  • Cookie notice: packetflo-consent stores acknowledgment in a cookie for up to one year and in local storage until cleared. The cookie is sent with applicable requests. The footer Cookies link reopens the notice; acknowledgment does not switch analytics or connection telemetry on or off.
  • Sign-in: Auth.js cookies support sessions, sign-in redirects, and authentication security checks. Names may include a secure prefix on HTTPS.
  • Display preferences: Local and session storage remember the theme and selected homepage, guide, and tool promotion content. Storage duration varies by feature.
  • Page navigation: When enabled, packetflo-page-session in session storage holds a random session identifier, navigation sequence, and last observation time. It is scoped to the browser tab and resets on the next observed navigation after 30 minutes of inactivity. It is not an account identifier.

Usage and performance analytics

Usage analytics help us decide which tools to improve and spot common problems. When enabled in production, Umami collects pageviews and events such as tool usage, broad error categories, and feedback ratings. Our custom tool events describe the tool and outcome, without including the diagnostic inputs you entered. Page performance measurements are sent directly to PacketFlo, not to Umami. Analytics runs independently of the cookie notice. Umami’s tracker does not require analytics cookies.

Umami also receives standard page and browser information, including the URL, referrer, title, language, and screen size, along with network request metadata. Page URLs may include query parameters or fragments, so diagnostic targets included in links may reach Umami even though our custom tool events omit them.

Page performance measurements

We measure loading speed, responsiveness, and visual stability to find slow pages and improve the experience across devices. In production, these records contain the metric and value, a measurement identifier and update sequence, an allowed public entry-page path, a mobile or desktop category, navigation type, and receipt time. We do not store IP addresses, account identifiers, full URLs, or diagnostic inputs in these performance records. The collection endpoint receives request metadata and uses transient IP-based limits to prevent abuse.

Performance requests omit account cookies and run independently of the cookie notice. Raw measurements are eligible for deletion after 30 days. Cleanup runs during collection and dashboard access, at most hourly, and can also run through a scheduled maintenance job. Historical performance events already sent to Umami remain subject to that provider’s retention settings.

Service providers

Data is processed by the providers needed to deliver each feature: hosting and database services, Cloudflare for network delivery and protection, Umami for analytics, Resend for email, Google when you choose Google sign-in, and Upstash when configured for rate limiting. Their processing and retention depend on the service and deployment settings.

Your browser may contact ipify.org to identify IPv4 or IPv6 connectivity. IP geolocation lookups can send the IP being examined to IP2Location; this may be your connection IP or a diagnostic target IP. Other diagnostics query external network services as required by the selected tool.

Retention and deletion

Retention varies by record. Rate-limit caches expire and authentication sessions have expiry times. Administrators can remove connection observations older than a chosen cutoff; the cleanup tool defaults to 60 days since the last observation. This is not a guaranteed automatic 60-day deletion schedule. Account, feedback, subscription, and email records have no general automatic deletion schedule in the application. Infrastructure logs, backups, and analytics have separate provider retention settings.

Your choices and rights

Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a copy of personal data, or to object to or restrict processing. Contact [email protected] for a request relating to your account, subscription, or other records. We may need information to locate the relevant records and verify the request. Clearing browser storage does not delete records already held by PacketFlo or its providers.

Children’s privacy

PacketFlo is an operational technical service intended for network engineers, developers, and system administrators. It is not directed toward children under 13 and does not knowingly collect personal information from children.

Changes to this policy

We may revise this Privacy Policy periodically to reflect infrastructure enhancements or regulatory updates. The revision date at the top of this document indicates when changes were last published.

Contact

For privacy inquiries or data requests, contact us at: [email protected]