AZIZ PACKAGING LIMITED

App-specific privacy policy

Aziz YouTube Uploader Privacy Policy

Effective date: 4 November 2026

Aziz Packaging Limited operates Aziz YouTube Uploader for its authorised operators. This policy covers the uploader's use of Google account data. It does not describe every service on the company's general website.

Data accessed

The requested permissions are youtube.upload, youtube.readonly and, through a separate consent, drive.readonly. Drive read-only permission can read files accessible to the selected account; the app uses the configured queue and source folder for publishing and does not request Drive edit or deletion access.

Purpose and use

Data is used to check the destination channel, read approved publishing instructions, retrieve selected video assets, upload them to YouTube, apply approved metadata and visibility settings, and prevent duplicate uploads. Google user data is not sold, used for advertising profiles, or used by this application to train general-purpose AI or machine-learning models.

Storage and providers

The connection helper saves credentials on the operator's computer. The operator controls and should protect those local files and the clipboard used during setup. Credentials used by the worker are stored as an encrypted secret in a private GitHub repository. During a run, the worker writes a temporary credential file and downloads video assets into runner storage; it removes its temporary files during normal cleanup.

Google provides Drive, YouTube and authorisation services. GitHub provides private repository storage and Actions runners. These providers process data needed to operate the workflow. A private upload ledger retains source file IDs, queue IDs, timestamps, destination video IDs and upload state to prevent duplicates. Operational logs may record queue IDs, video IDs and errors. Repository access is limited to people or apps authorised by the account owner.

Approved video content and metadata are sent to YouTube. Public releases are visible publicly; private and scheduled uploads use the selected YouTube visibility settings. Google and GitHub apply their own terms, privacy practices and retention rules.

Retention and deletion

Credentials are retained while publishing access is needed. Upload-state records remain until deliberately removed or the repository is deleted, because removing them may permit duplicate uploads. Source files in Drive and published videos in YouTube remain under the operator's separate control; stopping the uploader does not delete them.

To stop access immediately, revoke Aziz YouTube Uploader at Google Account connections. The operator can also disable the workflow and remove its GitHub secret and local credential files. Contact us to request deletion of data retained by the application. Deletion from Drive, YouTube or provider backups is governed by the relevant service and must be handled separately.

Human access and safeguards

Authorised Aziz operators may access application data to configure publishing, review content, troubleshoot failures or respond to a data request. Credentials must not be placed in repository source files or public pages. The workflow verifies the destination channel and source folder, keeps a durable upload claim, and processes at most one new source per run.

Google Limited Use

Aziz YouTube Uploader's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes and contact

We will update this page and its effective date if the app's data practices change. Questions and data requests: contact@azizpackagingltd.com, Aziz Packaging Limited, Duptara, Araihazar, Narayanganj, Bangladesh.