Privacy Policy — Fluency in Action Upload
1. Who we are
Fluency in Action Upload (“the Application”) is operated by Lunex AI Solutions, a sole proprietorship registered in Denmark (https://lunexaisolutions.com) (“we”, “us”, “our”).
Contact for any question about this policy or about data handled by the Application: contact@lunexaisolutions.com
2. What this policy covers
This policy covers only the Application: an internal command-line tool that publishes our own pre-produced educational videos to YouTube channels that we own and operate.
The Application is not a product, service or website offered to the public. It is not distributed, has no user accounts, no sign-up, and no interface that any third party can reach. It is run manually, from a single computer, by the operator named above, and the only YouTube account it can ever access is that operator’s own.
If you are a member of the public reading this page: the Application does not process any data about you. Watching our YouTube videos is governed by YouTube’s own privacy policy, not by this one.
Our public website at lunexaisolutions.com is covered by its own separate privacy policy, where one applies.
3. Use of YouTube API Services
The Application uses YouTube API Services.
By using the Application, the operator is bound by the YouTube Terms of Service.
Google’s handling of any data it receives is governed by the Google Privacy Policy.
4. What data the Application accesses
The Application requests exactly two OAuth scopes, and uses each for one purpose:
| Scope | Why it is requested |
|---|---|
https://www.googleapis.com/auth/youtube.upload | To upload a video file we produced to a channel we own, and to set its title, description, tags, category, “made for kids” declaration and visibility. |
https://www.googleapis.com/auth/youtube.readonly | To read back the channel id and title of the channel that was just authorized, so the Application can confirm the video is about to be sent to the intended channel before uploading. |
The readonly scope exists solely as a safety check. We operate six channels whose names differ by a single word, and the OAuth consent screen cannot be pre-set to a specific channel. Without reading the channel identity back, a mis-selection would be silent and would publish content to the wrong audience. The Application compares the returned channel id against its configuration and refuses to proceed on a mismatch.
The Application requests no broader scope. In particular it does not request permission to delete videos, read analytics, read or write comments, manage playlists, or access any subscriber or viewer information.
5. What the Application does not do
The Application does not:
- access, collect, or process data belonging to any person other than the operator;
- read viewer, subscriber, commenter or audience data of any kind;
- read YouTube Analytics or any performance, demographic or engagement metrics;
- collect personal information, contact details, location data or device identifiers;
- use cookies, tracking pixels, advertising identifiers, or any analytics of its own;
- display advertising, or use API data for any advertising purpose;
- sell, rent, license, trade or otherwise transfer any data to anyone;
- combine YouTube API Data with data from any other source;
- use API data to train, fine-tune, or evaluate any machine learning model;
- store, cache or retain any video, thumbnail, metadata or other content retrieved from YouTube. Content moves only in one direction: from our computer to our own channels.
6. What is stored, where, and for how long
The Application stores exactly two things, both only on the operator’s local computer and never transmitted anywhere except to Google’s own API endpoints:
- An OAuth client secret, issued by Google Cloud, identifying the Application.
- OAuth refresh tokens, one per authorized channel, which allow the Application to obtain short-lived access tokens without repeating the sign-in flow.
Both are held in a directory excluded from version control, with filesystem permissions restricting them to the operator’s user account. They are never committed to a repository, never written to logs, never printed to the screen, and never sent to any server other than Google’s.
There is no database, no cloud storage, no backup service, and no server component. No YouTube API Data of any kind is retained after an upload completes.
Tokens are kept until they are revoked or deleted, because their only purpose is to avoid a repeated sign-in. They can be destroyed at any time by deleting the local token files.
7. Sharing
We do not share API Data with anyone. There are no third-party processors, no subprocessors, no analytics providers, and no hosting providers involved in the Application’s operation.
The only party that receives data from the Application is Google/YouTube, which receives the video file and the metadata we choose to publish, in order to publish it.
8. Revoking access
Access can be withdrawn at any time and takes effect immediately:
- Via Google: https://myaccount.google.com/permissions — find the Application and select Remove access. This invalidates every token issued to it.
- Locally: delete the stored token files, which removes the Application’s ability to obtain new access tokens.
Revoking access does not affect videos already published; those remain under our control in YouTube Studio like any other video we have uploaded.
9. Security
The Application runs on a single machine under the operator’s control. Credentials are stored with restrictive file permissions, are excluded from source control, and are never logged or displayed. All communication with Google’s APIs uses HTTPS. There is no network service, no public endpoint, and no remote access path into the Application.
No method of storage or transmission is completely secure, and we cannot guarantee absolute security. If we become aware of a credential compromise, we will revoke the affected tokens and OAuth client immediately.
10. Children
The Application is an internal production tool and is not directed to children. It does not knowingly collect any information from anyone, including children. Every video it publishes carries an explicit audience declaration; our educational content is declared not made for kids, as it is written for adult and teenage language learners.
11. Your rights
Because the Application processes no data about any person other than the operator, there is ordinarily nothing to access, correct, export or erase on anyone’s behalf. If you nevertheless believe we hold data about you, contact us at the address in section 1 and we will respond within 30 days.
12. Changes to this policy
If we change how the Application uses YouTube API Services, we will update this page and change the “Last updated” date above before the new use begins. Material changes to the stated use case will also be notified to YouTube in writing, and approval sought, as required by the YouTube API Services Developer Policies.
13. Contact
Lunex AI Solutions — Denmark
https://lunexaisolutions.com
Email: contact@lunexaisolutions.com