Hardware-first. Bit-perfect. Deep Velvet.
The definitive bit-perfect music player for Android DAPs. Built for audiophiles who demand the full signal chain.
Hardware-First Engineering
Every architectural decision in Meringo starts at the DAC and works backwards. No compromises in the path between your files and your ears.
Meringo bypasses Android's sample-rate converter entirely — every sample reaches your DAC exactly as the recording engineer intended. No resampling. No dithering. No compromise.
The SQ engine is purpose-built for DAPs like the FiiO M21. Direct DAC passthrough, no middleware audio processing stack in the way of your high-res FLACs.
AcoustID fingerprinting scans your library and matches it against MusicBrainz — surfacing producer credits, session musicians, liner notes, and high-res artwork from the Cover Art Archive.
Toggle between your Local Vault of FLAC files and your Jellyfin Cloud server without blending the two sources. Each lens maintains its own identity, metadata, and playback context.
Your library, your Jellyfin credentials, your listening history — all encrypted on-device. No telemetry. No cloud sync. No data ever leaves your device without your explicit consent.
Tuned for the Snapdragon 680 / 4GB RAM target. Low memory footprint, efficient background scanning via WorkManager, and an interface scaled for a DAP's 4–5 inch screen.
"I built Meringo because I wanted a more refined, high-fidelity way to experience a music library."
Adam Siemaszko — Developer, Erie County, NY
Deep Velvet UI
Every screen in Meringo is designed to disappear — letting the music and its metadata take the foreground. Dark, layered surfaces. Warm gold accents. Nothing that doesn't earn its place.
Now Playing
Reference Track
The Vault · Local
Get in Touch
Questions, bug reports, or feedback — reach Adam directly. As a solo developer, I read and reply to every message personally.
support@meringo.appLegal
EFFECTIVE DATE: January 1, 2025 · BUILT BY ADAM SIEMASZKO
Meringo is a local-first music player built by Adam Siemaszko. I do not operate servers that collect your personal data. I do not run analytics pipelines. I built Meringo because I wanted a more refined, high-fidelity way to experience a music library — not to harvest data.
This policy describes what minimal data interactions the application has, and exactly why they exist.
Meringo collects no personal data on my servers. On your device, the app stores:
None of this data is transmitted to me or to any third party for advertising or tracking purposes.
The Identity Resolver uses AcoustID (libchromaprint) to generate an acoustic fingerprint of your audio files. This fingerprint is a compact mathematical representation of the audio signal — not an audio recording.
Fingerprints are submitted to the AcoustID public API solely to retrieve a MusicBrainz recording ID. No personal information, file names, or listening history is attached to these submissions. The AcoustID service is subject to its own privacy policy at acoustid.org.
Meringo integrates with the following public, read-only APIs to provide editorial content:
All external requests are for content retrieval only. Use of these services is subject to their respective terms and privacy policies.
All sensitive data — Jellyfin credentials, preferences — is encrypted using the Android Keystore system. The local Room database is stored in the app's private data directory, inaccessible to other apps without root access.
Meringo requests only the permissions required for operation: READ_MEDIA_AUDIO, INTERNET (for metadata APIs and Jellyfin), and FOREGROUND_SERVICE (for background playback).
Because Meringo does not collect personal data on any server I control, there is no data for me to provide, correct, or delete on my end. All data the app holds is stored on your device and can be removed by uninstalling the application.
The application is provided as-is. As a solo developer, I work hard to keep Meringo stable and respectful of your privacy, but I cannot guarantee it will be free of defects.
Questions about this privacy policy or Meringo's data practices? Write to me directly:
support@meringo.app