Terms of Service

Weirlog is compliance field-ops software for contract water and wastewater operators. It records field observations in an append-only ledger, computes report values from your permit configuration and your own data, produces reports, and stages them for review.

Weirlog does not submit, does not sign, and does not judge.

It never files. Weirlog does not transmit anything to NetDMR, CDX, or any other state or federal reporting system. Submission happens on the state’s own system, signed by a certified human under their own login.

It never signs. Weirlog applies no electronic signature. Where a report shows as signed, Weirlog has recorded that a named person attested they signed it themselves, elsewhere.

It never holds your state credentials. Do not enter them into Weirlog. There is no field for them, and any attempt to store them in a notes field is a misuse of the service under section 5.

It never renders a verdict. Weirlog shows a value’s position against your permit. It does not tell you whether you are in compliance, and it will not.

This boundary is deliberate and permanent. It exists because a shared-credential submission is not a valid electronic signature, and because the judgment about a regulated facility belongs to the certified operator responsible for it — not to software. Weirlog is not a filing service, a laboratory, a consultant, or a substitute for a licensed operator, and nothing it produces is legal, engineering, or regulatory advice.

Signing up creates an organization and makes you its owner. Owners and admins add members by issuing invitation links; an invitation can be redeemed only by the email address it was issued to, and cannot confer ownership.

Roles — owner, admin, operator, technician, lab tech — determine what a member may do. They do not partition what a member may see: every member of an organization can read that organization’s records. Add people accordingly.

Each login belongs to one person. Do not share credentials, do not create a shared “front desk” account, and do not let anyone act under another person’s login. Attribution is the point of the ledger; a shared login destroys it. You are responsible for everything done under your organization’s accounts, and for telling us promptly if you believe one has been compromised.

Weirlog computes from what you give it. Specifically, you are responsible for:

The accuracy of your permit configuration. Limits, monitoring windows, seasons, non-detect policy, sampling locations, and form selection are configuration you set from your own permit. Every computed value carries the policy it was computed under so it can be explained later — but the value is only as right as the configuration behind it.

The accuracy of what is entered. Readings, sample results, times, and locations are your firm’s record of what happened.

Review before anything leaves. A staged report is a draft for a qualified person to check. Review it, and sign and submit it yourself.

Certification. Ensuring the people performing and certifying work hold the certifications your state requires. Weirlog records certification data and checks it against the date of analysis; it does not verify with any state that a certification is genuine or current.

Your own retention obligations. See the Privacy Policy, section 10.

You should know this before you type anything into Weirlog.

Readings cannot be edited or deleted. The database refuses both. A mistake is fixed by recording a correction, which is a new entry that supersedes the earlier one and carries a reason. Both entries remain visible forever. The same principle governs computed reports, released procedures, plant events, and filed documents: they are retained rather than removed.

That is the product working as intended — it is what makes the record defensible years after the month it describes. It also means Weirlog is not the place to store anything you might later need to erase.

It also means deletion inside the application stops where the ledger begins. Where an admin can delete a client, that deletion is written to reach the sites, systems, permits, limits, and reports beneath it — but it cannot complete if any reading has ever been recorded under that client. The ledger’s append-only rule refuses the removal, the whole operation is rolled back with an error, and nothing is deleted. The same is true of a visit or a sample that has any reading attached. In practice: the record of a plant your firm has actually operated cannot be deleted from inside Weirlog, by anyone, including us through the application. Removing such a record is a deliberate act performed outside the application, on the terms set out in the Privacy Policy, section 11.

You may not:

enter state or federal e-reporting credentials, or any other party’s account credentials, into Weirlog; share a login, or use another person’s login; knowingly enter false or fabricated monitoring data, or use Weirlog to construct a record of work that was not performed; upload data you are not entitled to hold, or personal data your customer has not authorized you to share with a vendor; attempt to reach another organization’s data, probe or interfere with our access controls, or test the service’s security without our written permission; scrape, bulk-extract, resell, or sublicense the service or its content (the export in section 6 is the supported way to get your data out); reverse engineer, decompile, or copy the software, except where law says you may despite this clause; or use Weirlog to store or transmit malware, or in any way that breaks the law.

We may suspend access immediately where continued use threatens the service, another customer, or someone’s safety. Where we can tell you first, we will.

You keep all rights in the data you put into Weirlog. Your regulatory record belongs to the utility or facility that produced it, and to your firm — not to us.

You grant us only the permission we need to run the service for you: to store, process, transmit, compute over, back up, and display your data to your own users.

Any owner or admin can export the record at any time — twenty-two tables as CSV files in a single archive with a README naming each of them — without asking us and without our involvement. That capability is part of the service, not a favor, and it does not depend on our continued existence. Documents you filed are not in that archive and must be requested from us separately; the Privacy Policy, section 9, says exactly what the export does and does not contain.

We do not use your data to train models. Weirlog contains no generative AI, and its recommendations are exact-match lookups over procedures your own people authored and released.

Weirlog is provided as-is and as-available. We make no uptime commitment in these terms; where we have committed to one in a signed agreement, that agreement governs.

Weirlog is early-stage software, delivered to a small number of operator firms with hands-on onboarding. We will tell you about material changes to the service.

Fees, billing terms, and the term of service are set out in your written agreement with Hoss Automation. Weirlog does not sell subscriptions inside the application, and no purchase can be made through it.

To the fullest extent the law allows, Weirlog is provided without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted or error-free, or that any computed value, observation, report, or procedure is correct, complete, or sufficient for any regulatory purpose.

We are not responsible for regulatory outcomes. Weirlog does not file, sign, or judge. Every submission is made by a certified person exercising their own judgment, and responsibility for what is submitted stays with them and with your firm.

To the fullest extent the law allows, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data, arising out of these terms or your use of Weirlog, even if advised such damages were possible.

Our total liability arising out of or relating to these terms will not exceed the amounts you paid us for Weirlog in the twelve months before the event giving rise to the claim.

Nothing here limits liability that cannot be limited by law, including for fraud or for death or personal injury caused by negligence.

You may stop using Weirlog at any time; to close an account, follow the process in the Privacy Policy, section 11. We may terminate for material breach of these terms, or as set out in your written agreement.

Export your record before you go — and ask us for the filed documents the export does not carry. On termination we will make both available to you and will handle your data as described in the Privacy Policy, section 11, including where a statutory retention obligation means part of the record must be kept rather than destroyed.

We may update these terms. For material changes we will notify account owners before they take effect, and continuing to use Weirlog after that date means you accept them.

These terms are governed by the laws of the State of Indiana, without regard to its conflict-of-laws rules, and the state and federal courts located in Indiana have exclusive jurisdiction over any dispute arising from them.

Hoss Automation LLC · Greenfield, Indiana