MTO

Privacy Policy

Last updated: 27 September 2026

This policy explains how the Made to Order automation ("the application") accesses, uses, stores and shares Google user data. It applies to the application and to this website.

1. What the application accesses

The application uses the YouTube Data API v3 with two scopes: youtube.upload and youtube.force-ssl. Through them it accesses:

• Public comments posted on videos belonging to the application's own channel — including the comment text, the public display name and the public channel identifier of the person who posted it, and the public like count.
• The application's own channel data — its list of uploaded videos and their publication dates, so it can tell which comments are recent.
• The ability to publish videos and comments to that same channel.

It does not access any other channel, any other user's account, private messages, analytics, personal information, email, contacts, or files.

2. How that data is used

• Comment text is used to decide which request becomes the next video, and to generate that video.
• A commenter's public display name may be shown on screen in the published video, and in the public ledger, as the person who requested it.
• Like counts are used only to help rank requests.

No data is used for advertising, profiling, or any purpose other than making and publishing the channel's videos.

3. Automated processing

Comment text is processed by an automated language model to classify the request, check that it does not breach the channel's published content rules, and draft the video narration. This processing is automated; no person reads comments individually in the ordinary course of operation.

4. What is stored, and for how long

• Comment text, the public display name, the public channel identifier, the like count, and the comment's timestamp are stored locally on the operator's own computer, so that the public ledger can be generated and duplicate requests can be detected.
• This data is retained for as long as the request appears in the ledger. A request may be removed from the ledger on request — see Contact.
• OAuth credentials are stored locally on the operator's own computer and are never transmitted anywhere except to Google's own OAuth endpoints.

5. Sharing

The application does not sell, rent, or share Google user data with third parties, and does not use it for advertising. It does not transfer this data to any third party except as required to operate:

• Google, as the provider of the YouTube Data API; and
• a language-model provider, which receives comment text solely to classify it and draft narration as described in section 3.

Data is not shared with any other party, and is never made available to data brokers or advertisers.

6. Google API Services User Data Policy

The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

7. Security

Credentials are held locally with restricted file permissions and are not published. The application runs on a single private machine and is not exposed as a public service.

8. Children

The application is not directed at children and does not knowingly collect data from children.

9. Changes

This policy may be updated; the "last updated" date above will change accordingly.

10. Contact

To request removal of a comment's text from the ledger, or for any privacy question: converge.made2order@gmail.com.

---