UNKWN Upload Desk Privacy Policy

UNKWN Upload Desk — App Privacy Policy

This policy describes the UNKWN Sounds private publishing workflow, including the UNKWN Reels Windows client. It covers app account connections and publishing data. It is separate from the policies that apply to shopping on the UNKWN Sounds website.

Who operates the app

UNKWN Sounds operates the app for its authorized team. Contact unkwnsoundscontact@gmail.com with privacy questions or requests to delete app data.

Information used by the publishing workflow

Connected accounts: account or channel identifiers, public handles and names, granted permissions, authorization tokens, and connection-check results.
Selected media: the audio or video files the operator chooses, generated videos, captions, titles, artist names, and product links.
Local workflow records: filenames, file hashes, local file locations, schedules, queue entries, retry and error records, upload identifiers, published links, and upload-verification results.

How and why the information is used

The app uses this information to verify the intended social account, generate requested videos, upload authorized content, check publication results, recover interrupted operations, and prevent duplicate releases. YouTube access uses YouTube API Services, including video-upload permission and read access to channel and video information needed for those checks. Enabling a schedule authorizes the corresponding scheduled publishing workflow until it is paused or disabled.

Where information goes

When publishing is authorized, the selected platform receives the generated video, caption or description, publishing metadata, and the authorization required to process that request. Google/YouTube and Meta process those requests under their own policies. The app also reads public product data from Shopify to match sample packs. It does not send the selected audio to Shopify for product matching.

Google account data is not sold, used for targeted advertising, or used to train generalized AI models by this publishing workflow. If an operator sends a support request, the information they choose to include is used to investigate and respond. Do not send passwords or authorization tokens in support messages.

Local storage and retention

The UNKWN Reels Windows client stores publishing settings and release records on the operator's computer. Its saved account credentials use Windows-backed encryption. The app does not ask for or store the operator's Google password.

Failed or incomplete uploads retain their media for recovery. In the automated Reels workflow, source inbox files and generated publishing videos are removed only after the required platform uploads have verified receipts. A local history of filenames, hashes, and posting results remains available for duplicate prevention, including records older than the dashboard's 25-day view. These records remain until the operator deletes them or requests assistance removing them. Local backups or synchronized folders are controlled separately by the operator.

Pause, disconnect, revoke access, or request deletion

You can pause scheduled uploads in UNKWN Reels and disconnect an account in Connections. Disconnecting removes that account's saved local connection; it does not itself remove historical release records or delete videos already posted.

You may revoke Google authorization at any time through Google Account permissions. Remove UNKWN Upload Desk to revoke its Google access. Meta authorization can be managed through the connected account's app or business-integration settings.

To request deletion of app account data or local publishing records, contact unkwnsoundscontact@gmail.com and identify the account and app installation concerned. Because this is a desktop workflow, deletion may require the operator to remove records and backups from the computer or synchronized storage where they are held. Deleting app data does not delete content from YouTube or Instagram; manage already-published content on those platforms.

Third-party policies and changes

The workflow uses YouTube API Services. See the Google Privacy Policy and YouTube Terms of Service. Storefront visits and purchases are governed by the website's applicable policies. This app policy may be updated when the publishing workflow or its data practices change.