Skip to content
Opioid Audit

Towns

Every New Jersey town and county, graded on what it certified against what the books show.

State OverviewThe statewide map and the grade for every jurisdiction.RankingsEvery jurisdiction sorted by grade, misreported dollars and records status.
CountiesTwenty one county allocations, each with its towns rolled up.VendorsPayees across every ledger, with the towns that paid them.

Findings

What the record shows, one finding at a time, each traced back to the ledger line and the page it sits on.

All FindingsEvery finding published so far, newest first.Phantom ProgramsA program certified to the State with no matching payment in the books.Surveillance TechnologyLicense plate readers, cameras and subscriptions paid from opioid funds.Police Vehicles and GearVehicles, upfits, body armor and equipment paid from opioid funds.
Zero CertificationA report year certified at zero expended while the books show payments.Fake EncumbrancesAn encumbrance certified to the State with no open commitment in the books.Year-End Salary ReclassSalary moved onto the opioid account by journal entry at fiscal year end.Funding-Source SubstitutionWork previously paid from another fund moved onto the opioid account.

Articles

Reports, videos and notes on what the record shows in one town.

All ArticlesEvery article published so far, newest first.
ReportsThe certification read against the books, town by town.

Data

The rows, the documents and the rules behind every figure this site publishes.

How Grades WorkHow a grade is earned and what each one means.MethodologyHow we match a certification to the books.
DocumentsThe source documents, page by page.

Act

Pages for media, residents and legislators, and tips.

For MediaThe credit line, the brand kit and the documents.For ActivistsWhat to ask a council and which records to request.
For LegislatorsThe oversight record and the open recommendations.TipsSend a document about a town. Contact is optional.
State OverviewRankingsCountiesVendors
All FindingsPhantom ProgramsSurveillance TechnologyPolice Vehicles and GearZero CertificationFake EncumbrancesYear-End Salary ReclassFunding-Source Substitution
All ArticlesReports
How Grades WorkMethodologyDocuments
For MediaFor ActivistsFor LegislatorsTips
  1. Legal/
  2. Privacy policy

Privacy policy

Last updated 2026-10-05

  1. 01What is collected, and who holds it
  2. 02What is not collected
  3. 03Why any of it is collected
  4. 04Analytics, do not track and Global Privacy Control
  5. 05Anti abuse, the honeypot, the form check and the rate limit
  6. 06What happens to what you send
  7. 07How long each thing is kept
  8. 08Who else sees it
  9. 09Your rights, wherever you live
  10. 10Visitors from Europe
  11. 11Children
  12. 12Security
  13. 13People named in public records
  14. 14Changes to this policy
  15. 15Contact

01What is collected, and who holds it

Analytics, held by the analytics service
Visitor analytics through an analytics service, in an account this project holds. Pages viewed, referrer, approximate region, device and browser, and the network a visit comes from. The scripts load after first paint, and they are not loaded at all when an opt out signal is present.
Form submissions, held by the database and file storage provider
What you type into a form, and any file you attach. Rows go to a private table and files go to a private store. Contact details stay in that private table and are never joined to anything public.
Your IP address and device details, held in the private table and the project mailbox
Every submission records your IP address, its hostname and network, the approximate location our host reports, your operating system, browser and version, device type, screen size, language and time zone, the page you sent it from, the page that led you there, and the time. The hostname and network come from public lookups, one of them to a public service that maps addresses to networks. These details are kept for abuse prevention and to verify a submission. Only the people who read the project mailbox and the private table see them, and they are never published. A salted hash of the address is also stored so a rate limit can work.
The form check, run by a security service
Each form carries a check that tells a person from an automated sender. It loads only on pages with a form and runs in your browser, so the service that runs it sees your IP address and details of your browser. When you send the form, this site passes that service the result of the check and your IP address to confirm it. Nothing you type into the form goes to that service.
Request logs, held by the host
Standard request logs kept by the company that hosts the site, without request bodies. They exist to catch abuse and outages. This project never logs the contents of a form.
Receipts and notices, sent through a transactional mail service
If you give a contact address with a submission, a receipt is sent through a transactional mail service. Each submission and its technical details also go through that service to the project mailbox. No newsletter exists, and no list is built from that address.

The services above and the provider that hosts the project mailbox are the whole list. One company hosts the site. One provider holds the database and the file store. A transactional mail service sends mail. A security service runs the form check. An analytics service counts visits. Each acts on the instruction of this project and for no purpose of its own, except that the security service may also use what its check sees to improve the check. A public service that maps addresses to networks answers the network lookups. It is not a processor acting for this project.

02What is not collected

  • No user accounts, no passwords, no sign-in of any kind.
  • No advertising network, no advertising identifiers, no data sold or shared with a broker.
  • No third-party share widgets. Share links are plain intent URLs that run no script.
  • No chat, no session recording, no heatmap, and no fingerprinting to follow a visitor across pages or sites.
  • No payment details. Donations, if this project takes them, go to a hosted processor on its own pages, and card details never touch this site.

03Why any of it is collected

Hosting and its request logs exist to serve pages and to catch an outage or an attack. Form data exists so a submission can be read and answered, and so a correction can be traced to the record that prompted it. The salted hash, the honeypot and the form check exist so that a form is not a free channel for a flood.

In the language a European reader will expect, the first and third rest on the legitimate interest of running a public interest publication and keeping it available. The second rests on the step you took in choosing to send something. Analytics rests on consent, which is why an opt out signal stops it.

04Analytics, do not track and Global Privacy Control

Analytics runs through an analytics service in an account this project holds. It reports pages viewed, referrer, approximate region, device and browser, and the network each visit comes from. It is used to see which findings people read, which public bodies and other organisations read them, and whether a page is broken. It is used for nothing else.

When analytics is allowed to load, the page asks this site's own server which network the visit came from. The browser keeps the answer for up to thirty minutes, or until the tab is closed, and does not ask again in that time.

To answer, the server looks up the public name that the visit's address carries, if it has one. That lookup uses the full address. It also asks a public service that maps addresses to networks which network holds the block the visit came from, and sends that service only the block. The answer gives the name and number of that network and a type, such as government, school, internet provider or mobile carrier. It also gives the public name. Any part of that name that contains the address is removed. The first part, which usually names the machine, is removed too, unless it is a common network word such as pool or static.

The server keeps neither the address nor the answer. The address is never sent back to the browser and is never one of the values this site sends to the analytics service. The answer goes to the analytics service with the visit and is kept there for the time set out under retention below.

Where a browser sends a Global Privacy Control signal, or the older do not track header, the analytics scripts are not loaded, the network lookup for analytics does not run, and no analytics cookie is set. A form you choose to send still records the details listed above. Browser settings and content blockers also stop the scripts, and the site works exactly the same without them.

05Anti abuse, the honeypot, the form check and the rate limit

Every form carries a field that a person never sees and never fills. A submission that fills it is rejected before anything is written, so an automated flood leaves no row and no file behind.

Every form also carries the form check described above. A form that fails it is turned away before anything is written.

A rate limit counts recent submissions against the salted hash described above, per form. It counts against a hash rather than against a person, and the count is not kept as a record of anyone.

06What happens to what you send

Uploads are limited to a short list of types, checked, stripped of metadata and re-encoded before anything is done with them. Rows and files sit in private storage that the public site cannot read.

A tip sender is never named on the site. A response from a jurisdiction or a vendor is published verbatim beside the finding it contests, so send only what the jurisdiction or the vendor is content to have published. Nothing sent to this project is legally confidential, and publication is not promised.

07How long each thing is kept

  • A rejected submission and its attachments are purged after ninety days. Nothing survives that sweep.
  • An accepted submission is kept as provenance for the record it supports, for as long as that record is published.
  • A salted hash expires with the rate limit window it was stored for.
  • Request logs are kept to the retention the host sets, which is short.
  • Analytics data, including the network a visit came from, is kept to the retention setting on the analytics account this project holds, and is aggregated after that.
  • The network answer the browser keeps is not used after thirty minutes and is dropped when the tab closes. This site's server keeps no copy.

Deleting something removes it from the working store immediately. A copy can persist briefly in a backup before that backup rotates, which is true of every hosted system and is stated here rather than glossed.

08Who else sees it

Nothing collected here is sold, rented, traded or given to a data broker, under any circumstance. There is no advertising partner, no audience list and no exchange of any kind.

Where a lawful demand arrives for information about a submission, this project reads it carefully, objects to a demand that is improper or overbroad, and tells the person it concerns where the law allows that.

09Your rights, wherever you live

Several state laws in the United States and the frameworks that apply in Europe and the United Kingdom give a person rights over information held about them. This project honours a request for access, correction, deletion, a portable copy, or an objection to processing from anyone who asks, regardless of where they live.

The route is the contact form. A request that would destroy the provenance of a published finding is answered with an explanation rather than silence.

10Visitors from Europe

This is a New Jersey project about New Jersey public records. Its hosting, its database and its file store are in the United States, so a request from Europe is served from United States infrastructure and any data it carries is processed there. The rights set out above apply to you on the same terms as to anyone else.

11Children

This project does not knowingly collect personal information from anyone under 13, and where a framework sets the threshold at 16 this project treats 16 as the floor. If information from a child reaches this project anyway, it is deleted. Write through the contact form to ask for that.

12Security

Traffic runs over encrypted transport. Submission rows and uploaded files sit in private storage that the public site and the read only interface cannot reach. Uploads are restricted by type, checked, stripped of metadata and re-encoded. Access to the private store is limited to the publish pipeline.

No system is secure in the absolute, and this page does not promise that one is. The smallest amount of information is collected, and what is collected is kept in the narrowest place it can usefully sit.

13People named in public records

Where a produced document shows an official signing in a role, the document is reproduced as produced. Where a production carries the identity of a person who requested records, that identity is redacted with a printed label, the redaction is counted, and the viewer says a redaction was applied. Correspondence addressed to a requester is excluded from the site entirely.

If you believe a document on this site carries personal information that does not belong in a public record, write through the contact form and name the document and the page.

14Changes to this policy

This policy may change. A changed version carries a new version number and effective date at the top of this page. Nothing on this page is edited in place without that record.

15Contact

Replies come from the project mail domain. Inbound messages go to the project mailbox. Ask through the contact form.

Opioid Audit

Opioid settlement money was meant for treatment and recovery. New Jersey towns spent it on Flock cameras, surveillance drones, police gear, and told the State it went to programs that do not exist. We found it in their own ledgers, town by town, and we are publishing all of it with the pages cited. This is fraud, documented, and it is now public.

Towns and VendorsState OverviewRankingsCountiesVendors
FindingsAll FindingsPhantom ProgramsSurveillance TechnologyPolice Vehicles and GearZero Certification
ArticlesAll ArticlesReports
DataHow Grades WorkMethodologyDocuments
Take ActionFor MediaFor ActivistsFor LegislatorsTips
AboutAbout the ProjectContact UsLegal
© 2026 Opioid AuditPublication PolicyTermsPrivacyCorrections