Movie Maker Edit

Privacy Policy

Last updated: August 9, 2026

Movie Maker Edit is built so that your footage stays yours. Editing, rendering and levelling all happen on your own computer. This page says exactly what leaves it, when, and why.

Who this covers

This policy covers Movie Maker Edit Pro v7.2.0, the Windows desktop application, however you bought it: the Microsoft Store, Gumroad or Lemon Squeezy. It also covers the free browser edition, described further down.

What stays on your computer

Your clips, your soundtrack, your narration scripts, your project files and your finished movies. Importing, trimming, transitions, the soundtrack, preview, rendering, sound normalization and burned captions all run locally and involve no network connection at all. Files are written only to the folder you chose as your repository, and your projects are ordinary .mmeproj files on your own disk.

Your API keys are stored on your computer only. They are sent to the provider they belong to and to nobody else. They are never sent to Iacoletti Software, never included in usage reporting, and never written into a project file.

The optional AI features

Three features use an artificial intelligence provider, on a key that you supply and pay for directly. They are off unless you enter a key, and each one shows what a job will cost before it sends anything.

• Reviewing your clips, and reviewing the finished film. Small still frames sampled from your clips, roughly 213 by 120 pixels, are sent to the provider you choose. Whole clips are never uploaded.
• Narration. The audio of a clip is sent for narrating.
• Spoken voice. The text you typed is sent to be spoken.

In this browser edition these calls are relayed by our own server rather than sent to the provider directly, so your key and the frames, audio or text being sent do pass through Iacoletti Software on the way. We do not store them, log them or keep them: the key is used for that one request and discarded, and nothing sent is written to disk on our side.

This is a real difference from the desktop edition, where the key never leaves your machine and we are genuinely not in the path. The reason is technical rather than chosen. The editor page runs cross-origin isolated so it can use every core of your processor when it exports, and that same browser setting blocks the page from calling xAI or Google directly, so the request has to be relayed by the site it came from.

What you send is governed by that provider's own privacy policy: x.ai/legal/privacy-policy and policies.google.com/privacy.

Burning captions into a film sends nothing: the narration script already exists and the text is drawn onto the picture on your own machine.

What we record about you

The application reports how it is used, so that faults can be found and fixed and so that support can identify your licence. It never includes your video, your audio, your narration scripts, your typed text, or your API keys.

• Your email address and order number, supplied by the store when you activate. This is how an installation is tied to the purchase that paid for it.
• The last six characters of your licence key and the number of devices activated. Never the whole key.
• An install identifier, created at random on first run.
• Your IP address, used to derive an approximate location: country, region and city. Not street level.
• A profile of your computer: operating system, processor count, memory, graphics hardware, screen size and system language.
• Usage: which steps ran, whether they succeeded, how long they took, error text when something fails, and counts such as the number of clips and the resolution chosen.

If you bought from the Microsoft Store, none of the identity above applies to you. That edition has no licence key and Microsoft does not pass your identity to us, so what we hold is the anonymous install identifier, your approximate location, your machine profile and your usage. Microsoft holds your purchase, not us.

You can switch this off. Reporting can be turned off entirely, and everything already collected can be cleared, from inside the application. Doing so does not affect your licence.

Why we collect it

To support you when you write to us and to know which licence you hold. To find and fix defects, using the error text and the machine profile that produced them. To understand which features are used and which are abandoned. To handle a refund or a complaint without making you explain your purchase first. Under the UK and EU General Data Protection Regulation our lawful basis is legitimate interest for analytics and defect diagnosis, and performance of a contract for anything tied to your licence.

What we do not do

We will not send you marketing email. We will not sell your data, rent it or trade it. We will not share it with advertisers or data brokers. We will not build an advertising profile of you, and we will not use your data to train models. It is shared only with the infrastructure that stores it on our behalf: Vercel for hosting and Google for the spreadsheet where the records are kept. They act on our instructions and for no purpose of their own.

How long we keep it

Analytics for 24 months. Records tied to your licence for as long as your licence is active, and for seven years afterwards where tax and accounting law requires it.

Your rights

If you are in the UK, the EU, or another jurisdiction with comparable law, you may ask us to show you what we hold, correct it, delete it, provide it in a portable form, or stop processing it. Write to iacolettisoftware@gmail.com and we will respond within 30 days. You may also complain to your national data protection authority. Asking us to delete your data does not cancel your licence, and cancelling your licence does not by itself delete your data.

Payment

Purchases are handled by the store you bought from: Microsoft, Gumroad or Lemon Squeezy. They are the merchant of record and they handle payment, invoices, taxes, refunds and chargebacks under their own terms. Iacoletti Software never sees your card details.

The free browser edition

The browser edition processes your video in the browser tab itself. Your files are not uploaded to a server. The website records ordinary web analytics: pages viewed, referring site, approximate location from your IP address, and which links were pressed.

The optional AI features work there too, and they send the same material described above: still frames for a review, clip audio for narration, your typed text for a spoken voice. One difference matters. In the browser those calls are relayed by our own server rather than sent to the provider directly, so your key and the material do pass through Iacoletti Software on the way. We do not store, log or keep any of it: the key is used for that one request and discarded. The reason is technical rather than chosen. The editor page runs cross-origin isolated so it can use every core of your processor when it exports, and that same browser setting stops the page calling xAI or Google directly.

Children

This software is not directed at children under 16 and we do not knowingly collect their data.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new "last updated" date.