Dispatch: Privacy Policy

Effective 27 September 2026. Applies to the Dispatch desktop application.

What Dispatch is

Dispatch is a personal desktop application, run by its author on the author's own computer, that publishes the author's own videos to the author's own social media channels and reads back the public performance figures of those videos. It is not a product or a service. It has no user accounts, no hosted instance and no users other than its author.

Use of YouTube API Services

Dispatch uses YouTube API Services to upload videos to the author's own YouTube channels, to post a first comment under those videos, and to read the statistics and analytics of those videos. By using Dispatch you agree to be bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.

Data Dispatch accesses

Through the YouTube API Services, and only after the author signs in with Google and grants consent, Dispatch accesses:

• the identity of the connected channel (channel id and title), to confirm which channel it is posting to;
• the videos it uploads (id, title, description, publish time, privacy status), so it can track them;
• public statistics of those videos (views, likes, comments, shares) and their YouTube Analytics figures (watch time, average view duration, audience retention, audience country), so the author can compare how different edits perform;
• the ability to post one comment, written by the author, under the author's own upload.

Dispatch does not access any other user's data, does not read private data of any other channel, does not download YouTube videos, does not access subscriber lists, and does not use YouTube data for advertising.

Data Dispatch stores

Dispatch stores, in a database file on the author's own computer:

• the OAuth tokens that Google issues when the author signs in, kept in a database file inside the author's own user profile on the author's computer, readable only by that Windows account, and used only to call the API on the author's behalf;
• the ids and metadata of the author's own uploaded videos;
• snapshots of the statistics and analytics figures listed above, kept so that the author can compare videos over time.

These figures are refreshed from the YouTube API Services every time Dispatch runs. The author can delete any or all stored data at any time by deleting the database file. No data is stored on any server, and no data is shared with, sold to, or made available to any third party. Dispatch uses no cookies and no analytics or tracking of its own.

Revoking access

The author can revoke Dispatch's access to their Google account at any time from the Google security settings page at https://security.google.com/settings/security/permissions, or from Dispatch itself by removing the connected account. Revoking access invalidates the stored tokens immediately.

Children

Dispatch is not directed at children and does not knowingly collect information from anyone under 18. Its single user is its adult author.

Changes and contact

If this policy changes, the new version is published at this address with a new effective date. Questions about this policy: open an issue on the Dispatch repository.