Effective: August 26, 2026
Who operates Fleet
Fleet is currently operated by Navaneeth Penumarthi. Privacy and data requests can be submitted through the Fleet support page.
No Fleet backend or external database
The Fleet application has no developer-operated backend, hosted user account, telemetry pipeline, advertising SDK, note-sync service, or external database. Notes, folders, preferences, managed attachments, favourites, Trash, backups, and local diagnostics are stored on the user’s device and are not received by Fleet’s developer.
Jira connection data
Fleet connects to Jira Cloud only when configured by the user. The Jira site, account email, API token, selected teammates, and connection metadata are stored in an encrypted credential file on the laptop using Electron safeStorage. They are not written to local-note data or backups and are not sent to Fleet’s developer, website, analytics, or any Fleet database. Fleet does not ask for a Jira password.
Direct Jira communication
Jira reads and user-requested writes travel directly from the Fleet desktop application to the Jira Cloud site selected by the user. The API token is included only as authorization for those Atlassian requests. Jira issue data is displayed in Jira Space but is not copied into Fleet’s note store or note backups. Atlassian processes these requests under the agreement between the user or their organisation and Atlassian.
Website and download data
The Fleet website does not intentionally set advertising cookies or use cross-site tracking. The hosting provider may process ordinary request information such as IP address, user agent, requested URL, timestamp, and security logs to deliver and protect the site. The download host may record comparable delivery logs.
Diagnostics and updates
Fleet keeps local diagnostic logs designed to exclude note and Jira content. Diagnostics leave the device only when the user deliberately exports and shares them. Update checks are opt-in and may contact the configured release host to determine whether a newer version exists.
Payments
Fleet is free and open-source software. Fleet does not collect payment information and contains no purchase, subscription, or billing flow.
Retention and deletion
Users can delete notes, empty Trash, disconnect Jira, revoke the Jira token through Atlassian, and uninstall Fleet. Local application data can be removed through the operating system. Infrastructure security logs are retained only as long as reasonably needed for security, abuse prevention, and service operation.
Security
Fleet uses process isolation, narrow desktop interfaces, encrypted credential storage, local content sanitisation, and restricted external navigation. No security measure eliminates all risk. Suspected vulnerabilities should be reported through the support page and should not include real Jira tokens or confidential issue data.
User choices and rights
Depending on location, users may have rights to access, correct, delete, restrict, or object to processing of personal information. Because local note data is not received by Fleet, those requests are normally fulfilled directly on the device. Requests concerning website or support data can be submitted through support.
Children
Fleet is intended for professional users and is not directed to children under 16.
Changes
Material changes will be dated on this page. A future contributor must update this notice before introducing hosted accounts, note sync, analytics, payments, or any new transfer of user data.