Privacy Policy
Effective date: April 1, 2026
Retitle rewrites YouTube titles into clearer factual titles. To do that, the extension and backend process a limited set of page and transcript data.
Data Retitle processes
- YouTube video ID
- Original YouTube title text
- Transcript text returned by YouTube when available
- A generated install identifier stored in extension local storage
- Generated replacement title and transcript metadata such as language code and whether captions were auto-generated
- Local extension settings such as whether retitling is enabled
What leaves the browser
When Retitle requests a title from the backend, the following data can leave the browser:
- video ID
- original title text
- install ID
- transcript text when the user-IP InnerTube attempt succeeds
- transcript metadata used to classify the result
The backend sends transcript or title context to OpenRouter to generate the final rewritten title.
What does not leave the browser
- Gmail, Google account, or Chrome profile data
- browsing history outside YouTube pages where the extension is active
- cookies, passwords, payment data, or form entries
Storage
Retitle stores the following locally in Chrome extension storage:
- install ID
- whether retitling is enabled
- quota pause state
- usage snapshot for degraded-status display
- short-lived pending submission and cooldown state
The backend stores:
- cached generated title results keyed by video ID
- failure classification and transcript metadata
- monthly usage counters keyed by install ID
Sharing and selling
Retitle does not sell personal information. Data is used only to provide the retitling feature and related quota/accounting behavior.
Retention
- Extension local storage remains until the user removes the extension or clears extension storage.
- Backend cache and usage records remain in the Worker D1 database until they are manually rotated or deleted.
Contact
For privacy questions, contact retitledev@gmail.com.