Privacy policy

Last updated 17 August 2026.

Quiet Upload lets you publish your own videos to YouTube channels you own. This policy describes exactly what it touches and what it keeps.

What it accesses

With your consent, and only for channels you connect, the app uses YouTube API Services to:

read the channel's own details — its id, name, handle and description;
read the channel's counts: subscribers, total views and video count;
list your ten most recent uploads and read their titles, publication dates and durations. This list comes from your uploads playlist, so it can include videos you have set to private or unlisted;
read the view, like and comment counts of those videos;
upload the video file you choose, with the title, description, category and privacy setting you enter, and notify your subscribers as YouTube normally does for a new upload;
change that video's privacy setting after the upload finishes.

It requests the youtube and youtube.upload scopes for this, and openid email to know which account you are. It does not set thumbnails, edit videos it did not upload, or write to your playlists.

What it stores

Your Google account identifier and email address, and one encrypted OAuth refresh token for each channel you connect. Refresh tokens are encrypted at rest. Video files pass straight through to YouTube and are never written to disk here.

What it does not do

It does not use the YouTube Analytics API and cannot see your audience reports, watch time, demographics or revenue. The only numbers it reads are the public counts described above. It does not read your comments, your viewers, or any channel you have not connected. It does not sell your data, serve advertising, build profiles, or use any of it to train models, and it transfers nothing to third parties for their own purposes.

How it protects your data

The sensitive data this app holds is your OAuth refresh tokens, which grant access to the YouTube channels you connect, together with your Google account identifier and email address. These are protected by the following measures.

Encrypted at rest. Every refresh token is encrypted with authenticated encryption — AES-128-CBC with an HMAC-SHA256 tag, using the Fernet scheme from Python's cryptography library — before it is written to the database. The key is derived from a secret held in Google Secret Manager and is never stored in the database, in the source code or in the repository. The tag is verified on every read, so a tampered value is rejected rather than used. Anyone who obtained a copy of the database would see ciphertext.
Encrypted in transit. All traffic runs over HTTPS with TLS, between your browser and this app, between this app and Google's APIs, and for the direct video upload from your browser to YouTube.
No client access to stored data. Database security rules deny every read and write from a browser. All access goes through the server, which checks your signed session first and can only reach the records belonging to your account.
Tokens never reach the browser. Video files upload from your browser straight to YouTube over a session URL issued by Google. Access tokens and refresh tokens stay on the server and are never sent to the page or exposed to client-side code.
Signed, expiring sessions. Session and sign-in values are HMAC-signed with their own expiry and verified with a constant-time comparison, so they cannot be forged or replayed after they lapse.
Least privilege. The app requests only the scopes listed above, holds tokens only for channels you have explicitly connected, and stores no video content at all. Administrative access to the hosting projects is limited to the single developer named below.
Deleted on request, and on revocation. Tokens are destroyed on the timelines set out under “Deleting your data” below, so data is not retained once access ends.

Limited use

Quiet Upload's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Deleting your data

Disconnect a channel and its token is revoked at Google and deleted here immediately. Delete your account and every token is revoked and every record removed, at once. If access is revoked from Google Account permissions instead, the stored token is deleted within seven days. Any other deletion request is honoured within thirty days.

Who else handles it

The app is run by one person and has no staff. It does use infrastructure providers, which store the data on the operator's behalf and are not permitted to use it for anything else:

Google Cloud and Firebase (Cloud Functions, Firestore, Secret Manager) run the server and hold the encrypted tokens, in the United States.
Netlify serves the web pages. It does not receive your YouTube data or your tokens.
YouTube and Google APIs receive your video and its details, because that is the point of the app.

No one else receives your data. It is not sold, rented, or passed to advertisers, analytics services or data brokers.

How long it is kept

Encrypted refresh tokens are kept only while a channel stays connected. Your account record — your Google account identifier and email address — is kept while your account exists and is erased when you delete it. Channel names and counts are read live from YouTube when a page loads and are not stored. Server logs that may contain your account identifier are retained for up to thirty days and then deleted automatically.

Children

The app is not directed at children and is not intended for anyone under thirteen. It collects nothing from them knowingly. If you believe a child has used it, write to the address below and the account will be removed.

Changes to this policy

If this policy changes, the date at the top changes with it and the new version appears at this address. Changes that materially affect what is collected or how it is used will be notified by email to the address on your account before they take effect.

Governing terms

Use of this app is subject to the YouTube Terms of Service and the Google Privacy Policy.

Contact

foresightsystems00@gmail.com