1. Scope and operator
This policy applies to Ancient Deities Dossier™, the public website at ancientdeitiesdossier.neocities.org, and the companion application identified on its authorization screen as Ancient Deities Dossier™ Creator Console. The project is an independent educational media property. It is not operated by YouTube, Neocities, or any religious institution.
2. Public website data
The website is static and does not provide its own user accounts, comments, checkout, advertising profiles, or behavioral tracking. It may receive ordinary hosting logs through Neocities, such as an IP address, user agent, requested page, referrer, and request time, according to Neocities’ own service practices. Links to YouTube and other external services are governed by those services after you leave this site.
3. YouTube data accessed
When the channel owner explicitly authorizes the Creator Console, the application may request the minimum read-only permissions needed to retrieve:
- YouTube channel identity and public channel metadata;
- video identifiers, titles, publication status, and related video metadata;
- aggregate YouTube Analytics metrics authorized by the channel owner, such as views, watch time, audience retention, engagement, and traffic-source summaries;
- basic connected-account identity information only when needed to identify the consenting account and display the correct authorization state.
The published minimum-scope design uses youtube.readonly and yt-analytics.readonly. It does not request permission to upload, edit, or delete videos; post comments; manage subscriptions; or change the connected account.
4. How connected user data is used
Authorized data is used only to let the channel owner view and analyze Ancient Deities Dossier™ performance inside a protected local creator workflow, prepare internal performance summaries, and keep the site’s public episode catalog accurate. Connected user data is not used for advertising, credit decisions, surveillance, or unrelated profiling.
5. Storage and security
The public Neocities site never contains an authorization client secret, refresh token, Neocities API key, or private local credential. Authorization tokens are intended to remain on the channel owner’s computer in the operating system’s protected credential store. Local application logs should record actions and errors without recording access tokens. Data in transit uses HTTPS when communicating with YouTube, Neocities, or this website.
6. Sharing and sale
Connected user data is not sold, rented, or shared with data brokers or advertisers. It may be processed by YouTube to provide the authorized API, by Neocities to host the public site, or by essential local software components acting on the channel owner’s instructions. Data may be disclosed when legally required, but only to the extent required by valid process.
7. Retention and deletion
Live statistics may be cached locally only as long as needed for creator analysis. The default design is to refresh data from the authorized API rather than create a permanent remote profile. The channel owner can delete local cached analytics and revoke access at any time. Revoking connected access prevents future API access; the local application should then remove stored authorization credentials during its disconnect flow.
8. Your choices and controls
- Do not authorize the Creator Console if you do not want it to access the listed data.
- Review or revoke access through the connected account’s security and third-party connections settings.
- Disconnect the account from the authorized application to clear the local credential and cached creator data.
- Visitors can use the public site without connected-account authorization.
9. Children
The website is general educational media and is not designed to collect personal information from children. The Creator Console is an owner-operated administrative tool and is not offered to children.
10. Changes
Material changes will be posted on this page with a revised effective date. The policy will not be changed retroactively to permit materially broader use of previously collected connected user data without appropriate notice and authorization.
11. Contact
Privacy, data, licensing, and general requests may be sent directly through the protected Contact Us link. The destination address is not printed on the page. Requests concerning connected data should include “Creator Console Privacy” in the subject or opening line.