Privacy & Data Usage Policy

What our sensors record and publish, what we do with information from website visitors, and the terms for using our Signals.

Last updated March 2026

1. Overview

Dataplane.org NFP is a 501(c)(3) nonprofit that operates a global network of Internet sensors. We provide data, analysis, and statistics to network operators, researchers, and the security community.

This document covers two distinct things: (1) how we handle information related to the operation of this website, and (2) the terms under which our publicly published signal feed data may be used by others.

We have no interest in collecting personal information about website visitors, and we've tried to write this policy in plain language.

The short version

Our sensors record unsolicited traffic sent to them, and we publish Signals built from that traffic. Signals are free for non-commercial use. Commercial use and redistribution need our permission. We don't sell data and we don't run ads.

2. What We Observe and Publish

Our public Signals come from sensors in 65 metro areas that aren't advertised for any service, so any traffic they receive is unsolicited. We also run separate systems for research and measurement, described on our About page.

When unsolicited traffic reaches a sensor, we record details about it: the source address, the protocol, and what the sender tried to do. For some protocols that includes content the sender chose to send us, such as DNS query names, SMTP greetings and sender addresses, or the usernames and passwords tried against our SSH and TELNET sensors.

What we record

  • Source IP address of unsolicited inbound connections
  • Protocol (DNS, SSH, SMTP, SIP, VNC, Telnet, NTP, IPv6, etc.)
  • What the sender tried to do (e.g., a recursive DNS query or an SSH password attempt)
  • Content sent to the sensor when it's part of that activity (e.g., DNS query names or SSH id/password attempts)
  • Time of observation

What we hold back

  • Id/password pairs and DNS type/name pairs seen by only a few sensors are left out of the public Signals. This limits exposure of accidental login attempts and makes it harder for someone to use a Signal to identify our sensors.
  • Some known spoofing patterns are filtered out of some Signals for the same reason.
  • The full data set is available only to authorized researchers and special projects.
Important: Observational Data

Our data is observational. An IP address appearing in a feed means traffic was seen from that address toward our sensors. It does not imply intent, guilt, or that the device owner is responsible. The source may be spoofed, the device may be compromised, or it may be operating as expected for its role (e.g., a legitimate scanner or research host). We publish observation data, not determinations of malicious intent.

The Signals are available at dataplane.org/signals as plain-text files. Most are rebuilt hourly, and each covers the past seven days, so older observations drop off on their own.

3. Website Visitor Data

When you visit dataplane.org, minimal technical information is recorded by our web server in standard access logs: IP address, requested URL, browser user agent, and timestamp. This is standard HTTP server logging, retained for operational purposes (debugging, abuse prevention) and not used for marketing or profiling.

Analytics

We use privacy-respecting, aggregate analytics to understand how the site is used, such as which pages are visited, which feeds are downloaded most, and how users navigate. We do not use Google Analytics or any tracking pixels. We do not set third-party cookies.

Cookies

Dataplane.org does not use tracking cookies. If any cookies are set, they are strictly functional (e.g., session state for interactive tools) and contain no personally identifying information. No advertising cookies are ever used.

Forms and email

If you contact us via email, we retain that correspondence to respond to your inquiry. We do not add you to mailing lists without your explicit opt-in. If you subscribe to our newsletter via Substack, that subscription is governed by Substack's privacy policy.

Donations

Donation processing is handled by third-party payment processors. Dataplane.org does not store payment card information. Donor records are retained as required by nonprofit accounting and tax law.

4. Signal Feed Terms of Use

Signals are free for non-commercial use only, subject to the terms below. The same terms appear at the top of every Signal file.

Non-commercial uses we welcome

  • Academic and non-commercial research, including published work (please cite us)
  • Understanding activity seen on networks you operate
  • Teaching, training, and educational materials

Uses that need our permission

  • Any commercial use, including in products or services (see Commercial Use)
  • Redistributing a Signal, in whole or in part

Uses we ask you to avoid

  • Using Signals to target, harass, or otherwise harm the people or organizations associated with listed addresses
  • Treating a Signal as a block list, or claiming that listed addresses are definitely malicious
  • Mass abuse reports or other automated contact with listed address owners without checking the activity yourself
Informational, not a block list

Telling malicious from benign activity for any single entry is difficult because of NATs, address spoofing, and legitimate Internet research such as surveys. Signals are provided as-is, with no warranty or guarantee of accuracy, and you use them at your own risk.

5. Commercial Use

Signals are free for non-commercial use only. If you want to use them commercially, email first and tell us how you plan to use them.

We recommend a minimum donation of $1,000 (USD) a year from organizations that use Signals in commercial systems. Our nonprofit provides a public benefit, but the work costs money, and covering those costs is part of our responsibility. We think the recommended donation is reasonable and fair.

If you need data the public Signals don't cover, ask. We'll tell you what we can do.

6. Attribution Requirements

We ask that anyone using Dataplane.org data in a product, publication, or service includes attribution. Attribution can be as simple as:

Data sourced from Dataplane.org (https://dataplane.org)

For academic publications, we suggest:

Dataplane.org NFP. "[name] Signal." https://dataplane.org/signals/[name].txt. Accessed [date range].

If you publish findings based on our data, let us know at . We'd like to hear about it.

7. IP Address Delisting

Each Signal covers the past seven days. An address drops off about a week after our sensors last see the activity.

If you believe an IP address is listed in error, or if you represent the operator of a listed address and believe the listing is causing harm, you may contact us at with the subject line "IP Delisting Request." Please include:

  • The IP address(es) in question
  • The specific feed(s) where the address appears
  • Your relationship to the address (operator, ISP, etc.)
  • Why you believe the listing is in error

We'll look into it and reply. Keep in mind that if the activity continues, the address will keep appearing.

Note on compromised devices

If a device you manage was compromised and sending this traffic, fix that first. Once the activity stops, the address will drop off on its own within about a week.

8. Data Retention

Each published Signal covers the past seven days. Once an entry is older than that, it's no longer in the published file.

Published Signals
Past seven days. Most are rebuilt hourly; a few daily.
Raw sensor logs
Kept internally for operations and research. Not public, though the full data set can be made available to authorized researchers.
Website access logs
Standard server logs retained for up to 90 days for operational and abuse purposes.
Email correspondence
Retained for the duration of the relationship or inquiry, then archived for records purposes consistent with nonprofit obligations.
Donation records
Retained as required by U.S. nonprofit tax law (typically 7 years).

9. Third-Party Services

Dataplane.org uses a small number of third-party services to operate. We do not share data with these services beyond what is necessary for operation:

Substack

Our newsletter is hosted on Substack. Subscribers are subject to Substack's privacy policy. We do not share subscriber lists with third parties.

GitHub

We share code on GitHub. Interactions with our GitHub repositories are subject to GitHub's privacy policy.

Payment processors

Donations are processed by third-party payment processors. We do not receive or store payment card data. Donors interacting with payment processors are subject to those processors' privacy policies.

Hosting and infrastructure

Our sensors and servers are hosted with third-party infrastructure providers. We do not share signal data or visitor data with these providers beyond what is necessary for hosting.

10. Policy Changes

We may update this policy from time to time. Material changes will be noted in our newsletter and on this page with an updated "last modified" date. Continued use of our signals or website after a policy change constitutes acceptance of the revised terms.

We don't expect frequent changes.