Shared privacy policy

About this policy

This policy describes the two personal-use applications separately. Their Google projects and authorization grants remain independent.

Ember Budget Backups — data and permissions

When enabled, the app requests drive.file. It accesses its app-created or owner-selected Drive files, encrypted backup bytes, and file identifiers, names, sizes and ownership/sharing metadata. It checks the owner's email in Drive ownership metadata to verify the private destination. The scope permits managing app-accessible files, including deletion, but the worker makes no deletion requests.

The app receives OAuth credentials, including a refresh token, for unattended uploads. It requests no Gmail, banking, Google Sheets, or all-Drive access.

Budget-backup storage and use

The private database and recovery source are encrypted with age before upload. The live database remains on the owner's server. Encrypted queue copies and verification receipts also remain there. The restricted uploader receives a protected server credential and cannot read the live database.

Setup handles authorization codes and tokens in memory and transfers the grant directly to the server. The downloaded client configuration remains on the desktop until the owner removes it. The private recovery identity stays with the owner, outside the server and backup Drive. Snapshot and local-restore plaintext files are temporary and removed after use; this is ordinary cleanup, not guaranteed secure erasure.

Encrypted snapshots are transferred to the owner's Google Drive for backup and recovery. Automatic backup deletion is disabled: backups and receipts remain until manually removed. Revoking access stops future access but does not erase existing copies. The owner can delete Drive backups and arrange removal of local copies, receipts and credentials. Losing the recovery identity can prevent recovery.

YouTube collector — data and permissions

The collector uses YouTube API Services with youtube.readonly and yt-analytics.readonly. It collects the owner's channel/video metadata, including privacy status; performance statistics; retention/concurrency data; and Reporting impressions and click-through rates. It collects no individual viewer identities or comment text.

Collector storage and transfers

Data is stored locally in SQLite, raw and generated CSV files, and metadata summaries for reporting and analysis. Runtime OAuth tokens and configuration are protected with Windows-user DPAPI. Analytics files are unencrypted. Current local permissions allow Users to read and Authenticated Users to modify the files; storage is not owner-exclusive.

The collector communicates with Google OAuth and YouTube APIs and downloads Google reports. It implements no automatic AI, vidIQ or Discord transmission. Any separate owner-directed Codex analysis or manual sharing of files is a separate action governed by the chosen service's terms and data practices.

Collector retention, deletion and revocation

Metadata refresh/expiry maintenance targets 30 days and runs only when the tool runs. Historical authorized statistics can remain while authorization and video checks are current; the tool does not continuously maintain or delete data when idle.

A managed-cache/token deletion command removes managed local data and credentials. A revocation command also requests Google revocation and reports failure. The owner can alternatively revoke access through Google Account connections. Local deletion and successful remote revocation are separate operations. Neither action deletes YouTube content or cancels Google's reporting job. Unmanaged or manually copied files require separate removal.

Google policies and public pages

The collector uses YouTube API Services; collector use is subject to the YouTube Terms of Service. Google handles data under the Google Privacy Policy.

These public pages contain no financial records, reports, forms, application scripts, analytics tags or advertisements. The hosting/security provider may process IP addresses and ordinary request metadata to deliver and protect them. Google API data is used for the app features described here; these applications implement no sale or advertising use of that data.

Contact and changes

For questions, complaints, or assistance removing managed data, contact: fallenpumpkingmedia@gmail.com

This policy will be updated when the applications' data practices change.