darrenFeed Lens privacy
Effective 22 September 2026 · Version 0.4.0
Feed Lens adds custom text labels to social posts. Requests go directly to your TypeSafe account. The project operates no relay server, telemetry or advertising system.
Data sent to TypeSafe
Enabled platforms send loaded post text, your label rules and the platform name directly to TypeSafe. This includes preloaded posts off screen, quoted text and non-public posts you can access. Your API key authenticates requests; usage is billed to your TypeSafe account.
Each post is limited to 12,000 characters. Names, mentions, links and sensitive information in its text may be included. Requests contain classification questions and model parameters; the recipient sees your IP address and ordinary network metadata. Test connection sends a built-in sample with the selected platform’s saved label rules and requires your API key; it works while auto-labeling is paused.
The extension analyzes extracted post text. It does not read image or video files, run OCR, collect private messages, unpublished editor text, screenshots, social account passwords, cookies or browsing history. It cannot identify every sensitive item contained in post text.
Local storage and exports
Your key, labels, platform switches and language are stored in chrome.storage.local in this browser profile, without Chrome sync. Only trusted extension contexts can access that storage. Exports contain labels, switches and language and exclude your key. Imports replace those settings after preview and confirmation. Exported files may contain personal text in your label descriptions.
Requests and up to 300 recent results are held in background memory. Deduplication keys include post text, rules and the API key. Settings changes or background termination clear the cache. Post text is not written to persistent extension storage.
Purpose and third party
Feed Lens uses this data solely for authentication and requested text classification. It does not sell data or use it for advertising, credit decisions or unrelated purposes, and follows the Chrome Web Store User Data Policy Limited Use requirements. TypeSafe independently handles received data under its own privacy policy, including retention, service providers and processing regions. Feed Lens cannot promise zero retention or delete data on TypeSafe’s behalf.
TypeSafe privacy policyYour controls
Pause a platform and save to stop its future requests. Clear key stops future requests across all platforms and removes local credentials. Settings are checked before sending and retrying; requests already sent cannot be recalled. Uninstalling removes extension storage; exported files remain where saved. Contact TypeSafe for deletion of data it holds.
Contact and updates
Send privacy and security questions to the maintainer at the address below. Keep credentials and private text out of public issues. Changes to data recipients or purposes will be reflected in this notice.