Privacy policy

Scope

This notice applies to the current local development version of DBG Desk. The browser connects to a 127.0.0.1 server on the same computer. There is no public hosting service or external account integration. The effective date is October 17, 2026. Before a public service is operated, this notice will be reviewed for its actual operation and changes will be recorded here.

Debugging data

Executable paths, arguments, process IDs, breakpoints, registers, memory excerpts, call stacks, and debugger output are processed between the browser and local server to provide debugging features. They reflect the state of the connected GDB and target process. Memory and output can contain personal or confidential data used by the target, so inspect screenshots and logs before sharing them.

The current implementation does not upload debugging data to an external server. Recent debugger events are held in local server memory rather than a separate database or log file, and that state is not retained after server termination. Files written by the target program and operating-system or browser records are separate from information managed by DBG Desk.

Selected binary files

Files opened through the file picker or drag and drop are sent to the server on the same computer and copied into an operating-system temporary directory. They are not sent to an external server. The limit is 128 MiB per file, up to 32 files and 512 MiB in one server session. Originals are not modified. Temporary copies are deleted on normal server shutdown but can remain after forced termination or a system failure. Opening by path does not create this copy.

Browser storage and authentication

A temporary local API token is stored in the tab’s sessionStorage. A new token is created when the server starts. After the authentication URL is read, its token fragment is removed from the address bar. Closing a tab normally ends its session storage, although browser session restoration can affect retention. You can also delete the entry in browser developer tools. This version does not use tracking cookies, external analytics, or advertising scripts. The language is determined by the page URL; changing language does not send debugging data elsewhere.

Email inquiries

The contact address is psiwoo66@gmail.com. The contact form passes the subject and message to your default email application. The page does not itself send email or store form contents on the local server. If you send the message in the email application, your sender address, message, and any attachments are delivered to that Gmail inbox. The handling of transmission and storage also depends on the email services involved.

Include only information needed to answer the inquiry. Do not send authentication URLs, passwords, or memory dumps containing personal data. Requests to correct or delete an earlier inquiry can be sent to the same address. Before public operation, a retention period and deletion procedure for inquiry emails will be established and added to this notice.

External links and future advertising

Following an official-documentation link takes you to an external site whose own data policy applies. Google AdSense and other advertising services are not currently connected. Introducing advertising or analytics would require reviewing the actual providers, data practices, and any relevant consent or settings, then updating this notice. The description of this local version would not automatically cover a different public service.

Contact and operating status

Questions about DBG Desk and requests concerning data handling can be sent to psiwoo66@gmail.com. The project is currently in local development before public deployment. Operator identification and other policy details required for actual public operation remain to be completed before that stage.

Stop history and exports

The most recent 50 stop records are held only in the current page’s memory. Reloading or navigating to another page or language clears them. They are not automatically transmitted or written to persistent browser storage. Saving a report creates a local Markdown file containing the selected record’s registers, instructions, and call stack. Memory bytes and output logs are included only if selected. Workspace JSON contains the executable path, arguments, and breakpoints, but not the authentication token or binary file. Downloaded files remain under your control; review them before sharing and delete them when no longer needed.

Thread and frame inspection

Thread lists and local variables in the selected stack frame are processed between the browser and the server on the same PC. They are not automatically uploaded or stored permanently. Stop reports include thread and frame identifiers, but do not automatically include the full local-variable table.