4/19/2026 at 5:10:51 PM
Apparently this is officially documented at https://www.notion.com/help/public-pages-and-web-publishing#... buried in a note:> When you publish a Notion page to the web, the webpage’s metadata may include the names, profile photos, and email addresses associated with any Notion users that have contributed to the page.
by Tiberium
4/19/2026 at 5:46:30 PM
That's just ... absurd.The flaw itself is absurd but then just accepting it as "by design" makes it even worse.
by EMM_386
4/19/2026 at 6:33:14 PM
It's also trivially easy to fix. 1 min delete and deploy.by chinathrow
4/19/2026 at 7:33:03 PM
I'm guessing it's not trivial to fix without breaking other things? The weakness seems to be that anyone can turn UUIDs into details like email. But I assume this functionality is necessary for other flows so they can't just turn off all UUID->email/profile look ups. And similarly hiding author UUIDs on posts also isn't trivial.Conceptually, I agree it should be easy, but I suspect they're stuck with legacy code and behaviors that rely on the current system. Not breaking anything else while fixing this is likely the time consuming part.
by varenc
4/19/2026 at 8:24:22 PM
This is a rendering artifact, nothing more. If you can tokenize and protect PII on your platform, you can protect PII on your public pages. if (metadata.is_public)
Simple fix.
by reactordev
4/20/2026 at 2:46:09 AM
But a user's email isn't always forbidden. The API endpoint which turns UUIDs into a user email presumably also has use cases where you do want to expose the user email. For example, when seeing a list of people you've already invited via email to collaborate with, or listing users within your organization, etc. So a user's email isn't always forbidden PII, it depends on the context.The trouble is the UUID->email endpoint has no idea what the context is and that endpoint alone can't decide if it should expose email or not. And then public Notion docs publicly expose author UUIDs.
Their mistake was architecting things this way. From day 1 they should have cleanly separated public identifiers from privileged ones. Or have more bespoke endpoints for looking up a UUID's email for each of the narrow contexts in which this is allowed. They didn't do this, and they certainly should have, but fixing this mess is likely a non-trivial amount of work. Though I bet it could be done immediately if they really cared and didn't mind other things breaking.
I'm absolutely not defending their choice to expose emails in this way. They should have addressed this years ago when it was first reported, and I want them shamed for failing to care. But just trying to say it's likely not a one line fix.
by varenc
4/20/2026 at 11:55:10 AM
A users email should always be forbidden…It is not a public marker, it’s PII.
by reactordev
4/19/2026 at 7:43:41 PM
Of course they can fix it, come on.They can easily withold information they put out intenionally.
by chinathrow
4/19/2026 at 7:55:27 PM
The whole point of that comment is that it's not that easy. There are potential side effects and consequences that are difficult to architect around.by csallen
4/20/2026 at 2:18:45 PM
The fix IS easy. The side effects need to be dealt with accordingly. Why do you defend shit like this?by chinathrow
4/20/2026 at 1:36:37 AM
Except it is.If you can't easily architect around it, then don't do what you're trying to do.
"Oh I needed to disclose user data in order to make more money" isn't an acceptable excuse.
by markdown
4/20/2026 at 4:26:12 AM
No one's talking about excuses.by csallen
4/20/2026 at 2:19:14 PM
Looks like everyone does talk about excuses though.by chinathrow
4/20/2026 at 12:09:21 PM
> Oh I needed to disclose user data in order to make more moneyhmm maybe they should've paywalled?
by sysguest
4/20/2026 at 12:33:08 AM
You literally don’t know that. Add this to the mammoth file titled “HN comments in which the author makes some completely unsubstantiated technical claim”by UqWBcuFx6NV4r
4/19/2026 at 5:31:26 PM
This is, as a notion user with public pages, beyond stupid.by chinathrow
4/19/2026 at 8:34:15 PM
Don't attribute to stupidity what can be explained by malice.by ArchieScrivener
4/20/2026 at 5:55:10 AM
Yes! I’ve always maintained Hanlon’s razor needs to be reversed in matters of computer security.by sph
4/20/2026 at 6:24:16 AM
Theres just a higher form of malicious stupidity, where the people who own these platforms can be selectively, maliciously stupid where it comes to security.by protocolture
4/20/2026 at 5:29:14 AM
This phrase needs way more traction.by gib444
4/19/2026 at 6:54:54 PM
[dead]by huflungdung
4/19/2026 at 6:38:57 PM
Some CMSs do this in their RSS feeds as well. Can't recall which ones, but seen it.by mikae1