Launch test mode VersionFixer अभी pre-launch test mode में है। Official work 25 May 2026 से शुरू होगा, इसलिए कुछ conversions और payments manually review हो सकते हैं.
User data

Privacy policy

How VersionFixer handles account data, uploaded files, checkout references, support messages, and deletion requests.

This launch privacy page explains what is collected, why it is needed, how long files stay, and how users can request deletion. It should be reviewed by qualified legal counsel before enterprise contracts.
Files

Uploaded files are used only to detect type, create a conversion job, and deliver the converted result.

Customer ownership

Customers keep all rights to uploaded source files and generated output files. VersionFixer does not claim ownership, resale rights, or training rights over file content.

No training or resale

Uploaded file content is not sold, licensed to third parties, or used to train models.

Zero-retention workflow

Source files, temporary work files, logs, and generated outputs are stored in isolated job folders and scheduled for deletion after the configured retention window.

Account data

We store account email, plan, credits, jobs, and API key metadata needed to provide the service.

Contact forms

Messages sent through contact forms are stored for support and sent to the site administrator.

Cookies

Cookies may be used for login, language preference, checkout sessions, and abuse protection.

Deletion

Users can request account or file deletion through the contact page.

Third parties

Payment and infrastructure providers process only the data required for checkout, hosting, and delivery.

What we process

Uploaded design, print, CAD and 3D files are processed to detect type, create a compatibility job and deliver the requested output.

No content ownership

VersionFixer does not own, sell, license, or reuse customer file content. Uploaded files and outputs remain customer content.

Zero-retention file lifecycle

Each job uses private storage and is eligible for cleanup after 30 minutes. Customers may request deletion of any remaining job records or support records.

Account data

We keep the email address, display name, plan, credits, job history and API key metadata required to run the service.

Analytics

Analytics are optional and configurable. When enabled, events focus on product usage such as upload started, file detected and checkout started.

Deletion requests

Users can request deletion of account data, contact messages or remaining job files through the contact page.

Launch FAQ

Do you use uploads to train models?

No. The launch workflow is designed for conversion and compatibility handling only.

Who sees support messages?

Support/contact submissions go to the site administrator and can be stored locally for follow-up.

Can a user ask for deletion?

Yes. The contact page is the first deletion request channel until a self-service privacy center is added.

आज की विज़िट 1,004