Privacy policy

1. Who operates the tool

Lantern & Leaf Stories Publisher is operated by the owner of Lantern & Leaf Stories. Questions and privacy or deletion requests can be sent to nsadik1986@gmail.com.

The local publisher is for adult operation, not for children to sign up or supply personal information. The fact that the channel’s stories are made for children does not make this a children’s account service.

2. Information the publisher accesses

• Google authorisation: OAuth client configuration, access and refresh tokens, granted permissions and connection timestamps.
• YouTube channel information: the authorised channel identifier and information used to confirm the intended channel.
• Upload information: the selected video file, title, description, language and privacy settings; file size and integrity hash; transfer session, upload progress, resulting video identifier and processing/privacy verification.
• Local operation: queue controls, retry counters, timestamps and limited service logs.

The requested permissions are youtube.upload and youtube.readonly. This publisher does not request access to Gmail, Google Drive or YouTube Analytics.

3. Why information is used and shared

Information is used to authorise the owner’s connection, confirm the target channel, perform the authorised private upload, display its status, recover interrupted transfers and prevent duplicate or unintended requests.

Google receives the authorised API requests and uploaded file. The connected local story-production application receives a limited status view and can request pause, safe resume or cancellation. The bridge does not return Google credentials.

The publisher does not sell Google user data, use it for advertising, or use it to train AI models. The public information website is not connected to the publisher’s records.

This tool uses YouTube API Services. Google’s handling of information is described in the Google Privacy Policy.

4. Storage and protection

Active publisher records are stored on the operator’s Windows computer, separately from the story archive and the main app’s database. Client secrets, refresh tokens and resumable-upload addresses are protected with Windows account-bound encryption. Access tokens are held temporarily in memory.

The current installation also has inactive, encrypted installation/recovery copies that must be included in any complete cleanup. Local separation does not protect against all software running under the same Windows account. No absolute security guarantee is made.

5. Retention and deletion

In this development version, local records remain until removed by the supported revocation process or operator cleanup. A fully enforced automatic retention schedule and automatic cleanup after access is revoked externally are not yet implemented. These are outstanding requirements before this tool is represented as production/audit-ready.

For a deletion request, email the operator with enough information to identify the relevant connection or upload. Never send passwords, tokens, client secrets or private video files. The operator must include inactive recovery copies when carrying out a complete deletion request.

6. Revoke access

The local publisher’s Revoke action stops further uploads, allows an active bounded request to finish saving its state, requests revocation from Google, and removes local connection, consent-session and API upload records after Google confirms success. If confirmation fails, uploads remain stopped and the protected credential is retained so revocation can be retried.

You can also remove access directly in Google Account connections. Because external-revocation cleanup is not yet automatic in this build, also contact the operator to remove remaining local records and recovery copies.

Revocation does not delete videos already uploaded to YouTube, original story files or story archives. Those are managed separately by the owner.

7. Website visits and email

These information pages contain no analytics code, advertising, embedded video, contact form or third-party scripts. The hosting provider may process ordinary connection information, such as IP address and request logs, to deliver and protect the website. A private preview may require the hosting provider’s sign-in; that is separate from the local Google connection.

If you email the operator, your email address and message are used to respond and handle the request. Avoid including unnecessary personal information.

8. Changes

This notice will be updated when the publisher’s data practices change. The version date appears above. Contact the operator if you need clarification before authorising the tool.