Privacy Policy

App Identifier and Rip Count

When you first open Discs, the app creates a random identifier using Firebase Authentication. It is not associated with your name or email address. We use it to operate the free-rip allowance and purchase-related features.

Discs stores your lifetime rip count and the time it was last updated in Google Cloud Firestore. The count is used to enforce and restore the free-rip allowance, decide when to show certain app prompts, and understand overall ripping activity. It may continue to update after a purchase.

Discs also stores the number of free rips used under a one-way hash of your device's Android ID. The hash can't be turned back into the Android ID and is not associated with your name or email address. We use it only to operate the free-rip allowance.

Product Analytics

Discs uses Firebase Analytics to understand how the app is used and where features or hardware combinations cause difficulty. We collect app and session information, approximate region, device and operating-system information, navigation and feature-use events, ripping and playback statistics, purchase or entitlement status, grouped information about library and ripping activity, and the manufacturer, model, and USB identifiers of connected devices such as CD drives and music players.

Analytics events are associated with random identifiers assigned to an installation of the app. We do not send names, email addresses, advertising identifiers, audio files, filenames, music-library titles, search terms, or file paths to Firebase Analytics.

We use this information to measure feature adoption, understand different usage patterns, improve hardware compatibility, and identify areas of the app that need work. We do not sell this data or use it for advertising or cross-app tracking.

Discs also collects campaign and source information supplied by Google Play through the Play Install Referrer service. This helps us understand how installations were acquired.

Crash Reports and Diagnostics

Discs uses Firebase Crashlytics to diagnose crashes, errors, and hardware-compatibility problems. A report may include random installation and session identifiers, app and device information, operating-system and network information, approximate country, stack traces and exception messages, recent in-app events, and technical context about a connected device or disc.

Technical context may include drive manufacturer and model, USB identifiers, track and sector counts, ripping progress, and a disc identifier needed to reproduce a ripping problem. Reports do not include ripped audio, and we do not intentionally attach music filenames or library contents. We use these reports to investigate reliability and compatibility problems.

Metadata Lookups

When you insert a CD, Discs sends technical disc information, such as its table of contents and disc identifier, to our metadata servers to look up track names and artist information.

Album art is fetched from the Cover Art Archive using the relevant MusicBrainz release identifier.

When Discs verifies a rip, it sends the disc's table of contents to CTDB, the CueTools Database, and compares checksums on your device. If it finds read errors, it may download repair data from CTDB. No audio or checksums leave your device. Verification is on by default and can be turned off in settings.

Album Info Reports

If you tell us an album's info is wrong or missing, Discs sends a report when you tap Send. A report includes the disc's identifier and table of contents, any CD-Text on the disc, the album info Discs found and the other matches it offered, the album info as you saved it, the reasons and note you add, your app version, operating system, language, and CD drive model.

Reports are not linked to your app identifier, account, or music library. We record the country a report came from, not your IP address. If you include an email address, we use it only to reply to you and remove it from the report after 180 days. Each report is also emailed to our support inbox through Resend.

We use reports to fix matching problems in Discs and to improve album info, and we keep the disc and album details for that purpose. If Discs can't reach our servers, it keeps the report on your device for up to 30 days and sends it later.

Your Music

Music ripped by Discs is stored on your device. Discs does not upload your audio files.

Purchases

In-app purchases are processed through Google Play Billing. Discs receives purchase and product information and verifies purchase tokens server-side to provide the purchased feature. We do not receive or store your card or bank-account details; Google handles payment processing.

Website and Email Updates

discsmusic.com uses Google Analytics to understand which pages are visited. Analytics storage is denied by default and is enabled only if you select Allow in the website banner. If you decline or ignore the banner, no analytics cookies or persistent analytics identifiers are stored in your browser. The Google tag may still send limited, cookieless measurement pings. Your choice is stored in your browser and can be reset by clearing the site's stored data.

If you ask to receive product updates, we send your email address to Resend, our email delivery provider. We use it to send the updates you requested and keep it until you unsubscribe or ask us to delete it. Every marketing email includes an unsubscribe link.

Cloudflare hosts and protects the website and may process ordinary request information, such as IP address, browser information, requested page, and request time, to deliver and secure the site.

Service Providers

We use Google Firebase and Google Play, Cloudflare, Resend, the Cover Art Archive, and CTDB for app infrastructure, analytics and diagnostics, app distribution and purchases, website hosting and network security, email delivery, and music metadata, artwork, and rip verification. These providers process information on our behalf or provide a service you request. They may process information outside your country under the safeguards described in their applicable terms and privacy documentation.

Security

We use reasonable technical and organizational safeguards designed to protect information, including encryption in transit, restricted administrative access, network controls, pseudonymous identifiers where practical, and backups where appropriate. Access is limited to people and service providers that need the information for the purposes described in this policy. No method of transmission or storage is completely secure.

Retention

• Firebase Authentication and Firestore account records are retained until they are deleted.
• Firebase Analytics user- and event-level data is retained for no more than 14 months; aggregated statistics may remain available longer.
• Firebase Crashlytics retains crash reports and related identifiers for 90 days.
• Email subscriptions are retained until you unsubscribe or request deletion.
• Album info reports are kept to improve album info until they are deleted. An email address included in a report is removed after 180 days.
• Purchase and operational records are retained only as long as needed to provide the relevant feature, protect the service, and meet legal obligations.

Legal Basis

We rely on the following legal bases:

• Performance of our contract to operate the app identifier, free-rip allowance, purchases, and purchased features.
• Our legitimate interests to prevent abuse, diagnose failures, improve hardware compatibility, and understand which features are useful. We limit this information as described above and do not use it for advertising or cross-app tracking.
• Your consent for optional website analytics, marketing emails, and album info reports you choose to send. You may withdraw that consent at any time.

Your Choices and Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to the processing of your information, withdraw consent, or complain to a data-protection authority. Contact us to make a request. Because some app records are associated only with random identifiers, we may need the identifier shown in Discs to locate the relevant records.

Contact

telepheedi LLC is responsible for the processing described in this policy. Questions or privacy requests can be sent to privacy@discsmusic.com.