Privacy Policy
Rabbit Ears (formerly “MyTube”) is operated by Tran Huong. This policy explains what data is processed when you use the Rabbit Ears app on an iPhone or iPad.
1. Data stored on your device
Rabbit Ears does not require an account. Favorites, in-app playlists, watch history, saved progress, recent searches, and appearance choices are stored on your device using Apple storage technologies. A random client identifier used for service quotas is also stored on the device until you delete the app's data.
The app temporarily caches read-only YouTube responses on the device. Depending on the content, cache entries expire after about 30 minutes to 7 days and may be removed earlier by iOS when storage is needed. The YouTube API key is excluded from cache keys.
2. Rabbit Ears API service and YouTube
Rabbit Ears uses YouTube API Services. By using the app you agree to be bound by the YouTube Terms of Service, and Google processes data from those services under the Google Privacy Policy.
Browsing and search requests first pass through a Cloudflare Worker operated by Tran Huong, then go to the YouTube Data API. The request contains the search term or required content identifiers, region/language, app bundle identifier, and the random client identifier described above. Cloudflare also receives ordinary network metadata such as the IP address under the Cloudflare Privacy Policy.
The service protects the YouTube API key, validates requests, caches shared read responses, and enforces daily quotas. It hashes the IP address before storing a daily network quota counter. Client and hashed-network quota counters reset at the next day boundary in the service's Pacific time zone. Shared caches retain search responses for 6 hours, popular videos for 30 minutes, most other responses for 1 hour, and category/channel responses for 7 days; comments are not cached. Operational logs added by the service contain only the endpoint, cache status, and aggregate quota/circuit events—not search terms, content identifiers, IP addresses, client identifiers, or the API key. Cloudflare may separately process standard request metadata under its own policy.
Video playback uses the official YouTube IFrame Player inside a web view. Google/YouTube may receive ordinary network information such as IP address, cookies, diagnostics, and playback interactions under the Google Privacy Policy and YouTube Terms of Service linked above.
The player always runs in a non-persistent web session: cookies are discarded when the app closes, and any website data stored by earlier versions is deleted.
3. In-app purchases
Purchases are processed by Apple through the App Store and StoreKit. The one-time “Support Rabbit Ears” purchase (formerly “Remove Ads”) is a voluntary contribution; it does not unlock or restrict access to any video. Rabbit Ears only reads store-verified product and entitlement status. The app does not receive or store card numbers, payment details, or Apple Account passwords.
4. Advertising
Rabbit Ears shows no ads of its own, does not include Google Mobile Ads, does not use the Advertising Identifier (IDFA), and does not ask for App Tracking Transparency permission. Firebase ad-personalization signals are turned off. Ads that YouTube serves inside its own player are controlled by YouTube. Rabbit Ears does not sell your personal data.
5. Firebase Analytics and Crashlytics
In copies installed from the App Store, Rabbit Ears enables Firebase Analytics when the app starts. Analytics automatically receives app lifecycle and session events, in-app purchase events, approximate region, app/device details, and a random app-instance identifier. Rabbit Ears manually logs four feature events: whether playback started from saved progress, whether the Continue Watching shelf was shown, whether a pinned channel was opened, and how long after launch the first video started playing (a number of milliseconds). Rabbit Ears does not set a user ID or send video IDs, titles, playback position or duration, favorites, playlists, watch history, or search terms as custom Analytics data.
Firebase Crashlytics receives crash logs, stack traces, app state, app/OS versions, device type, storage and memory information, and installation identifiers needed to group and diagnose crashes. Crash reports may include recent generic Analytics events as breadcrumbs, but Rabbit Ears does not add user IDs or content details to them. Google processes this data under the Google Privacy Policy.
6. Retention and deletion
Library and history data remain on your device until you delete them in the app or uninstall the app. To comply with YouTube API Services policies, the app refreshes stored video titles, thumbnails, and channel names from YouTube at least every 30 days while you use it, and removes entries for videos or channels that are no longer available on YouTube. You can clear recent searches, history, favorites, and playlists from their respective screens. Device and service caches and quota counters expire as described above. Firebase Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal. Google Analytics user-level and event-level retention is limited by the property setting to no more than 14 months; standard aggregate reports may be retained longer. Apple, YouTube, Cloudflare, and other Google data follow their respective retention policies.
7. Your privacy choices
You can delete in-app data or uninstall the app at any time. Uninstalling removes Rabbit Ears' local app data, while data already sent remains subject to the retention periods above. Because Rabbit Ears has no account and does not expose Firebase installation identifiers, the operator generally cannot identify an individual Analytics or Crashlytics record from an email address. You may use the contact below for privacy questions.
8. Contact, support, and changes
For support, privacy questions, or requests, email danhhuongvn@gmail.com. This policy may be updated when the app or its providers change; the effective date at the top of this page will be revised.