State agencies publish their corporate registries as fixed-width mainframe files, undocumented layouts, and inconsistent bulk dumps. Our pipeline ingests every government release each business morning — parsing the layouts, normalizing the fields, deduplicating the records, and diffing each release against the last — then delivers what changed as a documented, versioned feed. You subscribe to the service; we run the infrastructure.
The records are public. Making them usable is the work — and it is not trivial.
Florida publishes its corporate registry as fixed-width ASCII with positional fields, packed officer blocks, and layouts that are documented incompletely or not at all. We reverse-engineered the record structures and validate every field offset on ingest.
Entity types, status codes, address components and ZIPs are normalized to consistent values. Malformed records are quarantined rather than silently dropped, so a bad source day is visible instead of corrupting the dataset.
States re-post the same bulk file under multiple dates. Florida's corporate event file repeats the previous day's contents roughly two days in five. We checksum every source file and deduplicate on record identity, so you are never billed for the same rows twice.
Registries publish snapshots. We diff consecutive snapshots to derive events — dissolutions, reinstatements, amendments, name changes, registered-agent changes — which the source does not provide as a clean stream.
Every source file is stored with a SHA-256 sidecar before parsing. Any output row can be traced back to the exact government file it came from, which is what makes the data auditable.
Column names, types and semantics are fixed and versioned. Files are written atomically to stable URLs, so an automated download never catches a half-written file.
Continuously monitored, delivered as documented CSV each business morning. Month-to-month, cancel any time.
A different product line, and a different kind of work. Five federal and state sources joined on PWSID — the public water system identifier — and scored for regulatory pressure, funding readiness and deadline proximity. Contains no personal data.
Free samples — the top 50 systems by trigger score from each radar, no signup: lead service lines · PFAS · resilience
Florida Business Filings, one entity per row:
| field | example |
|---|---|
| doc_number | L26000422256 |
| entity_name | 1010 HICKORY STREET, LLC |
| entity_type / status | FLAL · A |
| filing_date | 2026-08-13 |
| principal address | 2181 LAKESIDE DR E., FERNANDINA BEACH, FL 32034 |
| registered agent | PESTANA, MARINA M. |
| first_seen | 2026-08-14 |
Subscriptions are month to month, cancel any time. Files are delivered as downloads at stable URLs.
These are business registry datasets. There are things they are not for.
Official bulk data published by state agencies — the Florida Department of State Division of Corporations; the Colorado Department of State and the New York Department of State via their open-data portals; and the Texas Comptroller of Public Accounts. We use published bulk endpoints only. We do not scrape, and we do not access login-protected or restricted systems. FilingsDaily is not affiliated with, endorsed by, or connected to any state government.
Engineering, not access. The source files are fixed-width mainframe exports with undocumented layouts, duplicate postings, inconsistent field conventions, and no change stream. Building and maintaining a pipeline that parses them correctly, catches the state's repeated files, derives change events by diffing snapshots, and delivers a stable documented schema every morning is the product. If you would rather build that yourself, the sources are public and we will happily point you at them.
Florida filings and fictitious names refresh each state business day. Colorado refreshes daily after the state's own update window. New York runs about two days behind its own filings and we publish on that schedule. Texas is different and we say so on the product: it comes from the state franchise tax roll, where an entity appears roughly three weeks after it is chartered, so the Texas feed is about three weeks behind by design rather than by fault. The Florida change feed depends on the state's corporate event file, which in practice refreshes every one to two business days — so we publish it as a rolling 7-day window rather than pretending every day brings new events.
Plain CSV with a header row, UTF-8, one row per entity, owner, or event depending on the dataset. Column names and types are stable and documented. Files are written atomically, so a scheduled download never retrieves a partial file.
No. None of our sources contain telephone numbers or email addresses. Registered agent and officer names and addresses appear because they are part of the public registry record filed with the state.
Subscriptions are month to month and can be cancelled at any time from the link on your Paddle receipt or at paddle.net. You can also email support@filingsdaily.com; email cancellations are handled within one business day.
Paddle.com Market Limited is the merchant of record and payment processor for all purchases on this site, and refunds are handled under Paddle's refund policy. You can request a refund directly from the receipt Paddle emails you after purchase, or via paddle.net. We're also glad to help — email support@filingsdaily.com and we'll point you to the right place or flag anything unusual to Paddle on your behalf.
Five public sources, joined on PWSID: the EPA Service Line Inventory (66,414 systems), EPA UCMR 5 PFAS occurrence results, EPA's AWIA certification dataset (9,921 covered community water systems), Florida DWSRF project funding from FDEP, and the statutory compliance deadlines themselves. Each is retrieved from its official public endpoint. The scoring model, the PWSID identity graph that links the sources, and the change detection between snapshots are ours.
It is a 0–100 ranking of how likely a water system is to be spending money on a given problem soon, built from four weighted components: regulatory pressure, funding readiness, deadline proximity, and recent change velocity. It is an analytical estimate, not a prediction or a guarantee, and every input column is included in the file so you can check the reasoning or re-weight it yourself.
Often, yes. The pipeline is source-agnostic and new states are added regularly. Email us with what you need.
What we collect from you, and separately, what the datasets contain. Those are two different things.
Your name and business email, so we can identify your subscription and send access and renewal notices. Billing details, which go directly to our payment processor — we never see or store card numbers. Correspondence you send us. Delivery logs — the network prefix of the requesting IP address (never the full address), the time, and the file requested — for 90 days, to operate the service, diagnose failed downloads, and detect shared download links.
We have no customer account system, so we hold no passwords. We do not sell, rent, or share customer information, we run no advertising or cross-site tracking, and we do not send marketing email to people who have not asked for it.
The datasets are derived from records that state and federal governments publish as public records. They are not compiled from consumer data, purchased lists, or tracking.
Water infrastructure datasets are keyed on PWSID and describe water systems, not people. They contain no personal data.
Business registry datasets describe registered entities. Because state corporate and fictitious-name filings are public by law and name the people a business lists in them, these datasets do contain personal data. Specifically: names of registered agents and officers, including where the agent is a natural person rather than a company; names and street addresses of business owners, where a fictitious-name (DBA) filing lists a natural person as owner; and the principal and mailing addresses of the entity itself, which for sole proprietors and small companies are frequently residential addresses. These are the fields exactly as the state publishes them — we publish no field the source did not publish. Our sources contain no telephone numbers and no email addresses, and we add none.
We do not enrich, append, cross-reference against consumer databases, infer, or score individuals. We republish in normalized form and derive business events — never personal attributes.
The underlying record is a public filing held by the issuing agency, and we publish what that agency publishes. We cannot amend a government record — corrections are made at the source, and our next publication reflects them because we re-derive from source rather than keep our own copy of the truth. If you believe we published something the source does not say, email us and we will check it against the archived source file, which we retain with a SHA-256 checksum for exactly this purpose.
We use Cloudflare for DNS and delivery, a payment processor for billing, and an email provider for notices and support. They process data on our instructions; we do not sell data to or through them.
Customer records are kept for the life of the subscription plus seven years for tax purposes. Delivery logs are kept 90 days. Archived government source files are retained indefinitely with checksums, because dataset auditability depends on it.
To access, correct, or delete your customer data, email support@filingsdaily.com and we will respond within 30 days. Records we are required to keep for tax purposes stay for the seven years stated above even after a deletion request; everything else is deleted. We operate from the United States and process data there.
Business-to-business terms, version 2026-09-15. You agree to them by ticking the box before checkout.
A subscription to one or more datasets, delivered as documented CSV at stable URLs and refreshed each business morning. You are paying for the derivation work: parsing undocumented source layouts, normalizing and validating fields, deduplicating re-posted source files, diffing snapshots to derive change events, and maintaining a documented, versioned schema. The underlying government records are public and free; the datasets are not the records. We are not affiliated with, endorsed by, or acting on behalf of any government agency.
Subscriptions run month to month and renew until cancelled. Cancel any time from the link on your Paddle receipt or at paddle.net, or by email. Prices are as listed, exclusive of tax; we may change prices for future renewals with at least 30 days’ notice, and a price you have already paid never changes. Paddle is the merchant of record and handles all billing and refunds under Paddle’s refund policy — see refund terms below.
Government sources publish on their own schedules. A day on which the source does not publish is not a failure of delivery. Persistent non-delivery is.
While your subscription is current you have a non-exclusive, non-transferable licence to use the datasets internally for business research, market analysis, compliance, due diligence, and record-keeping, including in derived analysis you produce for your own business or clients.
No FCRA use. The datasets are not consumer reports and we are not a consumer reporting agency. You must not use them for any purpose covered by the Fair Credit Reporting Act, including decisions about credit, insurance, employment, housing, or tenant screening, or any comparable purpose under state law.
No unsolicited contact. No telemarketing, automated dialing, unsolicited commercial email, or contact violating the TCPA, CAN-SPAM, or state law. Our sources contain no phone numbers or email addresses; appending contact data from elsewhere and then contacting people is your act and your liability.
No bulk redistribution. You may not republish, resell, sublicense, or redistribute the datasets in bulk or as a substantially similar product. Producing your own analysis is permitted; reselling our files is not.
No unlawful use, and no credential or URL sharing to allow access by parties without their own subscription. Breach of this section terminates the licence immediately.
The datasets are provided as-is. We derive them from government sources that are themselves incomplete, inconsistently formatted, and occasionally wrong. We validate, quarantine malformed records rather than dropping them silently, and retain checksummed source archives — but we do not warrant that the data is accurate, complete, current, or fit for a particular purpose, nor that availability is uninterrupted. Do not use these datasets as the sole basis for a decision with legal or financial consequences; verify against the issuing agency.
To the maximum extent permitted by law we are not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, data, or business opportunity. Our total liability for any claim is limited to the fees you paid in the 12 months before the claim arose. You will indemnify us against claims arising from your use in breach of the section above.
These terms are governed by the laws of the State of Florida, with exclusive venue in the state or federal courts located in Florida. Material changes take effect for existing subscribers at the next renewal, with at least 30 days’ notice by email.