Security
Practical safety guidance for DBC files, support reports, and license keys.
Supported versions
| Version | Supported |
|---|---|
| 2.0.x | Yes |
| Older builds | No |
Reporting a vulnerability
Do not post sensitive vulnerability details publicly. Use the support contact configured for DBC Utility and include the affected version, operating system, reproduction steps, and impact.
App and file safety
- Keep the app updated.
- Only load DBC files from trusted teams or suppliers.
- Review changed DBC files before saving or sharing them.
- Keep your license key private.
Local app security
- The desktop UI talks to the embedded backend through Tauri commands; it does not expose a localhost TCP API.
- License data is encrypted locally, and its master key is stored through the operating system credential store.
- Linux activation requires an available Secret Service or desktop keyring such as GNOME Keyring or KWallet.
- Translation models and app caches are stored in the DBC Utility app data directory.
User guidance
- Do not share proprietary DBC files in public channels.
- Include the app version and operating system when reporting an issue.
- Do not send license keys unless a secure support path has been agreed.