Reduz is a bring-your-own-key Chrome extension operated by Three Things Media. Version 0.2.2 uses your chosen AI provider directly and keeps history in your browser. No sign-up or login is needed to use the extension. It makes no account, billing, or automatic backup requests.
What stays in your browser
Provider API keys, an optional YouTube Data API key, preferences, and custom prompts are stored in Chrome local extension storage. Summaries and source text are stored in a local SQLite database and files on Chrome's Origin Private File System. Reduz does not synchronize them through your Google account.
History may include titles, URLs, summaries, provider and model names, timestamps, token usage, source text, cleaned source text, and timestamped YouTube Moments. Browser-profile storage does not protect keys from someone who can read your profile on disk.
What goes to your AI provider
When you request a summary, cleanup, or Moments, the relevant text goes directly from the extension to the provider you selected: OpenAI, Anthropic, Google Gemini, DeepSeek, or xAI. Your key authenticates that request. The provider processes content under its own terms and privacy policy and bills API usage to you. Reduz does not receive the key or source text.
If you configure the OpenAI-compatible option, requests go to the endpoint URL you enter, using the API key you provide for it. You choose that endpoint and are responsible for trusting it.
Saving a summary image sends the completed summary to your provider to write an original headline. The PNG is then rendered locally. Repeated downloads may reuse the headline during the current extension session.
Optional source checking (Jev)
If you add an optional Jev verification key, Reduz sends the finished summary and the most relevant source passages to api.typesafe.ai so claims can be checked against the source. TypeSafe processes that content under its own terms and privacy policy. Remove the Jev key in Settings to disable this. Reduz does not receive a copy of it.
Pages, PDFs, and YouTube
Reduz reads a page when you request a summary. It requests temporary PDF-origin access when needed. YouTube captions are read from the selected watch page; an optional YouTube Data API key enables direct requests to Google for video metadata. Reduz does not continuously collect browsing activity.
Exports and deletion
History can be exported as JSON or Markdown ZIPs. Individual results can be exported as Markdown, PDF, DOCX, or PNG. Exports are generated locally and never include API keys. Settings lets you clear history and remove keys. Export a copy before uninstalling the extension or clearing browser data. Local history does not automatically move between browser profiles or computers.
Earlier versions
Earlier versions offered accounts and encrypted remote backup. Updating to 0.2.0 preserves local history and removes obsolete account state and backup keys from the extension. The legacy Reduz backup database was deleted on September 18, 2026. Remote backups can no longer be restored; local history in your browser is unaffected.
The website
reduz.app serves static product information. It does not accept source documents or run AI requests. A theme preference is stored locally in your browser. The hosting provider may process ordinary request metadata, such as IP address and user agent, to deliver and protect the site. See our cookies policy for browser-storage details.
Analytics and advertising
Reduz does not collect analytics in the extension, sell user data, or use content for advertising or cross-context profiling. No analytics or advertising scripts are included in this website.
Contact and your rights
Three Things Media, Postfach 101015, DE-85010 Ingolstadt, Germany. Contact support@reduz.app for privacy questions or requests concerning earlier server-side records. Where applicable, you may request access, correction, deletion, restriction, or portability of personal data, and complain to a supervisory authority.