Who is responsible
The party responsible for the data described here, the responsable in the language of Mexican data protection law, is César Hernández. fcp2aaf is a product of Soonus, the independent software studio he runs from Mexico: two names, and the chain ends at one person — the same one who answers the address below.
The contact for anything on this page, including a request to exercise the rights below, is support@soonus.net. The registered particulars the law asks for, meaning the full legal name, the tax identification and the postal address, are not published on this page. They are given in full, by return, to anyone who asks for them, whether that is a customer, a data protection authority or a client's compliance department.
The application
The conversion is a process running on your own Mac, reading your own disk. The .fcpxml, your media, the names of your projects and the AAF that comes out are never transmitted anywhere. There is no analytics inside the application, nobody is profiled, and there is no account to make.
Three things do use the network, and none of them is your work:
- Checking a licence, when one is activated. What travels is the licence key, the identifier of that activation, a name for the Mac, so that you can tell your machines apart when you release one from another, and a hashed identifier of the Mac's hardware, which ties the licence to that machine and lets us count how many Macs a licence has been on. The hash cannot be turned back into the identifier, and we keep it only beside the licence it belongs to. Nothing about a project, a timeline or a file is part of it. On the free plan it never happens at all: there is no licence to check.
- Asking whether there is a newer version. The application fetches a small file from our own server and compares version numbers against it. Nothing about you or your machine is sent in order to ask. You are asked the first time the application opens whether it may do this on its own, and whatever you answer can be changed at any time in Settings ▸ General.
- Reporting a crash — and this one is off until you switch it on, in Settings ▸ Advanced. It is never turned on for you, and a fresh installation sends nothing.
What a crash report contains is the kind of failure and where in the code it happened: the type of the error, the stack it came from, and a few tags drawn from fixed lists — the frame rate, the FCPXML version, whether the audio was embedded or referenced. What it never contains is the text of an error message, the name of a project, a clip, a file or a folder, the contents of any of them, or your IP address. That is not a promise to be careful with them: the reporter holds a list of the fields that may travel and copies nothing else, so a field invented by a future version of the reporting library does not start travelling on its own.
Crash reports go to Sentry, and they are the only thing this application ever sends there. Switching the option back off takes effect the next time the application opens, because the reporter cannot be stopped once it has started.
This website
The site is a set of static files served by Cloudflare. It sets no cookies of its own. The only thing it stores on your device is fcp2aaf.theme, a browser storage entry remembering whether you chose light or dark, which is never sent anywhere and can be cleared with the rest of your browsing data.
As host and network, Cloudflare processes what any web server processes to answer a request: your IP address, the page you asked for, and your browser's own description of itself. Those logs are kept for a short rolling period and are used to serve the site, to keep it up, and to rate-limit abuse.
Visits are counted with Cloudflare Web Analytics, which is aggregate and cookieless: no identifier is stored on your device and there is no tracking across other sites.
Every form on this site is protected by Cloudflare Turnstile, which examines the browser rather than the person and may store a short-lived token strictly to carry out that check. Without it, a form is a mailbox for scripts. You will not see it: there is no box to tick and no puzzle to solve, which is why it is said here — the check is there whether or not you notice it, and its script loads only where there is a form on the page.
There is no advertising, no social network widget, no third-party font, no session recording and no A/B testing on this site.
The mailing list
If you subscribe to the release notes, what is stored is:
- your email address
- the language of the page you signed up on, and which page it was
- the two-letter country code Cloudflare derives from your IP address — the address itself is not stored
That is held by Plunk, the service that keeps the list and sends the messages. It is used for one thing: an email when there is a new version of the application, saying what changed. It is not used for marketing, there is no automated sequence, and the list is never sold, rented, shared or handed to anybody else.
This list was a waiting list for the release, promising a single email on the day it happened. That day was 25 August 2026 and the promise was kept; what it now collects against is the release notes, which is why this section says so rather than still describing one message.
Every email carries an unsubscribe link, and writing to us has the same effect the same day — the record is deleted, not marked inactive.
The contact form
One page has a form on it: the contact page. What it collects is exactly what you type into it — your name, your email address and your message. It takes no files of any kind; the review form described below is the only one on this site that does, and only ever a photograph you chose to attach.
None of it is stored anywhere. There is no database behind these forms, no contact list and no ticket system. What happens is that the answers are formatted into a single email and delivered to our mailbox; that email is the only copy, and it is kept for as long as the conversation is useful and deleted when you ask.
Your address is used to reply to you and for nothing else. It is not added to the waiting list, to a newsletter or to any list at all — those are separate and are asked for separately.
Plunk delivers that email, in the same way any mail provider carries a message, and Cloudflare Turnstile checks the browser before it is sent. Nothing else is involved.
The review form
There is a second form, at /review/, and it is the one page here that is sent to you rather than found: it is asked for by email, after you have bought the software and used it. What it collects is your name, your email address, what you do, where you work, a rating and whatever you write — and, if you choose to add one, a photograph of you.
The photograph is optional and the form works perfectly well without it. If you do add one, your browser resizes it to 500 pixels on its longest side and re-encodes it before anything is sent: what leaves your Mac is that small copy, and the original never does.
None of it is stored anywhere either. The answers become one email with the picture attached, delivered to the same mailbox as everything else, and that email is the only copy. There is no database of reviews and no review system.
Nothing is published without your permission, and asking for it is the whole of the last step. The form shows you exactly what would appear — the words, the stars, your name, your job and your face — and then asks you to agree to it being published on fcp2aaf.com, on soonus.net and in material derived from them, and to it being translated. This site is written in two languages, and a review is worth as much to a reader who does not share yours — the translation carries the same words, not different ones. The sentence you agreed to is sent along with the review, so what is on file is the wording you actually read rather than whatever it says today.
Your email address is never part of what is published. It is how we reply, and it is how you take it back: write to support@soonus.net and a published review comes down. You do not have to give a reason.
When we ask for your project file
Reporting a fault is the form above, or an ordinary email if you would rather write one — they arrive in the same place and neither is stored anywhere but there. There is no database and nothing automatic: what exists is the correspondence, in a mailbox, kept for as long as it is useful and deleted when you ask.
Some faults cannot be found from a description. When that happens you may be asked for the .fcpxml, and occasionally for a piece of the media it points at. It is always a request and never something the application does on its own; it is used to reproduce that one fault and nothing else; it is never published or shared; and it is deleted once the fault is fixed, or sooner if you ask.
If your material is under NDA, say no. It costs you nothing, and most faults are found without it.
Buying a licence
Checkout is operated by Dodo Payments as merchant of record, on their systems and not on ours. What they collect is what a sale needs: your name and email address, your country and — where a tax authority requires one — your postcode, the rest of a billing address if you choose to give it, a business tax number if you enter one, and your payment method. Alongside that they collect what any payment company collects to decide whether a payment is genuine: your IP address, and a description of the device and browser you paid from.
Dodo is not our processor for that; it is responsible for it in its own right. It is the seller of your transaction, so it decides how that data is handled and answers for it under its own privacy policy. In practice that means a request about the payment — a copy of it, a correction, an erasure — has to go to them as well as to us, and that deleting our copy does not delete theirs. Card details never pass through anything of ours at any point.
What reaches us is the order, the name and email address on it, and the licence record it created — the key, its plan, and the Macs it is currently activated on. That is used to deliver the licence, to answer your email about it, to process a refund, and to keep the accounting records Mexican tax law requires.
The thank-you page asks Dodo who paid. The checkout returns you to /welcome with the payment's identifier, its status and your email address in the address bar; the page hands that identifier back to Dodo and shows the name and address Dodo has on the payment, rather than trusting what is in the bar. Nothing about it is stored, the reply is not cached, and the site's referrer policy keeps that address from travelling to any other site. Your browser's own history will keep it, as it keeps every address you visit.
If a payment is disputed, Dodo tells us and asks for evidence that it was genuine. What we can produce is the order, the invoice, and when the licence was activated and on which Macs — the same records described above, used that once to answer the dispute.
What it is used for
- running the licence you bought, and letting you move it between your Macs
- answering the emails you send, and the forms that become emails
- issuing and accounting for a sale, as tax law requires
- keeping the site available and rate-limiting abuse of it
- the single launch announcement, if you asked to be told
- finding and fixing the fault behind a crash, if you switched crash reporting on
- answering a disputed payment, if one is raised against an order
It is not used for advertising, it is not sold or rented to anybody, nobody is profiled, and no decision with a legal effect on you is taken automatically.
Where the data is
Those providers operate outside Mexico — mainly in the United States and the European Union, and in India, where Dodo Payments is based — so data handled by them is processed there.
Handing data to a provider so it can carry out the service you asked for is a remisión under Mexican law and needs no separate consent from you. Where European rules apply, those transfers rest on the safeguards each provider publishes for them.
How long any of it is kept
- Orders and licence records — while the licence is alive, and afterwards for as long as tax and accounting law requires them to be kept. Dodo keeps its own copy of the sale and its invoice for its own legal periods, which are its to set and outlast ours.
- Support correspondence — as long as it is useful as context for the next question, and deleted on request.
- The waiting list — until the launch email is sent, or until you unsubscribe, whichever comes first.
- Server logs — a short rolling period, set by Cloudflare rather than by us.
- Crash reports — a rolling period set on the Sentry project, after which they are discarded whether or not the bug was found.
- Anything sent to reproduce a fault — deleted when the fault is fixed.
Your rights
Under Mexican data protection law you have the ARCO rights: to access the data held about you, to have it rectified when it is wrong, to have it cancelled, and to oppose its use. You may also limit its use or disclosure, and withdraw a consent you gave.
If you are in the European Economic Area or the United Kingdom, the equivalent rights apply: access, rectification, erasure, restriction, objection and portability.
Exercising any of them is an email to support@soonus.net from the address concerned. There is no form and no fee, and the answer comes within the period the law sets — 20 working days in Mexico, a month under European rules.
One limit worth stating plainly: we can only act on what we hold. The payment itself belongs to Dodo Payments, which is responsible for it in its own right, so a request to see or erase what surrounds a purchase has to be made to them as well. Ask us and we will say so and point you at them rather than answering for half of it.
If the answer does not satisfy you, you may complain to the authority that oversees data protection in Mexico, or to the supervisory authority where you live if that is in the EEA or the UK.
Security
The strongest protection here is that most of the data never exists: your work stays on your own disk, so there is no copy of it to lose.
What does travel goes over HTTPS. Keys and credentials are held as encrypted platform secrets and are not in the source repository. No arrangement is perfect, and this one is not claimed to be.
Children
This is a professional tool for post-production and it is not directed at children. Personal data is not knowingly collected from anybody under the age at which they could agree to this on their own.
Changes to this policy
Changes are made on this page, with a new date at the top of it. A material change to what the application sends over the network is stated in the release notes as well.
Contact
Any question about this page, and any request to exercise a right in it: support@soonus.net.