Privacy Policy

Overview

Momento records gameplay and stores recordings on your Windows computer. The public build also supports YouTube upload after you import a Google Desktop OAuth client from a project you control.

Momento has no telemetry, analytics, advertising, Momento account, or cloud media library.

What Momento stores locally

Momento writes the following to your machine under %APPDATA%\Momento\ and the recordings folder you select in Settings:

• Recordings and clips: .mkv recordings and .mp4 exports in the folder you choose.
• Editor data: bookmark sidecars, thumbnails, and ownership markers beside the media they describe.
• Settings: capture, storage, game, and interface preferences in config.json.
• Logs: rotating diagnostic files under logs. Momento does not transmit them.
• Window and process state: local window placement, lock, and update state files.

The startup update request exposes your public IP address to GitHub as part of the HTTPS connection. Momento does not send machine specifications, usage history, installed games, recordings, or device selections with that request.

Update checks

An installed Windows build requests the latest stable release from api.github.com once when the process starts. It installs a verified update when Momento is idle. A manual check downloads and verifies the update, then offers Install now or Later. Source runs do not perform the startup check.

GitHub receives the source IP address and the fixed Momento-Updater/1 User-Agent, plus the standard metadata needed to serve an HTTPS request. If an update is available, Momento downloads signed metadata, its signature, and the installer from GitHub release hosts.

Momento verifies signed release metadata, the installer size, and the installer SHA-256 before staging an update. It does not send a Momento account identifier because Momento has no account system.

YouTube upload feature

The public build includes YouTube controls and Google client libraries, but it contains no Google OAuth project, client identity, or developer account data. You provide a Desktop OAuth client from a Google Cloud project you control. Read the YouTube setup guide for the required steps and Google restrictions.

Imported OAuth client

Momento reads the JSON file you select, validates its Desktop application structure and Google endpoints, and stores a normalised copy at %APPDATA%\Momento\youtube_oauth_client.dat. Windows Data Protection API (DPAPI) encrypts the stored copy and binds it to your Windows account.

Momento does not copy the imported client into recordings, logs, installers, source archives, or release assets. The original downloaded JSON remains where you saved it until you move or delete it.

Sign-in

Momento opens Google's OAuth 2.0 Desktop flow in your default browser. You enter your password on Google's site and review the requested permissions there. Momento never receives or stores your Google password.

Google expires refresh tokens for an External app in Testing after seven days when it requests Momento's YouTube scopes. You must connect again after expiry or complete Google's applicable Production and verification steps.

What Google data Momento accesses

Momento requests two YouTube API scopes:

• https://www.googleapis.com/auth/youtube.upload permits the upload you select and confirm.
• https://www.googleapis.com/auth/youtube.readonly permits one channels.list(mine=true) request after sign-in so Settings can show the connected channel's name, ID, and public avatar.

Momento does not request comments, analytics, contacts, email, or Google Drive data.

What Momento stores from Google

• OAuth refresh token: DPAPI-encrypted at %APPDATA%\Momento\youtube_token.dat.
• Channel name and ID: cached in config.json so Settings can identify the connected channel without another API request.
• Public channel avatar: cached at %APPDATA%\Momento\youtube_avatar.png.

Where uploaded videos go

After you confirm an upload, Momento sends the selected video, title, description, tags, category, audience choice, thumbnail if selected, and requested privacy setting to the YouTube Data API v3. Momento has no intermediary upload server.

Google restricts uploads from unverified API projects created after 28 July 2020 to private visibility until the project passes an audit. Google can apply that restriction even if you request Public or Unlisted. Google's videos.insert documentation describes the restriction.

Compliance with Google API Services User Data Policy

Momento uses information received from Google APIs under the Google API Services User Data Policy, including its Limited Use requirements:

• Google user data is used only to provide the user-facing YouTube upload feature.
• Momento sends upload content and metadata only to YouTube after your confirmation.
• Momento does not use Google user data for advertising, profiling, or unrelated features.
• Momento has no server that receives Google user data. A maintainer receives data only if you choose to include it in a support report.

Disconnect, revoke, remove, or uninstall

• Disconnect: Settings > YouTube > Disconnect deletes the local token, avatar, and cached channel details.
• Remove OAuth setup: the removal action in Settings > YouTube deletes the imported client and clears the local YouTube connection.
• Revoke access at Google: open Google Account permissions, select the app name you configured, and remove access.
• Uninstall: the default choice preserves settings and local account state. Accept the removal prompt, or use /PURGEUSERDATA for a silent uninstall, to delete Momento's AppData state.

The uninstaller does not delete recordings or exported clips, including when you request an AppData purge.

Children

Momento is not directed at children under 13. It contains no advertising. Google and YouTube apply their account and age policies when you use the upload feature.

Changes to this policy

If this policy changes meaningfully, the updated version will be posted here with a revised "Effective" date.

Contact

Open an issue in the Momento repository for privacy questions that do not expose sensitive data. Report vulnerabilities through the private process in the security policy.