Privacy.

Last updated: September 30, 2026.

Deepcut connects compatible AI clients to YouTube using Google OAuth. When you connect, Google asks you to approve the permissions Deepcut needs to search and manage playlists on the YouTube account you select.

Data we process

• Google account identifier and verified email when Google provides them.
• OAuth access and refresh credentials required to keep your connection working.
• Playlist, video, and search information needed to carry out the requests you make through Deepcut.
• Basic operational data such as quota usage, connection state, and security/session records.

How we use it

We use this data to authenticate you, perform the YouTube actions you request, prevent cross-user access, operate quota and safety controls, and maintain the service. OAuth credentials are kept server-side and are not intentionally included in model-visible tool output.

Sharing

Deepcut sends requests to Google/YouTube when necessary to provide the service and communicates tool results to the AI client you chose to connect. We do not sell personal information.

Control and deletion

You can revoke Deepcut's Google access from your Google Account permissions. Public production releases will also provide a documented account-data deletion process before general availability.

Security

Deepcut uses OAuth, PKCE, session-to-user binding, hashed Deepcut bearer tokens, confirmation safeguards for destructive actions, and restricted server-side credential storage. No internet service can guarantee absolute security.

Contact

For privacy questions, use the contact method on the support page.