Effective: August 26, 2026
Architecture
Fleet uses an isolated Electron renderer with context isolation, sandboxing, disabled Node.js access, a restrictive Content Security Policy, sender validation, and narrow typed operations exposed through the preload boundary.
Local-only application data
Fleet has no backend or external database. Notes and managed attachments are stored in Fleet’s local application data. Writes use a checksummed envelope, atomic promotion, and a rolling backup. Local notes are not transmitted to Jira, GitHub, the Fleet website, or Fleet’s developer.
Jira credentials
The current beta encrypts Jira connection credentials using Electron safeStorage and keeps them in a separate credential file on the laptop. Credentials are excluded from Fleet note data, note backups, renderer state, and exported diagnostics. They are used only by the Electron main process for requests sent directly to the configured Jira Cloud site.
Jira permissions
Fleet does not elevate a connected user. Jira continues to enforce project permissions, issue security, editable fields, allowed transitions, comment permissions, and workflow conditions.
Untrusted content
Jira rich text and Markdown previews are sanitised before rendering. External navigation is restricted to validated HTTPS or HTTP destinations and opens outside Fleet.
Open-source verification
Fleet’s complete source code is published under the MIT License. Release notes and assets are published through GitHub so users can inspect changes and compare release checksums.
Updates and releases
Update checks are disabled by default and contact GitHub Releases only when enabled or manually requested. Public production builds are intended to use Apple Developer ID signing, hardened runtime, notarisation, and stapled tickets.
The downloadable beta package is an evaluation build while Developer ID signing is being finalised. It is intended for invited beta testing rather than managed enterprise deployment.
Reporting a vulnerability
Report suspected vulnerabilities privately through Fleet support. Do not include a live Jira token, company issue content, employee information, or other confidential data. Allow reasonable time for investigation before public disclosure.
Scope and limitations
The security page describes the current beta, not a guarantee. Device compromise, malicious Jira content, third-party outages, user-approved actions, and administrator policy remain outside Fleet’s complete control.