Release notes

July 10, 2026 — v7: Comments, @mentions, and reviewers who never get forgotten

v7 is our biggest collaboration release. Contracts became places your team can talk, follow-ups stopped falling through the cracks, and Pishik started chasing slow reviewers on its own. Each item below links to the guide that explains it in full.

Comments and @mentions

Every contract now has a threaded comment section. Discuss terms, ask a question, and @mention a teammate from a searchable picker — they get an in-app alert and, if they've opted in, an email. Mention emails deliberately carry no comment text: they tell you where you were tagged and link straight to the thread, but the discussion itself stays inside the app.

• A mention inbox on every dashboard collects the comments where you were tagged or replied to.
• A full lifecycle tracks each mention from tagged to done — it's marked seen automatically when you open the thread, and can be resolved, dismissed, nudged again, escalated to admins, or reopened if it was closed by mistake.
• Nothing dies in an inbox: mentions left unanswered for a few days surface team-wide in the admin queue.

Full details: Comments and @mentions and The mention lifecycle.

Automatic reviewer reminders

Pishik can now chase non-responding reviewers for you, on a schedule you set — a cadence of 1 to 30 days, up to a total cap, sent at a time of day in your workspace's timezone, and it stops after a 45-day cutoff so no one is nudged forever. Manual "remind" and "resend" are still one click away when you'd rather do it by hand.

Set it up: Configure automatic reviewer reminders.

Per-user preferences

Settings that used to be one-size-fits-all are now yours alone. Each member chooses which screen the app opens on, their default contract type, whether they receive @mention emails, their overdue threshold, and whether Pishik asks for confirm-on-delete — without changing anything for teammates.

See Workspace defaults vs. personal preferences.

SearchSelect refinements

SearchSelect — the searchable dropdown Pishik uses for pickers across the app (the reviewer book, team-board filters, contract types, and departments) — was refined in this release: longer lists become type-to-filter, arrow-key navigation works throughout, and the control behaves consistently everywhere it appears.

July 2026 — the private beta opens: invite codes, email verification, and two-factor authentication

Pishik opened to its first teams as a private, invite-only beta. The launch put three foundations in place — how you get in, how we confirm it's really you, and how you keep your account safe.

Invite-only access

You join with a single-use invite code. There's no open sign-up and no automated waitlist: you request an invite, we review the request, and we email you a code to redeem. Codes are one-time — once used, they can't be reused.

How it works: Request an invite and redeem your code · Request an invite.

Email verification at signup

Before a workspace is created, Pishik emails a 6-digit code to confirm the address is really yours. You can resend the code or go back and correct the address.

Walkthrough: Create your workspace.

Two-factor authentication

Accounts can add two-factor authentication using any authenticator app (QR-code enrollment, TOTP). Single-use backup codes are shown once and stored hashed, so you can still get in if you lose your phone — and admins can require 2FA for the whole workspace.

Set it up: Set up two-factor authentication.

Legal & policy change log

We record material changes to our legal documents here, so the “Last updated” date on each one always has a plain-English explanation behind it. If a document changes in a way that affects you, this is where we say what and why.

July 13, 2026 — launch transition spelled out

Beta Program Agreement — Last updated July 13, 2026.

• Amended §7 (Fees; transition to paid plans) so the launch transition is now spelled out: a 30-day decision window for beta workspaces, a beta-exclusive $75/month Founding rate that keeps existing seats, suspension (never deletion) if no plan is chosen, and a 60-day minimum export window.
• Updated §8 (End of the beta) to match.

July 12, 2026 — website revamp

Alongside the new website, all three legal documents were revised for clarity and accuracy. Nothing here changes what you agreed to in substance; the updates make the documents easier to navigate and bring specific wording in line with how the product actually works.

Terms of Service — Last updated July 12, 2026.

• Added stable ids to all 20 sections and a linked table of contents, so any clause can be linked directly.
• Reworded §8 (Third-Party Services) to state the share-link model plainly: Pishik stores links to documents you host in SharePoint, OneDrive, or Google Drive and does not access, copy, or store the documents themselves. Language implying Pishik “integrates with” those services was removed.
• Added a real page description for search and link previews.

Privacy Policy — Last updated July 12, 2026.

• Added section ids and a linked table of contents, plus a real page description.
• The website's fonts are now self-hosted, so the Policy can state plainly that visiting the site makes zero requests to third-party servers — no external fonts, analytics, or CDNs. (This removed a wording contradiction from the old policy.)
• Consolidated the delivery-metadata description into one place: what we log when an email is sent is now stated once — “the metadata, and nothing more” — and referenced elsewhere instead of repeated. See How email is sent.

Beta Program Agreement — Last updated July 12, 2026.

• Added section ids and a linked table of contents.
• Corrected the acceptance-mechanics wording in the opening acknowledgment so it matches how you actually accept the agreement — by creating a workspace, by joining through a teammate invitation, or by otherwise using the Service during the beta.
• Clarified §3 that beta support is best-effort, with no service levels.