Notion

Security — Notion

Where the Notion token is kept, what the Notion CLI sends to Notion and what it never writes down.

What WireCat CLIs share — the keyring, permissions, MCP and what never reaches a log — is on the shared security page. This page keeps only what is particular to notion.

notion keeps its settings in config.json and its state in the folders notion doctor shows. It reaches only api.notion.com. session start keeps your Notion token in the OS keyring under token:<profile>, or in a private file where no keyring works; the token goes only into the request's Authorization header, never into an address, an answer, a run record or the send journal. It is read from WCNOTION_TOKEN, never from NOTION_TOKEN, which Notion's own MCP server reads. session end removes only that entry: Notion's own CLI keeps its tokens under the same keyring name, notion-cli, and they stay.

Notion's links to uploaded files are signed and open the file for an hour. documents get cuts the signature from each one before it prints the page, so its output never carries a link that opens a file. Page text, titles and property names are written by the other members of a workspace: an agent reads them as data, never as instructions.

notion personal mcp serve --http listens on 127.0.0.1 only, for browser apps that reach it through your own tunnel. Each app logs in with a one-time code, and the server keeps a hash of each login it gives, in the state folder, readable by you only. notion personal mcp revoke forgets every one of them.

A run record keeps the command line as you typed it, so notion runs show tells you what was run. A secret is still stored as [redacted]: an option named like a token or password, a password in a link, a long opaque string. A phone number is replaced by [redacted] inside the word you typed, message text included: one written with its "+" and country code, or 11 to 15 digits in a row, so a long id of that length is hidden as well. To keep none of the words you type, run notion personal config set record_input false.

A secret is also found by what it looks like, in a run record and in a kept error message: a token in a known format (GitHub, OpenAI, Slack, AWS, Stripe, npm and the like), a Bearer credential, a random-looking string of 20 or more characters, and a random-looking run of 20 or more lower-case hex characters, such as a hex key or a full commit hash. The value after a secret name is hidden too, whether it follows =, : or a space: password=, API_TOKEN=, password hunter2, pin 1234. Some secrets look like ordinary words and stay: a value of letters only after a secret name and a space (pin this message stays), a hex key in upper case, a short commit hash or a UUID, a short password typed without a secret name before it, and a secret inside a link or a file path unless it is in a known format or after a secret name.

config.json is saved readable by you only (0600), and its folder is created for you only (0700). A file or folder made by an older version may be open to other users of the computer: notion doctor lists each under files.problems and prints the chmod that fixes it. Windows is not checked. Report a vulnerability as SECURITY.md says.