Privacy policy

1. About the app

Money Backstory Uploader is a private desktop application operated by Money Backstory for the owner of the Money Backstory YouTube channel. It uses YouTube API Services to upload reviewed videos, attach thumbnails and captions, schedule publication, and check upload and publication status.

This policy covers the uploader and this informational website. Google’s handling of information is described in the Google Privacy Policy.

2. Data the app accesses and uses

Google authorization

Google OAuth access and refresh tokens let the app make authorized requests and continue an owner-approved publishing schedule. The owner signs in directly with Google; the uploader does not request or store the owner’s Google password.

Channel information

The app reads channel identifiers and channel details returned by YouTube to confirm that the connected account owns the configured channel.

Video and caption information

The app reads identifiers, metadata, processing state, privacy settings, scheduled publication times, and caption-track information needed to manage its queued uploads.

Owner-provided material

The app reads the local video, thumbnail, caption file, title, description, language, and publishing settings selected for each reviewed release, then sends the relevant material to YouTube.

Local operational records

The app keeps a publishing queue with release identifiers, local file references, upload progress, upload-session references, video and caption identifiers, publication times, and operation or error records. These records support upload recovery and help prevent duplicate uploads.

The app requests the Google permission https://www.googleapis.com/auth/youtube.force-ssl, which supports caption management as well as video operations. Google describes this permission more broadly than the publishing features listed here. The current uploader does not use comment-management or subscription-management features.

3. Where information goes

The uploader sends authorized API requests and selected upload material to Google and YouTube. Google receives information needed to process those requests. Published videos, titles, descriptions, thumbnails, and captions become available according to the owner’s YouTube visibility and publication settings.

The uploader has no advertising, data-broker, or analytics integration. It does not sell Google user data, use it for personalized advertising, or send Google account data to AI providers. Its Google account data is used for the publishing functions described above.

Limited Use: The app’s use and sharing of information received from Google APIs is limited to the publishing features described here and adheres to the Limited Use requirements of the Google API Services User Data Policy.

4. Local storage and security

Authorization tokens and publishing records are stored on the owner-controlled computer, outside the project’s source repository. The app restricts access to its token and queue files through operating-system file permissions. Requests to Google’s token endpoint and YouTube’s API use HTTPS.

The uploader does not itself encrypt these files at rest. The computer’s account security, disk protection, and backup settings are managed by the owner. Source videos and other production files remain wherever the owner stores them.

5. Retention and deletion

The current app keeps its authorization file, local publishing queue, and operation history until the owner removes them. It does not currently have a built-in retention timer or automatic deletion following revocation. Source video and production files are managed separately by the owner.

For removal of local uploader data, contact 93jslee@gmail.com. The owner can stop the uploader and its scheduled task, remove the local authorization file and queue database, and remove any copies under the owner’s control. Deleting queue records also removes the app’s upload history, so the owner must reconcile existing YouTube uploads before starting a new queue.

Deleting the uploader’s local data does not delete content stored by YouTube. To delete a video or change a release already scheduled there, use YouTube Studio.

6. Revoke Google account access

The owner can revoke the app’s authorization at any time from Google Account security permissions by selecting the app and removing its access. Revocation prevents further authorized API access once Google applies it; it does not by itself erase local queue records or cancel a YouTube publication schedule.

Stop the local uploader and follow the local-data removal process above when disconnecting permanently.

7. Website visits and contact

These pages contain no analytics scripts, advertising, embedded video players, forms, or application-set cookies. Following an external link takes you to a service with its own policies.

Vercel hosts this website and may process your IP address, browser or user-agent information, requested URLs, request times, and related technical information to deliver and secure these pages. The uploader’s Google tokens and local publishing queue are not sent to this website or its hosting service. Further information about the hosting provider’s practices is available in the Vercel Privacy Notice.

If you email the operator, the message and contact information you provide are used to respond to your request. Please do not send passwords, OAuth tokens, or client secrets.

8. Policy updates and questions

Changes to the app’s data practices will be reflected on this page with an updated effective date.

Operator: Money Backstory
Privacy and support: 93jslee@gmail.com