Privacy Policy

Sluice. Last updated 30 August 2026.

Sluice is a personal, self-hosted automation tool. Each person who uses it runs their own copy on their own server, using their own Google credentials. There is no hosted service, no shared backend, and no operator who receives your data.

What it accesses

With your authorization through Google OAuth, Sluice uses the YouTube Data API to:

• read public metadata about videos (title, description, duration, live status);
• check whether a video is already in a playlist you configured;
• add a video to a playlist you configured.

It requests the https://www.googleapis.com/auth/youtube scope, which is the narrowest scope that permits adding items to a playlist. It does not read your watch history, subscriptions, comments, or any other part of your account, and it never deletes anything.

What it stores

Sluice stores, in a plain file on your own server:

• YouTube video IDs it has already made a decision about, so it does not act twice;
• timestamps of when it last ran;
• log files recording what it added and why, deleted automatically after 7 days by default.

Your OAuth credentials are stored only in a local .env file on your own server. No personal information beyond this is collected or retained.

What it shares

Nothing. Sluice communicates only with Google's own APIs and YouTube's public RSS feeds. There are no analytics, no telemetry, no third-party services, and no transmission of your data to the author or anyone else.

Revoking access

You can revoke Sluice's access to your Google account at any time at myaccount.google.com/permissions. Deleting your copy of the software removes all stored data with it.

Contact

Questions or issues: github.com/IAtwi/Sluice/issues