Google API data handling

Privacy policy

This policy describes how Quarry Lens YouTube Lab uses Google and YouTube data. It applies to the owner-operated application, not to unrelated websites on the hosting domain.

1. Controller and contact

The application is operated by Nick Koops for his Quarry Lens YouTube channel. Contact: nickkoops99@gmail.com.

2. Google permissions and data

With the owner's explicit OAuth consent, the application requests youtube.readonly, youtube.upload, and yt-analytics.readonly. It can read the authorized channel's identity, video titles and privacy status, upload an owner-approved video, and read aggregate analytics such as views, watch time, and subscriber changes.

3. Purpose and limitations

These data are used only to authenticate the correct Quarry Lens channel, manage the owner's videos, and prepare private performance reports. The application does not sell Google user data, use it for advertising, or share it with unrelated third parties.

4. Storage and security

OAuth refresh credentials are stored on a private server with restricted file access and excluded from the application's public source repository. Access tokens are obtained as needed. Analytics API responses are processed for internal reporting and may be retained in owner-controlled operational records. No Google access tokens or private reports are made available on this public website.

5. Retention and deletion

Tokens are held only while the owner's connection is needed. Operational records may be retained for the owner's reporting and audit needs; there is currently no automatic fixed-period deletion policy. The owner can request deletion of locally stored tokens and related data at nickkoops99@gmail.com. Revoking OAuth consent stops future authorized API access, though local copies must be separately deleted.

6. Your choices

Google permissions can be reviewed and revoked at Google Account connections. The application requests only the permissions described above. It has no third-party user registration.

7. Website hosting

This information site uses Cloudflare to serve static responses. It sets no first-party cookies, has no forms, and loads no third-party analytics or advertising scripts. Cloudflare may process technical request data under its own service privacy terms to provide hosting and security.

8. Changes

Material changes to the app's Google data use will be reflected here. Last updated: 27 October 2026.