Perch Privacy Policy

Last updated: 7 July 2026

Perch ("the extension") is built to be private by design. This policy explains exactly what it does and does not do with your data.

The short version:

What Perch stores, and where

When you click Sync, Perch reads your own X (Twitter) bookmarks and/or home timeline (For You and Following) using your existing logged-in session, and stores them in your browser's local IndexedDB database on the extension's own origin. This includes post text, author, timestamps, engagement counts, media URLs, and topic tags Perch generates.

Optional auto-sync

You can turn on "Auto-sync on x.com," which quietly refreshes your local library while you are browsing x.com (roughly every 15 minutes). This runs entirely on your device using your own logged-in session; nothing is sent anywhere. It is off by default and can be toggled off at any time.

Optional AI features (bring your own key)

Perch's AI features (Ask your library, Research report, Extract resources, Digest, Smart-tag, and the semantic search index) are off by default. They only work if you add your own API key for Anthropic, OpenAI, or OpenRouter, or point Perch at a local model on your own machine (Ollama / LM Studio).

When you run an AI feature, the relevant post text is sent directly from your browser to that provider's API using your key. With a local model, the text is sent only to that server on your own machine and never leaves your computer. Perch does not proxy, log, or store these requests. Your use of those providers is governed by their own privacy policies:

Access to the AI providers is requested only when you first configure AI, the extension does not hold that permission unless you opt in.

Permissions, and why they're needed

What Perch does NOT do

Changes

If this policy changes, the "Last updated" date above will change and the new version will ship with the extension.