Security and file safety
How VersionFixer protects uploaded files, conversion jobs, payments, and worker access.
Every job is stored in a private folder that is blocked from direct web access.
Each conversion receives a separate job directory for input, work files, logs, and output.
Temporary job folders are scheduled for cleanup after 30 minutes by default.
Payment card data is handled by payment providers. VersionFixer does not store raw card numbers.
Desktop conversion workers should connect with scoped API keys instead of public open ports.
Production launch should use HTTPS, Cloudflare, restricted SSH/RDP, and monitored backups.
File lifecycle
Uploads are stored only inside private VersionFixer job storage. Each job receives separate input, work, logs and output directories, then is eligible for cleanup after 30 minutes.
Payment safety
Card details are handled by payment providers such as Stripe, PayPal or WooCommerce gateways. VersionFixer stores plan, credit and checkout references, not raw card numbers.
Worker isolation
Desktop conversion workers should use scoped API keys, private network rules and per-format queues so a failed CAD, 3D or Adobe job cannot affect another conversion.
Abuse protection
Executable extensions, dangerous filenames, unsupported formats and excessive request rates are rejected before a job is created.
Launch FAQ
How long are uploaded files kept?
The default cleanup window is 30 minutes. Production can reduce this window for privacy-sensitive accounts.
Can visitors download uploaded files directly?
No. VersionFixer job storage is blocked from direct browsing and download links are generated through authenticated WordPress handlers.
Does VersionFixer store card numbers?
No. Payments should be processed by PCI-ready providers. The site stores only subscription and credit state.