Privacy Policy

Last updated: August 29, 2026

Zoe Publisher is a private, owner-operated application. It uses Google OAuth 2.0, Gmail API read-only access, and YouTube API Services solely for the owner's private publishing workflow.

YouTube API ServicesUsed for uploads, processing/status reads, thumbnails, and playlist membership on the owner's channel.

Google Privacy Policypolicies.google.com/privacy

RevocationGoogle Account permissions can be used to revoke access.

DeletionAfter revocation or a valid deletion request, stored user-related Authorized Data is deleted as soon as practicable and within 7 calendar days, subject to legal requirements. Other stored YouTube API Data is deleted or refreshed within the periods required by YouTube Developer Policies.

1. Google services and OAuth permissions

Zoe Publisher uses Google OAuth 2.0 to authorize access only for the application owner. The current OAuth permissions used by the application are:

https://www.googleapis.com/auth/gmail.readonly - read-only access to the owner's Gmail data used as an upstream source for the private publishing workflow.
https://www.googleapis.com/auth/youtube.force-ssl - authenticated YouTube account access needed by the owner-operated publishing workflow.

No third-party user can connect a Google or YouTube account to Zoe Publisher.

2. YouTube API Services usage

Zoe Publisher uses YouTube API Services only for the owner's own channel. Depending on the configured workflow, it may:

upload original videos and associated title, description, language, category, tags, and visibility settings;
read the uploaded video's processing and upload status so the workflow can confirm successful processing and avoid duplicate uploads;
set a custom thumbnail for an uploaded video;
check whether an uploaded video is already in an owner-controlled playlist and add it when needed.

The application does not use YouTube API Data to create user profiles, sell advertising audiences, or provide third-party analytics.

3. Gmail API usage

Gmail read-only access is used by an upstream owner-operated workflow to locate and read selected source messages needed to generate the owner's publishing content. The permission is read-only: Zoe Publisher does not use this scope to send, modify, archive, label, or delete Gmail messages.

Raw email content is not published as a public API dataset and is not sold or rented. The publishing workflow uses only the information needed to construct and validate the owner's media output.

4. Data stored by the application

OAuth client credentials and refresh credentials are kept in private secret storage and are not exposed on this website. The application may maintain limited private operational state necessary for safe publishing, such as message identifiers, content fingerprints, YouTube video/channel identifiers, processing state, upload timestamps, and playlist reconciliation state. This state is used for duplicate prevention, recovery, and auditability of the owner's automation.

5. Sharing, sale, advertising, and cookies

Zoe Publisher does not sell or rent Google user data or YouTube API Data. It does not provide such data to advertisers or data brokers. Google user data is processed only as necessary to operate the owner's private workflow and by infrastructure providers acting on the owner's behalf where required to run the application.

This public compliance website does not use advertising or analytics cookies.

6. Revoking access

The owner may revoke Zoe Publisher's Google access at any time through Google Account permissions. Revocation prevents the application from obtaining new access tokens with the revoked grant.

7. Data deletion

If the owner revokes Google authorization or submits a valid request to delete Google Authorized Data held by Zoe Publisher, the application owner will delete the associated stored user-related Authorized Data and credentials as soon as practicable and within 7 calendar days, except where retention is required by applicable law. Other YouTube API Data is deleted or refreshed within the retention periods required by YouTube Developer Policies, including the applicable 30-day refresh/deletion rules.

Deleting locally stored authorization data does not automatically delete videos already published to YouTube. Published YouTube content can be separately managed or deleted through YouTube or an authorized YouTube API workflow.

8. Google API Services User Data Policy

Zoe Publisher's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

9. External policies

10. Contact

Privacy, revocation, or deletion requests may be sent to zoeyzhong16888@gmail.com.