Clip Architect Back to Clip Architect

Privacy policy for the Clip Architect application

Applies to Clip Architect for Windows  ·  Last updated 26 August 2026

Clip Architect is a desktop application that runs entirely on your own computer. It has no account, no sign-in and no server behind it. This policy describes what the application does with data, what it sends out and to whom, and what it deliberately does not do.

The short version

The developer of Clip Architect receives nothing. There is no server operated by us that the application talks to, no account to create, and no analytics, telemetry or crash reporting of any kind inside it.

What the application sends out, it sends only to the service you chose and configured with your own key: your text goes to your AI provider, your search terms to the stock footage library you picked, your narration to the speech engine you picked. Everything else — your files, your renders, your settings — stays in a folder on your computer.

There is a way to run it that contacts nobody at all: your own video files, plus a locally installed language model, plus no cloud speech engine.

Who is responsible

Clip Architect is published by Dragan Florin, an independent software developer trading as Diflowrin, based in Arad, Romania. Diflowrin is a trading name, not a separate company.

There is no Data Protection Officer. The application is made by one person, and that person answers privacy questions directly at the address above.

This policy covers the application. The website that hosts this page has its own, separate policy, which covers the contact form, comments and server logs: diflowrin.com/privacy-policy.

What stays on your computer

The application writes everything it keeps into a single per-user folder, which on Windows is %LOCALAPPDATA%\com.cliparchitect.desktop. That folder holds:

None of that is transmitted to the developer, and none of it is transmitted anywhere except as described in the next section. You can delete any of it at any time, and deleting the folder resets the application completely.

Your API keys

Keys you enter are stored in config.toml in that folder, in plain text, because the application needs to read them back to make requests on your behalf. They are never sent anywhere except to the service each key belongs to, as authentication for requests you asked for. Treat that file the way you would treat any file holding a credential. The application ships with no keys of its own and does nothing at all until you supply your own.

What leaves your computer, and where it goes

Every outbound request is made because you started a render, and every one goes to a service you selected in Settings. There is no intermediary: requests go from your machine directly to the provider.

The subject or script you type
To the AI provider you configured, to write the script and the footage search terms. OpenAI · Anthropic · Google · DeepSeek · Qwen · Moonshot · xAI · Groq · OpenRouter · others
The generated search terms
To the stock footage library you chose, to find clips. Their servers also see your IP address while the clips download. api.pexels.com · pixabay.com/api
The narration text
To the speech engine you chose, to be spoken. Edge TTS and Azure Speech are Microsoft services; ElevenLabs is its own company. Edge TTS (Microsoft) · Azure Speech (Microsoft) · ElevenLabs
Nothing else
Your video files, your music uploads, your renders and your settings are never uploaded. The cutting, subtitling and encoding are done by FFmpeg, on your machine.

Each of those providers is an independent controller of what you send it, under its own terms and its own privacy policy. Choosing one is your decision, and reading its policy before sending it anything is worth the five minutes. Links are listed further down.

The route that contacts nobody

If you render from video files already on your disk, and use a language model running locally on your own machine through Ollama, and do not use a cloud speech engine, then no request leaves your computer at any point. It follows from the options you picked rather than from a setting you have to find.

What the application does not do

Each of these can be checked rather than taken on trust. The source code is public under GPL-3.0 at github.com/diflowrin/Clip-Architect, and each of these can be checked there.

The Microsoft Store

If you installed Clip Architect from the Microsoft Store, Microsoft collects data about that acquisition, and may collect diagnostic and crash information from your device, under its own policy and its own settings — not under this one, and not through anything the application does. See the Microsoft Privacy Statement. We receive from Microsoft only the aggregate figures any publisher sees in Partner Center, such as how many times the app was installed. Those figures identify nobody.

Third-party services you may configure

None of these are contacted unless you choose them and supply a key. Their policies govern what they do with what you send.

Children

Clip Architect is a production tool for a general audience. It is not directed at children, it does not knowingly collect anything from anyone, and it has no account system through which a child's data could reach us.

Your rights under the GDPR

The developer does not receive, store or process any personal data through this application, so there is no file held about you to request access to, to correct, to export or to have erased.

Where your own use of the application involves sending personal data to a provider you configured, that provider is the controller of it, and the rights above are exercised with them. Data held on your own computer is under your control and can be deleted by deleting the folder named above.

If you have contacted us by email or through the website, that correspondence is covered by the website privacy policy, which sets out the legal bases, retention periods and your right to complain to the Romanian supervisory authority, ANSPDCP.

Retention

There is nothing held on our side to retain. On your own machine, settings, projects, cached footage and renders are kept until you delete them; the application does not expire or remove them on its own. Uninstalling removes the application, and deleting %LOCALAPPDATA%\com.cliparchitect.desktop removes everything it kept.

Security

Requests to providers are made over HTTPS. The application's backend listens only on the loopback interface, 127.0.0.1, on a port chosen at launch, so it is not reachable from your network or the internet. Your keys are stored unencrypted in your own user profile and are protected by your operating system's account permissions rather than by a passphrase; if that is not sufficient for your situation, use keys scoped and limited at the provider.

Changes to this policy

If the application ever starts doing something this page does not describe, this page changes first, and the date at the top changes with it. There is no mailing list, so checking that date is how you tell whether anything has moved.

Contact

Questions about this policy, or about anything the application does, go to admin@diflowrin.com or through the contact form. If you think the application does something this page fails to disclose, say so and it will be corrected — the source is public, so the claim can be settled either way.