How Wingman uses Google OAuth

FlyGD Wingman is a free, open-source EVE Online wormhole multiboxing toolkit for Windows. One of its three primary workflows uploads the fight footage you select to your own YouTube channel. That uploader is the only part of the application that touches Google.

The single scope

Wingman requests exactly one OAuth scope:

https://www.googleapis.com/auth/youtube.upload

This is the narrowest scope Google offers that permits uploading a video. Using it, Wingman calls one YouTube Data API v3 method, videos.insert, and calls it only when you have selected a recording and pressed upload. Nothing uploads on its own.

Wingman holds no scope that could read your YouTube account data. It does not list, edit or delete anything already on your channel, and it does not request your name, email address, profile picture, subscriptions, playlists, comments, watch history or analytics.

The application's Google OAuth client is verified by Google, so sign-in shows Google's ordinary consent screen. Sign-in uses Google's standard installed-application flow: your browser opens Google's own page, you authenticate with Google directly, and the response returns to a temporary listener on your own machine. Wingman never sees or handles your Google password.

The EVE tools do not use Google

Client previews, bookmark keybinds, combat alerts, Profiles, Skills and Fittings are independent of Google. They need no Google Account, they receive no Google or YouTube data, and no EVE data of yours is sent to Google. EVE authorization uses CCP's own EVE SSO and ESI services, described in the Privacy Policy. You can use the EVE toolkit without ever connecting a Google Account.

What is stored, and where

There is no FlyGD backend. Google data never reaches the maintainers, because there is no system that could receive it.

Credentials

Your Google OAuth access and refresh tokens are stored on your own PC in the application's data folder, as described in the Privacy Policy.

Channel info

The channel ID and channel title of your last successful upload, learned from Google's response and stored locally so the application can show you where uploads land.

Upload history

A local record mapping each uploaded recording to the YouTube URL it produced, kept on your PC so the application can show you what has already been uploaded.

Each upload sends

The video file you selected, plus the title, description, category and privacy status you set. Video data travels directly from your PC to Google.

FlyGD Wingman's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The Privacy Policy sets out the full disclosure, and how to revoke access at any time from your Google Account.

← Back to the FlyGD Wingman homepage