1. Introduction / Overview
SonicSyncSail is an offline-first music and video player. Its core media-library, playback, editing, and personalization features primarily operate on your device. Optional features use online or backend services, including internet radio, Google Play subscriptions, ProReward rewarded advertising, album-art web search, analytics, crash diagnostics, configuration, security checks, and user-directed Android sharing.
2. Information Stored Primarily on Your Device
SonicSyncSail primarily stores or processes the following information locally:
- Music and video metadata, including MediaStore paths and IDs
- Playlists, queues, favorites, play/skip history, and search history
- Local radio catalogue and radio state
- Tag-editing data and album art
- Pulse Editor segments and PulseSync queues and state
- Emotion tags and categories
- Dhvanic and equalizer settings
- Theme, player, and other user-interface preferences
- Cached entitlement state
This information is generally not uploaded to the SonicSyncSail backend. Clearing the app's storage or uninstalling the app normally removes app-private data, although Android backup or device-transfer features may restore some app data. Uninstalling does not delete your original music or video files. Metadata already written into original media files and public MediaStore ringtones may also remain after uninstalling.
3. Firebase Anonymous Identifier
SonicSyncSail currently has no traditional visible account and provides no username/password or profile login system. When subscription or reward backend features are used, the app can silently create or reuse a Firebase anonymous user identifier (UID). This is a pseudonymous technical identity, not a normal SonicSyncSail account. It is used for subscription entitlement, purchase restoration, reward verification, fraud and abuse prevention, and association of related backend records.
4. SonicSync Pro and Google Play Billing Data
SonicSync Pro is offered through Google Play Billing under product ID
sonicsync_pro, with monthly and annual regular plans. Google Play handles
payments and payment-card information. SonicSyncSail does not receive or store complete
payment-card details.
For billing and entitlement operations, SonicSyncSail and its backend can process:
- Product and base-plan information
- Raw Google Play purchase tokens and SHA-256 purchase-token references
- Subscription state, expiry, verification timestamps, and acknowledgement state
- Subscription lineage and anonymous ownership mapping
- Renewal, cancellation, grace, recovery, and expiration events
- Google Play Real-time Developer Notifications
- Voided or refund information and operational anti-duplicate or stale-token data
Raw Google Play purchase tokens are stored securely on the backend for subscription verification, restoration, reconciliation, and related billing operations.
5. Refund and Billing-Reconciliation Information
Google Play can send information about revoked or voided purchases, refunds, chargebacks, pending refund reviews, and subscription lifecycle events. Backend processing may retain hashed order, token, or event references; subscription state; refund-related operational information; and pending-refund response tokens when needed for the Google Play workflow. This information is used for billing correctness, subscription reconciliation, refunds and disputes, and fraud and security controls.
6. ProReward Pass and Rewarded Advertising
ProReward is separate from the paid SonicSync Pro subscription. It is earned through eligible rewarded advertisements, and rewards in release builds are verified by the server and associated with the Firebase anonymous UID. One verified reward currently grants 15 minutes of access, and verified reward time can accumulate up to two hours.
While reward access is active, current benefits include Dhvanic, unlimited PulseSync, and suppression of SonicSyncSail-controlled visual ads. ProReward is not money, virtual currency, or a purchased subscription.
Backend reward records can contain:
- Anonymous UID and claim ID
- Raw AdMob transaction ID and a hashed transaction reference
- Timestamps, reward amount, and ad-unit information
- The resulting reward expiry
7. Advertising and Consent
SonicSyncSail uses Google Mobile Ads and Google's User Messaging Platform (UMP). Active ad formats include standard banners, medium rectangles, interstitial ads, app-open ads, and rewarded ads. SonicSyncSail requests advertisements only when Google's consent system indicates that ads may be requested. Actual advertising, device, network, and personalization processing depends on Google/AdMob/UMP configuration and Google's policies.
Paid Pro and active ProReward access suppress SonicSyncSail-controlled visual ads. SonicSyncSail cannot remove audio advertisements embedded in third-party radio streams.
8. Firebase Analytics
SonicSyncSail uses Firebase Analytics. When enabled, the app's custom analytics helper sends feature category and action events. Those central custom analytics events do not intentionally include song names, search strings, or local file paths. Firebase may perform additional SDK-controlled processing according to Google's service behavior and configuration.
9. Firebase Crashlytics
Release builds enable Firebase Crashlytics for crash diagnostics, stability monitoring, and technical troubleshooting. SonicSyncSail does not add custom Crashlytics user IDs, custom keys, custom logs, or manually submitted exceptions in the audited implementation.
10. Firebase Remote Config
SonicSyncSail uses Firebase Remote Config for application update information, legal/policy version counters, configuration flags, and analytics-related configuration.
11. App Check and Play Integrity
SonicSyncSail uses Firebase App Check and Google Play Integrity-related protections for selected backend functions. These services support security, request integrity, and fraud and abuse prevention.
12. Online Radio
The radio catalogue is bundled with the app through assets or local data and is not fetched or refreshed from an online catalogue service. When you play an internet-radio station, the app connects to the selected third-party station or stream host, which receives normal network requests. Remote favicons or artwork may also be loaded from external hosts. Those providers have their own privacy practices, and SonicSyncSail does not control their availability, content, or embedded advertising.
13. Album-Art Web Search
The Tag Editor includes an optional web search. Only when you intentionally invoke it, the current song title may be sent as a Google image-search query. If you select a remote image, it may be downloaded from Google or another HTTPS image host.
14. Media Sharing and File Modification
When you choose to share selected audio, SonicSyncSail uses Android's standard share chooser. You select the recipient application or service. SonicSyncSail does not upload that media to its own backend; after another application or service receives the file, that third party controls its copy.
When you use editing features, SonicSyncSail may modify media metadata or artwork in the selected local file and may create a public MediaStore ringtone. Those file changes can remain after app-private data is cleared or the app is uninstalled.
15. Information SonicSyncSail Does Not Upload to Its Backend
The SonicSyncSail backend does not upload or store:
- Music or video files
- Playlists or local song metadata as a media library
- Emotion labels
- Pulse Editor segments or PulseSync media
- Local search history
- Generated ringtones
SonicSyncSail has no Firebase Storage media-upload feature and currently implements no external generative-AI service or API.
16. Service Providers and Third Parties
SonicSyncSail uses or interacts with services that include:
- Google Play and Google Play Billing
- Firebase Authentication, Cloud Functions, and Cloud Firestore
- Firebase Analytics, Crashlytics, Remote Config, and App Check
- Google Play Integrity
- Google Mobile Ads and Google User Messaging Platform
- External radio stream providers
- External artwork and image providers
- Recipients you select through Android's share chooser
These third parties process information under their own terms and privacy practices. SonicSyncSail does not control their services.
17. Data Retention
Local app data generally remains until it is deleted through supported app functions, app storage is cleared, the app is uninstalled, or Android backup or device-transfer features modify or restore it.
Backend records may be retained where reasonably needed for paid entitlement and restoration, subscription reconciliation, refunds and chargebacks, pending refund review, duplicate and fraud prevention, security, diagnostics, and legal or regulatory obligations. The backend does not currently define one universal deletion or expiration period for every subscription, reward, and operational collection.
18. Data Security
SonicSyncSail uses safeguards including Firebase App Check, Play Integrity, Google Play server-side purchase verification, server-side rewarded-ad verification, hashed token, order, and event identifiers for operational records, backend-only Firestore client access, and an encrypted local entitlement cache. No method of storage or transmission is completely secure, so SonicSyncSail cannot promise absolute security.
19. International Data Processing
Google, Firebase, AdMob, and other external service providers may process information outside your country. Their processing locations and safeguards are governed by their respective services and policies.
20. User Choices
- Grant or revoke Android permissions through system settings
- Clear SonicSyncSail application data or uninstall the app
- Use UMP privacy and advertising choices where available
- Manage SonicSync Pro through Google Play
- Choose whether to use rewarded ads
- Choose whether to initiate album-art web search
- Choose whether and where to share files through Android
- Request review or deletion of eligible backend information through the Data Deletion Request page
21. Data Deletion
Data deletion and Google Play subscription cancellation are separate actions. Uninstalling SonicSyncSail does not automatically delete remote backend records. Deleting SonicSyncSail data does not automatically cancel SonicSync Pro, and cancelling SonicSync Pro does not automatically delete SonicSyncSail data.
See the Data Deletion Request page for deletion information. SonicSyncSail has no visible user-created account or automated account-deletion feature. Because backend identity is pseudonymous, a request may require enough non-sensitive information to locate eligible records. Do not send raw Google Play purchase tokens by email.
22. Children's Privacy
SonicSyncSail does not intentionally solicit personal information from children. A parent or guardian who believes a child has provided information through the app or its services can contact us so the concern can be reviewed.
23. Changes to This Privacy Policy
This Privacy Policy may be updated to reflect changes in SonicSyncSail, its services, legal requirements, or privacy practices. The effective date above identifies the latest published version.
24. Contact
For privacy-related questions, concerns, or requests, contact:
Email:
contact@sonicsyncsail.com