Is Save ChatGPT to Notion safe?
Save ChatGPT to Notion sends failed Notion-save payloads and user identifiers to chatgpt2notion telemetry.
When Notion block appending fails, the extension posts error details to chatgpt2notion telemetry. For invalid URL failures, that telemetry includes the full Notion block payload generated from the ChatGPT conversation, along with a client ID, stored subscriber or Notion email when available, and save metadata.
Who publishes itorg - 6 other listings from the same operator, 2 of them carrying a finding
org - 6 other listings from the same operator, 2 of them carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
6 other listings published from this account, 7k+ users between them. 2 of them carry a finding.
Shared hosts - 3 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Findings
Notion append failures send ChatGPT save payloads to telemetry endpoint
When a Notion append fails while saving a ChatGPT chat, the extension can send the failed block payload and user identifiers to nodeapi.chatgpt2notion.com: DOM content, page URL, title, and stored IDs like client ID or Notion email.
- Severity
- Medium unwanted
- Type
- Unexpected
- CWE
- CWE-359
- Source
- Dynamic sandbox
A user starts a Save ChatGPT to Notion action and the Notion append operation fails.
The extension builds a failure log that can include the generated Notion block payload, user identifiers, and save metadata, then posts it to the chatgpt2notion telemetry endpoint.
- ChatGPT conversation contentQuestion and answer text from the saved chat (illustrative)
The failed Notion block payload can contain conversation text generated from the ChatGPT page.
- Current page URLhttps://chat.openai.com/c/example-chat (illustrative)
The request can include the page address associated with the save action.
- Page titleChatGPT - Project notes (illustrative)
The request can include the visible title of the ChatGPT page being saved.
- Stored user identifiersuser@example.com (illustrative)
The request can include a generated client ID or subscriber or Notion email read from extension storage.
Where it sends data
Destinations our analysis observed Save ChatGPT to Notion contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- nodeapi.chatgpt2notion.com
Save ChatGPT to Notion sends data to nodeapi.chatgpt2notion.com. 2 other extensions we have analysed send data here.