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: October 3, 2026

What changed: Analytics tools now load only after an exclusion check that lives in your browser (open any page with ?analytics=off, or send a Global Privacy Control signal, and none of them load), and campaign tags are limited to a fixed list; utm_content and utm_term are no longer kept by our own code, while the analytics tools still receive the address of the page you open as part of a page view. The buyer-intent event lists now name every event we fire, including the contact page opened for a demonstration or walkthrough. Earlier: the contact page's message composer is described: it prepares an email in your browser and sends nothing itself. Smart Draft is described as deterministic, with no external AI provider. Mentions of the retired evaluation offers now refer to the private demonstration.

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.

No cross-tenant analytics or benchmarks. We do not run cross-tenant analytics, anonymized benchmarks, or industry-comparison reports across customers. Each agency's records stay inside its own tenant workspace. Operational analytics surfaces (MS4 Metrics, the audit log workspace, IDDE response timelines, and readiness rollups) run on a single tenant's own records. If we ever offer optional cohort benchmarks in the future, they will be tenant opt-in and described in writing before any data leaves a tenant workspace.

No staff surveillance or productivity ranking. NPDESTracker is built for the program, not for surveilling the workforce. We do not provide inspector productivity scores, keystroke logging, location tracking outside the inspection record itself, or staff ranking dashboards. Per-record attribution and timestamps exist for audit purposes; they are not packaged as performance metrics.

Connected ArcGIS content. If your agency connects its ArcGIS organization, a staff member signs in with their own ArcGIS named user account through Esri sign in. We never receive, request, or store an ArcGIS password, and we do not ask your agency for an API key or a shared service account. The long-lived refresh credential is held server side and is never sent to the browser. NPDESTracker reads the maps, layers, and features that account can already see; it performs no writes against your ArcGIS content, so it cannot edit, publish, re-share, or delete it. Content read through the connection stays in your ArcGIS organization and is not copied into NPDESTracker. Files your team chooses to import, such as GeoJSON, shapefile, or CSV, are stored in NPDESTracker, with the original upload retained separately from the browser display layer. Each connection is scoped to one user in one tenant, and removing the application approval or disabling the account in ArcGIS ends what we can read. The full description is on the ArcGIS integration and security page.

Smart Draft data handling. Smart Draft (the assistive drafting feature inside Annual Reporting) is deterministic: it assembles a starting draft from linked evidence using templates inside NPDESTracker. It does not contact an external AI provider, and no customer data is sent to an 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 send us an email or otherwise contact us, we receive the information you choose to share: typically your name, title, agency, email address, and whatever you write in your message. The public website has no form that sends information to us or anyone else. The message composer on the contact page only prepares an email in your browser; you send it from your own email app, or copy it into one. Every contact path on the site, including the demo page, ends in an email to admin@npdestracker.com.

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 demonstration requests. 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 campaign tags, we keep only the campaign source, medium and campaign name, and only when each matches a short fixed list we maintain; anything else is dropped before it is stored, and utm_content and utm_term are never kept. What we keep stays inside your current browser tab (first-party sessionStorage, not a cookie, cleared when you close the tab) and travels with a click through to the application or into an email you send us, so we can see which campaign your interest came from. It is not transmitted to other websites. These limits cover what our own code keeps and forwards: unless analytics is turned off in your browser (see section 04), the analytics tools themselves still receive the address of the page you opened, including any tags in it, as part of a page view.

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 private demonstration or an 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.

Turning analytics off in your browser. Open any page of this site with ?analytics=off and none of the tools above will load in that browser until you open a page with ?analytics=on. The setting is stored in your browser only, as a first-party preference, and is never sent to us. We use it ourselves so our own visits are not counted. A browser that sends a Global Privacy Control signal is treated the same way.

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 demonstration requests. The events we fire are: sample workspace click, pricing page view, security page view, privacy page view, walkthrough request click, demonstration request click, contact page opened for a demonstration or walkthrough, contact email click, and checkout link click. Each event is the name of the action, the page or link it came from, plus, when present, the campaign source, medium and name from the fixed list described above, never the contents of a form, email, or compliance record. These event names are passed to the analytics layers 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 sends a Global Privacy Control signal, this site treats it as the same preference as ?analytics=off: none of the tools above load. This site does not read a Do Not Track signal itself; the analytics tools we use may honor it 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 on the public marketing website. It reports page views, a conversion event when the demo link is clicked, and the named buyer-intent events listed in the cookies-and-analytics section (sample workspace click, pricing page view, security page view, privacy page view, walkthrough request click, demonstration request click, contact page opened for a demonstration or walkthrough, contact email click, and checkout link click). Each event carries only its name, the page or link it came from, and, when present, the campaign source, medium and name from the fixed list described in the cookies-and-analytics section. Google receives those signals 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.
  • Google Fonts. The public website loads the Inter typeface from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). When a page loads, your browser requests the stylesheet and font files directly from Google, which receives the standard request data any web request carries, such as your IP address and user agent. Nothing you type on the site is involved, and we do not use these requests for tracking.
  • Email. When you email us, whether about a private demonstration, an 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.