This Privacy Policy explains how TranscodeX handles data when you use our browser-based video encoder, video compressor and the rest of this website. We keep it as simple and honest as possible: the tool is designed to process your videos on your own device, and it does not rely on uploading your source files.
1. What TranscodeX is
TranscodeX is a website that provides browser-based video encoding and compression tools. The encoder and compressor run FFmpeg compiled to WebAssembly directly in your browser. The normal workflow is local: you choose a video from your device, the browser processes it, and the output file is created and downloaded on your device.
2. Browser-based processing
During a normal conversion, your selected video is read into your browser and processed locally using WebAssembly (FFmpeg.wasm). The source video is not uploaded to our server by the converter, and the output file is created on your device. Video previews and outputs are held in browser memory as temporary object URLs and are released when they are no longer needed or when you leave the page.
3. What we do not collect
We do not store your source videos or your output files on our servers as part of the normal conversion workflow. There are no accounts, no profiles and no required registration, so there is no user database of your encoded files.
4. What the server receives
This website is hosted on a web server. When you load any page, standard web-server request logs may record technical data such as your IP address, browser user agent, the requested URL, and a timestamp. These logs are typical for any website and are managed by the hosting environment; the source video you process in the browser is not part of these logs during a normal conversion.
5. Cookies
The core encoder and compressor work without cookies. WordPress may set cookies if you log in to the site admin or leave a comment (such as saving your name and email in your browser). We do not run third-party advertising or social tracking cookies by default.
6. Comments
If you leave a comment on an article, WordPress stores the information you enter (name, email if provided, and the comment text) and may use your email to look up your Gravatar image. Your email address is not published and is not used for marketing.
7. Third-party resources
This site may load resources such as fonts from Google Fonts and, for blog author avatars and comments, images from Gravatar. Those services may collect data according to their own privacy policies when your browser contacts them. The core video tools do not send your video to these services.
8. External links
Some pages may link to external websites. We are not responsible for the privacy practices of other sites, and we encourage you to review their policies before sharing data with them.
9. Children’s privacy
The site is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will take reasonable steps to remove it.
10. Your choices and rights
Because the service has no accounts by default, there is no profile to delete. You can erase browser-side previews and outputs simply by closing the page or tab. Depending on your local laws, you may also have the right to access, correct or request deletion of personal data we hold about you; because of the local-processing design, we generally hold very little.
11. Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date at the top of this page. Continued use of the site after changes is your acceptance of the updated policy.
12. Contact
If you have any questions about this Privacy Policy, contact us at arybishal@gmail.com.
A note on the word “private”
Browser-based processing keeps your source files on your device during the normal workflow, which is why we describe the tool as local. We do not claim that any device, browser or connection is absolutely private. Browser extensions, other software on your device, or your own network can access data locally, so treat the promise as “designed to stay on your device”, not “impossible to intercept”.