Dreamstolife3D Shorts Pipeline – Privacy Policy

Last updated: October 22, 2026

Dreamstolife3D Shorts Pipeline is a private desktop tool operated by Dreamstolife3D (dreamstolife3d.ro). It edits videos made by Dreamstolife3D and publishes them to Dreamstolife3D's own accounts on YouTube, TikTok, Instagram and Facebook. It is used only by its operator; it has no other users, no server and no database. This policy explains what data the tool accesses, how it is used, stored and deleted.

1. Google / YouTube data

When the operator connects the tool to their YouTube channel through Google's sign-in page, the tool requests these permissions (OAuth scopes):

youtube.upload — to upload the videos the operator selects to their own channel, with the title, description, thumbnail and scheduled publishing time they choose.
youtube.readonly — to read the channel's own videos, playlists and their public statistics (views, likes, comments count), so the operator can see which uploads are scheduled or published and how they perform.
youtube.force-ssl — to update the operator's own videos (change the scheduled publishing time) and to add their own videos to their own playlists.

Data received from Google: an OAuth access token and refresh token, the channel ID and name, and metadata and statistics of the channel's own videos. The tool does not access viewers' personal data, comments' authors, subscribers' identities, Gmail, Drive, contacts or any other Google service.

Use. Google user data is used only to provide the features above to the operator: uploading, scheduling and organizing their own videos and showing them their own channel statistics. It is not used for advertising, it is not sold, and it is not used to train AI or machine-learning models.

Limited Use. Dreamstolife3D Shorts Pipeline's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and security. Tokens and channel data are stored only on the operator's own computer, in local files readable only by the operator's user account. Nothing is uploaded to any server of ours; data is exchanged only directly between the operator's computer and Google over HTTPS.

Sharing. Google user data is not shared with, transferred to, or disclosed to any third party.

Retention and deletion. Tokens are kept until the operator disconnects the tool. Access can be revoked at any time at myaccount.google.com/permissions; the local token and cached channel data are then deleted by the tool, or on request to the contact below within 30 days.

2. TikTok data

An access token and refresh token, and the TikTok open_id, after the operator authorizes the app on TikTok's login page.
Basic creator information returned by TikTok (display name, avatar, allowed privacy options, maximum video length), used only to show which account will receive the video and to respect the account settings.
The status of uploads the operator starts (processing / sent / failed).

This data is used only to upload the videos the operator chooses to their own TikTok account and to show the result. It is not used for advertising, profiling or analytics, and the tool does not read followers, messages or other content. Access can be revoked in the TikTok app (Settings and privacy › Security › Apps and services permissions).

3. Instagram / Facebook data

Access tokens for the operator's own Instagram professional account and Facebook Page, used only to publish the operator's videos and posts there and to read the insights (reach, views, likes) of the operator's own posts. Access can be revoked in Facebook's Settings › Business integrations.

4. Where data is stored

All tokens and data described above are stored only on the operator's own computer. There is no server and no database; nothing is sent to third parties other than the platform it belongs to (Google, TikTok or Meta).

5. Sharing

We do not sell, rent or share any data. Videos and their descriptions are sent only to the platforms the operator chooses, at the operator's request.

6. Retention and deletion

Tokens are kept until the operator disconnects the corresponding account. After access is revoked, the local token files and cached data are deleted by the tool, or on request to the contact below within 30 days.