Last updated: March 29, 2026
Jammin stores the basic information needed to run shared listening rooms, including your display name, room code, queue activity, playback state, and chat messages sent inside a room.
When you search or paste media into Jammin, the app may process YouTube links, video metadata, playlist data, and search queries so the room can stay synced. Jammin may also keep short-lived cache entries to reduce repeated API requests and improve performance.
Jammin relies on third-party platforms such as YouTube to fetch playable media and metadata. If account connection features are enabled in the future, Jammin may also temporarily process OAuth tokens and account data only for the feature you choose to use.
Jammin may store local session details in your browser, such as your display name, reconnect state, room code, or playback mode, so the app can restore your experience after reloads or reconnects.
Most room data is temporary and exists only while a room is active. Cached search results and service session data may be retained for a limited time to support performance, reconnects, or recent room recovery.
You can stop using Jammin at any time, leave a room whenever you want, and avoid connecting any optional third-party service. If you want data removed from a hosted Jammin deployment you control, you should clear the related browser storage and restart the room environment.
For support or privacy-related questions about this Jammin deployment, contact ronikagarwal1404@gmail.com.