Privacy Policy

Overview

Post is a local-first desktop workspace. The browser extension processes content only after an explicit action, such as choosing an “Add … to Post” context-menu command or opening the extension popup to save the current page. Post does not operate a cloud account, advertising, analytics, or profiling service for the extension.

Information the extension processes

Depending on what you choose to save, the extension may process:

• Website content such as the current page URL and title, text, images, video links, author information, timestamps, and other public metadata required to create the saved item.
• User-entered information such as a title override, note, selected Tags, or a new Tag name.
• Local Post workspace context such as the active Vault identifier and name, Tag identifiers and names, Tag colors and ordering, and recently used Tags.
• Temporary operational state, including pending save details and error messages needed to complete or explain a user-requested action.

The extension does not read or retain your general browsing history. It does not monitor pages that you do not explicitly choose to save.

How information is used

Post uses this information only to:

• Show the relevant save controls, Vault, and Tags in the extension.
• Create or update the item you asked to save in your local Post Vault.
• Download user-selected media at the requested quality.
• Detect duplicates and report save or connection errors.

Post does not sell user data, use it for advertising, use it to determine creditworthiness, or transfer it for purposes unrelated to the extension’s user-facing collection workflow.

Where information goes

Collected content is sent through Chrome Native Messaging to the Post desktop app installed on your computer. The desktop app stores saved content in the Vault and local SQLite database you control. Post does not send that content to a developer-operated server.

When you save an X post or video, the extension may request public post or media information from X domains, including cdn.syndication.twimg.com and video.twimg.com. Your browser and those services may process ordinary network information under their own privacy terms. Post uses those requests only to resolve the public content you selected.

Local storage and retention

The extension stores the active Vault and Tag list, recently used Tag identifiers, and short-lived popup or error state in Chrome extension storage. This keeps Tag menus available when the desktop app is closed and helps complete user-requested saves. Session data expires or is removed after use. Cached extension data remains on your device until it is replaced, cleared in Chrome, or the extension is removed.

Saved assets remain in your local Post Vault until you remove them using Post or your normal file-management tools.

Chrome permissions

• contextMenus provides the user-triggered right-click save commands.
• activeTab and scripting read metadata from the active page only when you invoke a collection action.
• nativeMessaging sends the requested item to your local Post desktop app.
• storage keeps local Vault, Tag, recent-use, and temporary interface state.
• webRequest observes X media requests without blocking or modifying them so Post can locate the selected playable video.
• Host access to X, Twitter, YouTube, and related media domains is limited to extracting or resolving content you choose to save.

Your choices

Using the extension is optional. You control when a collection action runs and which item, Vault, and Tags are used. You can clear the extension’s stored data through Chrome or uninstall the extension. You can review and delete saved items locally in Post.

Children’s privacy

Post is not directed to children under 13, and the extension does not knowingly collect personal information from children.

Changes and contact

We may update this policy when the extension’s behavior changes. The effective date above identifies the latest revision. For privacy questions or requests, open an issue in the Post GitHub repository.