What applies to every tool
No tool has accounts with JDE Projects, analytics, tracking, advertising, or crash reporting. Nothing you enter is sent to JDE Projects. Your data stays on the PC or server where you run the tool. It goes only to the servers and devices you point the tool at yourself, and to any service named in that tool's section below.
Where files are kept
The Windows tools keep their files in their own folder: where you unzipped the portable download, or the install folder, which is %LOCALAPPDATA%\Programs\(tool name) by default. They write nothing to the registry or to other programs' folders. Outside that folder there are only files you choose to save elsewhere, short-lived temporary files, and Simple SFTP Client passwords you ask it to remember, which go to Windows Credential Manager. The window each tool draws its screens in runs in private mode, so it keeps no browser cookies or storage between runs. The two server tools keep their data in the folders named in their sections. No tool encrypts its settings or data files. The one exception is a private key you generate with a passphrase in Simple SFTP Client or Simple SFTP Server. Everything else is protected by your Windows account or your server's file permissions, and by disk encryption if you use it.
Update checks
Each tool asks GitHub for the version number of its latest release, at api.github.com/repos/JDE-Projects/(tool name)/releases/latest. The request asks only for that release information and carries nothing about you or your data. GitHub sees your IP address, as it does for any web request, under the GitHub Privacy Statement. The Windows tools check when they start and when you press Check for updates. There is no setting to turn off the check at start. The two server tools check only when you press the button. A tool never downloads or installs an update on its own. If one is available, it shows a link you can choose to open.
Debug logs
Every tool except Simple CVE Tracker has a debug log that is off until you turn it on. (Simple CVE Tracker's section explains how its logging works.) While on, it writes a plain text file (the Windows tools name it Debug_Log_(date)_(time).txt, in the tool's folder) and sends it nowhere. It is there for bug reports, and it can hold server addresses, usernames, and file paths, so read it before you share it. Each tool's section lists what its log records. Unless a section says otherwise, logs have no size limit and the tool never deletes them. Delete them by hand when you are done.
Links and other outside services
Links to jde-projects.com and GitHub open in your browser only when you click them. The only services contacted besides GitHub are the ones named in the Simple CVE Tracker, Simple Network Dashboard, and Simple SFTP Server sections, plus the servers and devices you enter.
Licenses
No released tool contacts a license or payment service. If a paid edition is released, this page will name the service it contacts and what it sends before that edition is available.
Removing a tool and its data
Uninstalling a Windows tool asks whether to also remove the settings and data it created in its install folder. Answer yes to remove them. A file that is in use or locked can be left behind, so check that the folder is gone afterward. It does not touch files you saved elsewhere, such as exports, backups, or generated keys, or passwords saved in Windows Credential Manager. For the portable download, delete the folder.
This website
jde-projects.com is hosted on Cloudflare Pages and uses Cloudflare Web Analytics to count page views and measure page speed in total. It sets no cookies and uses no browser storage. Apart from Cloudflare's analytics script, it loads nothing from other sites. Cloudflare handles requests to the site under the Cloudflare Privacy Policy. If you email contact@jde-projects.com, your message is used only to reply.
Simple Account Balancer
What it stores
- simple_account_balancer.db in the app folder: account names, balances, transactions, payees, categories, notes, and autopay rules.
- If the database is found damaged at launch, the app tries to restore it from the newest good backup. Before replacing the damaged file, it saves a copy in the app folder as simple_account_balancer.damaged_<date and time>_<id>.db, and keeps that copy even if the restore then fails. When the restore succeeds, a matching -journal file, if one existed, is kept with the copy. When it fails, the journal stays with the data file, which is left unchanged. The app never deletes these copies.
- Backup copies of that database in a backups folder inside the app folder, or in a folder you choose. The app keeps the newest 5 by default (you can set 1 to 50) and the newest 3 copies made before a restore, and tries to delete older ones.
- simple_account_balancer.pref: theme, window position, the last account you had open, and your backup folder and backup count.
- CSV exports, only where you save them.
Passwords and keys
- The app has no sign-in and stores no passwords or keys.
Debug log
- Records IDs, dates, counts, update-check results, and error messages. Log lines leave out file paths, payees, amounts, balances, and names you type. In error messages, file paths are replaced with <path> and other quoted text with <text>.
- Each log file stops at 5 MiB and logging continues in a new file. The app keeps the active file plus at most 3 older ones (20 MiB in all) and deletes older ones when it starts, when logging is turned on, and when a file fills. It deletes only its own Debug_Log_*.txt files in the app folder. If a log file cannot be written, logging turns off and the app shows a warning. It also warns if an old log cannot be deleted.
Network connections
- Only the GitHub update check.
Keeping and deleting data
- Deleting an account, category, transaction, or autopay rule in the app removes it from the database. Backups made earlier still hold it until they are pruned or you delete them.
- To remove everything, delete the app folder, your custom backup folder if you set one, and any CSV exports you saved. Deleting the app folder also removes any saved copies of a damaged database.
Simple CVE Tracker
What it stores
- A SQLite database in its data folder (/opt/simple-cve-tracker/data with the included installer, /data in the container): downloaded vulnerability records, your watchlist, matches against it, settings, and sync progress.
- Temporary download files in the same folder. They are deleted after each sync, and one left by an interrupted download is removed by a later sync.
- The web interface can set a temporary cookie to carry an on-screen message from one page to the next. It holds no personal data and stops working when the service restarts.
Passwords and keys
- An optional NVD API key, entered on the settings page or set as the SCT_NVD_API_KEY environment variable. A key entered on the page is stored unencrypted in the database, and the page never displays it again. It is sent only to NVD, in the request header NVD requires.
- The app has no user accounts and stores no other passwords or keys.
Debug log
- There is no separate log file. Progress and errors go to the server's system journal, which keeps them for as long as your server's journal settings allow. Starting the service with --debug adds more detail.
- Log lines carry file names, record counts, sync positions, and error messages. The NVD API key is not written to the log.
Network connections
- Downloading vulnerability data is the app's job, so it contacts these public sources on a schedule and when you start a sync: the CVE Program's release files on GitHub (github.com/CVEProject), the CISA Known Exploited Vulnerabilities feed, the FIRST EPSS score file, and the NVD API. NVD requests include the date range being fetched. The other downloads fetch the current public files. Your watchlist is never sent.
- The GitHub update check runs only when you press its button.
- Links on a vulnerability page to CVE.org, NVD, and MITRE open only when you click them.
Keeping and deleting data
- Vulnerability records with no watchlist match are deleted after 90 days by default (the retention setting). Records that match your watchlist, the watchlist itself, and settings stay until you remove them.
- Removing a watchlist entry also removes its matches.
- There is no uninstaller. To remove everything, stop the service and delete the install folder, its data folder, and the systemd service file.
Simple Firearm Logbook
What it stores
- simple_firearm_logbook.db in the app folder: every field of each firearm record, including serial number, purchase and value details, storage, trust or NFA details, and disposition.
- Photos you import (saved as JPEG copies) in a photos folder, and copies of documents you attach in an attachments folder, both in the app folder.
- simple_firearm_logbook.pref: theme and window position.
- While a restore preview is open, an unpacked copy of the chosen backup sits in a sfl_restore_* folder in the Windows temp folder. It is deleted when the restore finishes, fails, or is cancelled, or when the app closes. One left by a crash is deleted at the next launch once it is over an hour old.
- During a restore, the current logbook is moved into a temporary sfl_restore_aside_* folder in the app folder. The folder is removed when the restore finishes. If a failed restore cannot be fully undone, the folder is kept and the error message names it.
- Exports and backups, only where you save them. Backups are ZIP files holding the database, photos, and attachments, and are not password protected.
Passwords and keys
- The app has no sign-in and stores no passwords or keys. The files above are not encrypted, so anyone who can open your Windows account can read them.
Debug log
- Records record numbers, counts, file names, statuses, and error messages. Windows user names inside file paths are replaced before writing.
- Each log file stops at 5 MiB and logging continues in a new file. The app keeps the active file plus at most 3 older ones (20 MiB in all) and deletes older ones when it starts, when logging is turned on, and when a file fills. It deletes only its own Debug_Log_*.txt files in the app folder. If a log file cannot be written, logging turns off and the app shows a warning. It also warns if an old log cannot be deleted.
Network connections
- Only the GitHub update check.
Keeping and deleting data
- Deleting a firearm removes its record, photos, and attachments. Deleting a photo or attachment removes its entry and tries to remove the file. If the file cannot be removed, the app shows a warning instead of reporting success.
- Backups and exports you saved elsewhere are not touched.
Simple Network Dashboard
What it stores
- In /var/lib/simple-network-dashboard: devices.json and a backup copy (device names, addresses, SSH usernames, metrics ports, and saved commands), known_hosts (the SSH host keys you approved), auth.json (the dashboard password hash), sessions.json (sign-in sessions), and caddy-root-ca.crt (a public copy of the certificate the dashboard's web server uses, so browsers can trust it).
- In your browser: a sign-in cookie (the server ends a sign-in after 24 hours, or after 30 days if you choose to stay signed in), a cookie that protects form submissions, and two local-storage entries, your light or dark theme and a random ID that identifies your browser to the dashboard. All of these go only to your own dashboard server.
Passwords and keys
- The dashboard password is stored only as an Argon2id hash, a one-way form that cannot be turned back into the password. Sign-in tokens are stored only as SHA-256 hashes.
- SSH passwords for your devices are kept in memory for the session and never written to disk. The app does not use SSH key files.
- A device's SSH host key is saved only after you approve it. If it changes later, the app refuses to connect.
Debug log
- Written to /var/log/simple-network-dashboard, readable only by the service account. Files are capped at 5 MB each, with three older copies kept (about 20 MB in total).
- Records device addresses, ports, usernames, the names of the commands you run and their output, and error messages. Sudo passwords and password prompts are filtered out.
Network connections
- While you are viewing a device, the server reads its metrics every two seconds over plain HTTP from the address and port you entered.
- SSH connections and commands go only to the devices you add.
- The GitHub update check runs only when you press its button.
- The installer downloads the Caddy web server from Caddy's package host (dl.cloudsmith.io) and installs it with apt.
Keeping and deleting data
- Expired sign-in sessions are pruned. Deleting a device or a command, or forgetting a host key, removes it from the saved files.
- The included uninstaller can back up your devices and host keys first, then removes the app, its data folder, and its log folder.
Simple Project Manager
What it stores
- Your projects live in the .xlsx workbook you open or save, wherever you keep it: names, owners, deadlines, status, progress, priority, tags, and notes.
- .spm_recovery.xlsx in the app folder: a recovery copy of unsaved work, including the path of the workbook it came from. It is deleted when you save, open, or start a project, or decline to recover it.
- simple_project_manager.pref: theme and window position.
Passwords and keys
- The app has no sign-in and stores no passwords or keys.
Debug log
- Records workbook paths, theme changes, update-check results, and error messages.
Network connections
- Only the GitHub update check.
Keeping and deleting data
- Deleting a project in the app removes it from the workbook when you save. The app never deletes your workbooks.
Simple RCON Tool
What it stores
- servers.json in the app folder: each saved server's name, address, port, game, and custom buttons. The app does not save the password you enter.
- simple_rcon_tool.pref: theme and window position.
- Console exports (the commands and server replies shown on screen), saved in the app folder only when you export.
Passwords and keys
- The RCON password is kept in memory while connected, sent only to that game server as the RCON protocol requires, and cleared on disconnect. It is never saved.
Debug log
- Records server address, port, game, every command you send (custom commands in full), update-check results, and error messages. Values written as password: or password= are replaced before writing. A password typed into a command in any other form is recorded as typed.
Network connections
- RCON connections go only to the servers you enter, and only when you press Connect. The RCON protocol itself is not encrypted, so the password and commands cross the network as the game server receives them.
- The GitHub update check.
Keeping and deleting data
- Deleting a saved server removes it from servers.json.
Simple SFTP Audit Tool
What it stores
- simple_sftp_audit_tool.pref in the app folder: theme and window position.
- Audit reports, only where you save them: the server address, port, software, algorithms, findings, and host key fingerprints.
Passwords and keys
- The app never signs in to the server it audits, and stores no passwords or keys.
Debug log
- Records the address and port you audited, the full audit output, host key fingerprints, results, and error messages.
Network connections
- Audits connect only to the address and port you enter, when you start one. The optional rate test opens many connections in quick succession to that server.
- The GitHub update check.
Keeping and deleting data
- The app deletes no files of its own. Delete saved reports and logs by hand.
Simple SFTP Client
What it stores
- servers.json in the app folder: each saved connection's name, server address, port, username, sign-in method (password or key), private key file path, starting folder, and whether a password is remembered. It never holds passwords.
- known_hosts in the app folder: the server host keys you approved.
- simple_sftp_client.pref: theme and window position.
- Console exports, saved in the app folder only when you export. Keys you generate, only where you save them.
- When you replace an existing key pair, a temporary backup of the old private key, named .sftpkey_bak_ plus random characters, in the same folder as the key. It is deleted once the new pair is saved. If the save fails and the old key cannot be put back, the backup stays on disk and the error message names it.
- An interrupted transfer can leave a scratch file named .(file name).(8 random characters).sxtpart in the destination folder, on your PC or on the server. The app leaves these out of its own file lists, but Windows Explorer and other programs show them. The app deletes any it finds in the local folder you are browsing each time you connect.
Passwords and keys
- Passwords are saved only when you tick "remember" and save a connection whose server address, port, username, and sign-in method match your last successful sign-in. They go only to Windows Credential Manager, under the name SimpleSFTPClient and an entry named server|username, or server|port|username for a port other than 22. Credential Manager protects them with your Windows sign-in. If saving fails, the app says so and does not mark the password as remembered.
- Private keys stay where you keep them. The app records only the file path and reads the key from there each time it connects. Key passphrases are never saved.
- Host keys: the first time you connect to a server, the app shows its key fingerprint and saves the key only if you trust it. If a saved key later changes, the app shows the old and new fingerprints and connects only if you choose to replace the saved key.
- Keys you generate are protected by a passphrase if you enter one, and saved unencrypted if you leave it blank.
Debug log
- Records server addresses, ports, usernames, sign-in method, host key types and fingerprints, local and remote file and folder paths, transfer details, and error messages, plus the SSH library's detailed connection messages. The app never passes a password or passphrase to the log. As a backstop, it also masks passwords inside web addresses and any private-key text before writing.
- Each log file stops at 5 MiB and logging continues in a new file. The app keeps the active file plus at most 3 older ones (20 MiB in all) and deletes older ones automatically. It deletes only its own Debug_Log_*.txt files in the app folder. If a log file cannot be written, logging turns off and the app shows a warning.
Network connections
- SFTP connections go only to the servers you enter, when you connect or test a connection.
- The GitHub update check.
Keeping and deleting data
- Deleting a saved connection removes it from servers.json and deletes its remembered password from Credential Manager. If Windows refuses to remove the password, the app shows a warning naming the leftover entry so you can delete it by hand.
- Uninstalling does not remove remembered passwords. Delete saved connections first, or remove the SimpleSFTPClient entries in Windows Credential Manager (Control Panel, Credential Manager, Windows Credentials).
Simple SFTP Server
What it stores
- server_config.json in the app folder: the port, and for each user their username, home folder, permissions, sign-in method, password hash, and allowed public keys.
- host_ed25519 in the app folder: the server's own private host key, created on first start.
- simple_sftp_server.pref: theme and window position.
- Files that users upload, inside the home folders you assign. Quick Start shares a QuickStart-Share folder in the app folder.
- When you generate a key pair over an existing one, a temporary backup of the old private key, named (key file name).tmp- plus numbers and random characters, in the same folder. It is deleted once the new pair is saved. If the save fails and the old key cannot be put back, the backup stays on disk.
Passwords and keys
- User passwords are stored only as bcrypt hashes, a one-way form that cannot be turned back into the password. The Quick Start password is generated fresh each time and never saved.
- Users' public keys are stored as text in server_config.json.
- The server's host key is a plain, unencrypted file. Anyone who can read the app folder can copy it and pose as this server.
- This app does not use Windows Credential Manager.
- Keys you generate are protected by a passphrase if you enter one, and saved where you choose.
Debug log
- Records usernames, permissions, home folder paths, connecting IP addresses, failed sign-ins, rejected addresses, and error messages. Passwords, passphrases, and private key text are replaced before writing.
- Each log file stops at 5 MiB and logging continues in a new file. The app keeps the active file plus at most 3 older ones (20 MiB in all) and deletes older ones when it starts, when logging is turned on, and when a file fills. It deletes only its own Debug_Log_*.txt files in the app folder. If a log file cannot be written, logging turns off and the app shows a warning. It also warns if an old log cannot be deleted.
Network connections
- The server listens on port 2222 by default, on every network connection the PC has. Who can reach it depends on your firewall and router.
- Pressing Get for the public IP asks api.ipify.org for your public IP address, or checkip.amazonaws.com if that fails. That service sees your IP address, since that is what it reports back. This never happens unless you press the button.
- To show your local network address, the app asks Windows which connection would reach 8.8.8.8. No data is sent to that address.
- The GitHub update check.
Keeping and deleting data
- Removing a user deletes their entry and, if you choose, their folder. Stopping Quick Start can delete its shared folder. If that folder existed before Quick Start started, the app warns you to check its contents first.
- If the settings file cannot be read, the app renames it server_config.corrupt-(date).json and keeps it. Delete it by hand.
Simple SSH Tool
What it stores
- devices.json in the app folder: each device's name, address, username, and saved commands.
- known_hosts in the app folder: the SSH host keys you approved.
- simple_ssh_tool.pref: theme and window position.
- Console exports (commands and their output), saved in the app folder only when you export.
Passwords and keys
- SSH passwords are kept in memory while connected and cleared on disconnect. They are never saved. The app does not use SSH key files.
- A device's host key is saved only after you approve it. If it changes later, the app refuses to connect.
Debug log
- Records device addresses, usernames, host key events, the names of the commands you run, whether they finished, and error messages. Command output is shown on screen but not written to the log. Any live session password is replaced before writing.
Network connections
- SSH connections go only to the devices you add, when you connect.
- The GitHub update check.
Keeping and deleting data
- Deleting a device or command removes it from devices.json. Forget removes a host key.
Simple UNA Device Manager
What it stores
- simple_una_device_manager.pref in the app folder: theme and window position.
- CSV exports, only where you save them: site, device name, MAC address, IP address, model, status, firmware, and uptime.
Passwords and keys
- Your controller username and password are kept in memory and never saved. The password is cleared when you disconnect, and the username when you close the app.
- The controller's certificate is not checked unless you tick "Verify TLS certificate", because self-hosted controllers usually use their own certificates. The connection is still encrypted either way.
Debug log
- Records the controller address, username, searches, device names, MAC addresses, site IDs, export paths, and error messages. The password is replaced before writing.
Network connections
- Sign-in, searches, and device removals go only to the controller address you enter. While connected, the app contacts it every five minutes to keep the session open.
- The GitHub update check.
Keeping and deleting data
- The app deletes no local files. Removing a device deletes it from your controller, after you confirm.
Simple UNA Log Viewer
What it stores
- simple_una_log_viewer.pref in the app folder: theme and window position.
- CSV exports, only where you save them: event time, site, category, severity, description, client, MAC address, access point, SSID, and network.
Passwords and keys
- Your controller username and password are kept in memory while connected and cleared on disconnect. They are never saved.
- The controller's certificate is not checked unless you turn verification on, because self-hosted controllers usually use their own certificates. The connection is still encrypted either way.
Debug log
- Records the controller address, username, requests and their search terms, response status, up to 2,000 characters of some controller replies (which can include log entries), and error messages. The password is replaced before writing.
Network connections
- Sign-in and log searches go only to the controller address you enter. While connected, the app contacts it every five minutes to keep the session open.
- The GitHub update check.
Keeping and deleting data
- The app deletes no files. Disconnecting clears your credentials and results from memory.
Questions and changes
Email contact@jde-projects.com with any privacy question. When a release changes what a tool stores, sends, or logs, its section and the review date above are updated.