Effective Date: 1 November 2026 · Operated by: Rohit Gupta, India
This Privacy Policy explains how MSLForge, available at https://mslforge.com (the "Service"), collects, uses, stores and protects information when you access or use the Service. The Service is operated by Rohit Gupta, India, and is currently being operated at the pilot stage, prior to registration of a separate business entity ("we", "us" or "our").
This Policy should be read together with our Terms of Use.
The information we collect depends on the features of the Service that are enabled at the time you use it.
Where company accounts are enabled, you may be required to create an account by providing information such as your company name, email address and password.
While the pilot operates with sign-in switched off, no account is required and we do not collect your name or email address through an account registration process.
When you use the Service, you may upload a Bill of Materials ("BOM") and, optionally, your own Material Summary List ("MSL") template. We process these files to generate the requested MSL.
We do not intentionally collect information beyond what is described in this Policy, except for contact details that you provide to us directly, for example an email address supplied when you contact us or request a demonstration.
We use uploaded files solely for the purpose of processing the BOM and, where applicable, the template to generate your MSL.
The extraction and formatting process is performed using fixed, hand-written rules. We do not use an artificial intelligence model or language model to process your documents, and the document-processing process does not involve sending your document to an external API or third-party document-processing service.
Uploaded files and generated outputs are deleted within four (4) hours of processing. We do not retain those uploaded files or outputs beyond that period.
Where company accounts are enabled, we also keep usage records for each account: how many BOMs were processed, when, which product, how long processing took, whether it succeeded or failed (and at which stage), and account events such as sign-ups, log-ins, invitations, saved templates and approvals. We use them to run, support and bill the Service. These records contain no file names, no file contents, no email addresses and no IP addresses.
If you choose to save a template or mapping for repeated use, that template or mapping is retained until you or we delete it. Saved templates and mappings are encrypted at rest, as further described under "Security".
Saved templates and mappings allow repeat uploads from your company to skip the initial setup steps automatically, once the relevant template or mapping has been approved.
Pilot-stage storage limitation: our current hosting arrangement does not guarantee that saved templates or mappings will remain available after a deployment or update. Until we move to guaranteed persistent storage, saved templates and mappings are retained on a best-effort basis and their continued availability is not guaranteed.
We do not share uploaded documents or saved templates and mappings with other customers. Your data is not shown to another company, is not used to train any artificial intelligence or other model, and is not reused for purposes beyond generating your own output or providing the functionality you request.
Once company accounts are enabled, company data will be separated by account-based access controls. A company will not be able to access another company's saved data merely by guessing a company name or a link.
The Service is hosted on Render, a third-party cloud hosting provider. The hosting provider operates the infrastructure on which the Service runs. The hosting-related access and security considerations are explained under "Security" below.
We use only cookies that are necessary for the operation and security of the Service.
csrf_token, is used on the login and signup forms. It remains valid for one (1) hour and is not readable by scripts.Fonts are served from our own server, so no third party receives your IP address when you load a page.
While sign-in is switched off during the pilot stage, all users of the Service use one shared workspace.
Each uploaded file and its corresponding output are associated with a randomly generated job ID that is not guessable. Uploaded files and generated outputs are deleted within four (4) hours of processing.
However, any template or mapping that you choose to save is stored in the shared workspace and may be used by anyone accessing the Service. You should therefore not save a confidential template or mapping while the shared-workspace arrangement remains in place.
The statement in this Policy that companies are isolated from one another through account-based access controls applies only after individual company accounts have been enabled. It does not apply to the current sign-in-disabled shared-workspace pilot.
We use the following measures and arrangements in connection with the security of the Service and information processed through it:
If your organisation requires a stronger security arrangement, for example deployment on your own infrastructure or an arrangement under which we do not hold a decryption key, you may contact us to discuss whether such an arrangement is feasible. These options may be considered for larger engagements and are not part of the standard pilot service.
Pilot-stage hosting limitation: the current hosting tier does not include a persistent disk. As a result, a saved template or mapping, or your logged-in session, may be lost when we deploy an update to the Service. Such loss may require you to complete the setup process again; it does not, by itself, mean that your data has been disclosed or accessed by another person.
We intend to move to persistent storage before onboarding paying clients. Until that change is implemented, the possibility of losing saved templates, mappings or sessions following a deployment is a limitation of the pilot service and should be treated accordingly.
Your BOM, your template and their contents remain yours. We do not claim any ownership rights over those materials before, during or after processing them through the Service.
Your use of the Service is also governed by the Terms of Use. The Terms of Use set out the conditions applicable to access to and use of the Service.
If we change the way we collect, use, store or otherwise handle your information, we will update this Privacy Policy to describe the relevant changes.
Where a change affects how your data is handled, we will notify you directly before the change applies to your account, where applicable and practicable. The updated Policy will be made available on the Service.
If you have questions about this Privacy Policy or wish to enquire about a specific document you have submitted through the Service, please contact us at guptarohit7351@gmail.com.
If you suspect unauthorised access, a data leak or any other security incident involving the Service, please email the same address, guptarohit7351@gmail.com, and include "Security" in the subject line.