How to prepare research data locally without uploading study files
What local processing changes when you are working with sensitive study files, and what responsibilities still stay with you.
Sometimes the safest upload is no upload
If the job is simply to reconcile files that are already on your computer, a cloud upload may add another copy of the data without helping the task itself. A local workflow keeps the merge and review step on the computer where you opened the files.
Local processing does not make an export automatically safe
Your output can still contain names, emails, study IDs, or a crosswalk. Store those files according to your study protocol and institutional rules. De-identification is a choice you make about fields; it is not a blanket certification.
Know exactly what leaves the machine
Research Data Merger does not send the study datasets you open to IMPLEMON, an AI service, or a cloud processor for the merge. Its core merge and export workflow can run offline after the app is installed.
Your institution may still control software installation
A university or hospital can require IT approval, administrator privileges, or an internal security review even for local software. That is separate from whether the app uploads data. If you are on a managed computer, check the local software policy first.
A small example
Study files on your computer
↓
Local review and merge
↓
Export to a location you choose
No research-data upload stepWhat local means in Research Data Merger
RDM processes the study files locally and does not upload them for merging. For deployment details, including managed institutional devices, see the Security & Privacy page.