Privacy Policy | NetDiag.dev

Last updated: January 2, 2026

TL;DR

We minimize data collection – we only collect information that we need to provide the NetDiag service or communicate with you. If you don't create an account, we only collect basic technical data (like IP addresses) as needed for service operation.
We do not sell your data. We only share your information with third parties when necessary to operate the service (for example, our payment processor or infrastructure providers) and for lawful reasons.
You control your data. If you sign up, you can request deletion of your account and data at any time, and we'll remove your personal info from our systems (with limited exceptions like backups). We also don't send any spam or marketing emails – only essential service-related messages.
We use privacy-focused services. For instance, Paddle handles all billing (we don't see your credit card details) and Plausible Analytics tracks our website usage without cookies or personal data. We strive to comply with reasonable privacy practices (though we are not currently undergoing formal GDPR/CCPA certification). If you have any questions or concerns about your data, you can always contact us.

Your privacy is important to us. This Privacy Policy explains what information we collect when you use NetDiag.dev ("NetDiag" or "the Service"), why we collect it, how we use it, and how we handle it. It also outlines your choices regarding your information. By using NetDiag, you agree to the collection and use of information in accordance with this Policy.

(If you do not agree with this Policy, please do not use the Service. We may update this Policy from time to time – see "Changes" below.)

Information We Collect

We collect only the minimum information necessary to operate and improve the Service. This information falls into a few categories:

Account Information

If you choose to create an account, we collect some basic details from you:

Email Address – used as your login identifier and for sending essential notices.
Password – if you register directly (not via an OAuth provider), we ask you to set a password. This is stored in hashed form (we never store plain-text passwords).

These pieces of information are required to create and operate your account (they allow you to authenticate and receive information). We might also generate an API Key linked to your account for authentication to the NetDiag API; the API key should be kept secret as it grants access to your account's capabilities.

Please note: If we later offer alternative login methods (like OAuth), we might collect equivalent info (such as your name or username from the OAuth provider) as needed.

Payment Information

If you upgrade to a paid subscription, we (through our payment provider) will collect billing information. NetDiag itself does not collect or store your sensitive financial details. For example, when you enter credit card or payment details, that information goes directly to Paddle, our payment processor. We do not see or keep your full credit card number or billing address – those are handled securely by Paddle.

NetDiag may store a record of your transaction such as an invoice ID, subscription status, and your country (for tax calculations), as provided by Paddle. We may also collect your name and business information if needed for invoicing (e.g., if you request an invoice with your company name or VAT ID), but this is generally optional and only for billing purposes.

Usage Data (Automatically Collected)

Like most online services, we automatically collect certain technical information about your use of NetDiag:

Server and API Logs: When you interact with our API or website, our servers record data such as your IP address, the endpoint or URL requested, your user agent (browser or client type), and the date and time of the request. We use this information for operational purposes – for example, to monitor performance, prevent abuse (rate limiting by IP or API key), troubleshoot issues, and gather aggregate statistics (like total requests per day). These logs typically do not include any content of your diagnostic queries (see Diagnostics Data below) beyond parameters needed to run them.
Website Analytics: We use Plausible Analytics on our landing website (NetDiag.dev) to collect anonymized visitor statistics. Plausible is a privacy-friendly analytics tool – it does not use cookies and does not collect personal identifying information. It tracks basic metrics like page views, referrer, browser, and country (by anonymizing your IP) in aggregate form. This helps us understand overall traffic and improve the site. (For example, we can see how many people visited the docs page, but not who they are.)
Cookies: NetDiag's web UI currently does not use any tracking cookies. If you create an account and log in via a web interface in the future, we may use a simple session cookie to keep you logged in during your visit. Such a cookie would contain only a session ID or token (no personal info) and would be temporary. Aside from that, we don't set any cookies for analytics (Plausible needs none) or advertising (we don't run ads).

Diagnostics Data

NetDiag is a network diagnostic service – you send us a request (for example, to ping a server or resolve a DNS query) and we return the results. By design, we do not store the content of these diagnostic results on our servers permanently. When you perform a check, the necessary data (target hostname/IP, etc.) is used transiently to execute the test and produce a result, then the result is sent back to you and not logged beyond short-term buffers or caches.

Example: If you call our API to ping example.com, our servers run that ping and return the latency results. We might keep a brief log that "API key X pinged example.com at 12:00 and got a result OK" for debugging or rate limiting, but the detailed results are not saved into a database.

Future Storage: In the current MVP, we do not provide a feature to save or review past diagnostic results on our side. If in the future we introduce a feature (e.g., a history of your last X checks, or persistent monitoring data), we will update this Policy. Any stored diagnostic results would be treated as your data: kept private to your account unless you choose to share them, and handled with the same care as other personal data.

In summary, if you don't sign up, we know very little about you (only technical data like IP and browser info, which isn't linked to your identity). If you do sign up, we know your email and whatever info you provide, plus some internal identifiers like your API key and usage logs. We purposely avoid collecting extraneous personal details.

How We Use Your Information

We use the collected information for the following purposes:

To Provide the Service: We use account and authentication information to log you in and let you use the NetDiag API. For example, your email and password (or API key) allow you to access your account and make authorized requests. We use your submitted diagnostic parameters (like the domain/IP you want to check) to perform the network checks and return results. Essentially, all the data we collect exists to enable you to use NetDiag as intended.
To Enforce Usage Limits and Ensure Quality: We utilize usage data (like request counts and IP addresses) to enforce rate limits and prevent abuse of the Service. This helps ensure that one user's heavy usage doesn't degrade the experience for others, and protects the Service from malicious activity. We also monitor logs to detect outages, bugs, or errors so we can fix them and keep NetDiag running smoothly.
To Communicate with You: If you sign up with an email, we may use that email address to send you important notices. This includes things like a welcome email, password reset emails, billing receipts or alerts (for paid users), and important announcements about the Service (for example, changes to these terms or privacy policy, incident reports, or planned maintenance). We do not send marketing or promotional emails unrelated to the Service without your consent. In fact, currently we have no newsletter or advertisement mailing list – so any email you get from us will be about your account or usage. We may also respond to you via email if you reach out for support or with a question.
For Billing and Account Management: If you are a paid user, we use information provided via Paddle (such as your subscription status and payment history) to manage your paid account. This might include sending you reminders about upcoming renewals, confirmation of successful payments, or follow-ups if a payment fails. Financial details like VAT numbers (if you provide them) are used on invoices but not for other purposes.
To Improve and Develop the Service: We may use aggregated, anonymized data to understand how people are using NetDiag. For example, we might look at overall metrics like "total checks performed per day" or which features/endpoints are most popular. This helps us identify what to improve or prioritize. None of this analysis identifies individual users – it's all statistical. Similarly, feedback you provide (like bug reports or feature suggestions) may be used to enhance NetDiag.
Security and Fraud Prevention: Information such as IP addresses, usage patterns, and other log data may be used to detect and prevent fraudulent, harmful, or unauthorized use of the Service. For instance, if we notice an account making an unusually high number of requests or other suspicious behavior, we might investigate using the logs, and take action such as throttling or suspension (per our Terms of Service). We also keep an eye on login attempts to detect brute force attacks or other security issues.
Legal Compliance: We may process your information as needed to comply with legal obligations. For example, keeping transaction records for accounting and tax purposes (required by law if we are selling services), or using your data to comply with lawful requests (see How We Share Information below). If you exercise data rights (like a deletion request), we will use your info to fulfill those requests as required by applicable privacy laws.

We do not use personal data for any kind of automated profiling or decision-making that has legal or significant effects on you. Any use beyond the above would either be described in this Policy or be subject to your consent.

How We Share Your Information

NetDiag respects your privacy, and we do not sell or rent your personal information to third parties. We share information only in a few specific circumstances, detailed below:

Third-Party Service Providers (Subprocessors)

We rely on a handful of trusted external services to operate NetDiag. We share data with them only to the extent necessary for them to perform their functions. These providers include:

Paddle (Payment Processor): When you make a purchase, your billing information is handled by Paddle. Paddle will receive data like your name, email, and payment details in order to process the transaction. They may also handle subscription management (e.g., recurring billing) and send you receipts on our behalf. We share with Paddle the minimum info needed (and Paddle in turn provides us information like whether a payment was successful, subscription status, etc.).
Cloud Hosting and Infrastructure: NetDiag's API servers are hosted on Hetzner data centers (currently in multiple regions). This means any data you send to the API (including possibly personal data like your IP address or any domain names you test) will pass through and be processed on Hetzner's servers. Similarly, our static website is delivered via Cloudflare CDN, which as a content delivery network will handle your HTTP requests and IP for the purpose of serving the site quickly. These providers are essentially extensions of our infrastructure – they are not allowed to use your data for anything outside the scope of providing services to us.
Email Service (if applicable): If we use a third-party email service (such as SendGrid, Mailgun, or similar) to send out emails (for verification, support, etc.), then your email address and the content of the email would pass through that service. We would choose a reputable provider and only use it to send communications you are entitled to receive. (At present, we haven't integrated a dedicated email-sending service; we may simply use our own SMTP or a basic service for transactional emails.)
Analytics: As noted, we use Plausible Analytics for website stats. Plausible will process visitor data (IP address, user agent) in real-time to give us aggregated stats, but it does not store any personal data about visitors. We have configured Plausible in accordance with their standard data policy (which is GDPR-compliant and does not track individuals).
Others: There may be other subprocessors in the future (for example, if we add an SMS alert feature, we'd use an SMS gateway, which would then handle phone numbers). We will maintain a list of the significant subprocessors in this Policy or on our website. All such providers are vetted for strong privacy practices. We require that our service providers only use your data as instructed by NetDiag, and not for their own purposes.

Employees and Contractors

NetDiag is a small operation, but if any team members or contractors are working with us, they might have limited access to your information only as needed to perform their work. For example, if you open a support ticket that requires debugging an issue, a developer might look at log entries related to your account. All persons who have access to personal data are bound by confidentiality and this Privacy Policy. There is no scenario where an employee would access your data out of curiosity or for non-service reasons.

Legal Requirements

We may disclose your information if required to do so by law or in response to a valid legal request from authorities (such as a subpoena, court order, or government demand). We will only share the data specifically demanded, and each request is reviewed to ensure it has appropriate authority. Unless legally prohibited, we would try to inform you if your data is subject to such a request.

Protection of Rights and Safety

We may disclose information when we believe it's necessary to prevent harm or fraud and to protect the rights, property, or safety of NetDiag, our users, or the public. For example, if we detect that someone is attempting to abuse our service to attack another party, we might report details to law enforcement or to the affected network. Likewise, if a user's actions on NetDiag are causing a security incident, we may share relevant data with parties who can help address it (such as affected ISPs or security researchers), but only as appropriate. We would only do this in good faith belief that it's reasonably necessary and legal to do so.

Business Transfers

If in the future NetDiag or its assets are acquired by or merged with another company, or if we undergo a reorganization, user information could be transferred as part of that deal. For instance, if NetDiag (currently a project) becomes part of a larger company, your data would likely be one of the assets transferred to the new owner. In such events, we will ensure that your information remains protected by this Privacy Policy (the new owner will be bound to the same terms for existing data, unless you consent otherwise). We will notify users of any ownership change and any choices you may have regarding your data in that event.

With Your Consent

In cases where you explicitly consent or request it, we may share your information. We will not share your personal information with any third party for purposes outside of this policy unless you give us explicit permission. For example, if you asked us to integrate with a third-party service and to send certain data to them, or if you participate in a joint program where you ask us to share data with another company, we would do so only with your clear understanding. Such consent can be revoked by you at any time, and we will stop the future sharing.

Aggregated or De-Identified Data

We may share information that has been aggregated or anonymized so that it cannot reasonably be used to identify you. For instance, we might publish statistics like "NetDiag performed 1 million checks this month" or "30% of requests in the last year were DNS lookups" – these insights contain no personal details. We might also share general usage trends publicly or with partners (e.g., showcasing global average ping times, etc.), but nothing that could tie data to specific users or individuals.

To summarize: your personal data stays mostly with us. The external parties that do get some of it (like Paddle or Cloudflare) need it to provide the underlying service (payment processing, content delivery) and have privacy obligations to protect it. We don't give out your information for marketing or unrelated purposes. And when in doubt, we err on the side of not sharing.

Data Retention

We retain different types of data for different lengths of time, based on necessity and legal obligations:

Account Data: For active users, we retain your account information (email, hashed password, API keys, etc.) as long as your account exists. If you delete your account, we will promptly delete or anonymize the personal data associated with your account from our primary databases.

Example: If you delete your account on our website, your email and any other identifying info will be erased from our user database, and your API key will be revoked. We may keep a non-identifying internal identifier solely to record that an account was deleted (for instance, to avoid re-issuing trial benefits), but that record will not contain personal info.
Diagnostic Data: Currently, since we do not store diagnostic results permanently, there is nothing long-term to delete here. Any transient diagnostic data is only in memory or short-term logs (see below). If in the future we allow saving diagnostic history, we will by default retain that data until you delete it or delete your account. We might offer in-app controls to clear specific results. We might also implement automatic pruning for very old data to manage storage, but that will be communicated if so.
Server & API Logs: Our logs that include IP addresses and request details are kept for a limited duration. We aim to keep logs only as long as necessary for debugging, security monitoring, and usage analysis, then automatically delete or anonymize them. In practice, low-level logs (with IPs) are typically kept for a short period (such as 30 days or less). Aggregate statistics derived from those logs (which contain no personal identifiers) may be kept longer. We periodically review our retention settings to ensure we're not retaining identifiable logs longer than needed.
Analytics Data: The analytics data from Plausible is aggregate and contains no personal identifiers. Plausible itself doesn't store raw personal data like full IP addresses (it discards or hashes them) and only keeps aggregate metrics. Therefore, there's no personal analytics data of yours for us to purge – it's always anonymous. We have access to historical analytics (e.g., page view counts over time) but again, nothing that identifies individuals.
Backups: We perform backups of our databases and systems to ensure reliability. These backups may contain your personal data (since they are snapshots of our system at given times). Backup files are securely stored and are only accessible to the team for disaster recovery. Backup retention time is limited; for example, we might keep daily backups for X days and weekly backups for Y weeks before deletion on a rolling basis. If you delete your account or data, that deletion will be reflected in our live database immediately, and within a short period your data will also disappear from backups once those backups age out. (In many cases, this will be within a few weeks or sooner.) We do not use old backups to retrieve deleted user data except in rare cases of accidental deletion or disaster recovery, and even then we would attempt to honor any deletions post-recovery.
Legal Requirements and Disputes: In certain cases, we might need to retain information for longer periods to comply with legal obligations or if reasonably needed for legitimate business interests, such as resolving disputes or enforcing our agreements. For example, financial records (invoices, transaction logs) may be kept for the duration required by tax law (commonly several years). If we are involved in a legal dispute or receive a legal order, we might retain specific information relevant to that issue until it is resolved, even if it surpasses normal retention periods.
Inactive Accounts: If an account remains completely inactive for a very long time (e.g., no logins or usage for a few years) and is not on a paid plan, we might remove the account and its data as part of routine cleanup. We would likely send an email warning to the registered address before doing this. This policy (if implemented) would serve to reduce stored data and free up unused resources. As of now, we have not set a fixed inactivity period for deletion (common practice might be something like 2-3 years of inactivity). We will update this section if we formalize an inactivity deletion rule.

When we delete data, we aim to ensure it is securely removed or anonymized in a way that it cannot be recovered or linked back to you. For instance, deletion might involve removing entries from databases and overwriting or encrypting personal identifiers. Keep in mind that while deletion from active systems is prompt, complete removal from all backups and caches might take a short time (but no more than a reasonable period, as stated above, typically not more than a few weeks).

Security

We take the security of your data seriously and implement industry-standard measures to protect it:

Encryption: Wherever possible, we use encryption to protect data. All communication between your device and NetDiag (website and API) is encrypted via HTTPS/TLS. Sensitive data at rest (like passwords, which are hashed, and any secret keys) is stored in encrypted form. For any stored diagnostic data (if and when we have it), we would also consider encryption if appropriate.
Access Controls: Access to personal data is limited to the people who need it to operate or support the service. For example, our operational team or admin interface can only be accessed by authorized personnel using strong authentication. We follow the principle of least privilege – even within our team, not everyone can access all data. Administrative access to servers and databases is protected by SSH keys, VPNs, and/or multi-factor authentication.
Security Practices: We keep our software and dependencies up-to-date with security patches. We configure our servers and network with best practices (firewalls, minimal open ports, etc.). We also utilize cloud security features (like Cloudflare's protection against DDoS attacks) to guard against common threats. Regular audits of logs and monitoring help us detect unusual activity.
Testing and Improvements: During development, we consider security implications of new features. We may run vulnerability scans or use tools to identify common vulnerabilities. If we discover any security issue, we act swiftly to patch it. We also welcome reports of potential vulnerabilities (you can contact us if you believe you've found a security flaw – although we don't have a formal bug bounty, we appreciate the help and will address valid reports).
No 100% Guarantee: Despite our efforts, no method of online data transmission or storage is completely secure. We cannot guarantee absolute security of your information. However, we will absolutely do our best to protect it and will notify you of any significant breach of your personal data in line with applicable laws.
Data Location: As noted, our servers are mainly in reputable data centers (Hetzner in Germany and other locales). These facilities have their own robust physical and network security. We entrust your data to these providers under strict contractual terms that they will safeguard it.
Employee Training: Though we are a small team, we are mindful of security in our operations. Team members handling user data are instructed on confidentiality and best practices (for instance, not transferring data to any local devices without proper encryption, etc.).
Incident Response: We have procedures in place to address potential data breaches. This includes identifying and fixing the root cause, notifying affected users and authorities as required, and taking steps to prevent future incidents.

In short, we apply appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. If you have specific questions about security, feel free to reach out.

International Data Transfers

NetDiag is a distributed service – by design, we have servers in multiple regions to perform network checks from different locations. Additionally, our infrastructure and third-party services may be located in various countries. Here's what that means for your data:

Data Locations: Our primary servers are currently in the European Union (e.g., Germany) and possibly other regions (the architecture includes servers in the US and Asia for multi-region diagnostics). The static site is delivered through Cloudflare's global CDN, which means your HTTP requests might be served by a server near you (which could be in any country). In short, your data may be transferred to or through countries other than your own as part of using NetDiag.
If You're in the EEA or Similar Regions: If you are located in a jurisdiction like the European Economic Area (EEA) with strict data protection laws, please note that your personal data (like account info, or IP address in logs) might be processed outside of that area. For example, if our main database is in the EU but you use an API server that's in the US, some data transit to the US is inevitable. We take steps to ensure lawful transfers: we rely on reputable providers and standard contractual clauses or equivalent safeguards where applicable. Hetzner (our host) and Cloudflare are both GDPR-compliant companies. Paddle (for payments) is based in the UK, which as of the last update provides data protection deemed adequate relative to the EU. We also limit what data actually flows across regions (for instance, internal service communication is kept secure).
Your Consent to Transfer: By using NetDiag, you consent to have your information transferred and processed in servers which may be outside your home country. We will handle your data according to this Privacy Policy no matter where it is processed.
External Services and Their Regions: Paddle may process payments using servers in various regions (UK, US, etc.), but as a user you'll interact through their secure checkout. Cloudflare might route your data globally as part of its CDN and security services. Plausible Analytics is an EU-based service (hosted in EU data centers), meaning analytics data stays in the EU. By aligning with privacy-focused providers, we aim to keep much of the data within privacy-friendly jurisdictions when feasible.
Legal Requests Across Borders: In the event we receive a legal request from a foreign law enforcement agency, we will carefully review it. Unless we determine that we are legally compelled and it's a valid request via a mutual legal assistance treaty or similar framework, we would not honor requests that conflict with the laws of the country in which the data is stored. For instance, if all your data is in the EU, a request from a non-EU government would have to go through proper EU legal channels. We stand by the principle of protecting user privacy across borders as allowed by law.
Ongoing Compliance: We monitor developments in data transfer regulations. If needed, we will update our practices (and this Policy) to ensure continued compliance (for example, adapting to new standard contractual clauses or data protection agreements as laws evolve).

In summary, no matter where your data travels, we apply the same privacy safeguards described in this Policy. We understand that cross-border data flow is a concern for many, so we're transparent about it and strive to minimize unnecessary exposure.

Your Rights and Choices

Depending on your location and applicable law, you may have certain rights regarding your personal data. Regardless, we want to make sure you have control over your information. Here are the measures in place:

Access & Correction: You have the right to access the personal data we hold about you. Most of your basic info (like your email) is visible in your account profile (if a profile interface is provided). If you need a full export of your data, contact us and we can provide a summary of what we have. If any of your information is inaccurate or outdated, you have the ability to correct it (for example, you can update your email if we implement that in account settings, or you can contact support for help). We'll be happy to correct any inaccuracies.
Data Portability: In line with laws like GDPR, you can request a copy of the data you've provided to us, in a common format. For now, since we store minimal data, this might simply be a JSON or text report containing your account info, usage stats, etc. We will provide this within a reasonable timeframe upon request.
Deletion (Right to be Forgotten): You have the right to request deletion of your personal data. As noted, you can delete your account at any time (if self-service deletion is available) or request that we delete it for you. Once deleted, your login will be disabled and personal data removed from live systems. We will also ensure that your data is erased from any downstream systems and will cease further processing. (Do note that a deleted account means you won't be able to use features that require login, unless you create a new account in the future.) We might retain certain minimal information after deletion if necessary (e.g., to note that an email was associated with a former account, for fraud prevention or to respect prior opt-out decisions), but we will anonymize it.
Consent Withdrawal: In cases where we rely on your consent to process data (for example, if we ever ask your consent for a new use of data), you have the right to withdraw that consent at any time. For instance, if you agreed to receive a newsletter (we currently don't have one), you could unsubscribe via an opt-out link or by contacting us. Withdrawal of consent doesn't affect processing already done, but we will cease the relevant processing going forward.
Opt-Out of Communications: As mentioned, we don't send marketing emails. If that changes and we start a newsletter or similar, we will only send it with opt-in consent, and you will have the ability to opt out easily (via an "unsubscribe" link or through your account preferences). For essential service emails (like billing or security alerts), you generally cannot opt out because those are necessary for us to communicate important information to you. However, we promise to keep those to a minimum. And again, no spam – we hate it as much as you do.
Do Not Track Signals: Currently, our website does not use tracking cookies or personalized ads, so we don't alter our behavior based on "Do Not Track" (DNT) browser signals. However, since we already refrain from cross-site tracking, our service is effectively privacy-friendly by default. DNT signals may be more relevant if we had third-party trackers, which we do not.
Restriction of Processing: In certain circumstances (for example, if you contest the accuracy of your data or the lawfulness of processing), you can ask us to limit processing of your data. This is kind of a temporary pause on processing. We will evaluate such requests and comply if applicable – though note if you ask us to restrict processing extensively, it might require us to deactivate your account while the restriction is in place (because we cannot provide the service without processing data).
Objection to Processing: If we ever were to process your data for direct marketing (we currently do not), you have the right to object and we would stop. You might also have the right to object if we were processing your data based on legitimate interests and you have a specific personal situation that makes you want to object. We will review objections and comply as required by law.
Automated Decision-Making: NetDiag does not make any significant decisions about you using algorithms or automated profiling. There is no credit scoring, job application filtering, or such happening here. If that changes, we will let you know and you'd have rights to human review of decisions.
Children's Privacy: NetDiag is a developer-oriented tool and is not intended for children under 13 (or the applicable age of digital consent in your region, if higher). We do not knowingly collect personal information from children. If you are under 13, please do not use our Service or provide any personal data. If we learn that we have collected personal data from a child under 13, we will promptly delete it. Parents or guardians: if you believe your child under 13 has provided personal information to us, please contact us and we will take steps to remove such information.
California "Shine the Light" (if applicable): We do not share personal information with third parties for their direct marketing purposes. If you're a California resident, this means we have nothing to disclose under that rule.
Privacy Authority Contact: While we are not formally established in the EU, if GDPR or similar laws apply, you have the right to lodge a complaint with a data protection authority (DPA) in your country. We prefer you contact us first so we can address your concerns, but it's your right to reach out to an authority if you believe we've violated any privacy law.

To exercise any of your rights or ask questions, you can contact us (see Contact Us below). We may need to verify your identity before fulfilling certain requests (for example, to ensure that the person asking for data deletion is indeed the account owner). We will respond to your request within a reasonable timeframe and in accordance with applicable law. Typically, we aim to get back within a few days, and resolve the request within 30 days. If for some reason we need more time, we'll inform you of the reason and extension.

We will not discriminate against you for exercising any of these rights. Our goal is to be transparent and helpful with regard to your privacy.

Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make changes, we will:

Post the Updated Policy: The latest version of the Privacy Policy will always be available on our website (likely on this very page). We will update the "Last updated" date at the top so you can see when the last changes occurred.
Notify You of Material Changes: If we make any material changes (i.e., changes that significantly affect how your data is used or your rights), we will provide a prominent notice. This might be through an email to the address associated with your account and/or a pop-up or banner on our site. For example, if we were to start collecting additional personal data or using it in new ways not covered here, we would inform you.
Your Review: We encourage you to periodically review this Privacy Policy to stay informed about how we are protecting your information. If you continue to use NetDiag after a revised Privacy Policy has become effective, it will signify your acceptance of the updated terms (unless otherwise required by law – for instance, we would explicitly seek your consent for new uses of data if needed).

If you do not agree with any updates to the Policy, you should stop using the Service and you may request that your data be deleted. We'll honor such requests as described above.

In summary, no surprises – we won't materially change how we handle your data without letting you know. If the project evolves, we'll update these terms so you're always aware of what's happening.

Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please reach out to us. We're here to help.

Contact Email: [email protected]

(You can also contact us at this email for any security reports or other inquiries related to privacy and terms. Since NetDiag is a small, developer-focused service, email is our primary contact method. We will do our best to respond in a timely manner.)

By using NetDiag.dev, you acknowledge that you have read this Privacy Policy and understood how we collect and manage your information. We appreciate your trust and are committed to keeping your data safe and your privacy respected.