UpQueue Privacy Policy

Version 2026-10-15 · 15 October 2026

This Privacy Policy explains how personal information is handled when you use UpQueue (the Windows desktop application) and related services on https://endlesscut.net. It describes how UpQueue uses Google sign-in and YouTube API Services and applies to users who connect a YouTube channel in the app, including users reviewing this policy for Google OAuth or API verification.

Controller / operator for UpQueue:

Operator: Viktoriya Lisitsa
Status: Australian sole trader
ABN: 71488618836
Product: UpQueue
Product website: https://endlesscut.net/en/upqueue
Legal and privacy contact: Viktoriya.Lisitsa@outlook.com

Read this policy together with the UpQueue Terms of Service and Licence Terms, the main Terms of Service, and the main Privacy Policy. For site-wide cookies on https://endlesscut.net, see the Cookies Policy.

1. What UpQueue is

UpQueue is desktop software for Windows that helps you manage a local upload queue and send video files from your computer to YouTube using Google sign-in and the YouTube API. Video bytes are sent from your device to Google; they are not uploaded through the endlesscut.net storefront server for publishing.

The website https://endlesscut.net provides product information, account registration, licence purchase where available, and downloads. Account and payment processing for UpQueue may use the same account system as other products on the site.

2. Whose information this covers

This policy applies if you:

visit the UpQueue product pages on the website;
create or use an account to buy or manage an UpQueue licence;
install and run the UpQueue Windows application;
connect a YouTube channel through Google sign-in inside the application.

3. Information processed on the website (account and licence)

When you use the website for an UpQueue account or licence, we may process information needed to operate your account and licence, including:

email address and authentication data;
licence status, activation code, expiry, product coverage, and device-binding status;
order and payment status;
technical and security data, such as IP address, needed to operate and protect the service;
support messages you send us.

Full payment card details are handled by the payment provider shown at checkout and are not stored by us as full card data.

A single website account may contain one or more independent licences. Each licence may have its own activation code, expiry date, product coverage, renewal status, and device binding.

For EndlessCut-only legal documents and the Russian-language public offer and payment/refund rules used at RUB checkout, see the relevant legal pages on https://endlesscut.net. UpQueue product pages link to this Privacy Policy for UpQueue-specific processing.

4. Information processed in the UpQueue application (on your computer)

The application stores data locally on your Windows PC. By default, the profile folder is `%LOCALAPPDATA%\UpQueue\UpQueue\` through Windows application data paths. You can point to another folder with the `UPQUEUE_DATA_DIR` environment variable.

Typical local data includes:

`upqueue.sqlite3` — your upload queue, including local file paths, titles, descriptions, tags, visibility, schedule and upload state, YouTube video IDs when assigned, and linked channel identifiers;
`connections/` — one DPAPI-encrypted file per connected YouTube channel containing Google OAuth tokens, including access and refresh tokens as returned by Google;
`license.bin` — a DPAPI-encrypted licence cache containing the activation code, expiry, last successful online validation time, product key `upqueue`, and a hashed device-binding value; raw hardware identifiers are not stored in this file;
`oauth_token.bin` — a legacy single-account token file from older versions, if still present; the app may migrate it into `connections/`;
log files in the application log directory, with secret redaction; logs are not sent to us automatically.

Depending on how you use UpQueue, the application may also process Google / YouTube account connection data, queue and publishing settings, and licence verification data as described in this policy.

We do not receive your video file content through our website servers for publishing to YouTube.

5. Google OAuth and YouTube API Services

5.1. When you connect YouTube, you use Google’s OAuth sign-in flow in your browser using the desktop installed-app flow with a temporary local redirect. Google’s terms and privacy policy apply to that sign-in process.

5.2. UpQueue uses YouTube API Services to upload and manage videos according to the metadata and files you configure in the app, including operations such as resumable upload through `videos.insert`, channel identity through `channels.list`, and updating publish time or privacy through `videos.update`.

Google’s handling of information is described in the Google Privacy Policy. You can also review the YouTube Terms of Service.

5.3. OAuth scopes and Limited Use. By default, the app requests these OAuth scopes:

`https://www.googleapis.com/auth/youtube.upload`
`https://www.googleapis.com/auth/youtube.readonly`
`https://www.googleapis.com/auth/youtube.force-ssl`

UpQueue’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

We use Google user data only to provide the user-facing YouTube connection, upload, scheduling, and publishing functions that you request in the application. We do not use Google user data for advertising.

5.4. Revoking access. You can revoke UpQueue’s access to your Google account at any time through Google Account permissions. Revoking access stops future authorised API calls by UpQueue using that connection. It does not by itself delete data already stored on YouTube or local data stored on your computer.

5.5. Disconnect channel. In the application, Disconnect channel deletes the encrypted OAuth credential file for that channel. A record of the channel name and identifier may remain in the local database until you reconnect or delete local application data.

5.6. Uninstalling UpQueue or deleting its local profile folder removes local queue data, locally stored tokens, and the local licence cache. It does not by itself delete your website account, order records, or server-side licence record.

6. Why we use this information

We use information to:

provide and secure your website account and UpQueue licence;
activate and enforce one-computer device binding for the licence;
operate the local upload queue and send configured uploads to YouTube at your direction;
provide the Google / YouTube functions you explicitly use;
process purchases, licence status, and renewals where applicable;
respond to support requests;
prevent abuse and unauthorised access;
comply with applicable law.

For licence activation and status checks, the app sends the activation code, product key `upqueue`, and a hashed machine identifier to the licence service at https://endlesscut.net.

7. Network requests from the application

Besides uploads and API calls to Google / YouTube using your authorised channel connection, the application may contact:

https://endlesscut.net — for licence activation at `/api/license/activate` and licence status at `/api/license/status`, using the activation code, product key `upqueue`, and hashed machine identifier;
https://endlesscut.net/updates/upqueue/stable.json or `test.json` on test builds — to retrieve the applicable update manifest when an update check occurs.

Diagnostic codes for licence network errors are designed for logs and the user interface. They are not a separate telemetry product, and application logs are not automatically sent to us.

8. Sharing and service providers

We may share or transmit information only as needed for the relevant function, including with:

Google / YouTube — when you connect a channel and use YouTube functions in UpQueue;
hosting and email providers — to operate the website, account, licence infrastructure, and transactional email;
the payment provider shown at checkout — when you purchase or renew a licence. For RUB checkout, the payment service is Prodamus; other locales may use the provider shown at the relevant checkout.

We do not sell personal information.

We do not sell Google user data or use Google user data for advertising, personalised advertising, creditworthiness, or advertising profiles.

9. Retention

Website account and licence data: retained while needed to operate your account and licences and for order, accounting, security, legal, and dispute-resolution requirements.
Application data on your device: retained locally until you disconnect channels, delete the relevant local data, or uninstall the application.
Google / YouTube data on Google systems: governed by Google, YouTube, and your account settings.
OAuth credentials stored locally by UpQueue: retained until you disconnect the relevant channel, remove the local application data, or otherwise revoke and remove the connection.

We do not keep personal information longer than reasonably necessary for the purpose for which it is processed, subject to legal and record-keeping obligations.

10. Security

We use reasonable technical and organisational measures to protect information held by us.

On your computer:

OAuth token files are encrypted using Windows DPAPI for the current Windows user;
the local licence cache is encrypted using Windows DPAPI;
queue data in SQLite is stored as local files protected by your Windows account and device security;
logs are designed to redact secrets and are not automatically uploaded to us.

No security measure can guarantee absolute security.

11. Your choices and privacy rights

You can:

disconnect a YouTube channel in UpQueue;
revoke UpQueue access through your Google Account permissions;
delete local UpQueue data from your computer;
contact us about personal information held in the website account or licence systems.

Where the Privacy Act 1988 (Cth) applies to us, you may have rights under that Act. Depending on where you live, you may also have rights under other applicable privacy laws. This policy does not limit rights that cannot lawfully be waived.

For access, correction, deletion, or other privacy requests relating to information held by us, contact Viktoriya.Lisitsa@outlook.com.

For information held by Google or content shown on YouTube, use the relevant Google and YouTube account tools.

12. Updates to this policy

We may update this policy when the product, legal requirements, Google / YouTube requirements, service providers, or data practices change.

The version date at the top of this page will be updated when the policy changes. Where applicable law requires notice, consent, or another action before a change can apply to particular processing, we will follow that requirement.

Continued use of UpQueue does not replace any consent or other legal basis that applicable law requires us to obtain separately.