RamondaX Privacy Policy

RamondaX

Copyright © 2026 Aleksandar Marković

Published by RamondaX

Website: https://ramondax.com

Last updated: 2026-11-12

This Privacy Policy explains how RamondaX handles information when you install and use the RamondaX Windows desktop application. RamondaX is designed as a local music player. It does not require a RamondaX account, cloud library, subscription, analytics service, or online profile for normal playback.

This policy applies to all official RamondaX builds for Windows, including the version distributed through the Microsoft Store and the standalone Windows installer.

1. Information We Collect

RamondaX processes information needed to play and manage music on your Windows device. This can include local file paths, filenames, folders, track metadata, playback state, playlists, favorites, settings, generated artwork cache, generated waveform cache, logs, diagnostics files, crash records, and recovery information.

RamondaX does not upload your music files, library, playlists, favorites, playback history, or metadata to RamondaX servers.

RamondaX does not access your microphone, camera, location, contacts, or payment information, and it does not use advertising identifiers.

2. Information Stored Locally

RamondaX stores application data locally on your device, in these locations:

  • %APPDATA%\com.ramondax.player for settings, library and playback state, playlists, favorites, the SQLite library database, the metadata store, and the artwork and waveform caches.
  • %LOCALAPPDATA%\com.ramondax.player for data that Microsoft Edge WebView2 keeps while it displays the RamondaX interface, such as its cache.
  • %APPDATA%\RamondaX for logs, crash records, diagnostics ZIP files, the session recovery marker, and temporary File Explorer hand-off files.
  • The Windows temporary folder for temporary technical files described in this policy.

When RamondaX is installed from the Microsoft Store, Windows keeps the files RamondaX creates in these locations private to the RamondaX app package (under %LOCALAPPDATA%\Packages), while RamondaX continues to see them at the paths listed above.

Local files can include:

  • app_settings.json for application settings, including whether the first-launch welcome screen has been completed.
  • player_state.json and playback_state.json for library and playback restore.
  • user_collections.json for playlists and favorites.
  • ramondax-library.db and related SQLite files for the local library database.
  • metadata-store.json for locally extracted track metadata.
  • artwork-cache/ for generated artwork cache files.
  • waveform-cache/ for generated waveform cache files.
  • logs/ for application logs and local crash records.
  • diagnostics/ for diagnostics ZIP files you create.
  • session_state.json for unexpected shutdown recovery.
  • shell-open/ for short-lived lists of files you open from File Explorer.
  • music-player-seek-trace.log in the Windows temporary folder for technical seek records written while diagnostics mode is on.
  • Temporary generated files used for diagnostics or cache maintenance.

These files remain on your device unless you copy, export, delete, or share them.

3. Music Files

RamondaX plays audio files that you import, drag into the app, select through the file picker, or open through Windows file associations and File Explorer. RamondaX reads supported local audio files from their existing location. It does not upload your imported music files to RamondaX servers and does not copy your music library into a RamondaX cloud service.

RamondaX stores references to your music files, including local paths and related identifiers, so it can restore your library, playlists, favorites, and playback session. Removing a track from your library removes it from RamondaX only; RamondaX does not delete audio files from your device.

When you open files from File Explorer, Windows passes their paths to RamondaX. If RamondaX is already running, the paths are passed locally to the open RamondaX window. With the standalone installer, opening several selected files at once uses a local File Explorer helper that writes the list of selected file paths to a temporary file in %APPDATA%\RamondaX\shell-open. RamondaX deletes that file after reading it and removes any leftover files after one hour.

4. Bundled Demo Tracks And First Launch

RamondaX includes three demo tracks in its installation. The first time RamondaX starts with a new profile that has no music of its own, it adds these demo tracks to your local library and shows a welcome screen. If you choose Try Now, the first demo track starts playing. RamondaX then stores locally that the welcome screen has been completed, so it is not shown again. Profiles that already contain your own music are not changed.

The demo tracks are read from the RamondaX installation folder. Nothing is downloaded, and no information is sent to RamondaX or to any other party when the demo tracks are added or played. You can remove the demo tracks from your library at any time.

The demo tracks were created with Suno, an AI music creation service. They contain metadata embedded by Suno, such as a link to the track page on Suno and content provenance information (C2PA Content Credentials). RamondaX reads this metadata locally like any other track metadata and does not contact Suno.

5. Metadata

RamondaX reads metadata from local audio files to display information such as title, artist, album, duration, file format, bitrate, sample rate, and related technical details where available. Metadata processing happens locally on your device.

RamondaX may store extracted metadata locally in JSON state files, the SQLite library database, and the local metadata cache. Metadata is not sent to RamondaX servers.

6. Artwork Cache

RamondaX may extract embedded artwork from your local audio files and store derived artwork cache files locally. Artwork cache files are used to display cover art more quickly in the application and in supported Windows media surfaces.

Artwork cache files may reflect images embedded in your music files. The cache remains on your device and can be cleared from the application settings by clearing generated cache.

7. Waveform Cache

RamondaX may analyze local audio files to generate waveform peak data for display in the player. Waveform data is stored in memory and may also be stored in local waveform cache files so that the same tracks can load faster later.

Waveform cache files are derived from your local audio files and may include local cache identity data associated with the original file. They remain on your device and can be cleared from the application settings by clearing generated cache.

8. SQLite Database

RamondaX uses a local SQLite database to store and query library information. The database can store track references, full local paths, normalized paths, filenames, directories, metadata, duration information, file size and modification time, availability status, playlists, favorites, and import summary counts.

The SQLite database is local to your device. RamondaX does not upload the database to RamondaX servers.

9. Playlists And Favorites

RamondaX stores playlists and favorites locally. Playlist and favorite records can include playlist names, timestamps, track identifiers, track keys, collection keys, and references to tracks in your local library.

Playlists and favorites remain on your device unless you choose to share files from your application data folder.

10. Playback State

RamondaX stores playback state locally so it can restore your experience. This can include selected track information, playback position, volume, playback mode, current view, playlist route, playback context, and queue/session data.

Playback state is used only for local application behavior and is not uploaded to RamondaX servers.

11. Recovery Information

RamondaX stores local recovery information to detect and recover from unexpected shutdowns. This can include a local session marker with a start time and process identifier. If RamondaX detects that a previous session did not close cleanly, it can show a recovery notice and preserve local data where possible.

RamondaX may also create local backup files when a JSON state file or SQLite database appears corrupt. These recovery files remain on your device.

12. Diagnostics

RamondaX includes local diagnostics tools to help troubleshoot playback, device, startup, import, and recovery problems. Diagnostics mode can be enabled from Settings and is active for a limited time. Diagnostics mode can allow additional local diagnostic events to be written for support and troubleshooting.

You can also create a diagnostics ZIP from Settings. The diagnostics ZIP is created locally on your device and can include version information, operating system and architecture information, settings snapshot, audio output device information, playback runtime diagnostics, diagnostics status, and recent log files.

RamondaX does not automatically upload diagnostics ZIP files. They leave your device only if you choose to share them.

13. Crash Information And Application Logs

RamondaX writes local application logs and may create local crash records if an unexpected error or panic occurs. Logs can include technical events, playback errors, recovery events, startup information, app data paths, executable paths, audio device details, file names, file extensions, path hashes, and in some cases full local file paths.

When RamondaX creates a diagnostics ZIP, recent logs included in that ZIP are scrubbed to reduce exposure of full local file paths. This scrubbing is intended to reduce sensitive path disclosure in diagnostic exports, but logs stored locally on your device may still contain technical information and local paths.

While diagnostics mode is on, RamondaX may also append technical seek records to music-player-seek-trace.log in the Windows temporary folder when you seek within MP3 files. These records can include the full local path of the track. The file stays on your device and is removed when you clear generated cache from Settings.

You can open the logs folder and clear old logs, crash logs, and old diagnostics ZIP files from Settings.

14. Windows Integration

RamondaX integrates with Windows to provide desktop music player behavior. These integrations are local to your Windows device and can include:

  • MP3 and WAV file associations.
  • "Open with RamondaX" entries in File Explorer, including opening several selected files at once.
  • Passing newly opened files to an already running RamondaX window (single-instance handling).
  • Opening Windows Default Apps settings when you choose file-association help.
  • Windows System Media Transport Controls for media metadata, artwork, timeline, and transport controls.
  • Windows taskbar controls and playback progress.
  • Power lifecycle events such as suspend, resume, display changes, lock, and unlock.
  • AppUserModelID and taskbar identity information for Windows shell integration.

The standalone installer registers file associations and the File Explorer selection helper in the Windows registry, and its uninstaller removes them. The Microsoft Store version registers file associations through its app package, and Windows removes them when the app is uninstalled.

Windows may display track title, artist, album, artwork, playback position, duration, and related media information through its own local media controls and shell UI.

15. Third-Party Components

RamondaX includes third-party software components, including open source libraries and runtime components used for the desktop application, audio processing, storage, user interface, and Windows integration.

Third-party components are governed by their own licenses. Third-party notices and license texts are included with RamondaX. If FFmpeg components are distributed with RamondaX, they are provided under their applicable LGPL license terms and corresponding notices are included.

Third-party components used by RamondaX do not create a RamondaX cloud account, analytics profile, or automatic upload of your music library.

RamondaX displays its interface with Microsoft Edge WebView2, a Windows component provided and updated by Microsoft. RamondaX uses WebView2 only for its own local interface and does not use it to load remote websites. Microsoft may collect diagnostic data from WebView2 as described in the Microsoft Privacy Statement (https://privacy.microsoft.com/privacystatement) and according to your Windows diagnostic data settings.

16. Microsoft Store

If you install RamondaX from the Microsoft Store, Microsoft processes information related to how you get, install, and update RamondaX under the Microsoft Privacy Statement. Microsoft may provide RamondaX with aggregated reports through Microsoft Partner Center, such as acquisition statistics, ratings and reviews, and app health and crash reports that Windows collects according to your diagnostic data settings. RamondaX uses this information only to maintain and improve the application.

17. Internet Connectivity

RamondaX does not require internet access for normal local music playback. RamondaX does not include analytics or advertising SDKs, does not synchronize your library to the cloud, and does not automatically upload telemetry. RamondaX itself does not check for updates or download content; Microsoft Store updates are handled by Windows.

RamondaX may open external URLs only when you choose an action that requires it, such as opening the Privacy Policy, Terms of Service, Support page, or Windows settings. When you open a website, your browser and the website you visit may process information according to their own policies.

18. Security

RamondaX uses local application storage, path validation, scoped local artwork asset access, and diagnostics path scrubbing for exported diagnostics. These measures are intended to reduce unnecessary exposure of local files and paths while preserving normal playback, import, artwork, waveform, diagnostics, and Windows integration behavior.

No desktop application can guarantee that local files are immune from all risks. You should only share diagnostics ZIPs, logs, application data, or cache files with people or services you trust.

19. Data Retention And Deletion

RamondaX keeps local application data until it is replaced, cleared, deleted, or removed by you or the application. Some generated caches are pruned automatically by the application. You can clear generated artwork, waveform, and temporary cache files from Settings. You can also clear old logs, crash logs, and diagnostics ZIP files from Settings.

When you uninstall RamondaX:

  • Microsoft Store version: Windows removes the app package together with the app data that RamondaX created. Files created earlier by the standalone installer version stay in their original folders.
  • Standalone installer: the uninstaller offers an option to delete application data, which removes %APPDATA%\com.ramondax.player, %LOCALAPPDATA%\com.ramondax.player, %APPDATA%\RamondaX (logs, crash records, diagnostics ZIP files, and recovery information), and the seek trace file in the Windows temporary folder. If you do not select this option, these files stay on your device until you delete them.

You may also remove RamondaX application data at any time by deleting the local application data folders listed in section 2. Removing local application data can reset your library, settings, playlists, favorites, playback state, caches, diagnostics, and recovery information.

20. Your Rights And Choices

Because RamondaX stores application data locally, many privacy choices are controlled directly on your device. You can choose which music files to import, whether to create diagnostics exports, whether to share diagnostics files, whether to clear generated cache, whether to clear old logs, and whether to remove local application data.

RamondaX does not sell your personal information, does not share it with third parties for advertising, and does not use it for profiling.

Depending on your location, you may also have legal rights regarding personal information that cannot be waived. To contact RamondaX about privacy questions, use the Support page listed below.

21. Children's Privacy

RamondaX is a general-purpose desktop music player. It is not directed to children and does not knowingly collect personal information from children through a RamondaX account or cloud service.

22. Changes To This Policy

RamondaX may update this Privacy Policy for future releases. Material changes will be published on the official RamondaX website or through other appropriate distribution channels. The "Last updated" date at the top of this policy shows when it was last revised.

23. Contact

Website: https://ramondax.com

Privacy Policy: https://ramondax.com/privacy

Terms of Service: https://ramondax.com/terms

Support: https://ramondax.com/support