Effective date: August 12, 2026. Last updated: September 7, 2026.
oSamp is a desktop application developed by Rafał Danis (the “Developer”). Privacy contact: kontakt@ifcode.dev.
Data processed by the application
The core player functions operate locally. oSamp reads audio files selected by the user, their paths, metadata and cover images, and stores settings and playlists on the device. This data is not sent to the Developer.
If the user connects a Google/YouTube account, oSamp receives read-only access to YouTube data needed to display the channel, playlists and their contents, including private playlists, liked videos and the user's uploads. The application stores a Google refresh token, channel name and playlist cache locally. It does not read the Google password and cannot modify the YouTube account.
When the lyrics feature is used, the application sends the track title, artist, album and duration to LRCLIB. When YouTube content is played, technical connection data may be processed by Google/YouTube under their own policies.
Sharing, transfer, and disclosure of Google user data
oSamp does not send Google user data to the Developer or to any server controlled by the Developer. The Developer does not sell, rent, or share such data with advertising platforms, data brokers, information resellers, or any other third party for its own purposes. Google user data is not used for advertising, marketing, profiling, credit-worthiness, or to train or improve generalized artificial-intelligence or machine-learning models.
Google user data may be transferred only to the following recipients and only to the extent required to provide a feature explicitly selected by the user:
- Google/YouTube - oSamp communicates directly with Google and YouTube services to perform OAuth sign-in, retrieve the YouTube data authorized by the user, and play selected content. Google/YouTube receives the related API requests, authorization token, and technical connection data under its own policies.
- LRCLIB - only when the user explicitly requests lyrics for a selected track, oSamp sends the track title, artist, album, and duration required to find the lyrics. If the selected track comes from YouTube, these fields may originate from data returned by YouTube. oSamp does not send LRCLIB the OAuth token, Google Account identifier, channel information, playlist lists, playlist privacy status, liked-video list, or any other Google Account data.
Except for the cases described above, oSamp does not transfer or disclose Google user data to any third party. No external service provider processes OAuth tokens, channel data, or playlists on the Developer's behalf. This data remains on the user's device and is not read by the Developer or any other person.
oSamp's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Purpose and security
Data is used only to provide features selected by the user. The Developer does not use it for advertising or analytics and does not receive a copy of locally stored data.
Connections to external services use HTTPS, and Google sign-in uses OAuth 2.0 with PKCE. Locally stored data is protected by the security of the user's operating-system account and device.
Retention and deletion
Data remains on the device until the user signs out, removes playlists or application data, or uninstalls oSamp. Signing out of YouTube removes the stored token and account data from the application. Access can also be revoked in the Google Account security settings. Because oSamp does not create its own account and the Developer does not store user data on a server, there is no separate oSamp account to delete.
Changes
This policy may be updated when the application changes. The current version will be published at this address.