NPDESTracker

Privacy

Privacy policy.

This policy covers both npdestracker.com, the public marketing website, and the NPDESTracker application at app.npdestracker.com. Customer agreements govern the contractual terms of an annual deployment; this page summarizes data handling in plain language.

Last updated: May 29, 2026

Overview

The short version.

If you never submit a form or email us, we know essentially nothing about your visit beyond the basic technical exchange your browser has with our hosting provider to deliver the page.

If you do contact us, we receive what you send, we use it to respond, and we don't sell it, share it, or add you to any marketing list. You can ask us to delete it at any time.

The sections below say the same thing in more detail, plainly and without legal theater. If something is unclear, email admin@npdestracker.com.

01 · Customer data inside the application

Customer data inside the application

This privacy policy covers both the public marketing website at npdestracker.com and the NPDESTracker application at app.npdestracker.com. Wood Technologies LLC operates NPDESTracker. Customer-side data handling inside the application is summarized here for procurement and IT review.

What we hold for customers. When an agency uses the NPDESTracker application, customers create accounts (name, email, role) and enter municipal compliance records (sites, outfalls, BMPs, structures, inspections, IDDE incidents, complaints, tasks, activities, enforcement actions, annual report answers, and attachments uploaded by staff). All customer records are scoped to the customer's tenant.

How we use that data. We use customer data to operate the product (rendering the workspace, running queries, producing the annual report, generating audit trails) and to provide support when a customer requests it. We do not sell customer data. We do not share customer records with advertisers, data brokers, or marketing lists.

Smart Draft and external AI. Smart Draft (the assistive drafting feature inside Annual Reporting) runs in a default deterministic mode that does not contact an external AI provider. An optional external AI mode can be configured per tenant; when enabled, Smart Draft may send a limited, field-whitelisted slice of linked record context to a configured AI provider. The full disclosure is on the Smart Draft page.

What you should not upload. The application is built for municipal compliance records, not for personally sensitive data. Please do not upload Social Security numbers, payment card numbers, health information, or other sensitive personal data into compliance records or attachments.

02 · Information we collect from the marketing website

Information we collect from the marketing website

Information you give us. When you fill out the demo request form on /demo, send us an email, or otherwise contact us, we receive the information you choose to share. Typically that's your name, title, agency, email address, and whatever you write in your message.

Information collected automatically. Like virtually every website, our hosting provider receives basic technical information with each page request, including your IP address, browser type, and the URL you requested. This is used for site delivery, security, and diagnostics.

We use website analytics tools and Google Ads + Microsoft Advertising UET conversion tags to understand how visitors find and use the public site, and to measure which advertising campaigns lead to demo opens, pricing engagement, and pilot inquiries. These tools may receive page views, clicks, scrolling, device and browser information, and approximate location based on IP address. They look at how the public marketing website is used, not at customer compliance records inside the application. We do not sell visitor information.

Campaign source (UTM) tags. If you arrive via a link with UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), we remember those tags inside your current browser tab using first-party sessionStorage and forward them along when you click through to the application or send us an email, so we can see which campaign your interest came from. This is first-party storage only — not a cookie, not transmitted to other websites, and cleared automatically when you close the tab.

03 · How we use information

How we use information

We use the information you provide to respond to your inquiry. If you email us about a pilot or annual deployment, we use your contact details to follow up and coordinate next steps. If you email us with a question, we use your email address to reply.

We do not sell your information. We do not share it with advertisers, data brokers, or marketing lists. We do not use your information for marketing unless you've explicitly asked us to.

04 · Cookies and analytics

Cookies and analytics

The public website uses website analytics tools to understand how visitors find and use the site. Typical signals include page views, clicks, scrolling, device and browser information, approximate location based on IP address, and general site usage. Some of these tools record session activity such as where visitors click or scroll on a page so we can understand which parts of the site are useful and which are confusing.

These tools observe how the public marketing website is used. They do not receive customer compliance records from the application. We do not sell visitor information.

About cookies. Our own site code does not set any cookies. The analytics and ad measurement tools listed above (Microsoft Clarity, Google Ads, Microsoft Advertising UET) load on the public website and may set their own first-party browser cookies as part of standard measurement — for example, to recognize that a session continued across page loads. We do not read those cookies in our own code. You can block these tools through standard browser privacy settings, an ad blocker, or a privacy-focused browser extension, and the site will still work normally.

Buyer-intent events. On the public marketing website we fire a small set of named events so we can see which advertising campaigns and which pages lead to demo opens, pricing engagement, and pilot inquiries. The events we fire are: sample workspace click, pricing page view, security page view, privacy page view, walkthrough request click, pilot inquiry click, contact email click, and checkout link click. Each event is the name of the action plus any UTM tags from the link you arrived on — never the contents of a form, email, or compliance record. These event names are passed to the analytics layers already loaded on the public site (Google Ads, Microsoft Clarity, Microsoft Advertising UET, and Vercel Analytics).

Google Ads conversion tracking. The public website loads a Google Ads tag (AW-18184217672) so we can measure which advertising campaigns lead to the buyer-intent events listed above. The signals Google receives are those event names plus standard request data your browser already sends to any website. We do not upload customer compliance records or visitor lists to Google, and the Google Ads tag is only present on the public marketing website, not inside the application. We do not currently run Google Ads remarketing or audience lists from these events.

If your browser is configured to send a Do Not Track or Global Privacy Control signal, the analytics tools we use may honor those signals according to each provider's own configuration. You can also block analytics and ad scripts through standard browser privacy settings or an ad blocker.

05 · Data sharing and service providers

Data sharing and service providers

Running a website means a small number of service providers receive information incidental to delivering the site:

  • Cloud hosting provider. Our hosting provider receives basic request data (IP address, user agent, URL) required to serve each page. This is standard for every modern website.
  • Website analytics providers. We use Microsoft Clarity and Vercel Analytics on the public marketing website. These providers receive the page-view and behavior signals described in the cookies-and-analytics section and process them on our behalf so we can understand how visitors use the site.
  • Google Ads. We use a Google Ads tag and a single conversion event on the demo CTA so we can measure which advertising campaigns lead to demo opens. Google receives the conversion event and standard browser request data; it does not receive customer compliance records or visitor lists from us.
  • Microsoft Advertising (UET). We use a Microsoft Advertising UET tag on the public marketing website to measure ad conversions and campaign performance on Microsoft and Bing search ads. Microsoft receives page-view signals and conversion events plus standard browser request data; it does not receive customer compliance records or visitor lists from us. The tag is only present on the public marketing website, not inside the application.
  • Email. When you email us, whether about a pilot, annual deployment, or a general question, your message is delivered through standard email infrastructure.

We do not share your information with any other third party for marketing, advertising, or resale.

If we add a form-handling service in the future (for example, to process demo requests server-side rather than via email), we will update this policy and identify the provider.

06 · Data retention

Data retention

Email correspondence is retained in our email system for as long as reasonably necessary to respond, maintain business records, and support future conversations. You can request deletion at any time by emailing us.

Technical server logs are retained by our hosting provider according to their standard retention windows.

07 · Your choices

Your choices

You can ask us to show you the information we have about you, correct anything that's wrong, or delete your information from our records. Email admin@npdestracker.com and we'll take care of it. These rights apply regardless of where you live.

08 · Children's privacy

Children's privacy

NPDESTracker is built for municipal staff and public agencies. The public website is not directed to children under 13, and we do not knowingly collect information from them.

09 · Changes to this policy

Changes to this policy

If this policy changes, we'll update the "Last updated" date at the top and note what changed in a short summary. For material changes, we'll do our best to flag them where visitors can notice, not just quietly update the page.

Contact

Questions about this policy?

If anything here is unclear, or you'd like us to access, correct, or delete information you've shared with us, email us directly.