Privacy Policy

MapVerge Operator is operated by its individual owner for their own local Windows workflow.

Effective date: 12 September 2026 · Contact: [email protected]

Google and YouTube access

The application uses YouTube API Services. The owner grants access in Google’s browser consent flow. The approved permission categories are: view the owner’s YouTube account information; upload/manage videos within the upload permission; and view nonmonetary YouTube Analytics reports. No monetary analytics, playlist-write or broader Google permission is requested.

Application policy further restricts use to the specifically approved private integration and bounded read-only observations. Public/unlisted execution remains blocked before an actual successful API audit and separate publication authorization. Google’s handling of data is explained in the Google Privacy Policy.

What is used and why

Channel identity, owner-video metadata, private-test upload/processing/thumbnail checks and dated nonmonetary analytics support the owner’s workflow. The application stores permitted raw statistics and simple calculations locally. Advanced live derived analytics and revenue inference remain disabled. Original research, media and independent production work are separate from YouTube API observations.

Storage, protection and sharing

Windows Credential Manager protects imported client/refresh credentials and protected resumable-session data. Access tokens and transient OAuth exchange values remain in executor memory. The owner’s Desktop client configuration stays outside Git at the approved local location. Tokens, credentials and secret-store contents are excluded from general SQLite records, logs, public pages and Codex/model context.

The application does not sell YouTube API data, share it with advertisers or unrelated users, or expose a public analytics dashboard. Google receives the requests necessary for the owner-authorized features. Local files and SQLite hold operational data; the same-user Windows worker stores no password. Authorized production model work is separate and does not receive Google credentials.

Retention, refresh and deletion

Statistical observations have a finite one-year purpose horizon and continuing authorization/resource checks within 30 days. Mutable channel/video metadata is refreshed or deleted within 30 days. Daily authorization maintenance and seven-day resource refreshes are scheduled locally. Minimal audit receipts retain required structure and provenance rather than raw mutable API responses.

To delete local operational API data, the owner runs:

ytctl analytics-delete-local --acknowledgement DELETE_LOCAL_API_DATA

This disables affected analytics use and purges operational API data. It does not delete YouTube videos or original local research/production. Applicable archive and backup deletion is tracked separately with a seven-day owner-deletion target; unknown copies are not claimed erased.

Revoke access

The owner can remove access in Google Account permissions, or run:

ytctl youtube-revoke --acknowledgement REVOKE_GOOGLE_ACCESS

Revocation triggers local API-data cleanup. If a remote revocation request fails, its pending/failed state is recorded honestly. Continued use requires valid authorization; stale or revoked access fails closed. For privacy questions or deletion assistance, contact [email protected].

Website and device operation

These static information pages use no application analytics, tracking cookies, advertising, login forms or embedded YouTube player. Cloudflare Pages hosts this website and may process IP addresses and request/security logs to deliver and protect the pages; see Cloudflare’s Privacy Policy. A different host requires the notice to be updated.

The worker runs while the same Windows user is logged in and the device is on. Shutdown does not extend retention deadlines. Stale access is blocked and due maintenance resumes on the next run; the owner must ensure timely operation or retirement/deletion.

Changes

The owner reviews this notice before materially changing data uses or permissions and obtains any required renewed authorization. No private postal address is requested or published on this site.