Privacy policy

TableWorkbench reads selected files and pasted table content in the browser. Parsing, supported transformations, comparison, matching, and generation of output files run locally. The application has no table-upload endpoint for receiving your source records. It does not send filenames, cell values, pasted content, or values entered in operation rules to a processing server. Browser workers are used for supported computation; a worker is part of the local browser workflow rather than a remote file-processing service.

This description applies to the application’s data path. It does not certify the security of your device, browser extensions, operating system, or other software running alongside the page. Use a device and browser appropriate for the information you handle. If your organisation restricts how particular data may be processed, check those rules before selecting a file. Local processing is a specific behaviour of the tool, not a universal guarantee about every component of your environment.

Opening pages, changing routes, and loading scripts, styles, fonts, or images can generate network requests for website resources. The hosting provider may record information associated with those requests, such as the requested path, request time, IP address, browser details, and response status. These infrastructure logs are separate from the contents of a table selected inside the workbench. The application does not put imported cell values into page URLs as part of its table-processing workflow.

This site uses Pageview to count page visits. Your browser loads a script from app.pageview.app and sends visit events, including the page URL and referring page, to that service. It does not send selected files, cell values, pasted content, or operation-rule values. The site does not use advertising trackers or session replay. The hosting provider may also retain ordinary access logs, whose retention is outside this workbench’s control. Following an external link creates a separate interaction with that website.

The current version does not save imported tables into localStorage, IndexedDB, or a cloud project store. Working data remains in browser memory. Reloading, closing the tab, or clearing the relevant workspace ends that workspace’s in-memory work. Export files you need before taking those actions. A browser warning about leaving a page is a convenience, not a backup mechanism, and it should not be treated as a guarantee that every navigation path will preserve your work.

Compatible operations in the shared table workbench can use the current table across in-site tool or language changes. Specialised tools can maintain separate workspace state. Follow the handoff controls shown for the tool you are using, and save a file when a separate import is required. Clearing one specialised workspace should not be assumed to erase every other workspace or a downloaded file. Close the tab after exporting if you want to end the entire page session.

Clearing application state releases the data held by that workspace. It does not delete the original file, previously downloaded results, or a copy you made elsewhere. Nor does it promise to remove every trace that a browser or operating system may retain through its own memory management, crash handling, history, or backups. The tool does not provide a device-wide erasure service. Keep this distinction in mind when working on a shared device.

If you copied table content to the clipboard, that is another copy managed outside the table session. Clipboard history or synchronisation settings can differ between devices and operating systems. The same principle applies to screenshots, email attachments, and files saved into a synchronised downloads folder. Before sharing or disposing of data, consider the copies you created through your normal workflow as well as the table visible in the page.

An export creates a new file rather than actively overwriting the selected source. Your browser handles saving that download, and its settings determine the location and whether it asks you for a filename. Downloaded tables, workbooks, contact files, event files, and archives remain on your device after the page session ends. Clearing the workbench does not remove them. Choose an appropriate destination and manage those files using your usual storage and access controls.

An archive can contain several kinds of output. A result table, an exception report, and a source manifest may each reveal different information. A manifest can include filenames or record locations. A report can retain original values so that changes can be reviewed. Inspect the package before sending it to another person. Selecting a transformed result does not mean every supporting report has been transformed in the same way.

A saved rule file describes selected settings and does not contain the entire imported table. It can still include column names, fixed values, replacement text, mappings, or other configuration that reveals information about your work. A rule that replaces an internal category name or sets a specific email address can expose that value even when no source record is included. Review a rules file before sharing it or storing it outside the location you normally use for business data.

Rules also serve a different purpose from result files. Loading a rule does not restore the source data from an ended session. Keep the inputs and outputs needed for your task independently. If you use a rule with another dataset, review its settings and confirm that the same field meanings apply. This is both a correctness check and an opportunity to avoid unintentionally carrying a private constant into a new output.

The masking tool can remove selected columns, replace text, partially mask values, or use consistent tokens according to the options you choose. These actions do not establish complete anonymity. A remaining combination of dates, locations, descriptions, or rare attributes can still reveal information. Token mappings are particularly sensitive because they can connect transformed values to their originals. Review the selected output and supporting files before deciding that a package is suitable to share.

Imported cell contents are displayed as data, not executed as spreadsheet formulas, macros, or scripts. A receiving spreadsheet can behave differently when it opens a CSV. Protected table exports can prefix formula-like values and report the affected count. Raw exports preserve the strings, which another application may interpret. Select the output mode for your destination and inspect it. No CSV setting can control every possible receiving application’s interpretation of a value.

The contact page shows any public email address that has been configured. An email link opens your own mail application; it does not automatically attach a table or send a report. You decide what to include and when to send it. Use a small fictional reproduction for a problem report when possible. The maintainer cannot retrieve your local table merely because you visited a particular tool page.

Generating a calendar, contact, or store-import file does not upload it to a destination account. If you subsequently import or share that file, the receiving service’s own handling applies. Check the file and the destination before proceeding, especially when an import may create duplicates or update existing records. The workbench’s local-processing design describes what happens here; it does not extend control over data after you deliberately deliver it elsewhere.