← Home

Privacy Policy

In force from 6 October 2026. Written to follow Vietnam's Decree 13/2023/ND-CP on personal data protection. Data controller: MoExtension, Ho Chi Minh City.

This English text is provided for your convenience. The Vietnamese version at moextension.com/privacy is the governing text; where the two differ, the Vietnamese wording prevails.

1. Principles

We collect exactly what is needed to issue licences, prevent licence sharing, and fix the problems you report. Nothing is collected for advertising, no data is sold, and we build no behavioural profiles.

This policy describes what the system actually does as of the date at the top of the page. When we change how data is handled, we update this document first.

2. What we collect

When you sign in with Google

From Google we receive your account's email address, display name and profile picture, so we can recognise you on the website and in the MoExtension app. You sign in on Google's own page; we never receive and never ask for your Google password.
A sign-in session signed by our server, kept in the app (90 days) or in your browser's storage (30 days). Signing out deletes it.

When you buy

The email of the Google account you buy with, so we can add the plan to that account, send your receipt and support your order.
Order details: order code, chosen plan, amount, timestamp, and the transaction reference the bank generates during reconciliation.

We do not receive and do not store card numbers, account numbers or any payment credentials: the money goes straight from your banking app to the receiving account, and we see only the transfer note and the amount.

When you activate or start a trial

A hashed machine identifier. The panel reads the machine identifier issued by your operating system (MachineGuid on Windows, IOPlatformUUID on macOS), hashes it with SHA-256 on your own machine, and only the hash ever leaves. We never receive the original value and cannot work backwards from the hash.
The operating system name in general form, for example "Windows 11" or "macOS 14".
The computer name your operating system assigned (for example DESKTOP-7Q4M), sent by the app so you can recognise and remove the right machine on the Account page.
First and most recent activation time for each machine.
When you start a trial in the app: your Google account email, and up to 4 hardware hashes (Windows: BIOS UUID, system drive serial number, motherboard serial number; macOS: the machine serial number). The app hashes them with SHA-256 on your machine and only the hashes leave, so each machine and each account gets one trial.
With older panels that still start a trial by email: the email address you enter. We send a 6-digit code to that address and only start the trial once you type the code back, so we know the address is yours. The code is stored only as a hash, works for 15 minutes and only once. To stop mass mailing, the server counts code requests by email, machine hash and IP address hash.

The panel and the app do not read and do not send: local IP address, MAC address, Windows account name, drive list, or the list of installed software.

When you send a problem report

This is where the most data is collected, so here it is in full. When you actively press send, the report carries:

The description you typed, and your email if you filled it in so we can reply.
The last four characters of your licence (also shown on the Account page), to find your order.
Technical context: panel version, the host application in use (After Effects or Premiere Pro) and its version, the operating system, plus the machine hash so we can tell that several reports came from the same machine.
Roughly the last 50 lines of the panel's technical log - error and warning messages the panel itself produced while running. File paths are replaced before anything leaves your machine: a path pointing into your project becomes %DUONG% plus the file extension - a fault in an .aep, an .mp4 or an .ffx file are three different things, so we need the extension but not the name. Paths pointing inside MoLib's own folders are kept for diagnosis, but the account name inside them is replaced too. Your project names and file names do not travel with the report.
Up to 3 screenshots that you attach yourself. We never capture the screen on our own and never capture in the background; images travel only when you choose the files.

What we cannot filter is the text you type and the images you attach. If the report concerns a sensitive project, please do not paste full paths into the description, and look over the screenshots before sending.

When you download MoFX

MoFX is free software with no licence and no product key. The download page asks for your email address before the download starts. The server records exactly the six fields below, and nothing else:

The email you type, lower-cased.
The time of your most recent download.
A SHA-256 hash of your IP address. The original IP address is not stored anywhere.
Which edition of the page you downloaded from - the Vietnamese one or the English one.
The language you were reading the site in.
The number of downloads made with that address.

We keep one row per email address - the most recent download and a download count, not a history of every one.

That address is used for two things and no third. One: telling you when a new version or a bug fix is out. Two: if it matches the address you used to buy MoLib, our admin pages show a "uses both products" mark on your customer record - only our own staff see that mark, and it changes neither your price nor your rights. No advertising, no sharing with anyone, no selling. To come off the list, send us one line at the support address and we remove it without asking why.

The MoFX software itself does not send us your project content, file names, or statistics about what you do with it.

When you use MoTools

MoTools shares its licence server with MoLib and collects the same groups of data listed above: your email and order details when you buy; the machine hash, computer name, activation times and your Google account when you activate or start a trial; and the report contents when you choose to send a problem report. Each record also carries a product label (MoLib or MoTools) so that one product's licence cannot unlock the other, and so we can sort problem reports by product.

The MoTools machine hash is computed separately: the machine identifier is combined with the word "motools" before hashing, so it never matches the MoLib hash of the same machine. MoTools reads MachineGuid on Windows and IOPlatformUUID on macOS, like MoLib.
A problem report sent from the MoTools panel carries the same items as a MoLib one, including the technical log with your file paths replaced by %DUONG%. The panel reads an image from your clipboard only when you paste into the report card, and the image leaves your machine only when you press send.
The tools run on your machine. The panel does not send your project content, file names, or statistics about which tools you use to our server.
A few tools connect to outside services when you use them, and that data does not pass through our server: Download links fetches video straight from the site whose link you paste; Transcribe and Cut fillers send the clip's audio to Groq using your own API key; Get tools fetches ffmpeg and yt-dlp from their original publishers (GitHub, gyan.dev).

When you visit the website

The site sets no tracking cookies, embeds no advertising code and uses no third-party analytics. The site keeps your sign-in session (with your account's email, name and picture) in your browser's storage until you sign out or 30 days pass; while you sign in, a random anti-forgery string is kept for at most 10 minutes. The payment page remembers your pending order code for the browser session, so a reload does not create a new order.

For the problem report form, we store a hash of your IP address to stop bulk flooding. The original IP address is not stored.

If you open the site through a referral link (with ?ref=), your browser remembers the referral code for 30 days and the server stores that code with a hash of your IP address for 7 days, so the referrer is credited when you sign in. The code is attached to your account at your next sign-in, if the account has no referral yet. The original IP address is not stored.

3. What it is used for

Issuing, verifying, renewing and revoking licences.
Sign-in: recognising you on the website and in the app by your Google account.
Limiting the number of machines per licence, and detecting licence sharing.
Granting one trial per machine and per account, and contacting you about your trial (support, trial period) at your account email.
Reconciling payments and handling mismatched transfers.
Sending receipts, order notifications, and notices about changes to the terms.
Telling you about new MoFX versions and fixes, at the address you left when downloading.
Reproducing and fixing the problems you report.
Keeping each product's licence limited to that product, and sorting problem reports by product.

We do not use your data for advertising, do not share it with third parties for marketing, and do not sell it under any circumstances.

We do not collect your project content, the files you edit, or statistics on which presets you use and how often.

4. Processors and transfers abroad

We use the providers below. Their servers sit outside Vietnam, so using the service means personal data is transferred abroad within the meaning of Decree 13.

Google - verifies sign-in. Sends us the email, display name and profile picture of the account you choose.
Cloudflare - runs the website, the licence server, the database and the asset store. Processes everything listed in section 2.
Resend - sends transactional email. Receives the email address and the contents of the message (receipt, email verification code for older panels, order notifications).
SePay - reconciles bank transactions. Receives the transfer note, the amount and the transaction reference; it receives neither your email nor your licence details.
VietQR - renders the bank transfer QR image. Receives the amount and the order code. Since 22 August 2026 our own server fetches that image, so your browser no longer connects to VietQR directly.

We transfer data to no one else, except on a lawful written request from a competent state authority.

5. How long we keep it

Your account (email, name, picture from Google) - kept until you ask us to delete it.
Orders and licences - kept while the licence is valid and for the record-retention period required by accounting and tax rules.
Machine activation records - kept until you remove the machine from your account or the licence ends.
The trial ledger - kept long term. It is the only record that guarantees one trial per machine; it contains only the machine hash, hardware hashes, timestamps, and the account email that started the trial.
Email verification codes - stored only as hashes and useless after 15 minutes; the request-count rows (email, machine hash, IP hash) are deleted automatically after 2 days.
Screenshots attached to problem reports - deleted automatically after 90 days.
The MoFX download row - all six fields (email, time, IP hash, page edition, language, download count) live in one row and are kept until you ask to be removed from the list; removal deletes the whole row, not just the email.
Hashed IP addresses used for flood protection - deleted automatically after 24 hours.
Referral codes with a hashed IP address - deleted automatically after 7 days; a code attached to your account is kept with the account.
Licence strings in readable form, held briefly when issued - deleted automatically after 24 hours. Outside that window the database holds only their hash.

6. Security

Sign-in goes through Google: we hold no password of yours.
Licence strings are stored as SHA-256 hashes. Even a database leak does not reveal them.
Machine identifiers and IP addresses are stored hashed only, never in original form.
All connections to our servers use HTTPS.
Asset download links are signed and expire after 15 minutes, so a link shared elsewhere cannot be reused.
The admin console requires a password plus two-factor authentication.

No system is perfectly secure. If a data breach affects you, we will notify you at your registered email and report it to the competent authority as required.

7. Your rights

Under Decree 13/2023/ND-CP you have the right to:

Be informed that your data is being processed.
Access and request a copy of the data we hold about you.
Have inaccurate data corrected.
Withdraw consent, and object to processing.
Request deletion of your data.
Request restriction of processing.
Complain, denounce, litigate and claim compensation as provided by law.

Send requests to the support email below. We respond within 72 hours and complete the request within 30 days.

One straightforward note: if you ask us to delete all your data while your licence is still valid, we no longer have any way to verify your right to use the software, and the licence will stop working. The trial ledger alone is retained as a technical anti-abuse record - it holds nothing that identifies you apart from an email address, and the email in that ledger can be deleted.

8. Children

The product is aimed at professional users and is not directed at children under 16. We do not knowingly collect children's data. If we find that we have, we delete it as soon as we are told.

9. Changes to this policy

When we amend this policy we update the date at the top of the page. For changes that widen what we collect or what it is used for, we give at least 30 days notice by email to your registered address.

10. Contact

Anything relating to personal data: support@moextension.com.