Are data breach roundups subscriber only?

Meta
,
1

Two weeks ago, it seemed as though the roundups had been moved to being subscribers only but last week it was back to being available for everyone. I am just hoping to get some clarity on what the plan is for these posts.

1 Like
2

It appears that there is some A/B testing going on in the background for 2026 to determine if readers perceive the content to be valuable enough to provide their email address, so strictly speaking, the answer to your question is no.

3

No offence but, this is kind of a non answer. Obviously its not subscriber only currently as anyone can tell from last weeks post.

What I would like is a definitive answer from someone on staff, This way we are not relying on a guess. Even if it seems to be a reasonable explanation. :slightly_smiling_face:

Although, I have been told that staff does not have any obligation to actually provide an update so who knows…

1 Like
4

This week’s data breach roundup has reverted to subscribers only, so my previous observations have been revalidated.

5

Yeah, thats a bummer. Not sure why its appropriate to put content not everyone can access, in the general section of the forum.

1 Like
6

Hi, you can become a subscriber for free :slight_smile:

2 Likes
7

When did PG start doing personalized ads?

1 Like
8

Not sure what you are referring to.

1 Like
9

Must be my mistake :upside_down_face: promoting becoming a subscriber felt very ad adjacent, especially as it does not contribute to answering the post. :person_shrugging:

1 Like
10

Upon further inspection, it appears that the @privacyguides bot account has broken functionality and chronological order by posting about the data breach roundup from two weeks ago:

There is not a data breach roundup for February 27th - March 5th yet. I had grossly assumed that the bot was fully functional when it is not, so feel free to unmark my post as a solution.

11

Indeed, since it is not the 5th yet :slight_smile:

The Feb 19th post was incorrectly tagged on our blog, so the bot didn’t pick it up. Then I fixed the tags last week and the bot picked it up :laughing:

1 Like
12

There were not any GitHub commits from February 22nd to February 28th in any of the GitHub repositories, so how were the tags corrected?

13

All these news brief posts at Privacy & Security News are published in Ghost and not on GitHub.

1 Like