Legal Documentation

privacy policy.

Last Updated: August 29, 2026

Sevdah ("we", "our", or "the application") is a free, open-source desktop music player application built with Go, Wails v2, Vue 3, and SQLite. We take user privacy extremely seriously. This Privacy Policy describes how Sevdah handles and protects your data.

01. zero personal data collection & zero telemetry

  • No Analytics / Telemetry: Sevdah does NOT collect, transmit, track, or share any analytics, crash logs, IP addresses, telemetry, or personal usage statistics.
  • No Third-Party Tracking: There are no tracking pixels, advertising SDKs, cookies, or remote user tracking mechanisms embedded in the software.
  • No Remote Application Servers: We do not operate any external database or application backend that stores your user data. All processing occurs 100% locally on your machine.

02. google oauth 2.0 & google drive api usage

Sevdah connects to Google Drive via official OAuth 2.0 authentication solely to stream and organize your personal music files:

Data Accessed

  • Audio Files & Metadata: The application reads audio files (.mp3, .flac, .wav, .ogg, .m4a, .aac, .opus) within the Google Drive folders you designate.
  • Playlist Sync: To support cross-device playlist syncing, the application reads and writes a playlists.json file exclusively in your designated root music folder on Google Drive.

Storage & Security of Tokens

  • Local Storage Only: Your OAuth access and refresh tokens are stored exclusively inside your local SQLite database (~/.config/sevdah/music.db) on your operating system.
  • No External Token Transmission: Your OAuth tokens are never transmitted to any third-party server, service, or intermediary.
  • Direct Google Communication: All API calls are made directly between your local desktop application and https://www.googleapis.com/.

Google API Services User Data Policy Compliance

Sevdah's use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy , including the Limited Use requirements.

03. local data storage & caching

To provide fast performance and offline metadata browsing, Sevdah stores the following files locally on your machine:

~/.config/sevdah/music.db

SQLite Database

Cached track metadata (tags, lyrics, sample rate, format), user favorites (starred tracks & albums), custom playlists, and local settings.

~/.config/sevdah/covers/

Album Cover Art Cache

Binary cover artwork extracted directly from the headers of your audio files.

~/.config/sevdah/artists/

Artist Metadata Cache

Artist biographies and public photos fetched from public open metadata providers.

All local caches remain entirely on your computer and can be cleared at any time by deleting the ~/.config/sevdah/ directory.

04. local audio proxy server (:8990)

The application runs a lightweight HTTP server on localhost:8990 solely to stream raw audio bytes and serve cached cover art to the local frontend UI. This proxy:

  • • Is bound only to your local loopback interface (localhost / 127.0.0.1).
  • • Is not accessible over the public internet or local network.
  • • Does not store audio data on disk beyond serving active streaming range requests.

05. third-party services & apis

For enhanced metadata and artist artwork, the application queries public web APIs:

Deezer API / Wikipedia API / TheAudioDB:

Used only to fetch public artist biographies and photos based on artist names. No user identifiers, cookies, or Google credentials are sent to these services.

06. your rights & control over data

  • Revoking Access: You can revoke Sevdah's access to your Google account at any time via Google Account Permissions .
  • Data Deletion: You can delete all locally cached data at any time by removing the ~/.config/sevdah configuration folder from your system.

07. policy changes

If we update this Privacy Policy, the revised version will be published on this page and in the official repository with an updated revision date.

08. open source transparency

Sevdah is 100% open-source software. You are encouraged to inspect our complete source code on GitHub. For inquiries, please open an issue in the official repository.