I want to understand the app.
Your collection stays private.
I build CLAUDIO myself. Technical and limited usage signals help me find connection problems and decide which features to improve. I do not need to know which books, albums or episodes you listen to.
No means no.
Usage analytics does not start without consent. Declining does not send an event either. You choose in the CLAUDIO Guide and can change your choice under Settings → System → Usage data. Switching it off stops transmission. Existing consent can carry over through a device backup or iCloud Sync.
What helps me improve the app.
I want to know when a source cannot be reached, playback or sync fails, and which features people use. Signals can include error categories, the source type such as SMB or Jellyfin, the output route such as Bluetooth or CarPlay, and opening read-along or the equalizer. Search terms are not sent.
What is recorded besides errors.
With permission, selected interactions and usage frequency are recorded too: opened sections, playback starts, sleep timer use, and purchase offer views and outcomes. The plan and broad library-size ranges are included. Some signals are sent on each use; there is no general daily cap. This helps me find friction in setup and everyday use without knowing the contents of your collection.
The technical information included.
TelemetryDeck adds device and app information: model, operating system, app version, screen size and orientation, language, region, time zone, appearance and accessibility settings. App session counts and durations are included too. CLAUDIO also records the connection type and whether a VPN connection is active.
What I do not receive.
No book titles, song titles, podcast names, filenames, server addresses, credentials or search text. Signals contain no audio content or transcripts. CLAUDIO has no advertising and does not link usage data to a CLAUDIO account.
How signals are connected.
TelemetryDeck processes the data on servers in the EU. A repeatedly hashed, app-specific identifier groups events from the same installation. This makes it possible to examine flows within that installation. The identifier is not joined across devices, through iCloud or with other apps. It would therefore be inaccurate to claim that every event is entirely isolated.
This website sends no analytics events of its own.
No analytics or advertising scripts are built into this site. Text, images and the promo video are served as static files. If you open a blog post, Discord or the App Store, that service’s own notices apply. The website host may keep technical server logs.
The boundary is clear to me: I need signs of what works in CLAUDIO and where it gets stuck. Your collection does not belong in that analysis.Tobias Reithmeier
You already have
plenty to listen to.
Start with your own files. For free.