This policy covers one feature of the ViralDNA.io platform: ViralDNA Sync for CapCut, the tool at viraldna.io/capcut-sync that turns a folder of images and a list of timestamps into a CapCut project with the timeline already cut.
It has its own policy because it works differently from every other tool on the platform. Everywhere else, you upload a file and we store the result on your account. Here, the files never leave your computer at all, and we store nothing. The paragraphs below explain exactly what that means, field by field, so you can check the claim rather than take our word for it.
Everything else about your ViralDNA account, including sign-in, billing and the other tools, is covered by the Platform Privacy Policy. This document adds to it and does not replace it.
The short version.
Your images and your audio file are never uploaded, never transmitted, and never stored. Your browser reads them on your own machine and sends us only a small list of names, pixel dimensions and timings, typically a few kilobytes. We use that list to build a project file, hand you the resulting .zip, and keep no copy of it. There is no database record, no file storage, and nothing to delete afterwards.
When you select a folder, your browser opens each image locally to read its width and height, and reads the file name. Nothing is transmitted at this stage. When you press the download button, your browser sends us a short list describing the timeline. Our server uses that list to generate a CapCut draft, packs it into a .zip together with a small script, and sends the .zip back in the same response. The request is processed in memory and the response ends the transaction.
The reason your images stay put is not a courtesy, it is how the tool is built: a CapCut project references images by their location on your disk, so the actual image data is never needed on our side.
Exactly the following, and nothing else:
| Field | Example | Why it is needed |
|---|---|---|
| Image file names | 00-05.jpg | The script has to find the same files on your disk and CapCut references them by name. |
| Pixel width and height of each image | 1920 × 1080 | To compute the crop or fit scale for each clip. |
| Start time and duration of each clip | 5.0s → 6.0s | This is the timeline itself. |
| Audio file name and its length | voiceover.mp3, 45.0s | Only if you added audio, so the project length can follow it. |
| Name of the folder the images sit in | Edit 3 | The name only, never the path. The script uses it to find the folder on your computer so you do not have to type a path. |
| Project name, aspect ratio, frame rate, fill or fit | 0909, 16:9, 30 | The settings you chose on the page. |
| Interface language | English | So the instructions inside the package are written in your language. |
Because the request is made while you are signed in, it also carries your session, which tells our server which account is asking and whether that account is entitled to use the feature. That check reads your plan; it writes nothing.
A note you deserve rather than fine print: file names are text you chose. If you name a file after a person, a client or an event, that name is in the list we receive. We do not read, index, profile or retain those names, but if you would rather they never reach us, rename the files before you use the tool.
Nothing. The list described in section 2 exists only for the seconds it takes to build your package. It is not written to a database, not written to disk, not placed in a queue, and not copied into an analytics system. The .zip is generated in memory and streamed to you; we do not keep a copy of it, and it cannot be re-downloaded from us. Because we hold no record of your project, there is nothing for you to request, export or delete afterwards, and nothing that could be exposed in a future incident.
Two ordinary exceptions apply, and they are technical rather than about your content:
The .zip contains your project's draft files, a plain-text script, and a readme. Once it is on your computer it is yours, and this is what it does:
.vdna-yedek before updating it.Nothing in the package is licensed from, or communicates with, CapCut or its developer.
This feature sends no data to any third party. There is no analytics call, no advertising pixel and no external API involved in building your package. Our hosting provider necessarily processes the request in transit, and our authentication provider verifies your session, both as described in the Platform Privacy Policy. If you paid for a plan, that billing relationship is with Stripe and is unrelated to this feature.
If we ever change how this feature handles data, we will update this page and change the date at the top before the change takes effect. If a change ever meant that your images or audio would be transmitted or stored, we would say so in plain language on the feature page itself, not only here.
Questions about this policy, or about anything the package does on your machine: support@viraldna.io.