Privacy Policy
EYU SUITS does not upload your files. Every tool runs on your own computer. This page says what does travel over the network and when, what is kept on your computer, what this website and our providers see, and what you can ask of us.
Version 2026-11-02. Last updated 9 November 2026
1. Who is responsible
EYU SUITS is published by EYU LABS. Where this page says "we", it means EYU LABS. You can reach us at the address on our contact page. For the payment itself, Freemius is the merchant of record and has its own responsibility for the data it collects (section 6).
2. Your files
The files you work on are not uploaded. Every tool runs locally, against files on your own disk, using your own processor and graphics card. Video is encoded on your machine, speech is transcribed on your machine, and images are upscaled and backgrounds removed on your machine. There is no upload step and no queue on our side. We do not receive your files, your file names, or a record of what you did with them. That is how the software is built, and the application has no code that sends them.
3. When EYU SUITS uses the internet
These are all the occasions. None of them involves the contents of your files.
- Checking your licence. When you enter a key, and about every two weeks after that, EYU SUITS sends the key and a machine identifier to our activation service. The identifier is a SHA-256 hash made from your computer's Windows machine ID and the identifier its motherboard's firmware reports. It is neither of those IDs itself, but it is the same every time, so it can recognise the same computer and it is personal data in the way a device identifier is. The service runs on Cloudflare and passes the check on to Freemius, which records which machines a key is active on, using the first part of that hash as the device's identifier. Like any connection, the request also carries your IP address, which Cloudflare and Freemius can see. Our own code on the activation service stores nothing about activations or machines; the one thing it keeps is described under update years in section 7. Cloudflare processes every request to run the service and may keep short-lived technical logs under its own policy, and Freemius keeps the activation record. No file names, no file contents, no record of which tools you ran.
- Fetching a model or an engine part. Transcription, upscaling, frame interpolation, stem separation and background removal each use a model file too large to ship inside the installer. The first time you run one, EYU SUITS downloads that model from its publisher: GitHub, Meta's file server, or Hugging Face, depending on the model. Optional engine parts in Settings come from the Python package index and PyTorch's download server. That is a file coming to you, not information going out, though the publisher's server sees your IP address and the request, as any server does.
- Saving from a link. When you use Save from a link, EYU SUITS contacts the site of the link you pasted, and the servers that site uses to deliver its media. Those sites see your IP address and the request. Nothing about you is sent to us.
- Checking for updates. Only when you press Check for updates in Settings, never in the background. EYU SUITS sends the licence key, the machine identifier described above and the version of EYU SUITS you have to our activation service, which asks Freemius about the licence at that moment and works out whether your update period covers a newer version. If it does and you choose to update, the service gives the application a download ticket (good for ten minutes, for your licence and machine and that one version) and the update is sent to you through our service from private storage that Cloudflare runs for us (R2). Nothing about your files, or about what you did with the application, is sent. What the service keeps is in section 7.
- Error reports, if you agree. The first time you open EYU SUITS it asks whether it may send a report when a tool fails: "Ask me each time", "Send automatically" or "No thanks". Settings, under Diagnostics, changes the answer at any time. Until you answer, and if you answer no, nothing is sent. A report holds the error and the lines of the tool's own log, the options used, the type and shape of the file (what kind it is, its extension, size, length, picture size and codecs), the version of EYU SUITS, Windows, the graphics card and how much memory the computer has. It leaves out file names, folders, your Windows user name, passwords, keys, the addresses of anything you pasted, and the file itself. With "Ask me each time" you read the report before anything goes; with "Send automatically" at most five go in a session, one for each kind of error, and never for a wrong password or a full disk. It goes to our report service on Cloudflare, which removes anything personal it still finds, keeps it as section 7 says, and emails us when a new kind of error appears. It carries no licence key, machine identifier or account, and our service does not store your IP address. To stop one computer from flooding the service, it counts requests per address for up to a minute, in memory only, and forgets the address when the minute is over (Cloudflare, which carries the connection, can see it). Every report your computer sent is listed in Settings, under Diagnostics.
- Nothing else. EYU SUITS sends no usage data and no analytics, whatever the settings say.
The Follow us buttons in Settings, and the notice that suggests them (shown at most twice, and never again once you have followed), open our social media profiles in your own browser. That is your browser's connection, not the application's: EYU SUITS itself sends nothing to those sites.
The free trial does not use the internet at all.
4. What stays on your computer
Your settings, your pinned tools and saved setups, the last few files you opened, the licence key you entered and the signed proof that goes with it, caches and downloaded models, and the files you make. None of it is sent to us.
The trial record. When you start the free trial, and only then, EYU SUITS writes a small record of the trial's start date, the last date it was seen, and an identifier of this computer's hardware (the identifier the motherboard's firmware reports, in the clear, not hashed). It is written in several places on your computer, some of them hidden, so that the trial runs once per computer. It stays there when you uninstall EYU SUITS, which is what stops the trial being restarted by reinstalling it. It contains nothing about you or your files and is never sent anywhere. We keep it for the same reason we write it: to run the trial once per computer. If you want it removed, write to us and we will tell you where it is and how to delete it. Removing it lets the trial start again on that computer.
5. This website
The site you are reading is separate from the application, and it is deliberately plain.
- No tracking of our own. The site's own pages contain no analytics script, advertising pixel, session recorder or other tracking code of ours, and no outside fonts. The typefaces, the stylesheet and the scripts of the site itself are served from this domain.
- Cloudflare. The site is served through Cloudflare, which sits between your browser and our host to deliver pages and to block abuse. Cloudflare sees the requests to the site, including your IP address, and it may set a security cookie (cf_clearance) if it decides your browser needs checking. Cloudflare can also measure traffic to a site it serves with its own web analytics, which sets no cookies; if that is on for this site, a small Cloudflare script reports page views and load times to Cloudflare, and we use the figures only to see whether the site is up and quick.
- Our host. Our hosting provider records the ordinary things a web server records: the IP address of the request, the page asked for, the time, and the browser string. That is how a server is run and how abuse is spotted. We do not build profiles from it and we do not combine it with anything else. How long the host keeps those logs is set by the host.
- Our social media profiles. The footer links to our profiles on X, YouTube, Instagram, TikTok and LinkedIn. They are ordinary links: nothing from those sites is loaded on this site, and they hear from your browser only if you click one. After that, their own privacy policies apply.
- Cookies from WordPress. Reading this site sets none of our own. If you log in to the dashboard, WordPress sets the cookies it needs for that.
- Pressing Buy. The agreement opens on this site. Only after you confirm it does your browser go to Freemius's checkout page. What the checkout collects, and any cookies it sets, are covered by Freemius's own privacy policy.
6. Buying a licence
Payment is handled by Freemius, which is the merchant of record for every sale. You are on its checkout, and it collects what a payment service has to collect: your name, your email address, your billing country for tax, your card or PayPal details, and technical data such as your IP address. We never see your card number. Freemius gives us your email address and the data relating to your transaction, so that we can deliver your key, manage the licence and support you.
Freemius also keeps a customer record for your order and runs a customer portal where you can see your licence and the devices it is active on. Its privacy policy covers what it holds, how long, and where. It asks buyers in some countries whether they want product updates and offers, and we use your email address only for your licence and for support unless you said yes to that.
What you agree to before you pay. Before checkout you confirm the Terms of Service, the Licence Agreement, the Privacy Policy, the Refund Policy and your request for immediate supply. This site does not store that confirmation against your order and sets no cookie. The ordinary record any web server keeps that a page was requested is all there is on our side.
7. What we hold, why, and for how long
- Your order and email address. The categories are your name, email, billing country and the details of the order. Providing them is required to buy, and the trial needs none of them. We hold them to issue your key again if you lose it, to support you, and to keep the tax and accounting records the law requires. Kept for as long as the licence is live, and then for as long as the law where we are established requires.
- Support emails. Held so that a conversation makes sense the second time you write. Kept for as long as needed to help you and to deal with any follow-up. Tell us if you want one deleted.
- Licence activations. The key, and for each machine the hashed identifier described in section 3. Held by Freemius while the licence is active, so that the activation count means something, and removed when you release a machine. Our own activation code stores nothing about activations.
- Update years. When you add an update year to a licence, our activation service keeps a record of it in a database Cloudflare runs for us (D1), so that the update-year key can be used once and only on that licence: a one-way hash of the update-year key, the number of the licence it was added to, how many devices it covers, and the dates it was added and last checked. For 120 days it also keeps the update-year key itself, encrypted, to check now and then that the purchase was not reversed by a refund or a chargeback; after 120 days the key is erased. The rest of the record is kept for as long as the licence has update years, because it is what proves the year was paid for. No name, email address or machine identifier is in it.
- Update downloads. To keep one licence from being used to hand the update out to others, our activation service keeps, for each licence and day, how many updates it downloaded (at most five a day): a one-way hash of the licence's number, the date and the count, erased after about a week. Each ticket it issues is a random number with its use count, erased after about a day. No name, email address, key or machine identifier is in either. The update files themselves sit in private storage and are readable only with a key the service gives to a licence that is entitled to that version.
- Error reports. If you agreed: the report text exactly as you were shown it, the version of EYU SUITS and the time, kept for 90 days and then deleted, and a count of how often each kind of error has been reported, deleted when it has not been reported for 90 days. Nothing in a report identifies you, and we do not link one to a licence or an order. Our legal basis is your consent, which you can withdraw by changing the setting; reports already sent cannot be traced back to you, so we cannot pick yours out to delete it before the 90 days are up.
- The trial record. On your own computer, as section 4 says. We do not receive it.
The lawful bases, for those who need them named: performing the contract you bought, for orders, keys, updates and support; our legitimate interest in a working and unabused product, for licence checks, update limits, the trial record, server logs and security; your consent, for error reports and for marketing if you gave it; and legal obligation, for tax records. We do not make decisions about you by automated means beyond accepting or refusing a licence key, and we do not profile you.
8. Who receives it
Freemius (the payment and licensing platform) and the payment services it uses; Cloudflare (the activation service, the storage and delivery of updates, the report service and its email to us, and the delivery and protection of this site); our hosting provider; the publishers of the model files you download; and the sites you point Save from a link at. We do not sell, rent or trade your data.
9. Where it is held
Freemius is a United States company, Cloudflare is a United States company that runs servers around the world, and our host and the model publishers may be anywhere. So data about you can be processed outside the country you live in, including in the United States. We pass data to these providers only as needed to complete your purchase and keep your licence working. Each of them describes the safeguards it uses for transfers in its own documents: Freemius says it uses an approved mechanism such as the EU standard contractual clauses where a transfer is restricted, and Cloudflare says it relies on standard contractual clauses and is certified under the EU-US Data Privacy Framework. We have not signed any transfer agreement of our own with them beyond their standard terms.
10. Your rights
Depending on where you live, you may have the right to ask what we hold about you and to get a copy, to have anything wrong corrected, to have data deleted, to get it in a portable form, to object to a use or ask us to restrict one, and to withdraw consent you gave. We will respect these where the law gives them to you, and we will deal with a request as quickly as we reasonably can, within any time the law sets. We may need to confirm who you are first. We cannot delete what we have to keep, such as tax records, or what we need to deal with a legal claim. We will not ask you to create an account to make a request.
Write to the address on our contact page. Most of what we could hold about you is also held by Freemius, and a request about that goes to Freemius too. If you think we have handled your data badly, you may complain to the data protection authority where you live, though we would rather you told us first and gave us the chance to fix it.
11. Keeping it safe
The site is served only over an encrypted connection and tells the browser so. It refuses to load scripts, styles, fonts or frames from other places, and it cannot be placed inside a frame on another site. It publishes no list of its users, and the parts of the publishing software this site does not use are switched off. The activation service signs its answer, and the application holds only the matching public key, so a valid proof cannot be produced on your computer. Each update is sealed so that the file on its own is unreadable, and signed with a key that never leaves our own computer; the application checks that signature, and the licence, before it installs anything. No system is beyond reach, and these measures reduce risk without removing it. What we can say is that there is very little here to take: no card numbers, no files, no passwords of yours.
12. Changes
If this policy changes in a way that matters, the date at the top changes with it and we will say what changed. Where the law requires us to tell you, or to ask for your consent again, we will. A change does not apply to data we collected earlier in a way that the earlier policy did not allow.
13. Contact
Questions about any of this go to the address on our contact page.