RowDesk is designed around browser-local processing for your raw CSV and Excel data. Review important transformations, keep your source file unchanged and export a separate prepared CSV.
Processed locally in your browser in local mode.
Review what will change before applying it.
No raw dataset is sent to RowDesk servers in local mode.
Export a separate CSV. Your source stays unchanged.
Your raw dataset stays on your device in local-processing mode.
Browser-based data processing keeps the raw dataset on your device in local-processing mode. The browser works with a dataset loaded from your file; export creates a new file from that working data.
Choose a CSV or an XLSX sheet to prepare.
Load the tabular data into your browser workspace.
Apply selected operations on your device in local mode.
Inspect proposed changes and the resulting dataset.
Download a separate, prepared CSV.
In local-processing mode, your raw dataset is not uploaded to RowDesk servers. This statement concerns file contents, not every network request associated with loading a website or using separate account and billing services.
The core workflow does not require storing your customer or business dataset on a RowDesk server to clean or compare it. Local CSV processing and local Excel processing refer to the tabular data loaded into the browser.
Operations affect the working dataset. Cleaning values, removing duplicates and filtering records do not overwrite the original CSV or XLSX file on your device.
The prepared CSV reflects the rows and columns you retain after review. Download it separately and handle that file according to your organization's data policies.
Safe data preparation also means understanding what an operation will do. Preview important transformations before they affect the working dataset, rather than discovering unintended changes in the final export.
Explore preview and change reviewCheck the scale of an operation before applying it.
Inspect before-and-after examples in the relevant columns.
Review the records that will be excluded from the output.
Apply the proposed operation only after reviewing its consequences.
Applied transformations stay visible while you work. Session controls let you reconsider your changes without altering the original source file.
Review the operation, affected fields and impact summary for each applied step. The history describes the active session; it is not permanent cloud version history.
Undo the most recent transformation and redo it while the session remains active. Undo later steps first if you need to return to an earlier state.
Start again from the originally loaded data using reset. Save any outputs you need before discarding the session changes. The original source file remains unchanged.
The local-processing workflow avoids requiring remote storage of your raw dataset. Account, billing and permitted usage metadata are separate from that file content. Local mode should not be read as a claim that the whole service never uses the network.
When evaluating secure CSV cleaning, consider your device, browser environment, access permissions and handling of downloaded files. Processing locally does not eliminate those responsibilities or replace your organization's security review.
This page does not claim zero risk, end-to-end encryption, certification or regulatory compliance. It describes the local-processing workflow and change controls, not a guarantee that every dataset or use case meets your organization's requirements.
Practical answers about file contents, session controls and the boundary of local processing.
In local-processing mode, the raw dataset is processed in your browser and is not uploaded to RowDesk servers. This is a statement about dataset contents, not a blanket claim about website, account or billing traffic.
No. Cleaning, deduplication and filtering operate on the working dataset. Export produces a separate CSV rather than overwriting the original CSV or XLSX file.
In your browser on your device when using local-processing mode. CSV and XLSX are loaded as tabular data for the workspace. The prepared output is CSV.
Yes. Important transformations provide a preview of their impact, including affected rows, before-and-after values or proposed removals as applicable. Confirm the proposal before applying it, then inspect the resulting session step in Changes.
You can undo and redo transformations during the active session. Undo the latest step first; reset returns the working dataset to the originally loaded data. Do not rely on session history being available after closing the workspace.
The core local-processing workflow does not require a server-side copy of your raw dataset. This is not a promise of permanent browser storage or automatic recovery. Keep your original file and save needed exports before resetting or ending a session.
This marketing website currently has no configured analytics SDK. The product's analytics design permits limited usage metadata, such as event names, operation types, bucketed file sizes or row counts, durations and success/failure codes. It excludes raw cell values, dataset samples and filenames or email addresses from the dataset. These design limits are not a claim that no service or infrastructure logs exist.
Process locally, review important changes and export a separate file.
