1. Who this policy covers
This Privacy Policy describes ClipForge Desktop 0.3.0 and these companion information pages. The Publisher is Théodore Groslière, based in France. For privacy questions and requests, contact groslieretheodore@gmail.com. Postal contact address: 77 rue des Martyrs, 75018 Paris, France.
ClipForge performs substantial work on your own computer. This policy distinguishes that local processing from information you choose to send to AI providers, social platforms, the website host or the Publisher. Operating the desktop app does not itself give the Publisher remote access to your projects.
If you use ClipForge for an organization or process other people’s content, you must also meet your own obligations toward those people. This policy does not replace their notices or permissions.
2. Information processed
| Category | Examples | Purpose and location |
|---|---|---|
| Media and edits | Imported videos, audio, source URLs, transcripts, word timestamps, sampled frames, cuts, captions, hooks, titles and descriptions. | Video analysis and editing, normally stored and processed on your computer. Selected data is transmitted when you enable an external feature. |
| Project records | Creator names and handles, rights notes, styles, manual statistics, export records, file paths and project history. | Organizing your library locally. Rights notes may contain personal information you choose to enter. |
| AI connection data | Provider selection, model IDs, API keys, responses, token counts and known cost calculations. | Connecting to the selected provider, creating suggestions and reusing received responses locally. |
| Social account data | TikTok account identifier, display name and avatar URL; YouTube channel identifier, title and avatar URL; granted scopes, connection dates and OAuth tokens. | Identifying accounts you authorize, maintaining the connection and performing the upload you confirm. Connection credentials are stored locally in encrypted form. |
| Upload records | Target account, video copy, caption, audience and disclosure settings, progress, status, platform video/post IDs and upload session details. | Preparing, transferring, resuming and tracking your chosen upload. Private transfer URLs are stored in the encrypted connection vault. |
| Diagnostics and contact | Application/runtime versions, error messages, tool status, log extracts, your email and information you choose to send. | Troubleshooting locally, or handling a request when you send it to the Publisher. A diagnostic export is created locally; it is not automatically emailed. |
| Website delivery | IP address, requested page, request time and browser/network information made available to the host. | Delivering and securing these pages. The hosting layer may also process access/authentication information for a private preview. |
ClipForge does not ask for TikTok or Google passwords. Authorization takes place with the selected platform in your browser. Do not put passwords or API keys into project notes or support messages.
3. Local processing and optional connections
Without an optional AI connection, transcription and editing can run locally. Importing from a source URL contacts the relevant source service. Downloading or updating tools and speech models contacts their distribution hosts, including GitHub and model distributors; those hosts receive normal network request information.
The desktop application is not a centralized cloud media library. Its default user-data location on Windows is %APPDATA%/ClipForge, although an imported or configured studio may use another folder.
Optional account and AI features are not necessary to use local editing. If you do not provide the relevant key or platform permission, those optional features cannot run.
4. AI providers and what is sent
When you choose AI analysis, ClipForge sends candidate transcripts, editing instructions and relevant context to the provider you select: OpenAI, Anthropic Claude or Google Gemini. If image analysis is enabled, sampled video frames are also sent. AI translation may send the full transcript in batches. ClipForge does not send the whole video file to an AI provider through its current analysis implementation.
Your key is used with the selected provider’s native API. A Claude or Gemini key is not routed through OpenAI. API responses and usage receipts may be cached on your computer to support resuming work without requesting the same received result again.
Providers process data under their own terms, account settings, service regions and retention arrangements. Free and paid offers can differ. ClipForge does not promise that a provider never retains inputs or uses them to improve its services. Check the applicable policy before transmitting confidential, sensitive or third-party material.
6. Purposes and legal grounds
Information is used to provide the editing and publishing features you request, keep your connections working, preserve project history, and handle support or privacy requests. Optional data is not required for unrelated features.
Where the GDPR applies to processing for which the Publisher is responsible, the relevant grounds are performance of the requested service or steps at your request, legitimate interests in responding to ordinary inquiries and maintaining security, consent where it is legally required for an optional use, and compliance with applicable legal obligations. Platform authorization permits a technical connection; it does not by itself establish consent from everyone appearing in a video.
The current desktop code does not send routine product analytics or advertising events to a Publisher analytics service. The Publisher does not receive your media through a central ClipForge backend, sell project data or use your projects to train a Publisher-operated model through this release.
7. Recipients and international processing
Depending on the features you select, recipients may include your chosen AI provider, TikTok, Google/YouTube, source-content hosts, tool/model distributors, and any person with access to your computer, synchronized folders or backups. Support information you send is received by the Publisher and the email provider used for that correspondence.
The contact address shown here uses Gmail, so Google may process correspondence. The public ClipForge information pages are intended for https://lucasstagnette.fr/clipforge/ on OVHcloud. See OVHcloud’s data protection information.
Some recipients operate outside your country or the European Economic Area. Their applicable arrangements may include adequacy decisions, standard contractual clauses or other legally recognized safeguards. The relevant provider can give details for your account and service. This notice does not assert that every transfer remains in France or the EU.
8. Retention and backups
- Projects and media: local source copies, transcripts, frames, exports and project records remain until you remove them. There is no automatic expiry of the whole local library. Cache cleanup may move items into a recoverable archive rather than immediately erase them.
- AI keys: session-only keys remain in engine memory until it stops. Remembered keys remain encrypted until you use the corresponding forget control or delete the user-data vault.
- OAuth connections: the active local credentials remain until disconnected, replaced or deleted. Provider-side authorization may outlast a local disconnection.
- Upload copies: frozen transfer files and sessions are retained while an upload is pending or interrupted. The application removes them after it confirms final availability or inbox receipt. Upload history can remain after that cleanup.
- AI caches and receipts: stored with the project to support resuming work; removing an active connection alone does not remove these files.
- Logs and database backups: logs and database copies rotate. Backups, recovery files and copies you make may retain older records after an active record is removed. Rotation is not a guarantee of deletion by a particular date.
- Support correspondence: For the time needed to answer the request, then up to six months after resolution, unless a legal obligation or an ongoing dispute requires a longer period. Verification documents, if exceptionally necessary, are removed after verification unless a specific legal duty requires retention.
- Website infrastructure logs: Operational access and security records are kept for the periods required by the applicable hosting service and legal obligations, or for the time needed to investigate an identified security incident. Records under the Publisher’s control are then removed or anonymized when no longer needed. OVHcloud may operate its own technical and security retention under the applicable hosting contract; contact the Publisher for the arrangements applicable to this website.
Third-party copies, including published posts and AI request records, follow the relevant recipient’s retention rules. The Publisher cannot erase a file stored only on your computer without your involvement.
9. Disconnect, revoke and delete
- Disconnect a social account: use Publier → Mes comptes → Déconnecter. This removes the active local account connection and its token. It does not automatically erase upload history, backups, exports or already published content.
- Revoke platform access: remove ClipForge or the OAuth application name you configured from the connected-app controls in TikTok. For Google/YouTube, use Google security permissions. Revocation and local disconnection are separate actions.
- Forget an AI key: select the provider in ClipForge settings and choose the disconnect/forget control. Revoke the key in the provider’s console if you want it invalidated there as well.
- Remove local data: close ClipForge and locate the current workspace and preferences through its File menu. Remove the relevant project/media files and local database records. For a full reset, after backing up anything you want to keep, remove the ClipForge user-data folder and any separate imported studios, recovery files or backup copies. This can permanently delete all local projects. Exported files stored elsewhere and external source videos require separate removal.
- Ask for help or exercise rights: email groslieretheodore@gmail.com with the connection or data concerned. The Publisher can address information it holds and guide local deletion; it cannot remotely delete your files or third-party posts. Do not send credentials. Requests are handled under the applicable statutory deadlines.
Removing the app alone preserves its user-data folder by default. To delete a published video or ask an AI provider to delete request records, use that provider’s controls or privacy request process.
10. Security
Remembered API keys, OAuth tokens, application secrets and private transfer sessions are encrypted using Windows account protection through Electron’s secure-storage facilities. Other local material, such as videos, transcripts, project metadata, AI caches and upload history, is not encrypted by ClipForge itself. Use device encryption and access controls where appropriate.
External API requests use HTTPS. The local app interface uses a loopback service with controls for local mutations. Diagnostics attempt to redact credentials, but review a report before sending it: file paths, content fragments or other personal information can appear in errors. No protection can eliminate every risk.
11. Website, cookies and tracking
These static information pages contain no advertising tags, analytics scripts, third-party fonts, embedded videos or contact form. Clicking an email link opens your own email software. Links to other services bring you under those services’ policies.
The hosting and access layer may process operational logs and use strictly necessary security or authentication mechanisms. A private preview may require a hosting-platform login. These mechanisms are separate from the ClipForge desktop application. The hosting provider may also derive operational visit statistics from server logs. This policy describes the static ClipForge pages; other pages on the same domain may use additional services described in their own notices.
12. Your rights and contact
Where applicable, you may request access, correction, deletion, restriction or portability of personal information, object to processing based on legitimate interests, and withdraw consent for future optional processing. The scope of a right depends on the information, processing and applicable law. Withdrawing consent does not change the lawfulness of earlier processing.
Contact groslieretheodore@gmail.com. We may request only the information reasonably needed to identify the relevant records and verify your request. Do not send identity documents unless a proportionate verification need has been explained.
You may complain to a competent data protection authority, including the CNIL in France, or the authority where you live or work. Your use of these controls does not waive any right to complain.
ClipForge is not designed to solicit children’s personal information. Do not use it to process or publish content about children without the necessary authority and safeguards. Contact us if you believe information about a child was sent to the Publisher improperly.
13. Policy updates
The revision date appears at the top of this page. Material changes to data purposes, recipients or user choices will be explained before the new processing applies, with additional notices or permissions where required. For questions about the current release or this policy, contact groslieretheodore@gmail.com.
5. TikTok and YouTube integrations
TikTok
After you authorize the connection, ClipForge reads the basic profile needed to label the account. Inbox uploads use the video-upload permission. If an eligible application and account authorize Direct Post, ClipForge additionally reads current creator publishing permissions and submits the publication settings you confirm.
The selected video is transmitted to TikTok. Inbox delivery requires finalization in TikTok; the current inbox endpoint does not receive the locally prepared caption. Copy it into TikTok yourself. Direct Post, where permitted, transmits the caption, visibility, interactions and applicable commercial/AI disclosures.
YouTube
ClipForge uses YouTube API Services. It requests upload access and read-only access to identify the authorized channel and track the uploaded video’s status. A confirmed upload sends the video, title, description, tags, visibility, audience setting and relevant disclosure/notification settings to YouTube. The integration does not automatically import your analytics; the current statistics feature is manual or CSV-based.
These platforms receive network information directly and apply their own policies. See TikTok’s applicable Privacy Policy and the Google Privacy Policy.