Privacy Policy

1. Privacy-First Design

LinkedOut is built with your privacy as a core principle. We do not track your identity, we do not log the LinkedIn posts you read or analyze, and we do not sell or share your personal information with any third party for advertising or profiling purposes.

Where we do collect data — such as anonymous diagnostic and usage information described below — it is used solely to improve the reliability and quality of the extension, and never to identify you personally.

2. User Data Collection

We collect the minimal data necessary to function and improve LinkedOut. We do not collect any personal identifier data (such as names, email addresses, or LinkedIn credentials). The data processed includes:

  • API Keys: You provide API keys for third-party AI services (Google Gemini, Anthropic Claude, OpenAI) to run the analysis.
  • Extension Settings & Preferences: User configuration selections (e.g., chosen AI model, theme settings, and custom persona settings) are stored to maintain extension behavior.
  • LinkedIn Post Content: The text content of the LinkedIn posts you choose to inspect or analyze.
  • Anonymous Diagnostic & Usage Data: We may collect anonymous interaction data (button clicks, features used, extension version, error reports, and classification summaries) to monitor reliability and system performance.

We do not collect passwords, personal identities, email addresses, or connection lists.

3. User Data Handling and Usage

We handle and process your data under a strict privacy-first model:

  • API Keys: API keys are processed client-side strictly to authenticate requests sent to the respective AI providers.
  • LinkedIn Post Content: Post text is read dynamically when you request an analysis and sent directly to your chosen AI provider. We do not store, log, or read this text on our own backend.
  • Usage Analytics: Diagnostics and usage metrics are processed anonymously for troubleshooting and application development.

4. User Data Storage and Retention

We govern user data storage and retention with security-first practices:

  • Browser Storage: API keys and extension preferences are stored solely in your browser's local sync storage (chrome.storage.sync). We do not have access to this local storage, and the keys are never uploaded to our servers.
  • Temporary In-Memory Storage: LinkedIn post text is held temporarily in-memory during the analysis process and is discarded immediately after execution. It is never stored.
  • Retention: Local settings persist until you remove them or uninstall the extension.

How it works (with code):

// 1. Stored strictly in local browser sync storage (Popup)
const handleSave = useCallback(async () => {
  await chrome.storage.sync.set({ linkedout_settings: settings });
  setSaved(true);
}, [settings]);
// 2. Retrieved locally and sent directly to the AI providers (Background script)
const activeKey =
  settings.provider === "gemini" ? settings.geminiKey
  : settings.provider === "claude" ? settings.claudeKey
  : settings.openaiKey;

// Directly initialized client-side:
const genAI = new GoogleGenerativeAI(activeKey);
const model = genAI.getGenerativeModel({ model: "gemini-3.1-flash-lite" });

Inspect it yourself:

You do not have to trust our word. You can verify this independently at any time:

  1. Open Chrome DevTools inside the extension popup or by inspecting the extension's background page / service worker.
  2. Navigate to the Network tab.
  3. Trigger an analysis or save your settings.
  4. Verify that the only outgoing requests containing your API keys are sent directly to the official endpoints of your AI provider (e.g. Google's generativelanguage.googleapis.com, Anthropic, or OpenAI). No keys are ever sent to our backend.

5. User Data Sharing and Third-Party Disclosures

We do not sell, rent, trade, or share your data with advertisers, data brokers, or any unauthorized third parties. Data sharing is limited to:

Third-Party AI Service Providers: The extension transmits post content to your chosen AI provider (Google, Anthropic, or OpenAI) using the API keys you provide. Your interactions are subject to their respective privacy terms. We encourage you to review them:

6. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the date at the top of the page. Continued use of the extension after any changes constitutes your acceptance of the updated policy. We encourage you to review this page periodically.

Last updated: July 2026