Veracity Privacy Policy
Last updated: November 19, 2026
Veracity is a Chrome extension that helps users review claims in YouTube videos and understand their content. This policy describes the data processed by the YouTube extension and its online features.
Information processed
Depending on the features you use, Veracity may process YouTube video identifiers, URLs, titles, channel names, descriptions, captions or transcripts, your questions and chat messages, generated reports and translations, glossary and learning data, settings and API keys that you provide. A learning profile, if supplied, may also be used to adapt explanations.
Local storage and files
Settings, API keys, video-related data, history, reports, chats, translations and learning data may be stored locally in your browser. If you select a folder, Veracity may also save and read documents and backups in that folder. Files saved there are separate from browser storage. Protect your device and your API keys; browser-local storage is not a dedicated secret vault.
Third-party services
When you use an online feature, Veracity sends the information needed for that feature directly to the relevant service. Depending on your settings and the feature, this can include video details, transcript excerpts or full transcripts, claims, search queries, URLs, chat messages and any learning profile you supply. Your API key is sent to the corresponding provider for authentication. For transcription or speaker identification, Gemini may receive the YouTube video URL and process the video. For translation or Gemini voice generation, the relevant text may be sent to Gemini. Browser or system voices can instead process speech locally.
- Google Gemini, OpenRouter, OpenAI, Anthropic and xAI: Depending on the feature and selected provider, the service may receive video metadata, transcripts, claims, source excerpts, questions, conversation excerpts, glossary terms or the optional learning profile. OpenRouter may also route requests to the chosen model provider.
- Serper, Jina Search, ScraperAPI and Google Fact Check Tools: The configured services may receive search queries derived from video claims and related search parameters.
- Jina Reader: To read a source, Veracity may send that page's URL to Jina Reader. This can occur without a Jina API key when a search service is configured.
- YouTube and Google: YouTube supplies video information and captions. YouTube thumbnail requests may also be made when showing video history.
These requests use HTTPS. API keys are sent to the provider they authenticate, including when testing a key. Providers process data under their own privacy policies and account settings; their retention and use practices may differ. See Gemini, OpenRouter, OpenAI, Anthropic, xAI, Serper, Jina, ScraperAPI and Google and YouTube.
Purpose
Information is used to retrieve and assess video content, search for sources, provide reports, answer questions, offer transcripts, translations and learning tools, and save or restore your work. Veracity has no advertising or advertising trackers, does not sell user data, and does not use it for advertising targeting or credit profiling. The information received from Google APIs is used in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Retention and deletion
Data stored in the browser remains there until you remove it using available controls or remove the extension and its local data. Removing the extension does not necessarily delete files you exported or saved in a selected folder; delete those files separately. Third-party providers apply their own retention periods and deletion procedures.
Your choices
The extension requests consent before its features are enabled. You can withdraw consent in its settings; this disables its features and removes optional service permissions. You can choose which features to use, which supported services and keys to configure, and whether to select a local folder. You can remove stored video data through available extension controls and remove or replace API keys in settings. Avoid submitting sensitive information in questions or learning profiles. Review the privacy policies of the providers you choose.
Changes and contact
This policy may change when Veracity changes. The date above identifies the latest revision. For privacy questions, contact the project through its GitHub issue page. Issues may be public; do not post API keys, transcripts or other sensitive information there.