Tinyo Privacy Policy

Privacy Policy · Updated October 11, 2026

Tinyo respects your privacy and processes only the information needed to provide the product.

Information We Process

• Account information: the account identifier from Sign in with Apple, Tinyo user ID, display name, and built-in avatar ID.
• Device security information: a random device ID, device public key, and request-signing information.
• Music information: Apple Music permission state, music region, and track information needed for playback and discovery.
• Listening feedback: likes and removals, longer listening, song changes, playback outcomes, and associated times and durations. A quick song change is recorded but is not treated as dislike.
• Optional usage analytics: Welcome preselects analytics; you can deselect it before continuing with Apple sign-in. Events are sent only after you actively continue with the choice enabled or enable analytics later in Me. Starting with 1.4.2, this choice controls both PostHog and Google Firebase. They receive installation identifiers, platform, and limited app open, onboarding, playback, song change, favorite, and share-sheet event types. Firebase also processes SDK session and lifecycle events, app/system versions, and device information. Tinyo does not attach track titles, music IDs, library contents, or Tinyo account IDs. IDFA/IDFV, advertising personalization, automatic screen reporting, and app session replay are disabled.
• Favorites and local data: favorite track IDs, favorite timestamps, playback queues, necessary settings, and caches.
• Support information: issue descriptions, optional email, and device information that you choose to provide.

On-Device Diagnostic Logs

Tinyo records diagnostic information such as request and response status, timing, and error categories on your device, in the debugger/Console and rolling files in the app sandbox. The rolling log files are retained for up to 7 days or 20 MiB in total, whichever limit is reached first. Logs exclude tokens, private keys, signatures, full account or device identifiers, and personal music library contents. Tinyo never automatically uploads diagnostic logs. Log files are shared with a recipient you select only when you initiate sharing via ShareLink in Welcome or Profile.

Firebase Crash Reports

Starting with 1.4.2, Firebase Crashlytics sends crash stack traces, random SDK installation identifiers, and necessary app/system/device diagnostics to Google to improve stability. Reporting is default on, independently of usage analytics, and can be disabled using Share crash reports in Me. Tinyo does not attach account identities or music metadata and does not send local rolling log files; local logs and Crashlytics reports are separate data flows. SDK automatic uploads remain disabled; at startup the app requests submission or deletion of pending reports according to the crash preference. Disabling prevents new submissions and clears pending reports on subsequent launches; reports already submitted cannot be recalled. Disabling does not remove the SDK crash handler, and a local diagnostic cache may remain.

How We Use Information

• Establish and protect Tinyo accounts.
• Provide playback, discovery, favorites, and cross-device restoration.
• Store profiles and necessary service state.
• Improve product quality and investigate problems.
• Process account deletion and support requests.

Community and public Favorites

• When you use community features, public votes, comments, comment likes, reports, and blocks are separate from personal favorites. New hearts cast independent votes, historical favorites do not backfill, and charts do not identify who saved a song. Capabilities depend on what the app provides.
• When public-profile and dynamic Favorites features are provided, profiles display names, built-in avatars, and random public profile IDs. The whole Favorites list defaults to Public and can be made Private in Me. Private hides the list, not the profile; old links and saved references stop exposing songs when the list becomes private.
• Saving another person’s playlist stores a live reference, not copied music, individual favorites, or votes. Sharing includes a public link and up to three previews, not full listening history or internal authentication IDs.
• Comment text is sent to the configured moderation service, including OpenAI; pending comments are visible only to their author. Reporting, blocking, and moderation state support community safety. No unverified third-party retention period is promised.

Separate support feedback

Feedback does not require Tinyo sign-in. Active submission sends a subject, message, follow-ups, optional email, version/build, platform, OS, language, and necessary App Attest/conversation-access materials; it does not automatically attach accounts, listening history, location, or logs. Text and email may identify you. Drafts stay in current memory and credentials in this device’s Keychain, not account sync. Replies are viewed on the original device without automatic email or push. Account deletion does not automatically delete support conversations; contact info@xunova.tech for privacy requests.

What We Do Not Do

• We do not sell personal information.
• We do not upload your complete Apple Music library.
• We do not upload or store Apple Music audio files.
• We do not upload the device-signing private key.
• We do not ask for an Apple ID password or verification code.
• We do not use music data for third-party advertising profiles.

Third-Party Services

Apple provides sign-in, MusicKit, system playback and sharing; Microsoft Azure hosts accounts, favorites and functionality feedback, and OpenAI provides comment moderation. Keeping the preselected Welcome analytics choice and actively continuing with Apple sign-in, or enabling it later in Me/Profile, allows PostHog and Google Firebase to process installation-level events within the scope above. PostHog does not autocapture; Firebase also measures sessions and lifecycle events after analytics is enabled. Google hosts Crashlytics diagnostics according to the separate crash preference. Neither analytics provider participates in music recommendations. Providers may process connection information and IP addresses; disabling GeoIP enrichment does not imply no IP processing. XUNOVA’s separate service handles active support feedback. Sharing, exports and email recipients apply their own rules; website analytics and app analytics differ.

Website visits versus the app

The XUNOVA website, including Tinyo product and support pages in both languages, uses Microsoft Clarity for website visits and interactions, including session replay and heatmaps. Clarity may process browser, device, requested-URL, and website-identifier information; cookie use is subject to applicable consent requirements and browser restrictions. Website analytics are separate from the Tinyo app’s optional PostHog/Google Firebase analytics and independent crash reports. The website does not receive your Apple Music audio or complete music library. Names, email addresses, and messages submitted through the website contact form are used to handle requests you actively send and are configured to be masked in Clarity recordings.

Community deletion

Successful account deletion clears associated public votes, comments, comment likes, reports, blocks, public profiles and related references through the erasure flow. Signing in again does not inherit the deleted community identity. Exported Apple Music playlists and third-party shared copies are managed by you or their recipients. Account deletion does not automatically delete independent support conversations or identify random-installation historical analytics.

Retention and Deletion

Account information and necessary service data are retained while providing Tinyo. You can edit your profile, sign out, or delete your account from Profile. Successful deletion clears the associated cloud account, devices, listening events, and local favorites and feedback; it also disables analytics and crash reporting and resets analytics identifiers. Exported Apple Music playlists remain under your control. PostHog/Firebase analytics installation identifiers are not linked to the Tinyo account, so account deletion cannot precisely locate historical analytics or crash reports. Third-party retention follows their configuration and policies, not the 7-day/20 MiB local-log limit; contact info@xunova.tech for requests involving historical third-party data. Account deletion does not automatically delete support conversations; messages and optional email remain until an administrator deletes them, and you can contact support with conversation details to request deletion.

Your Choices

• Manage Apple Music permission in system settings.
• Edit your profile and favorites in Tinyo.
• Deselect preselected analytics in Welcome, or turn off optional analytics later in Me and reset both local analytics identifiers.
• Disable crash reporting separately in Me without changing usage analytics, music playback, or personal favorites.
• Share on-device diagnostic logs only when you choose to.
• Sign out.
• Delete your account from Profile.
• Contact us with a privacy request.

Contact

Operator: Hangzhou Xulian Information Technology Co., Ltd. Privacy contact: info@xunova.tech.