Legal & Compliance Declaration
| Application | TuneTube - Listen to YouTube Music |
|---|---|
| Target Platform | Amazon Appstore Testing & Review Board |
| Date | June 2026 |
1. Developer Entity & Metadata
| Field | Declaration Details |
|---|---|
| Application Name | TuneTube - Listen to YouTube Music |
| API Architecture | Official YouTube Data API v3 & YouTube IFrame Player API |
| Commercialization Basis | Paid Download / Premium Subscription for Independent UI/UX Framework |
| Legal Contact | support.tunetube@gmail.com |
2. Core Architecture & YouTube API Sourcing
TuneTube functions strictly as a custom visual client interface layer. The application does not store, host, distribute, or independently provide any audio or video assets. All multimedia streams and related metadata are fetched in real-time using official channels:
- Dynamic Data Ingestion: Search results, track metadata, album artwork URLs, and playlists are dynamically requested directly from the official YouTube Data API v3 endpoints during an active user session.
- Native Media Rendering: Video and audio playbacks are instantiated through the official YouTube IFrame Player API. No media binaries are downloaded or re-hosted on developer-owned servers.
- Provider Control Preservation: Because content is sourced natively via public endpoints, all content restrictions, regional geo-blocking parameters, and copyright flags applied by YouTube or its creators are fully and automatically respected by the application.
3. Commercialization Justification & Compliance (ToS Section II.R)
The YouTube API Terms of Service explicitly permit commercialization when an application introduces substantial, independent value and functionality beyond raw data presentation:
- The Charging Metric: Users do not pay for access to YouTube video or audio content. They pay exclusively for the TuneTube Lean TV Experience, advanced UX accessibility frameworks, and a highly responsive custom design layout.
- Separation of Services: No native API capabilities or search functionalities are locked behind arbitrary paywalls that violate standard YouTube API access structures.
4. Absolute Elimination of Core Policy Violations (ToS Section III.A)
TuneTube is explicitly engineered to eliminate the common triggers that cause automated or manual Amazon store rejections:
- No Splitting of Audio/Video Streams: The application never isolates or peels audio components from video wrappers. Video containers remain intact during player instantiation.
- No Offline Local Storage / Ripping: Caching or local retention of raw audio/video files is completely blocked. Content is pulled dynamically via safe HTTP streams and dropped instantly on session destruction.
- No Background Playback Exploits: Stream rendering mirrors the active window focus state. Minimizing or obscuring the application automatically forces immediate execution of standard pause loops, complying with visual presentation guidelines.
- Preservation of Ads: TuneTube does not employ ad blockers, script injection filters, or custom playback blockers. All native programmatic advertisements delivered by YouTube play natively inside the client framework.
5. Technical Architecture and IP Security
- Official Endpoint Usage: The application depends strictly on official Google Cloud Console APIs. No private, internal, or reverse-engineered client signatures are contained within the package binaries.
- Brand Separation: The branding ("TuneTube") establishes a unique consumer identity. It avoids trademark confusion by maintaining dedicated icons and clear declarations that it operates as an independent client.
- Privacy Protocols: Profile authentications use Google OAuth Device Flow. Passwords are never stored. The backend stores only the minimum account profile fields and an encrypted OAuth refresh token needed to maintain the YouTube session.
6. Binding Compliance Affirmation
The development team of TuneTube - Listen to YouTube Music guarantees that this application serves solely as an overlay interface framework utilizing standard, publicly accessible API infrastructure. It respects all regional geo-blocking parameters, content type limitations, and streaming rules dictated by the upstream provider.
Contact
For legal and compliance inquiries, contact support.tunetube@gmail.com.