Privacy,
in plain language.

1. Who we are and what this covers

Clipse is an independent Chrome extension developed by Nicolas Delahousse. It summarizes user-selected YouTube videos from their captions and lets you save, search, and revisit those summaries.

This policy covers the Clipse extension and this website, clipse.delahousse.xyz. For questions about our handling of information, contact delahoussenicolas@gmail.com.

2. Information the extension handles

API keys and preferences

You can enter an OpenAI API key and, optionally, a TypeSafe API key. Clipse stores these keys locally using Chrome’s extension storage and sends each key only to its corresponding provider to authenticate requests. It also stores your model choice, caption and output languages, summary length, category definitions, and onboarding preferences. API keys are not included in summary-history exports.

YouTube captions and video information

For videos you ask Clipse to summarize, it reads available captions and relevant metadata such as video identifiers, URLs, titles, channel names, duration, caption languages, and caption-track information. YouTube content scripts also read page and video-card information needed to display the summarization controls and identify the correct video. Clipse does not record your camera or microphone, capture video frames, or analyze visual demonstrations.

Saved summaries and processing state

Clipse stores generated summaries, takeaways, timestamps, supporting caption excerpts, classification results, generation preferences, and creation dates in your Chrome profile. It also stores job status and relevant tab/video context to manage and recover processing. The extension does not upload your saved library to a Clipse account or developer-operated server.

How this information is used

Information is used to provide the features you request: retrieve captions, classify and summarize videos, display and revisit results, manage jobs, save your preferences, and export or restore your library. Clipse does not use this information to build advertising profiles, sell data, or determine creditworthiness.

3. What goes to AI providers

AI requests use HTTPS and your own provider accounts. Clipse does not control those providers’ retention, account settings, or processing practices. Deleting data in Clipse does not delete information a provider has already received. Consult OpenAI’s privacy policy, OpenAI’s API data controls, TypeSafe’s privacy policy, and Google’s privacy policy for their practices.

Provider processing may take place outside your country, including outside the European Economic Area. Applicable transfer arrangements and retention controls depend on the provider and your account terms. Do not submit content you are not permitted to share with the selected providers.

4. Browser permissions and access

Clipse’s YouTube host access allows it to add controls and read captions and video context. Tab access identifies the correct source video, opens or activates it when requested, and handles timestamp navigation. For caption extraction, Clipse may create a temporary muted video tab; it closes that tab when appropriate while preserving a tab you have activated or navigated elsewhere.

The side panel displays your library, summaries, and settings. Local storage retains preferences and results. Alarms and a packaged offscreen document support reliable background jobs and caption parsing. Clipboard access is used when you click Copy to copy a summary. Tab and video context are used for these features, not for unrelated browsing-history collection.

5. Retention, deletion, and security

Local settings and saved results remain in your Chrome profile until you change or remove them, remove the extension’s stored data, or uninstall the extension. Processing records may remain locally for job management and recovery.

• Delete summaries: delete an individual saved summary or use Clear all history in Settings. A deleted summary can remain temporarily available to the extension’s Undo feature; uninstalling or clearing the extension’s stored data removes the remaining local records.
• Remove keys: clear the corresponding key field in Settings and save. To stop using Jev, select OpenAI classification and clear the TypeSafe key if you no longer need it. Revoke a key in the provider’s account if you want to invalidate it.
• Remove all local extension data: uninstall Clipse or clear its extension storage. Clearing summary history alone does not remove API keys, preferences, or all processing records.
• Manage backups: exported JSON files contain summaries and source excerpts. You control these files and must delete downloaded copies and any copies you shared separately.

Network requests to the supported services use HTTPS. Keys are stored in Chrome’s local extension storage; Clipse does not add a separate encryption layer to that storage. Protect your browser profile and device, and avoid sharing API keys. No storage or transmission method can be guaranteed completely secure.

6. Website visits and support messages

This website is a static product and privacy site. Its pages do not ask for API keys or receive your extension’s captions, summaries, or saved history. The demo video, images, fonts, and scripts are served with the site; playing the demo does not load a YouTube embed. We do not add advertising trackers or analytics scripts to these pages.

The site is hosted through OpenAI Sites and Cloudflare. Hosting and security infrastructure may process ordinary request information such as your IP address, requested URL, browser information, request time, and security-related cookies or identifiers to deliver and protect the site. Infrastructure logs and retention are governed by the hosting services’ applicable policies and settings. See OpenAI’s privacy policy and Cloudflare’s privacy policy.

If you contact us by email, we receive the information you choose to send, including your email address and message. We use it to respond and keep relevant support correspondence only as needed to address the request and meet any applicable obligations. Please do not include API keys or sensitive transcript content in a support message.

7. Your choices and privacy rights

You choose whether to request a summary and which optional classifier to enable. You can change preferences, revoke API keys, delete local history, manage backups, or uninstall the extension at any time.

Where European or similar data-protection rules apply, processing necessary to provide the features you request is based on providing that requested service. Website security and responding to support messages rely on the legitimate interests of operating the site securely and assisting users. Optional provider processing is initiated by your choice to enable and use that feature.

Depending on your location and the applicable law, you may have rights to access, correct, erase, restrict, object to processing, or obtain a portable copy of personal information, and to complain to your local data-protection authority. Contact us to make a request. We generally cannot access data stored only in your Chrome profile; the extension’s export and deletion controls let you manage it directly. Requests about data held by OpenAI, TypeSafe, Google, or a hosting provider may need to be directed to that provider.

8. Chrome Web Store Limited Use

Clipse’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

We use and transfer extension data only as necessary to provide the disclosed summarization and library features, or as otherwise permitted by that policy. We do not sell extension user data, use it for personalized advertising, or use it to determine creditworthiness or for lending. The developer does not routinely receive or read your captions or summaries. If you voluntarily provide information for support, access is limited to addressing your request and any permitted security or legal needs.

9. Changes and questions

We will update this policy when Clipse’s practices change and revise the date above. Material changes that require additional disclosure or consent will be communicated through the extension or another appropriate channel before the changed processing begins.

For privacy questions or requests, contact Nicolas Delahousse at delahoussenicolas@gmail.com.