Summary: the pub-mcp program and extension do not send your data to the developer or any third party. Your data is processed on your own computer; it goes only to Naver (the blog you asked it to write to) and, if you ask your agent to use an image link, to that image's address. If you contact the developer yourself, that message is handled as described under "Contact and support" below.

The pub-mcp browser extension ("the extension", currently working with Naver Blog only) works together with the pub-mcp program that you run on your own computer ("the local program").

What the extension handles

• The content of posts that your AI agent asks it to write (title, body, images, tags), received from the local program and typed into the Naver Blog editor in your browser.
• The names and numbers of your blog's categories (up to 200), read from the Naver editor in your browser when your AI agent asks for the category list or a post names a category. The local program keeps them in your own data folder and passes the list to your AI agent so it can choose one or ask you. After 24 hours the list is read again on the next request and overwritten; otherwise it stays on your computer until you delete the data folder (for example with pub-mcp uninstall --purge-data). They are not sent to the developer.
• The Naver Blog ID of the account you are logged in with (read from the Naver Blog page you have open) and your logged-in state, to tell the local program which account is connected.
• The list of your existing posts on Naver Blog (title, address, post number, time, and whether each is public or private), read from your own blog with your logged-in session, to check that a post was saved or published and to avoid duplicates.
• A small structural snapshot of the Naver editor page (tags and layout only, text removed, about 4 KB) that is passed to the local program when the editor does not look as expected, for troubleshooting.
• A random installation ID, the job in progress, pending results, and the last error, kept in the browser's local extension storage (chrome.storage.local) so work can resume after a restart.

What it does not do

• It does not send any data to the developer or to any third party. There is no developer-operated server, no analytics, no advertising, no tracking.
• The extension code never reads or stores your Naver password or cookies. When it reads your own blog pages, the browser sends your Naver cookies to Naver as usual, exactly as when you browse.
• It does not sell or share data, and does not use data for purposes unrelated to its single purpose.
• It does not run remotely hosted code.

Where data goes

• Between the extension and the local program: only on your computer, through Chrome Native Messaging.
• To Naver: the post content that you asked your agent to write is entered into blog.naver.com in your logged-in browser, exactly as if you typed it. Naver's own privacy policy applies to that.
• The local program keeps its records (accounts, posts, job history) in a database file, and copies of images your agent supplies in a media folder, inside your user data folder. pub-mcp does not upload them anywhere except as part of the post you asked for.
• Images: if your agent gives the local program an image link, the local program downloads it from that address (a normal web request from your computer to that site). If your agent names a file on your computer, the local program reads that file to attach it to the post. (Your AI client, such as Claude, has its own privacy policy for what you tell the agent.)
• Image records: If your agent passes an image's source address and licence note, the local program stores them in its records in your user data folder. They are not sent to the developer.