Terms of Service

Version 2026-08-06-v1. Not legal advice -- see the project's internal compliance documentation for the full caveat. Have an attorney review this before it's relied on beyond the current prototype stage.

1. What this is

This product ("the Service") is an AI-assisted proofreading tool for court-reporting transcripts, built for scopists and proofreaders. It extracts text from a draft PDF, checks it against formatting rules for a selected jurisdiction, and runs a proofreading pass -- either a live call to an Anthropic Claude model, or (when no API key is configured) a heuristic demo-mode fallback that is clearly labeled as such everywhere it appears in the product's output. The Service produces suggested corrections and flags for human review; it does not certify a transcript, replace a scopist's or proofreader's professional judgment, or verify anything against the original audio recording.

2. Your account

You need an account to use the Service. You're responsible for keeping your login credentials confidential and for all activity under your account. Tell us if you believe your account has been compromised. You can delete your account at any time from the Account page -- see Section 7.

3. Your responsibility for consent and authorization

You are solely responsible for having whatever client consent, engagement-agreement authorization, or other legal basis is required before uploading a transcript to the Service. At upload, you're required to affirmatively confirm this; that confirmation is recorded against the specific document you're uploading and is part of the permanent audit record for that document. The Service has no way to independently verify that a real, signed consent exists -- recording your confirmation is not a substitute for actually having obtained it.

4. How your content is handled

A transcript you upload is processed through a local, pre-network classification step that checks for signals of PHI-adjacent (protected health information-adjacent) content -- things like medical or clinical terminology, Social Security number patterns, or date-of-birth references. Based on that classification, the document is routed through one of two API paths/organizations for the proofreading pass. This classification is a deliberately over-inclusive routing heuristic, not a certified PHI detector or a claim of HIPAA Safe Harbor de-identification -- see Section 6 for what that does and doesn't mean for you.

5. Sharing and access within the Service

By default, only you can see a document you upload. You can grant another account of your choosing view-only access to a specific document; you can revoke that access at any time. Every access to a document -- yours, a grant you made, or (in rare cases) an administrative override for support or investigation purposes -- is recorded in an audit log, including denied access attempts. Administrative access is never blended into your own activity record; it is always logged as a distinct, identifiable action.

6. No PHI-handling or compliance guarantee

The sensitivity classification described in Section 4 is a heuristic, not a certification. Using the Service does not, by itself, make your use of it HIPAA-compliant, and the Service does not represent that any particular document has been properly de-identified or handled under a Business Associate Agreement. If your use of the Service involves protected health information, you are responsible for determining whether that use meets your own legal and regulatory obligations, independent of anything this product does internally.

7. Deleting your content and your account

You can delete an individual document at any time from that document's page; this permanently removes the stored file and any exported files. You can delete your entire account from the Account page; this deletes every document you own the same way, removes every sharing grant involving your account, and de-identifies your account record. In both cases, a minimal audit-trail record is retained (that a document or account existed and was deleted, by whom, and when) -- this record never contains your transcript content, and exists to satisfy the audit-logging commitments described in Section 8, not to retain your content after you've asked for it to be removed.

8. Audit logging

The Service keeps a real, append-only log of account and document activity -- signups, logins (including failed attempts), uploads, processing, views, downloads, sharing grants and revocations, sensitivity-classification outcomes, and deletions. This exists to support the access-control and audit commitments described in this project's internal compliance documentation, and so that if something goes wrong, there's a real record to investigate rather than only a policy describing what should have happened.

9. No warranty

The Service, including any AI-generated suggestion, correction, or flag, is provided without warranty of any kind. It is a proofreading aid, not a certification of accuracy. Nothing the Service produces should be treated as verified against the original audio recording -- several of its own checks (for example, flagging a raw number without resolving it) are deliberately left unresolved for exactly this reason, and are documented as such in the product's own output.

10. Changes to these terms

If these terms change in a way that matters, we'll ask you to accept the updated version before you can continue using the Service. The version you accepted is recorded on your account.