A short week on the site, and both changes are about the product telling you the truth instead of leaving you to guess. The extension has not moved, and there is a section at the end about what that means.
Opening a private report no longer looks like a broken link
Until this week, following a link to a report you were not signed in to see gave you a page that said nothing was there. That is technically accurate and practically misleading, because something was there, and the person who sent you the link knew it.
Now the page says so. It tells you the report is private, that it exists but only some people can open it, and who those people are: the person who filed it and the team that owns the site.
The part worth knowing is what happens next. Signing in from that page takes you to the report rather than dumping you on a dashboard, because the address you were trying to reach is kept through the sign-in. The link a colleague sent you still works; it just needed you to be somebody.
One deliberate detail: the page still answers with a 404 status underneath. A crawler or a script is told nothing about whether the report exists, and only the human reading the screen gets the explanation. The ambiguity that was protecting your reports is still doing its job.
Badge progress stops falling when old reports are purged
Reports do not live forever on the free plan, and when old ones are cleared out the count of what you have filed goes down with them. That is correct for storage and wrong for anything that was measuring what you have done.
The visible version of this was badges. Progress towards one could go backwards: you were eleven reports into a badge that needs twenty, and after a purge you were nine, with nothing you did causing it. The “to go” figure moved the same way.
Several things were reading the same decaying number. Badge progress is now counted from a total the purge cannot lower, so what you have filed stays filed. The same correction stops the “first report filed” moment from being treated as new again after a purge, which previously could fire a second time for somebody who had been using the product for months.
None of this changes what is stored or for how long. It changes what the product remembers about what you did, which is a different thing and the one that should not have been reversible.
What is actually in your hands
The site is released continuously, so everything above is live while you are reading it. There is nothing to update and nothing to install.
The extension has not changed. The Chrome Web Store is serving 1.11.0, published on 19 September, and that is what you have. Work has landed since then and none of it has been released, so the version number on our side is still 1.11.0 as well.
That is worth stating plainly rather than leaving implied. A release note that mixes the two leaves you wondering whether what you just read is waiting on an update you have not done, and this week nothing is.