Privacy Policy
Draft published November 1, 2026. This document must be reviewed against the final public application implementation before OAuth verification.
Who we are
XiDOS Software is the software-development name used by The Way To Native Chronicles for the applications described on this website.
What information the applications use
Channel Analyzer obtains channel and video information through Google's YouTube Data API and YouTube Analytics API after the channel owner authorizes access. The program is designed to request the read-only OAuth scopes youtube.readonly and yt-analytics.readonly. Information may include video IDs, titles, descriptions, dates, available performance metrics and original uploaded filenames when returned by YouTube.
Next Video Advisor reads user-selected local video CSV exports and uses those records with locally running AI software. File Name Discoverer reads a locally selected CSV export. Neither of those utilities needs Google sign-in to operate on locally supplied files.
Why we use the information
Channel data is used to create requested exports, help users analyze and organize their own videos, and provide inputs for companion creator tools. We do not request permission to upload, edit or delete videos.
Where data and credentials are stored
The current desktop applications are designed to perform their processing on the user's own computer. Channel Analyzer stores exported files locally and may store Google authorization tokens locally to maintain authorized access. Those tokens should not be shared with others. The website itself does not collect the customer's YouTube credentials or perform YouTube OAuth sign-in.
Sharing and third parties
Google processes authorization and API requests according to its own policies. Ollama-based local AI operations are designed to run on the user's machine. We do not offer advertising-based sale of customer YouTube account information. Software purchases or contact made through Buy Me a Coffee are subject to that service's separate privacy practices.
Data retention and removal
Users control local CSV exports and application-generated data on their devices and can remove those files. They can revoke an application's Google access using Google Account third-party connections. Revocation does not automatically delete local exports; those must be removed separately. Local app preferences and cached tokens may also need to be removed using application documentation.
Security
Do not send anyone your OAuth client configuration, access tokens or refresh tokens. We aim to request the minimum Google access required and to preserve on-device processing. No method of software or internet access can guarantee absolute security.
Google API Services User Data Policy
Use of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements where applicable. This site is not affiliated with or endorsed by Google or YouTube.
Contact and policy questions
Questions about our software or this policy can be directed through our Buy Me a Coffee page or our YouTube channel. A dedicated, monitored privacy contact address should be added before requesting Google's production verification.