Privacy Policy

quill-ytmusic — last updated 2 November 2026

Scope

This policy covers the personal application quill-ytmusic. The application has exactly one user: its owner. It is not offered to the public, has no sign-up, and accepts no accounts other than the owner's own.

What information is accessed

• Your YouTube Music listening history, read directly from your own account.
• Your liked songs and the contents of your own playlists, read only to avoid recommending songs you already have.
• Your account display name, used only to confirm which account is authorized.

Access is granted through Google OAuth 2.0 using the https://www.googleapis.com/auth/youtube scope. You can revoke it at any time at myaccount.google.com/permissions.

Where information is stored

All data stays on the owner's own computer. Specifically:

• An OAuth refresh token is stored in a local file whose access permissions are restricted to the owner's operating-system account.
• Recommendation results are held in memory during a run. Only the final playlist is written, and it is written to your own YouTube Music account.
• No listening data is copied into any external database, analytics service, or cloud storage controlled by anyone other than the owner.

How information is used

Solely to generate a private weekly playlist of music you have not yet listened to. Nothing else. There is no advertising, profiling, or model training built on your data.

Third parties

No third party receives your data. The application communicates only with Google's own API endpoints, and only for the read and write operations described above. No data is sold, rented, traded, or shared.

Data retention and deletion

• Local credential files can be deleted at any time; doing so removes the application's ability to access your account.
• Generated playlists live in your own YouTube Music account and can be deleted by you directly, exactly like any other playlist.
• Revoking access at the Google permissions page immediately invalidates stored tokens.

Security

Credentials are stored in local files with owner-only filesystem permissions. OAuth is used rather than password storage, so the application never sees or holds your Google password. Tokens are transmitted only over HTTPS to Google.

Children

The application is not directed at children and is not used by anyone other than its owner.

Changes

Any change to this policy will be reflected on this page with an updated revision date.

Contact

Questions about this policy: marshall.dillard90@gmail.com