Every version of the agreements you accept when you use SynthCounsel, with the content hash that identifies its exact text.
| Version | Effective | Status | Content hash (SHA-256) |
|---|---|---|---|
| 2026-04-05 | April 5, 2026 | In force | 5cc852264b220cbea5163b0d6c042b0829f8920fd4a8251fcbd4ede5f7fd2e2dContent baseline recorded 2026-08-12, then re-based twice on the same date. First to add a link to this version archive beneath the effective date. Second because lib/pricing.ts is a Terms source and gained the firm annual and white-label figures — but the Terms recite only Pro, Annual, and Per-Document, none of which changed, so the text a user reads is byte-identical. No right, obligation, price, or disclosure in this document changed, and no re-acceptance was required. Re-based again 2026-08-20 for the same reason: CREDIT_ALLOCATIONS gained a `free_throttled` row so the abuse-defence downgrade would actually reduce the AI allowance it had always claimed to halve. free_throttled is an internal anti-sharing state, never sold and never quoted — the Terms interpolate only PRICING.pro.price, PRICING.annual.price and PRICING.perDocument.price, all unchanged. The rendered text is byte-identical and no re-acceptance was required. |
Current version 2026-04-05, effective April 5, 2026.
| Version | Effective | Status | Content hash (SHA-256) |
|---|---|---|---|
| 2026-08-13 | August 13, 2026 | In force | ac3a4010898e41c4d0b719551042602783d700905f3c5a16f4d7577d94414d25Corrected how we describe deletion. The previous version said deleted data was “permanently purged” and that a delete request was completed “within 30 days”, with no mention of backups. Our database keeps a rolling point-in-time recovery window — currently 7 days — so residual encrypted copies can briefly outlive the live-system deletion, which made the old wording impossible to satisfy literally. The 30-day live-system schedule is unchanged; what changed is that the backup window is now disclosed. No right was narrowed and nothing new is collected. |
| 2026-08-12 | August 12, 2026 | Superseded August 13, 2026 | 74d7b1594e0f1fbc0171ecb8dba374629c94d02130959499fa5c3884f1389317Corrected the description of how long our AI provider keeps the content we send. The previous version said Anthropic does not retain it. Anthropic is contractually barred from training on it, which was stated correctly, but it is deleted within 30 days rather than immediately — and content its Usage Policy flags is kept up to 2 years, with the resulting safety classification scores up to 7 years. We do not hold a zero-retention agreement. Verified against Anthropic’s published terms on 12 August 2026. |
| 2026-04-05 | April 5, 2026 | Superseded August 12, 2026 | 1b79706d392f60478796ed7aa53a365703c80be775cac4aff00deb65e35d783b |
Current version 2026-08-13, effective August 13, 2026.
| Version | Effective | Status | Content hash (SHA-256) |
|---|---|---|---|
| 2026-08-13 | August 13, 2026 | In force | f539a94964b8d35ed991df8d8491a0fdfe0ceb365c2d6f89a2270f6328b06036Corrected how this page describes the documents the service produces. It said we “generate court-ready PDFs”. Whether a court accepts a filing is not something we can promise, so that wording is withdrawn and the page now says we generate formatted PDFs. Nothing about what the service does, or what you receive, has changed — only the accuracy of the description. |
| 2026-04-05 | April 5, 2026 | Superseded August 13, 2026 | d5414fb3a497f92b37b9a25c981ce4e80047391207485e3efd9cda1589658e2e |
Current version 2026-08-13, effective August 13, 2026.
A version number alone does not prove what a document said. The hash above is computed from the exact source that produces the published page, and the same value is stored with your acceptance when you agree to these documents. If you ever need to establish what you agreed to, that record identifies the specific text — not merely the label it was filed under.
Any change to the text of these documents changes the hash, and our build fails until the change is recorded here. We keep a copy of the source behind every version listed above.
We began recording content hashes on 12 August 2026. A version that was published before that date is recorded as it stood on that date; we do not claim a hash for any earlier state of the text.
You can read, print, download, and keep any of these documents at any time, without signing in. If you would like a copy of a superseded version, or the record of what you accepted and when, write to support.
This page describes how we keep records. It is not legal advice.