How to reach us, and what we can’t take yet

Security vulnerability

Email security@ourelectedportfolios.com

Open

Correction to a filing

The figures on this site are drawn from real 2025 US House filings now, so a correction is a real thing to report — but no address takes one yet

No route

Press, feedback, anything else

No general address is configured, and there is no public issue tracker

No route

Your account or your data

There are no accounts, no mailing list and no tracking; the host’s ordinary request log is the only thing there is to ask about

Not applicable

If you have found a flaw in this site — a way to read or write something you shouldn’t, an exposed credential, an injection, a broken authorization check — send it to security@ourelectedportfolios.com. That address is published at /.well-known/security.txt in the RFC 9116 format, and it is the only address this project monitors.

A report is easiest to act on when it carries:

• the URL or endpoint, and the exact request you sent
• what you expected to happen, and what happened instead
• enough detail for someone else to reproduce it once
• whether you have disclosed it elsewhere, and any deadline you are working to

Please don’t test against anyone else’s data, and don’t run load or denial-of-service testing against the site. There is no bug bounty and no payment — the site is free, has no paid tier and takes no money today — so a report here is a favour to the people who read it rather than a transaction, and it is treated as one. The security.txt file lists no encryption key, so until it does, treat plain email as plain email.

There is now something to correct, and still no route to report it on. That gap is ours rather than yours, and this is what stands behind it. The figures here come from periodic transaction reports filed with the Office of the Clerk of the House for calendar 2025: 515 reports found, 449 read, 7,645 transactions between them. The other 66 are scanned paper that nothing here can read — they are recorded as unread rather than dropped, so the coverage is partial and countable. Nothing from the Senate is published, and no year other than 2025 is loaded.

When a correction route opens it is published in this section, and two things will be true of it. A correction needs to name the filing and the field, because that is what makes it checkable against the source document — every filing the ingest saw, readable or not, is stored with its address at the House Clerk, though no page on this site links out to one yet. And where the disclosure itself is wrong, the amendment is filed with the House Clerk, not with us: this site reports what was filed. It is not the record, and it cannot change one.

Two things that will never be a correction. A disclosure report gives a dollar range, never an exact amount; where a range looks imprecise, that is the filing, faithfully reproduced. And 35 transactions carry a notification date earlier than the trade date they report. Those are the filers’ own slips, kept as filed rather than tidied up, because a database that silently repairs a public record stops being a copy of it.

There is no general contact address. Not a slow one — none. Press enquiries, feature requests, data questions and “is this thing on?” all have no route today, and the repository is private, so there is no public issue tracker to file to either.

The security address is not a substitute for one. It is monitored for vulnerability reports, and a queue full of general mail is how a real report gets read three weeks late. When a general address exists it will be listed in this section — and the fact that this paragraph is still here is how you will know it doesn’t.

A contact page often exists so people can ask what a site holds on them. This one holds nothing. There are no user accounts — registration and sign-in are not built. These public pages load no analytics or tag script and set no cookies at all; the server doesn’t so much as look for a session on them. There is no mailing list to leave, and no paid tier, so there is no subscription to cancel and no charge to dispute. Two things are the exception, and they are not nothing: the hosting provider keeps an ordinary request log, which records your IP address the way every web server does, and if a script on this page ever violates its Content-Security-Policy your browser posts a truncated report of that violation to the same log. Both are described in full on the privacy page, and nothing is layered on top of them.

None of that is a permanent promise. The site is intended to carry advertising eventually, and advertising changes this paragraph. When it does, it will be written down here first rather than discovered afterwards.