Liquid Gold · liquidgold.cc

Privacy Policy

Last updated August 31, 2026

1. Overview

BourdonLab operates liquidgold.cc ("Liquid Gold"). This policy explains what we collect, why, and the choices you have. Questions go through bourdonlabs.com.

2. Information we collect

Account identity. When you sign in with Google, we receive your name, email address, and avatar to create and operate your account.

Your library activity. The channels you explore and follow, bookmarks, votes, notebooks, and learning progress.

Purchase records. What you bought and when, so receipts and download recovery keep working. Payments run through Polar — card details never touch our servers.

Technical data. Request metadata used to run the service and defend it from abuse, including Cloudflare Turnstile checks on forms.

3. How we use it

We use this information to operate your account, deliver purchases, and keep the service working. We do not run third-party product analytics or advertising trackers.

4. Public channel data

Exploration reads public YouTube data. The channel pages built from it are public — anyone can view them, the same way anyone could watch the source videos. Your private library, votes, and notebooks stay tied to your account and are not published.

5. Agent connections

AI agents you connect receive scoped OAuth tokens to read what you approved — nothing more. They never receive your password or your browser session. Disconnecting an agent revokes its access.

6. Email

You receive purchase receipts and, if you opt in, daily channel update digests. Every email carries an unsubscribe link, and you can also turn digests off from your profile or at /email/unsubscribe.

7. Retention and deletion

We keep your data while your account is active. If you want your account and its data deleted, contact us through bourdonlabs.com and we will remove it.

8. Cookies

Liquid Gold uses cookies for session authentication only. We do not run advertising trackers or sell personal data.

9. Changes to this policy

We may update this policy as the service changes. The effective date above always reflects the current version.