Social Archiver: Privacy Policy (Firefox extension)

What the extension sends, and when
- Pages you choose to archive: the page URL, and for clips the extracted title, text, author and date, are sent to Social Archiver's API (social-archiver-api.social-archive.org) only when you archive or save a clip.
- Saved-post imports (Instagram, Reddit, X): when you start an import, post metadata (URLs, IDs, text, media URLs, timestamps) from your logged-in session is sent to Social Archiver for archiving. Cookies, authorization headers and other session credentials are never sent to our servers.
- Sign-in: your email address (email link) or a device-pairing code. The extension stores an auth token locally to keep you signed in.
- Usage diagnostics: only if you allow "technical and interaction data" when installing. You can change this in Firefox's add-on permissions and turn diagnostics off in the extension's settings. Diagnostics are event names and coarse states (platform type, success or failure, latency bucket, extension version). They never include page URLs, page titles, selected text, clipped content, cookies, tokens or email addresses. Social Archiver may forward this privacy-filtered event data to Amplitude for product analytics.

What it does not collect
Browsing history, page visits, keystrokes or form data, or data from pages you do not archive.

Local-only features
Reader mode, Clip to Obsidian, Markdown downloads, and the optional Local Media Helper and Immich connections process data on your device or send it only to destinations you configure (your Obsidian app, your own Immich server, a helper running on your computer).

Storage
Local data (settings, recent archive history, auth tokens) stays in Firefox's extension storage. Archived content is stored on Social Archiver's servers (Cloudflare). All transmission uses HTTPS.

Deletion
Remove the extension or clear its data to delete local data. For server-side deletion, contact support@social-archive.org.

Full policy: https://social-archive.org/privacy