ARIA PLAYER / LEGAL

Privacy Policy

How personal information is handled when you use Aria Player and this legal website.

Draft · Not yet effectiveFor review only. Company, contact and other placeholder details will be completed before this draft takes effect.
On this page

Introduction

Welcome to Aria Player. Aria Player is provided by Your company Name ("we", "us" or "our"). This Privacy Policy (the "Policy") explains the information processed when you use our Android application (the "App", package com.ariaplayer.app), its related online features and this legal website.

Please read this Policy to understand what is processed on your device, what is sent to external services, how information is used and the choices and rights available to you. The App is primarily a local media player. It does not currently provide user accounts, social profiles, paid subscriptions or a cloud media library.

This is a review draft based on App version 0.1.41. It is not yet effective. Operator details, public-release data arrangements and the placeholders in this document must be completed before it becomes the final policy. Viewing this page is not consent to processing.

The Types of Personal Data We Collect and Use

The following information is processed in connection with the App. Information used locally is distinguished from information transmitted to external services.

  • Local media and metadata. With the access you grant through Android, the App reads audio, video and image files to find, display and play your library. This includes file names, locations or local identifiers, song titles, artists, albums, duration, artwork and other available file metadata. The current App does not upload your audio, video or image files to us. Some song metadata is sent for online lyric matching as described below.
  • Local App data. Playlists, favorites, recent and most-played history, local play counts, playback position and queue information, preferences, selected folders, imported lyrics and cached lyrics are stored on your device. Local history and file identifiers are not included in our custom analytics events.
  • Information you provide when contacting us. If you contact us, we receive the email address or other contact details you use, your message and any attachments you choose to provide. Please avoid sending passwords, sensitive information or media files unless needed for your request.
  • App and device information. When Firebase Analytics is enabled, its SDK processes installation identifiers, app version, device model, operating system, language, session and usage information. Online services also receive ordinary network request information. These practices are explained in the analytics, lyrics and website sections below.

Android permissions. Depending on your Android version and the feature used, the App may access audio, video and images; selected documents or folders; older Android storage permissions; playback notifications; and permission to modify system sound settings. Internet access supports lyrics, enabled analytics and legal pages. Foreground playback and wake-lock permissions support playback while the App is in the background.

Media access is used for library functions. Selected document access is also used for lyric import. A ringtone, alarm or notification sound action may write a sound file and change a system setting when authorized. File deletion may delete the actual media file; sharing makes selected content available to another application you choose.

The current App does not request access to your microphone, camera, contacts or precise location. You can manage the permissions available for your Android version in device Settings. Refusing or revoking access may limit the related features.

Online Lyrics and Song Metadata

When lyrics are loaded, the App first checks imported, local, embedded and cached lyrics. If suitable lyrics are unavailable and usable song metadata exists, it can automatically request lyrics from external providers. You do not have to press a separate search button for this request to occur.

  • LRCLIB. Matching and search requests may include the song title, artist and, where used, track duration.
  • NetEase Cloud Music. Search requests may include the song title and artist. Retrieving a matched lyric uses the provider's catalog identifier.
  • Network information. Each provider receives your IP address and ordinary request information, including the App's user-agent. The identified lyric requests use HTTPS. The audio file itself is not transmitted by lyric matching.

The App may try another provider if a match is unavailable. Returned lyrics can be cached locally. Providers process the requests under their own terms and privacy practices. Their request-log retention and processing locations have not been verified for this draft.

The current App has no separate online-lyrics switch. Using it without a network connection prevents new lyric requests, but does not erase requests already received by a provider.

Cookies and Similar Technologies

The App uses local storage and caches to save preferences, library information and lyrics. Enabled Firebase Analytics uses SDK-managed installation identifiers and may store pending events on the device. These technologies serve different purposes from browser advertising cookies.

The legal pages we provide do not set cookies, use browser local storage or embed advertising, analytics tags, contact forms or third-party fonts. The site is hosted on Cloudflare Pages. To deliver and protect the pages, Cloudflare necessarily handles network request information, such as the requested address, IP address, request time and browser or device request headers. Any hosting or security records are subject to the hosting service's processing practices.

Following a link to another website subjects that visit to the other website's practices. Blocking browser cookies does not disable Firebase Analytics inside the App or its lyric requests.

Analytics Information

The App integrates Google Firebase Analytics to measure active users, playback users, retention, actual listening duration and playback failures. Collection is enabled in the current debug and internal builds. The reviewed release configuration disables collection by default; the final public-release configuration remains to be confirmed.

When enabled, Firebase can automatically record first open, sessions, user engagement and screen information, along with app, device and installation information. Google can derive approximate geographic information from network information. The App does not request precise-location permission for analytics. Installation identifiers are pseudonymous identifiers that can distinguish installations; the data is not described as fully anonymous. We do not set a separate account-based user ID.

Our custom events record:

  • app_active: visits to the foreground and activity across a business-day boundary while the App remains visible;
  • playback_start: when a music playback task starts playing;
  • playback_progress: increments of actual elapsed music playing time;
  • playback_end: the end of a playback task and its categorized reason; and
  • playback_error: a categorized playback failure and, where available, a safe error code.

Custom fields include a business date based on Hong Kong time, played duration in milliseconds, end reason, error type and optional safe error code. Our custom analytics events do not include song titles, artists, file names, media paths, lyric text, media files, custom track IDs or custom play IDs. This exclusion applies to analytics events; the separate lyric requests described above do send song metadata.

Advertising ID collection and ad-personalization signals are disabled in the reviewed configuration. The current App does not integrate an advertising SDK, Firebase Authentication, Firestore or Crashlytics. Pending analytics events may be stored while offline and transmitted later; delivery is not guaranteed.

The current App has no in-app analytics consent or opt-out control. The applicable legal basis and any required consent arrangements for public-release analytics are your analytics legal basis and consent arrangements. Those arrangements must be finalized and implemented where required; reading this Policy does not provide that consent.

How We Use Your Personal Data

Information described in this Policy is used for the following purposes, according to the feature and build you use:

  • to find, organize, display and play media you make available to the App;
  • to save local playlists, favorites, playback history, settings and playback state;
  • to match, retrieve, import and display lyrics;
  • to perform file sharing, deletion and system sound actions you request;
  • when analytics is enabled, to measure activity, retention, playback use and listening time, and to investigate categorized playback failures;
  • to deliver and protect the legal website, respond to your messages and handle privacy or copyright requests; and
  • where applicable, to meet legal obligations and establish, exercise or defend legal rights.

We do not use the current App to sell personal data, deliver targeted advertising or build an account-based profile across your devices. We do not use its analytics to make decisions producing legal or similarly significant effects about you.

Where applicable law requires a legal basis, it must be appropriate to the activity, such as providing a requested feature, complying with a legal obligation or consent where required. The market-specific legal bases and any necessary notices remain to be confirmed in this draft. This paragraph does not itself authorize additional processing.

How We Share Your Personal Data

Information may be received by the following parties for the purposes described:

  • Google Firebase Analytics. Google processes enabled analytics events and related SDK information to provide analytics services. See Firebase privacy information and Google's Privacy Policy.
  • Lyric providers. LRCLIB and NetEase Cloud Music receive lyric lookup information directly from the App. They operate independently; identifying them does not imply a partnership or endorsement.
  • Website hosting. Cloudflare receives requests for these legal pages and associated network information. See Cloudflare's Privacy Policy.
  • Destinations you choose. If you share media through Android, the receiving application or service receives the content you select. If you email us, the email providers involved handle the message as part of delivery and storage.
  • Legally required recipients. Information we hold may be disclosed where required by law or a valid legal process, or where lawfully necessary to protect rights and address misuse. A reference to possible disclosure does not grant unlimited access to your device.

The current App does not upload your media library to a cloud storage service. We do not sell your media files or analytics records. Independent services' processing is governed by their applicable terms and policies; we do not promise control over all information already received by those services.

The Security of Your Personal Data

The App uses Android's permission and application storage controls for local access. The identified lyric services and legal website are accessed through HTTPS. These measures help protect access and transmission, but no device, storage system or network transmission can be guaranteed completely secure.

You can help protect local information by controlling access to your device, reviewing permissions and sharing destinations, keeping software current and maintaining backups of important files. These suggestions do not transfer our legal obligations to you.

Data Retention

Retention depends on the information and where it is held:

  • Local media. Original files remain in the locations you manage until deleted by you or another authorized application. Uninstalling the App does not automatically delete those files.
  • App-managed information. Preferences, playlists, playback history, imported lyrics and caches remain locally until changed, cleared or removed. Android's Clear cache and Clear storage actions have different effects; Clear storage can remove App-managed information.
  • Device backups. Android backup is enabled. Device or account backup settings may retain or restore some App data. Uninstalling does not necessarily remove backup copies.
  • Analytics. The confirmed event and user data retention configuration is your analytics data retention period. It remains to be verified before public release. Aggregate reporting may have different retention from underlying event and user data.
  • Support correspondence. The intended retention period or criteria are your support correspondence retention period, subject to applicable legal obligations and the need to resolve requests or disputes.
  • Provider records. Lyric providers, Cloudflare and other independent services apply their own retention practices. Relevant request-log and hosting retention details remain to be verified; this draft does not promise a deletion period on their behalf.

Clearing App storage, removing a permission or uninstalling does not itself delete information already transmitted to an external service. For questions or requests about information we hold, use the contact details below once finalized.

International Data Processing

Google, lyric providers, Cloudflare and email providers may process information on infrastructure outside your country. The processing locations depend on the service and its arrangements; the location of users or the Hong Kong business date used in reports does not determine where data is stored.

The applicable processing locations and any required international-transfer safeguards are your international data processing locations and safeguards. These arrangements remain to be verified for the intended release markets. This draft does not claim that a particular data residency or transfer mechanism is already in place.

Information Relating to Children

The intended audience and any applicable minimum age for public release are your intended audience and minimum user age. Age requirements and any necessary parental consent arrangements must be confirmed for the release markets. The current App does not implement age verification or a parental consent system.

If you are a parent or guardian and believe a child's information has been processed inappropriately, contact your email address once the address is finalized. We will consider the request and any steps required by applicable law. Please provide only information reasonably needed to explain and locate the issue.

Complaints

If you have a concern about how information is handled, you may contact your email address once the contact details are finalized. Describe the issue and how you would like us to respond, without sending unnecessary sensitive information.

Depending on applicable law, you may also complain directly to a competent data protection or privacy authority. You do not have to give up that right or contact us first where the law allows a direct complaint.

Changes to This Policy

We may update this Policy to reflect changes to the App, information practices, service providers or legal requirements. The updated version and effective date will appear on this page.

Where required by applicable law, we will provide additional notice and obtain any necessary consent before a relevant change takes effect. Continuing to read this page or use the App is not treated by this draft as blanket consent to new data collection.

Contact

For privacy questions and requests, please contact:

Operator: Your company Name
Address: your company address
Privacy email: your email address

The contact details are placeholders for this review draft and are not functioning contact channels.

Your Rights and Choices

Depending on your location and applicable law, you may have rights to request access to, correction or deletion of personal information, a copy or portability of information, restriction of processing, objection to processing, or withdrawal of consent where processing relies on consent. Withdrawal does not affect the lawfulness of processing carried out before it. Rights are subject to the conditions and exceptions under the law that applies.

You can manage Android permissions, choose the files and folders made available, clear local App data and stop using the App. Some local playback features work offline. The current App does not provide an analytics opt-out, an online-lyrics switch or an account deletion page.

To raise a privacy request, use your email address once the address is finalized. We may request information reasonably needed to verify the request and locate relevant records. The App has no account-based identity, so locating particular pseudonymous analytics records may require additional information; we cannot identify a record from your name alone. We will not ask you to send your full music library or passwords for this purpose.

Requests concerning an independent provider's own records may need to be directed to that provider. Any response, appeal or further remedy will follow applicable law.

Contact: your email addressBack to top