Privacy
Frogtoon is meant to help people browse, watch, save, and return. That means the product may store preferences, account session details, library actions, and playback-related context so the experience can remain useful from one visit to the next. This page explains the practical categories of information involved.
What may be stored
Examples include market selection, language selection, autoplay and mini-player preferences, saved artists, saved albums, saved playlists, liked songs, recently opened items, and account session state. These are used to make the product feel persistent instead of reset on every visit.
Third-party sources
Frogtoon works with outside providers for music metadata, images, search results, and video playback. Those services may have their own policies and technical requirements, especially when playback or data resolution relies on their platforms.
Operational use
Caching, request logging, and related operational tools help the app respond faster, reduce duplicate lookups, and diagnose problems such as failed video resolution or save errors. The purpose is product reliability, performance, and service continuity.
Cookies and consent
Frogtoon uses a cookie preference flow to distinguish cookies that are necessary for core product behavior from cookies used for analytics or marketing. Users should be able to review and change those preferences later instead of being locked into a one-time choice.
FAQs
These are the practical questions that tend to matter once people move from browsing into using Frogtoon as part of their day-to-day listening flow.
Yes. Frogtoon uses cookies, local storage, and similar browser technologies for sign-in continuity, preferences, cookie consent state, and other practical site behavior. Optional analytics and marketing storage should remain tied to the user's consent choices.
It can if something only saved locally on one device instead of persisting server-side. The product should be honest about that distinction because cross-device trust depends on people knowing whether something was saved just for the current browser or for the account more broadly.
No. As the product evolves, the privacy details may need to change to reflect new features, integrations, or storage patterns. The intent is to keep this page updated so the explanation stays aligned with how the app actually behaves.
Next Step
Privacy is easiest to understand when it is paired with product behavior. If you want the practical version, the Cookie Policy, Features, and Help pages explain how consent, playback, saving, and account flows work in the actual interface.