Local database processing
When you select a SQLite file, browser JavaScript reads it into local memory. Table browsing, SQL execution, row editing, schema inspection and database export occur in the browser session. The application does not need to transmit the selected database file to a server to provide these features.
What the website may receive
Like most websites, the hosting infrastructure may receive ordinary request information such as IP address, browser type, requested pages, timestamps and error logs. The site may use analytics to understand page visits and general usage. Database filenames, table contents and SQL query text should not be intentionally sent as analytics events.
Browser storage
The application may use browser storage for local preferences and workspace information, such as query tabs or query history. This information remains associated with the browser profile until it is cleared by the user or browser.
Downloads and original files
Editing occurs against the in-memory database. Save DB creates a download of the current state. The application does not silently replace the original database file on disk.
Your responsibilities
Use databases that you are authorized to access. Consider the security of the device, browser profile and installed extensions when opening sensitive files. Clear browser storage and downloaded copies when working on a shared device.
Third-party resources
The page may load libraries, analytics or other website resources from third-party services. These services can receive normal web-request data, but the selected database is not intentionally included in those requests.
Questions
Privacy and security questions can be directed to the site operator, CodeMasterLk. This page should be updated when the data-processing behavior of the service changes.