Privacy Policy

§1 Quick summary

Before the legal detail, the short version: IDection Audio has no servers of its own and no user account. It plays music that is already on your phone, on your local network, on a server you set up yourself, or in your own Dropbox, Google Drive, pCloud or S3-compatible storage — which it only reads, never changes. These are the only places outside your phone the app ever sends anything to, and why:

We add no analytics or advertising of our own, there is no cross-app tracking, and we sell data to no one. The only diagnostics sent are produced by Google's own libraries — the Cast SDK when you cast, and ML Kit when you translate lyrics — and they never reach us. Everything else — your favorites, your usage history, your saved sources (including your SACD discs and your Dropbox, Google Drive, pCloud and S3 sources), the settings of your DACs — lives only on your phone.

§2 Data controller

IDection Audio is developed and published by Sergio Augusto Carvallo Crisóstomo, as an individual — there is no company behind it. For any question about this policy or your data, write to support@idection.com.

§3 Data we collect and why

Credentials for your network sources

When you add an SMB or WebDAV connection, we store the alias, host, port, remote folder, and the username/password you enter. They are stored encrypted in the operating system's secure storage (Android Keystore on Android, the Keychain on iPhone), only on your phone. They are used solely to connect to THAT server when you choose to play something from it — they never leave your local network toward us or any third party. An S3 source is stored the same way; see "S3-compatible storage" below.

If you choose to export your sources to a file (to move them to another device), that file contains your passwords, encrypted: with a key built into the app if you leave the file password empty — so anyone with the app could open it — or with a password you choose. The file goes only where you save it, and the app warns you to keep it somewhere safe.

Usage data and favorites, on the device

To show you rankings such as "Top 10" tracks or the most used receivers, we store locally which sources, DLNA/Chromecast receivers, libraries, and tracks you used, and how often, together with your favorites and favorite groups. This information is kept in a local database (Isar) on your device and is never transmitted to any server — not even ours, because we don't have one. Likewise, for the "DSF receivers" setting it keeps, only on your phone, the name and the network identifier (UDN) of the DLNA receivers found on your network, and whether you marked each one to receive DSD audio as is. If you use Export/Import, the file is created only where you choose to save it.

USB DACs (direct USB bit-perfect output)

When you connect a USB DAC and use it from the app, Android first asks you whether to allow IDection Audio to access that device. The app then reads what the DAC declares about itself — its name, manufacturer, USB identifiers (vendor and product ID), supported formats, sample rates, and volume range — in order to send it your music as is and to show you its spec sheet. The settings you choose for each DAC, such as its maximum volume limit, are stored only on your phone. None of this is transmitted, unless you decide to share a DAC report (see below).

On iPhone there is no such prompt: iOS itself manages USB audio devices. The app reads what iOS and the DAC report — its name, the sample rates it accepts, and whether it understood the DSD-over-DoP test, if you run it — to play each track at its original sample rate and to show you the DAC's details. This too is kept only on your phone.

DLNA+: your DLNA receivers

In the DLNA+ tab, the app talks directly to the DLNA receivers on your local network to show what they are playing and to control them. Besides standard DLNA/UPnP, to offer a receiver's equalizer, inputs, sleep timer or its own queue, the app may use the local control interface that the receiver itself exposes on your network (over HTTP or TCP). The app recognizes the receiver's family from what the receiver reports, and keeps on your phone which family it uses and which features it didn't answer, so they are not offered again; if a receiver asks for a PIN and you enter one, it is also kept on your phone, for that receiver only. All of this stays inside your local network and on your phone: nothing is sent to us or to anyone outside your network.

SACD discs

When you add an SACD disc image (.iso) as a source, the app stores, only on your phone, the disc's name and where it is. For a disc on your phone, that is Android's permission to read that one file, which you grant by choosing it in Android's file picker — the app does not get access to the rest of the folder. On iPhone, the discs on your phone are the .iso files you put in Files › On My iPhone › IDection Audio, the app's own folder. For a disc on one of your network sources (SMB or WebDAV), it is the path of the file on that server, which is read with that source's credentials, inside your local network. The track you play is extracted from the disc into the app's cache, which empties itself as it fills up. If you pick a cover image for a disc, a copy of it is kept in the app's private storage. On iPhone you choose it from your photos: the app opens your photo library only for this, when you tap "Choose image", and copies only the image you pick. The disc is never uploaded anywhere, and nothing about it is sent to us or to any third party.

Your Dropbox, Google Drive and pCloud: read-only access

You can add your own Dropbox, Google Drive or pCloud as a source to play the music you keep there. In every case the app only reads: it lists your tracks and plays them. It never uploads, modifies, moves, renames, shares or deletes anything in your cloud storage. You sign in on Dropbox's, Google's or pCloud's own screen, so the app never sees your password.

Dropbox — read-only, its own folder only. The app is registered with Dropbox with access limited to its own app folder (Apps › IDection Audio; the name of the "Apps" folder depends on the language of your Dropbox account), which Dropbox creates when you connect. It cannot see anything outside that folder. It asks only for read-only permissions: files.metadata.read (to list the files in that folder), files.content.read (to play them) and account_info.read (to show which account the source belongs to). It has no permission to write.

Google Drive — read-only. The app asks Google for its read-only permission, drive.readonly, which Google shows as "See and download all your Google Drive files". Before Google's screen, the app explains what this permission allows and what it does not. It is needed so you can choose a folder and browse the music inside it: Google's narrower drive.file permission only lets an app see files picked one by one, not what a folder contains. With read-only access the app cannot create, upload, change, move, rename, share or delete anything in your Drive — Google itself rejects any such request.

The app uses this access only to list the folders and files of the folder you choose as a source (and the folders inside it, as you browse them in the app) and to read the tracks you play. Google Docs, Sheets, Slides and other Google documents are not shown and are never opened. The app does not search, index or analyze your Drive, and it does not read any file you do not open in the app. (A Google Drive source created track by track in an earlier test version keeps using the narrower drive.file permission: it sees only the tracks chosen in Google's file picker, and "Remove from the app" only hides a track in the app.)

pCloud — read-only. The app is registered with pCloud with access to your folders and read-only permission: pCloud does not let it create, upload, change, move, rename, share or delete anything. Before pCloud's screen, the app explains what this access allows and what it does not. You sign in on pCloud's own page, opened in your browser — including two-step verification or "Continue with Google" if you use them. The app uses this access only to list the folders and files of the folder you choose as a source (and the folders inside it, as you browse them in the app) and to read the tracks you play. Your pCloud Crypto folder is not shown: it is encrypted on your own devices and the app cannot read it.

In every case, the email address of the account (to label the source) and the folder you chose are kept only on your phone. Your music travels straight from Dropbox, Google or pCloud to your phone, in parts as it plays — it never passes through us, because we have no servers. "Wi-Fi only" is on by default: unless you turn it off, the app does not use your cloud sources on mobile data.

Google API Services User Data Policy. IDection Audio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Data from your Google Drive is used only to show you your folders and play your music in the app: it is not used for advertising, it is not sold or transferred to anyone, it is not used to train any model, and no person reads it.

S3-compatible storage

You can add a bucket of an S3-compatible storage service as a source — for example Backblaze B2, Wasabi, Cloudflare R2, IDrive e2, Amazon S3, or your own NAS with S3. You enter its address (endpoint), the bucket, an Access Key ID and its Secret Access Key, and optionally a folder. They are stored encrypted in Android Keystore (the Keychain on iPhone), only on your phone, like the credentials of your network sources. The app uses them only to sign its requests to the address you entered: the secret key itself is never sent, and nothing reaches us. The app only reads: it lists the files of that bucket and folder and reads the tracks you play, so a read-only key is enough — and recommended. Your music travels straight from that service to your phone, in parts as it plays. "Wi-Fi only" applies to S3 sources too.

Song lyrics

The lyrics you see come from the song file itself: a .lrc file with the same name next to it, or the lyrics saved in the file's own tags. The app does not ask any service for lyrics, so the title, the artist or anything else about what you are listening to is never sent anywhere. They are read on your phone, and we do not store them.

Lyrics translation (Google ML Kit)

If you turn on translation in the lyrics view, the lyrics are translated on your phone with Google's ML Kit library: the text of the lyrics is not sent to any server for translation. The first time you translate from or into a language, ML Kit downloads that language's model (about 30 MB) from Google.

As Google documents, that library, not IDection Audio, sends diagnostics and usage data to Google: information about the phone (manufacturer, model, Android version), the app's package name and version, per-installation identifiers that are not intended to identify you, performance metrics, error codes, and, for this feature, the source and destination languages and the language it detected. Google says it encrypts this data in transit and does not transfer it to third parties. We never receive it. If you never turn on translation, none of this is sent. Details: ML Kit data disclosure. The target language you choose is stored only on your phone.

Casting logs (Google Cast SDK)

To stream to Chromecast devices, the app uses Google's Cast SDK. That library, not IDection Audio, sends anonymized logs to Google about how casting works: device discovery events, casting session events, general information about the phone, and which app is casting. According to Google, these logs contain no identifiers that can be traced back to you, are encrypted in transit, are used only to improve the casting experience, and are kept for a short period before being aggregated. We never receive them, and neither we nor you can turn them off or request their deletion. Details: Cast SDK data disclosure.

The iPhone version of the same library declares to Apple, in its privacy manifest, the kind of data it collects for these logs: a device identifier, product interaction and other diagnostic data, used for analytics and for the casting feature to work, not linked to you and not used for tracking. That is why the App Store's privacy label for IDection Audio lists those three items. We do not collect them ourselves and never receive them.

Notification access: what we do NOT read (Android)

The app asks for Android's "Notification access" for two specific purposes, and it is worth being explicit because it is a broad permission: Android requires it to be enabled in order to see which other apps are playing something (the only way to offer playback control of other apps, in the Stream module), and the same access lets the app silence alerts on demand, when you turn on Do Not Disturb in the app, until you turn it off or the chosen time without playback runs out.

What the app does with this access is limited by design: we do not read, store, or transmit the content of any notification. Technically, the service does not implement the methods that receive notifications — not from messaging apps, not from email, not from anything else. You can revoke this access at any time in Android settings, and the rest of the app keeps working.

Status of your Bluetooth devices (Android)

The "Bluetooth audio" screen reads from the system which audio device is connected, with which codec, at which volume, and with how much battery, in order to show it to you. This information is read on the spot and is neither stored nor transmitted. With the Plus add-on you can also ask the system to use a different codec, on devices that allow it: some phones do not let apps read or change the codec, and on those the app says so and does not offer the option. That request never leaves the phone. We do not access any other data from your paired devices, nor your contacts, nor messages.

Diagnostics log

We keep, locally and only on your phone, a technical log of errors and of some of the app's internal decisions — for example, a playback error, which source, receiver or DAC was active at that moment, whether a track was sent as is or converted before sending it to a receiver, the app's battery setting (for example, "unrestricted") when it starts sending to a receiver, or the reason Android gave for closing the app the previous time (for example, low memory or an error). It may include file or folder names, the names of your sources, local IP addresses and the names of devices on your network (such as receivers or DACs), as well as the app and Android versions — never your passwords. It is visible on the Home screen, under System → Diagnostics, and it is never sent anywhere on its own: it only leaves your phone if you share it yourself. Entries older than 30 days are deleted automatically.

If you decide to share it (the "Share" button on that same screen), the system's share sheet opens so you can choose where to send it — email, WhatsApp, or any other app you have installed. You make that submission yourself, choosing the destination; we do not receive it automatically, and the app or service you choose to send it with is governed by its own privacy policy, not ours. The same screen shows the email address you can send it to if you would like us to review it.

Reporting a DAC that doesn't work

If you use "My DAC doesn't work" on the Bit-perfect screen, the app builds a text with your DAC's technical details (name, manufacturer, USB identifiers, and what it declares: formats, sample rates, and volume) and the app's diagnostics log. The app doesn't send it on its own: you share it, with the app you choose (for example, your email), to support@idection.com. When you do, we receive what you send and the address you send it from. We use it only to fix the problem and improve compatibility with that DAC. We don't share it with anyone, and you can ask us to delete it by writing to that same address.

Reporting a DLNA receiver

If you use "Report this device" (DLNA+ › Profile and input) or "Write to us" when a receiver doesn't accept a command, the app builds a text with what the receiver reports about itself (its name, manufacturer, model, services and formats), what the app detected (the family it recognized and the features the receiver answered or rejected) and the app's diagnostics log. The app doesn't send it on its own: you share it, with the app you choose (for example, your email), to support@idection.com. When you do, we receive what you send and the address you send it from. We use it only to fix the problem and improve compatibility with that receiver. We don't share it with anyone, and you can ask us to delete it by writing to that same address.

What we do NOT do

• We add no analytics, advertising, or tracking SDKs. The only diagnostics sent are those of Google's own libraries described above — the Cast SDK when you cast, and ML Kit when you translate lyrics — which we never receive.
• We do not access your location — the network permission used to discover Chromecast/DLNA devices is explicitly declared to Android as "never used for location". On iPhone the app asks only for local network access, and never for location.
• We do not read the content of your notifications, even with the access enabled (see above).
• We do not read, index, or upload the content of your music files to any server.
• We never upload, change or delete anything in your Dropbox, Google Drive, pCloud or S3 storage: the app only reads. In Dropbox, Google Drive and pCloud the access itself is read-only, and in Dropbox it is limited to the app's own folder.
• We do not open, read or index your documents in Google Drive: the app only lists the folders and files of the sources you add and reads the tracks you play.
• We do not sell data to anyone, under any circumstances.

§4 Who data is shared with

Only with these destinations, and only when you use that specific feature:

• The server you set up (your NAS, your PC with a shared folder, your DLNA server) — it receives the credentials you entered yourself, so it can authenticate you.
• Dropbox (Dropbox, Inc.) — only if you add a Dropbox source: your phone signs in to Dropbox and reads, with read-only access, the files in the app's own folder. Dropbox handles that data under its own privacy policy.
• Google (Google Drive) — only if you add a Google Drive source: your phone signs in to Google and, with read-only access, lists the folders of that source and reads the tracks you play. Google handles that data under its own privacy policy.
• pCloud (pCloud AG) — only if you add a pCloud source: your phone signs in to pCloud and, with read-only access, lists the folders of that source and reads the tracks you play. pCloud handles that data under its own privacy policy.
• The S3-compatible storage service you choose — only if you add an S3 source: your phone sends it requests signed with the key you entered, to list that bucket and read the tracks you play. That service handles that data under its own privacy policy.
• Google (ML Kit) — only if you turn on lyrics translation, it receives the diagnostics described in §3, collected directly by Google's library, and serves the language models. The lyrics themselves are translated on your phone.
• Apple (App Store), on iPhone — it processes purchases of Plus and its packs through the App Store. We only receive confirmation that the purchase exists, never your Apple ID, payment method or banking details.
• Google Play (Google LLC), on Android — it processes purchases of Plus and its packs through Google Play Billing. We only receive confirmation that the purchase exists, never your payment method or banking details. Each time the app starts it also asks Google Play, on your phone, whether a newer version is available, and Google Play offers to download it; this uses Google Play's in-app updates service and sends no data of ours.
• Google (Google Cast SDK) — it receives the anonymized casting logs described in §3, collected directly by Google's library. They are not shared with us or with anyone else.
• Other devices on your local network, when this device is a DLNA receiver or library — while you have "DLNA library" turned on, devices on your local network can browse and play the music in the folders you published. While you have "DLNA receiver" turned on, this device answers a device on your local network that asks for it with its own Wi-Fi signal strength, band (2.4/5/6 GHz) and link speed, so the sending device can show whether the connection is good. It does not include the name of your Wi-Fi network, your location or any identifier, and it stays inside your local network.
• The DLNA receivers on your local network, in DLNA+ — the app sends them the commands you give and reads their state, through DLNA/UPnP or the local control interface each receiver exposes. It stays inside your local network.
• Whoever you choose, when sharing the diagnostics log, a DAC report or a DLNA receiver report — the app opens the system's share sheet and you decide the destination (email, WhatsApp, or another installed app). It is not an automatic submission on our part; see the details in §3.

§5 Permissions and why we request them

On Android

Besides the list above, the app uses Notification access, which is not a regular permission but a switch you grant in Android settings. It requests it to see which other apps are playing something and to silence alerts on demand, when you turn on Do Not Disturb in the app, until you turn it off or the chosen time without playback runs out; it does not read the content of any notification. The details are in §3, and you can revoke it whenever you want without the rest of the app stopping working.

To use a USB DAC, the app does not need a permission declared in advance: Android asks you, when you use a DAC from the app, whether to allow IDection Audio to access that specific device. If you say no, the app does not use the DAC directly.

On iPhone

On iPhone the app does not ask for access to your location, camera, microphone, contacts, calendars or Bluetooth, and it does not use Apple Music or your music library. A USB DAC needs no permission: iOS handles it.

§6 Security

Every credential (network sources) is stored encrypted using flutter_secure_storage, backed by the operating system's own Android Keystore — the same mechanism banking apps use to protect sensitive data on the device. They are never stored in plain text, nor in the local database. They only leave that secure storage if you export your sources yourself, and then the file is encrypted (see §3).

Your Dropbox and pCloud sign-ins and your S3 keys are kept the same way, encrypted in Android Keystore. Your Google Drive access is managed by Google Play services on your phone; the app only keeps a short-lived access token in memory. Neither is ever sent to us.

The app also opts out of Android's cloud backup, so its data — settings, history, favorites, and credentials — is not copied to the backup of your Google account.

On iPhone, the same library keeps every credential, your Dropbox and pCloud sign-ins and your S3 keys in the iOS Keychain, encrypted by the system; your Google Drive sign-in is kept in the Keychain by Google's sign-in library. Like the data of any app, the app's data can be part of the backup of your iPhone (iCloud or your computer), which is yours and under your control; none of it is ever sent to us.

§7 Retention and how to delete your data

Since there is no account and no server of our own, all your data lives on your device. You can delete it yourself at any time, without having to contact us:

• A single source (a network connection or an SACD disc): tap the delete icon next to it, in the Sources section. Deleting an SACD disc does not touch the .iso file itself.
• A Dropbox or Google Drive source: delete it in Sources. Deleting the last source of an account also deletes that account's sign-in and saved names from your phone. To revoke the app's access completely, use Dropbox → Connected apps or Google Account → Third-party connections. Nothing in your Dropbox or Google Drive is deleted when you delete a source.
• A pCloud source: delete it in Sources. Deleting the last source of an account also deletes that account's sign-in from your phone. To revoke the app's access completely, remove IDection Audio from the apps connected to your pCloud account, in your pCloud account settings. Nothing in your pCloud is deleted when you delete a source.
• An S3 source: delete it in Sources; its keys are deleted from your phone with it. To revoke them completely, delete or disable the key in your storage service. Nothing in your bucket is deleted when you delete a source.
• The cover image you picked for an SACD disc: "Remove cover art", in that disc's window under Sources.
• The cache of downloaded files (including the tracks extracted from SACD discs): the "Cache" card on the Home screen, under System.
• The diagnostics log: the delete icon on the Home screen, under System → Diagnostics. In any case, entries older than 30 days are deleted automatically.
• Everything at once: uninstalling the app deletes absolutely all of the above — nothing remains on any server, because there was never a copy outside your phone. On iPhone, deleting the app also deletes its folder in Files, including the music you copied into it: move it elsewhere first if you want to keep it.

If you emailed us a diagnostics log or a DAC report, we keep it only as long as we need it to look into the problem, and we delete it sooner if you ask us at support@idection.com.

§8 Purchases: Plus and its packs

IDection Audio works fully and without ads in its free mode: all audio, high resolution included, except DSD and SACD (also over DoP), the equalizer, favorites, local folders and sources, and two DLNA connectors — one library and one player, either using them on your network (as a client) or publishing this device as one (as a server).

90-day free trial. Output to a USB DAC (direct USB bit-perfect output on Android; each track at its original sample rate on iPhone) and DLNA+ can be tried free for 90 days, with one trial for both. It can be started until March 31, 2027; on Android it also ends that day at the latest, and on iPhone it lasts its full 90 days. After it, bit-perfect comes with Plus Hi-Res and DLNA+ with Plus Cast (or both with Plus). On Android, the app keeps the trial's start date on your phone. On iPhone, the trial is a zero-price purchase in the App Store, and the app reads its date from the App Store. Nothing about the trial is sent to us.

Plus is a one-time purchase — it is not a subscription and it is never charged on a recurring basis. It unlocks everything: Cast (streaming to Chromecast, unlimited DLNA connectors and DLNA+), Hi-Res (playing DSD audio — DSF, DFF and SACD discs in ISO —, also over DoP to your USB DAC, and the USB DAC output) and Sources (network sources: SMB/Samba and WebDAV; read-only cloud sources: Dropbox, Google Drive, pCloud and S3-compatible storage).

The same features are also sold as three packs — Plus Cast, Plus Hi-Res and Plus Sources —, each a one-time purchase too: the first pack you buy has its regular price and each of the next ones a reduced price, so the three together cost the same as Plus. Buying Plus or a pack only unlocks features in the app; nothing about it is sent to us.

On Android purchases are processed entirely through Google Play Billing; you can restore them on any device where you sign in with the same Google account, using the "Restore purchase" button on the Plus screen. If you have a promo code, you redeem it in Google Play like any promo code. On iPhone they are processed entirely through the App Store; "Restore purchase" restores them on any iPhone signed in with the same Apple ID.

§9 Children

IDection Audio is not directed at children under 13 and does not knowingly collect data from children.

As explained in §3, the app has no server of its own: we keep no copy of credentials anywhere we can access. So if a child in your care used the app, the most effective step is not to write to us, but rather:

• Credentials for a network source (SMB/WebDAV): they live encrypted only on that phone. Uninstalling the app deletes them completely, or you can change the password of that server directly.

If instead you wrote to us directly (for example, by email, sharing personal information or a DAC report), we can delete that specific communication on request: support@idection.com.

§10 Changes to this policy

If we change what data we collect or how we use it, we will update this same page and the date in the header. Important changes (for example, adding a new type of data shared with a third party) will also be announced inside the app.

• Version 1.10 (October 28, 2026): DLNA+, which controls the DLNA receivers on your local network (also through the local control interface some receivers expose), and what it keeps on your phone; reporting a DLNA receiver that doesn't respond, which only you send; the 90-day free trial of USB bit-perfect output and DLNA+, which replaces the Beta; the free mode described as all audio, high resolution included, except DSD and SACD; Plus Cast now includes DLNA+. The policy now lives at idection.com/audio/privacy and the contact address is support@idection.com. Nothing new is sent to us.
• Version 1.9 (October 25, 2026): the free mode includes two DLNA connectors, one library and one player, as a client or as a server: publishing this device as a DLNA library or player now uses the same free connector as using one on your network. Nothing new is sent to us.
• Version 1.8 (October 25, 2026): purchases: besides Plus, the same features are sold as three packs (Plus Cast, Plus Hi-Res and Plus Sources), and Plus is described as a one-time purchase. The Bluetooth permission is described without tying the codec switch to Plus. Nothing new is sent to us.
• Version 1.7 (October 25, 2026): the policy now also covers IDection Audio for iPhone: credentials in the iOS Keychain, purchases through the App Store, the iPhone permissions (local network, multicast discovery, Photos only to pick an SACD cover, background audio, the app's folder in Files), what the Google Cast library for iPhone declares to Apple, and that deleting the app on iPhone also deletes the music copied into its folder. It also lists the cloud sources among what Plus unlocks, as they have been since each one was added. Nothing new is sent to us.
• Version 1.6 (October 24, 2026): adds §11 on the open-source components under the LGPL (FFmpeg and FFmpegKit): how they are linked, where to get their exact source code, and that nothing in any license agreement for the app limits your rights over them. Nothing about your data changes.
• Version 1.5 (October 22, 2026): you can add your own pCloud as a source, with read-only access (the app explains it before pCloud's screen, and your pCloud Crypto folder is not shown), and a bucket of S3-compatible storage, whose keys stay encrypted on your phone and which the app only reads. Your music goes straight from them to your phone; "Wi-Fi only" applies to both. Nothing new is sent to us, and no new Android permission is requested.
• Version 1.4 (October 22, 2026): Google Drive sources now use Google's read-only permission (drive.readonly) instead of picking tracks one by one: you choose a folder in the app and browse the music inside it, and the app explains the permission before Google's screen. The app still cannot upload, change or delete anything in your Drive — Google rejects it — and it does not show or open your Google documents. "Wi-Fi only" for cloud sources is now on by default. Nothing new is sent to us or to any third party.
• Version 1.3 (October 22, 2026): you can add your own Dropbox or Google Drive as a source. Access is read-only in both: in Dropbox, only the app's own folder (Apps › IDection Audio); in Google Drive, only the tracks you choose yourself in Google's file picker (the drive.file permission). The app never uploads, changes or deletes anything in them, and your music goes straight from them to your phone. Includes the Google API Services User Data Policy statement (Limited Use), how to revoke access, and a "Wi-Fi only" option. The only new permission is the one Google's sign-in library adds so that Google Play services can tell the app when you remove its access (see §5).
• Version 1.2 (October 12, 2026): the app asks again for the permission to show Android's battery dialog (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS), because on some phones music stopped in the middle of a song while the app was in the background; it describes SACD discs (what is stored and how to delete it); the diagnostics log also notes the app's battery setting when it starts sending to a receiver and why Android closed the app the previous time; and "connectors" are now called "sources", as in the app. Nothing new is sent on its own to us or to any third party.
• Version 1.1 (October 11, 2026): the DAC report button is now called "My DAC doesn't work", and the report is used only to fix the problem: it is no longer tied to sending a Plus code. The diagnostics log now keeps only the last 30 days. Nothing new is collected or shared.
• Version 1.0 (October 11, 2026): first version for IDection Audio, the music app of the IDection suite. It comes from the last policy of IDection Player (version 1.4, September 26, 2026), with these differences: the app plays music only, so there is nothing about video, subtitles, or access to your videos; it describes direct USB bit-perfect output to USB DACs and the DAC report; the diagnostics log is described in more detail (it may include local IP addresses and the names of devices on your network); it describes exporting connectors and that the app opts out of Android's cloud backup; the permission to ask you to turn off battery optimization is no longer requested, and two types of foreground service are added. Nothing new is sent on its own to us or to any third party.

§11 Open-source components (LGPL)

IDection Audio uses FFmpeg (version 8.1.2) and FFmpegKit, licensed under the GNU Lesser General Public License, version 3 (LGPL). They are linked dynamically: they ship as separate shared libraries inside the app (.so files on Android, dynamic .framework bundles on iPhone), built without GPL or non-free parts.

The exact source code of those versions — with the scripts that build them and the source code of the libraries they include (LAME, TwoLAME, SoX Resampler and Shine under the LGPL; Vorbis, Ogg, Opus, Speex, iLBC, OpenCORE AMR and VisualOn AMR-WB under permissive licenses) — is available, with SHA-256 checksums, at github.com/skrvaxdev-source/idection-sitio/releases/tag/lgpl-ffmpeg-8.1.2.

Nothing in this policy or in any license agreement for IDection Audio — including the App Store's standard license agreement — limits the rights the LGPL gives you over those components, including modifying them and reverse engineering for debugging such modifications. The full license texts are in the app, under About › Licenses. These components do not collect or send any data.

§12 Contact

For questions, data access or deletion requests, or any concern about this policy: support@idection.com.