{"generatedAt":"2026-11-20T15:12:52.422Z","source":"heygrc-web","contract":"v1","product":"heygrc","canonicalHumanPage":"https://app.heygrc.com/changelog","note":"Scrubbed mirror of the heyGRC product changelog. GitHub PR URLs removed. Not the heygrc.com marketing site release notes (docs/CHANGELOG.md).","markdown":"# heyGRC Product Changelog\n\nAll notable user-facing changes to heyGRC, grouped by month.\n\n## November 2026\n\n### Features\n\n- **Audit evidence export.** On Scale, export your pull requests and findings by framework and control for any period in the last 400 days, as CSV or a print-ready PDF; every plan sees a preview in the console.\n\n## October 2026\n\n### Features\n\n- **Milestones (early access).** For organizations in early access, heyGRC checks each GitHub milestone against your triage questions and linked policies when it is created or edited, and lists the ones worth a security consult on a new Milestones page, with the pull requests and issues attached to each. Owners and admins can record Consult, Not needed or Done with a note and export the decisions to CSV.\n- **Weekly milestones email.** Every Monday, owners and admins of an early-access organization get a short email listing the milestones still waiting for a decision; each person can switch it off in Settings.\n- **Milestones from GitHub Projects.** For early-access organizations, adding an issue or pull request to a GitHub Project now also brings its milestone into the check, once your admin approves the read-only Projects organization permission for the heyGRC app.\n- **Findings page.** A new Findings page lists every finding heyGRC posted on your pull requests, one row per finding, with the controls, your policy and a link to the review, filtered by period and severity and exportable to CSV.\n- **Link your whole policy set.** Link up to 20 documents, each under its own name with no type to pick, and rename any of them from its row.\n- **Word files from Google Drive.** heyGRC now reads Word (.docx) documents you link from Google Drive, so policies kept as Word files no longer need converting first; old .doc files are still not supported.\n- **Engineering policies read more fully.** Secure development, AI, operations and other internal policies now have their own reader that keeps far more of their binding rules (up to 40 per document), so reviews can apply them.\n- **Reviewer checklists count as rules.** Lines in your linked policies that tell reviewers what to ask for a kind of change, such as \"If a change touches X, ask whether Y\", are now read as rules, so reviews can apply them instead of skipping them. Not yet available for organisations whose reviews run on the EU model.\n- **A home for your policies.** The new Context page gathers everything heyGRC reads (Google Drive documents, pasted links), shows whether each source is current, and keeps a change log.\n\n### Improvements\n\n- **Reviews ask the questions your linked rules require.** When a linked policy says a reviewer must ask something for a kind of change, heyGRC now raises that question as a low finding naming the rule, at most two per review, and never on a public repository for a private Drive rule.\n\n- **Fewer repeat notifications.** When a push brings back an issue heyGRC already raised on the pull request, even reworded or pointing at another file, it stays in the summary comment instead of being posted again; it is posted once more only if it gets more severe.\n- **Internal ids in logs are no longer flagged as personal data.** Reviews stop raising a finding when a log line carries only internal identifiers such as user, tenant or trace ids, and still flag names, emails, IP addresses and any id sent to an outside vendor.\n\n- **API links add documents instead of replacing your DPA.** A document linked through the heyGRC API or from Google Drive without a type is now added as its own document; to replace one, pass its `pack_id`. Deleting by type answers 409 when more than one document has that type, and the 21st document answers 409 `pack_limit_reached`.\n\n- **Each review reads the rules that matter to the pull request.** heyGRC now picks the rules from all your linked documents that match the changed code (for example an endpoint, an [AllowAnonymous] attribute or an appsettings secret), gives priority to keeping at least one rule from every document that matches, and on private repositories names the document it quotes.\n\n- **Inline comments say they are AI.** Each inline review comment now ends with \"AI-generated review\", so a developer who only sees that one comment still knows it came from heyGRC's AI.\n\n- **Two-step verification at sign-in.** If you turned on two-step verification in ISMS Copilot, the heyGRC console now asks for your authenticator code too, or a recovery code.\n\n- **The Company page is now your Company profile.** Same page, clearer split: your sector, frameworks in scope and commitments live under Company profile, while your policies and documents live under Context.\n\n- **Private Google Docs link again.** Choose a document in Google's file picker from the Context page, or open it with heyGRC from Google Drive and confirm it in one click; the Doc stays private in your Drive.\n\n- **Better ISMS in the console footer.** The console footer now reads \"heyGRC, a product by Better ISMS\", the same company name you see when you sign in.\n\n### Fixes\n\n- **Signing out of heyGRC keeps other sessions connected.** Sign out now ends the session on that browser only, so other devices and connected AI tools keep working until they sign out themselves.\n\n- **Clear message for files with no rules.** When a linked file has no rules heyGRC can read, such as an interactive web page or an app prototype, its card now says when heyGRC found very little text and suggests linking a policy or standard instead of asking you to try again.\n\n- **Findings that get more serious are announced again.** When a later push makes a finding heyGRC already raised more severe, for example Medium to High, heyGRC now posts it again once so it is not missed.\n- **Older documents get the newest reader.** A linked document heyGRC read before its current policy reader is read again with it, once on its own and whenever you click Read again, and the new reading goes into use only if it keeps every rule heyGRC could quote before.\n- **Policy quotes in review comments.** Quotes from your linked policies now appear when the policy uses typographic dashes or quote marks, and heyGRC no longer quotes a sentence your policy says no longer applies.\n- **Reviews keep your linked policy rules when you link many documents.** When your linked documents filled the space heyGRC sets aside for them, a review could leave out all of their rules; reviews now include them.\n- **Text policies in any encoding.** Plain text policies saved in other encodings (for example from Windows Notepad) are now read correctly.\n- **Reviews no longer fail on pull requests containing emoji.** A pull request whose long description had an emoji right at the length limit could be left unreviewed with a provider error; heyGRC now shortens text without splitting characters.\n- **Policies and standards no longer wait for a DPA fact.** A security, vulnerability, privacy or other linked document no longer stays \"Not in use yet\" because it names no data processing agreement; that check now applies to linked DPAs only. Click Read again on a held document to apply it.\n- **Resend your confirmation email.** Signing up with email now leaves a check-your-email note on the sign-in page with your address and a resend button, and a sign-in attempt on an unconfirmed account opens the same note instead of a raw error.\n- **Open with heyGRC before GitHub is connected.** Opening a Google Drive file with heyGRC from an account that has not installed the GitHub App now explains that GitHub comes first, offers the install, and brings you back to link the file, instead of showing a generic error.\n\n### Privacy & legal\n\n- **Support chat loads only when you open it.** The heyGRC console no longer loads the Chatbase support chat, or its cookie, when a page opens; it loads when you click the chat button.\n- **US state privacy law terms in the DPA.** The DPA that covers heyGRC now includes section 10 with the service-provider terms for the CCPA/CPRA and comparable US state privacy laws, on the Trust Center.\n\n## September 2026\n\n### Features\n\n- **New plans.** Starter $39 / 100 PRs, Pro $149 / 500, Business $399 / 2,000. Existing subscriptions keep their price.\n- **Onboard your coding agent.** The Reviews and API keys pages have a Copy prompt card for Claude Code, Cursor, Copilot, Codex or any other coding agent. The agent fetches the official setup instructions, tells you the steps only you can do, and sets your company context and frameworks after you confirm.\n- **Link several documents per organization.** The Company card lists one row per linked document (a DPA, a privacy policy, a vulnerability policy, a security policy, or another kind), each with its own state, address, quoted passages, and replace/remove actions. File upload is gone: new uploads are refused.\n- **Paste the Google Drive or Docs link you already have.** Share links are rewritten to the readable export endpoint (keeping the resource key), so linking a policy that lives in Drive works without a separate recipe.\n- **The link form names Drive share links.** The Company URL hint says Google Drive and Docs share links work when anyone with the link can view.\n- **Google Drive documents, by share link.** Link a policy that lives in Drive on the Company page with its share link, and heyGRC reads it when anyone with the link can view; the one-click pick of private files from your Google Workspace is in progress.\n\n### Improvements\n\n- **Checkout starts on Pause at the limit.** When you pick a plan, pausing at your limit is preselected with a warning first, and extras with a spend cap stay one click away.\n- **Linked documents are checked for changes daily.** heyGRC now checks your linked URLs and Google Drive files every day instead of every week, and a file that has not changed is confirmed without downloading it again.\n- **Create a key for agent setup.** When you create an API key, choose Reviews config (the default) or Agent setup, which also lets your coding agent sync your compliance context with /heygrc:setup. Agent setup keys are for owners and admins.\n- **Uninstalled organizations are deleted within 30 days.** A daily purge removes an uninstalled org's data inside the documented window; billing holds keep only billing metadata, and review content goes first.\n\n### Improvements\n\n- **The linked document card lists the passages reviews can quote.** It names a DPA only as one example of a policy. Leftover notes stay closed underneath. If the snapshot is too large for the reviewer, the card says so.\n\n- **The Company card says whether reviews quote your document.** A document that is not in use says so, shows the address you linked, and keeps notes about what was not captured behind a closed row. Save company context sits with the profile fields. Read again runs the current check.\n\n### Features\n\n- **Linked documents work on real DPAs and stay fresh.** The compiler takes as much of your document as it can and lists what it did not capture as documented gaps on the card. A pack stays out of use only when the core promise breaks: no DPA coverage found, the document says it is a summary, or the read was incomplete. Linked URLs are re-read weekly in the background: detected changes recompile and swap in only after validating, and a failed re-read keeps the previous snapshot with a note on the card. The card now shows when the snapshot was made, when the link was last checked, and when it was last confirmed unchanged.\n- **Linked document on Company.** Point heyGRC at the DPA you already keep. Use this document authorizes short quotes of it on your pull request comments, including public repositories.\n\n- **OT and energy frameworks in the picker.** You can select IEC 62443, NIST SP 800-82 Rev 3, and ISO/IEC 27019:2024.\n- **Aerospace frameworks in the picker.** You can select EASA Part-IS, UK CAA cyber oversight, DO-326/ED-202, and the space-systems standards.\n- **WA Cyber Security Policy in the picker.** You can select the 2024 WA Government Cyber Security Policy.\n\n### Improvements\n\n- **Clearer CRA label in the picker.** The EU Cyber Resilience Act now shows as \"CRA (EU Cyber Resilience Act)\" so it is not a bare acronym.\n\n### Fixes\n\n- **The Google Drive blocked message shows once.** The panel now keeps one short line pointing to the message over Google's window, and on small screens that message sits at the bottom so Google's Sign in stays visible.\n- **Google Drive says when your browser blocks it.** If your browser keeps Google out of heyGRC, the Drive panel now says a file picked in Google's window cannot come back, shows the setting to change in Edge, Safari, or Chrome, and offers to paste a share link instead.\n- **Agents can link several documents.** The API now takes a document type when linking, lists every linked document, and removes one document at a time instead of all of them.\n- **Google Drive asks before replacing a document.** Picking a file of a type you already linked now asks whether to replace it or link it as another document.\n- **Plan page for admin teammates.** The plan and billing card now shows for members with the admin role, not only the account that first connected GitHub, so a teammate granted admin access can see and manage the plan. Multi-org admins keep the setup card until org-labeled billing ships.\n\n---\n\n## August 2026\n\n### Fixes\n\n- **First-run Plan is a GitHub setup card.** With no organization, Plan no longer says billing is unavailable. Install the GitHub App, then Activate. Company, Settings, and API keys use the same setup card.\n- **Origin summary link on later reviews.** A later Origin review links back to the current summary. GitHub reviews still use the comment permalink.\n- **Origin report-an-issue link.** Origin reviews point the Tally report field at the Origin PR URL, not github.com. GitHub reviews are unchanged.\n- **Origin first review.** A first Origin review still posts when the install cannot list existing reviews.\n\n### Features\n\n- **Public-repo fair use.** Public repositories stay free, with a limit of 500 reviews per organization per month. Extra public reviews resume the next calendar month. Private reviews are unchanged.\n- **NSW and Victorian security-policy packs in the picker.** You can select the NSW Cyber Security Policy and Victorian Protective Data Security Standards, and a search for ASD ISM finds the Australian ISM.\n- **Japan frameworks in the picker.** Reviews can now target Japan's APPI, the My Number Act, METI cybersecurity management guidelines, and JIS Q 27001.\n- **Australia and New Zealand frameworks in the picker.** Reviews can now target the Australian ISM, APRA CPS 234, the New Zealand Privacy Act 2020, and NZISM.\n- **Automotive and related frameworks in the picker.** Reviews can now target ISO/SAE 21434, UN R155, HITRUST, Korea's ISMS-P, and Singapore's MTCS.\n- **Your commitments, cited in the review.** Reviews can now cite how your own organization implements a control. Fill the commitments card on the Company page, or send rows via the API, and a finding says your rule, not just the control number.\n- **On-demand spend cap.** Paid plans can set a monthly dollar limit on extra private reviews. The console warns at 80 percent. Reviews pause at the cap with a neutral GitHub check. Public repos stay free.\n- **Connections.** See GitHub and Origin in one place. Adding Origin attaches it to the same organization.\n- **Included with ISMS Copilot.** On an ISMS Copilot Standard, Pro or Business plan? heyGRC is included: 100 private reviews a month on one org. Activate it on the Plan page with the same account.\n\n\n- **Console language.** Set the language of the heyGRC dashboard in Settings, in English, German, Spanish, French, Italian, Dutch, or Polish. This is your interface language, separate from Review language, which sets the language of the GitHub review comments.\n- **Claim an Origin install in the console.** After you install heyGRC on Cursor Origin, `/setup` claims that install the same way GitHub does.\n- **Cursor Origin reviews.** Native Origin repos can get the same heyGRC pull request review as GitHub. Repos mirrored in from GitHub stay on GitHub.\n- **Upgrade to a higher plan in the console.** Paid organizations can move from Starter to Pro or Business without opening the Stripe portal.\n- **Review language.** Settings and `/v1/config` can set GitHub compliance review comments to English, German, Spanish, French, Italian, Dutch, or Polish. Control IDs and the heyGRC check name stay English.\n\n### Improvements\n\n\n- **See when you haven't run a review, and when a payment needs attention.** The console now nudges you to connect a repo and run your first review, and flags a failed payment with a link to update your card.\n- **See spending limits before you upgrade.** Free and trial organizations can now see on the Plan page that paid plans support a monthly spend limit for on-demand reviews.\n- **Console sidebar.** Reviews, company context, settings, plan, and API keys stay in a left nav, and Home is reviews plus GitHub install instead of the old card stack.\n\n- **Quieter PR reviews by default.** Inline comments are high and critical only; medium, low, and info stay in a short summary. Clean PRs no longer get an empty sticky comment (the green check-run is the signal). A shadow severity pass logs unverifiable highs for later tuning without changing placement yet.\n\n### Features\n\n- **Sign in with GitHub.** You can create a heyGRC console account, or sign back in, with your GitHub account, alongside Google, Microsoft, and email.\n\n- **Connected repositories on Reviews.** After you install or change GitHub repo selection, Reviews lists those repositories before the first pull request.\n\n- **COBIT 2019 in the framework picker.** The console catalog includes COBIT 2019 alongside the other shared frameworks.\n\n## July 2026\n\n### Features\n\n- **Plan ladder on the console.** The console shows Starter, Pro, and Business private-review allotments with tiered checkout.\n\n- **On-demand reviews (opt-in overage).** Paid plans can allow extra private reviews beyond the included allotment when on-demand is enabled in the console.\n\n\n### Improvements\n\n- **Framework picker lists the full registry.** The console framework catalog includes every framework heyGRC knows (was stuck at an older 79-entry dump).\n\n### Privacy\n\n- **Uninstalling removes your stored account name.** Removing the heyGRC GitHub App now clears the GitHub account name held on an unclaimed installation record.\n\n### New\n\n- **Install the GitHub App first; claim the console later (dev).** Installing heyGRC on GitHub is enough for default-framework PR reviews under free/trial limits. Creating a heyGRC account later **claims** that installation (history and quota kept). Soft-landing signup still finishes the claim; marketing primary CTA stays **Get started** until this is proven in production.\n\n- **EU inference (opt-in).** Organizations can turn on EU inference in console Settings so compliance reviews are processed by Mistral on the EU regional endpoint (zero retention, no silent fallback to global models). Default path is unchanged. Large PRs on the EU path use a smaller review budget and may be marked partial more often. Platform kill-switch + evaluation gate apply before this is fully live.\n\n- **Public review counter for heygrc.com.** The marketing homepage can now show a live all-time count of compliance reviews run (platform total, including dogfood). Backed by a read-only public aggregate RPC; no per-org data is exposed.\n\n- **One summary per pull request, updated in place.** heyGRC no longer posts a new summary comment on every push. Each PR now gets a single summary that updates as you push, and a separate short review only when genuinely new findings appear; unchanged re-runs stay silent apart from the check run. A `/heygrc` mention that finds nothing new confirms completion with a reaction on your comment. Thanks to the customer who reported the noise on collaborative PRs.\n\n- **Dark mode.** The heyGRC console now follows your device's appearance automatically, and you can pin Light or Dark under Settings > Appearance.\n\n### Fixes\n\n- **Finish setup when you install from GitHub first.** If you install the heyGRC GitHub App before you have a heyGRC account, you now land on a clear “Almost there” step to create an account or sign in, instead of losing the install. Primary buttons on heygrc.com say **Get started** and open console signup first; you connect GitHub from the dashboard next.\n\n- **Connect heyGRC to a GitHub organization.** Setting up heyGRC on a GitHub organization now works end to end: install the app, choose your repositories, and continue straight to picking your compliance frameworks. Previously, connecting on an organization account could stall after repository selection, or show a \"you must be the GitHub owner\" message even when you were an admin. Any repository admin can now complete the connection.\n","byteLength":20973}