ConvertXLab handles all file uploads and conversions through an ephemeral, in-memory pipeline. This policy outlines our technical workflow, confirming that we do not store user-uploaded files on our servers .
1. In-Memory Processing Workflow
When a User uploads a file through the browser dropzone, it follows a strict memory-only route:
The browser sends a multipart HTTP POST request containing the file bytes.
Our Node.js proxy server (running Express with Multer in-memory storage configuration) intercepts the request and buffers the raw bytes directly into RAM memory ('req.file.buffer').
The Node.js proxy makes a secure server-to-server call to our local Python FastAPI service, piping the buffer directly over HTTP.
The Python microservice wraps the incoming stream in RAM memory using a 'BytesIO' object. The conversion library processes the data entirely in-memory.
Once converted, the output bytes are sent back as an HTTP attachment response stream directly to the proxy, which forwards it to the User's browser.
On request completion, both the raw buffer and output stream are immediately garbage collected in both Node and Python runtime environments.
2. Storage Exclusion
Our servers do not write user files to disk, temporary folders, cache paths, or permanent cloud storage. The only files stored in our hosting system are administrative and media assets (like blog images) uploaded manually by authorized administrators via secure CMS dashboards.
3. System Log Constraints
Our application databases do not store your files. MongoDB logs metadata about the conversion (timestamp, input MIME type, target format, byte size, and success status) for audit purposes, but does not capture file names or contents.
In addition to the specific items described above, you agree that this document governs all related aspects of our platform, user interface, backend converters, and connected third-party integrations. This document represents a complete understanding between the parties.
We reserve the right to modify these terms, conditions, and descriptions at our sole discretion. Any changes will be posted on this page and the Last Updated date will be revised accordingly. Your continued use of the platform after updates indicates your consent to the changes.
If any provision of this document is found by a court of competent jurisdiction to be invalid, the parties agree that the court should endeavor to give effect to the parties' intentions as reflected in the provision, and the other provisions of the document remain in full force and effect.
Please be aware that our technical infrastructure processes requests using automated filters. Any automated attempt to reverse-engineer our converters, perform unauthorized security probing, or extract metadata from our platform components without authorization will result in immediate IP banning and access revocation.
For any questions, concerns, or requests regarding this document, please contact our legal desk via email at [email protected].
Furthermore, our organization regularly reviews this document to ensure alignment with changes in data protection legislation. In addition to technical safeguards, we provide training to our developers regarding security best practices and secure coding principles. We seek to protect our platform integrity by proactively resolving errors, deallocating unused memory profiles, and minimizing the logging of external identifiers. By accessing the conversion tools on our site, you confirm that you appreciate this framework and support our efforts to maintain a safe, clean, and private platform. We thank you for choosing ConvertXLab.