Yaazh

Yaazh Privacy Notice

Last updated: November 17, 2026

This notice describes the desktop Yaazh application, its optional service integrations and Yaazh Cloud, the developer's server. It is also published at https://yaazh-cloud.vercel.app/privacy. Contact the developer at nagipragalathan@gmail.com with privacy questions.

Information used

Yaazh works with the recordings, media, project files, captions, titles, and other content you provide or create in the editor. Local project files and settings are stored on your computer.

When you connect Google Publishing, Yaazh uses Google authorization credentials and reads your Google account email address and Drive account identifier to identify the connected account and keep publishing destinations associated with it. It stores the account identifiers, destination folder and spreadsheet identifiers, and publishing metadata in local application files. Google refresh tokens and Desktop OAuth client credentials are stored in the operating system credential store.

Signing in

Yaazh requires you to sign in with a Google account before it opens. Sign-in asks Google only for your basic profile (the openid, email and profile scopes) and does not request access to your Drive, Sheets or other Google data. Yaazh stores your Google account identifier, email address and name in the operating system credential store on your computer, to show who is signed in and to keep you signed in. It keeps no Google access or refresh token for sign-in and never sees your Google password. Signing out removes this from this computer; you can also remove Yaazh under Google Account connections.

Yaazh Cloud (your plan)

You sign in on Yaazh Cloud's sign-in page, which Yaazh opens in your browser. Google gives that page an ID token (your account identifier, email address and name, signed by Google). Yaazh Cloud checks it with Google and keeps it for at most ten minutes, until the Yaazh app on your computer collects it with a one-time code; it is deleted when collected. Yaazh then uses it once to start your session with Yaazh Cloud, which tells Yaazh which plan you are on and what it includes. Yaazh Cloud stores:

  • your Google account identifier, email address and name;
  • your plan and whether your account is active;
  • when you signed up, each time you signed in (with the Yaazh version and operating system), when you were last seen, and your last Yaazh version and operating system;
  • each use of the in-app AI assistant and each export: the time, and for the assistant only the provider and model, for an export only its format, height, frame rate, length and whether it carried a watermark.

Yaazh Cloud never receives your recordings, projects, captions, prompts, assistant conversations or files. It does not store your IP address; to limit request rates it keeps a one-way hash of the address for about a minute. Yaazh keeps a token for Yaazh Cloud in the operating system credential store, and a signed copy of your plan, the uses not yet sent and the list of plans in its app-data folder, so it works offline for up to 14 days; after that it uses the Free plan until it can reach Yaazh Cloud again. Signing out removes the token and the cached plan from this computer. Contact the developer to have your Yaazh Cloud account deleted.

Google Drive and Sheets

Yaazh uses Google access to prepare a publishing folder and tracker in your account; upload the videos and cover images you choose; write publishing metadata and file links; and read or update tracker values, including status and custom columns. Connecting does not by itself export or upload a video, although workspace folders and a tracker may be created automatically after connection.

The recommended access mode requests only the Google Drive files created or authorized for the app. The optional all-files mode requests broader Drive and Sheets access for existing destinations. Changing a setting does not revoke a previously granted permission; you can revoke that permission in your Google Account.

Google API requests are made from the desktop application to Google's services. Yaazh's Google Publishing feature does not use a developer-hosted database for your Google files or refresh tokens. Your uploaded content remains in your Google account under the sharing settings applied there.

Connected assistants and other services

If you enable MCP or connect an AI assistant, that client can receive the content and tool results it requests, including project information and, when used, publishing metadata. An assistant can invoke authorized tools to edit or publish. Use only clients you trust. A public tunnel, if you configure one, routes traffic through the selected forwarding provider. External imports and other optional service integrations send requests to their respective providers. Those providers' privacy practices also apply.

Yaazh's Google Publishing integration does not sell Google account data, use it for advertising, or provide it to a general-purpose AI model for training. Sending information to an assistant is controlled by your choice to enable and use that connection; the assistant provider's own terms apply.

Retention and control

Local data remains until you remove it. Google files remain in your Drive until you delete them. Disconnecting in Yaazh clears its saved Google refresh token and attempts to revoke it at Google; if offline, revoke access directly through Google Account connections. Disconnecting does not delete your Google files or local project data.

You can remove uploaded files and the publishing tracker through Google Drive, remove local projects and settings from your computer, and disable the MCP server or stop a tunnel to end assistant access. Contact the support email above if you need help locating Yaazh's local data.

Security

Yaazh uses HTTPS for Google API requests, browser-based Google authorization with PKCE, and the operating system credential store for refresh credentials. Keep your computer, Google account, and assistant connection tokens secure. Anyone you give an assistant connection token to can use the editor tools available through that connection.

This notice may be updated as Yaazh's features change; the date above identifies this version.

Recording and device permissions

Screen recordings can contain private information visible on screen. Depending on the options you enable, recordings can also contain microphone/system audio, webcam video, cursor movement and keystroke visualization. Choose sources carefully and stop recording before entering sensitive information. Camera and microphone requests use the platform permission flow; Yaazh does not automatically approve webview device requests. Change device permissions in Windows Privacy & security settings.

Cloud captions, plugins and downloads

Using cloud captions sends the selected audio to Groq; cloud text conversion sends the selected text. Your API key authenticates those requests. The Store edition keeps the Groq key only in session memory; re-enter it after restarting Yaazh, or clear it in Settings to remove it sooner. Other editions store the key in local app settings. Store-edition startup removes a Groq key left in those settings by older versions. Local caption models are a separate option and may need a model download. Do not enable a cloud operation for content you do not want to share.

Installing a remote plugin authorizes the manifest's endpoint and actions. Invoking an action sends its explicit input to that server; approved media-host permissions allow direct media downloads. Local developer endpoints are available only in explicit development mode. Disable or remove a plugin in the plugin manager to stop further calls. Data already sent is subject to that provider's retention policy; contact that provider to request deletion. Local exports and downloaded media are retained until you delete them.

The Store edition excludes built-in Pinterest/video site-extraction providers and browser-based AI generation providers. Other editions may offer these separately. Optional AI clients and forwarding providers receive the information you send through them and have their own privacy terms. Ending MCP access or disabling a plugin does not erase information already received by an external service.

Uninstalling

Uninstall Yaazh through Windows Settings > Apps. User-created projects and exported media remain so that uninstalling does not erase your work. In the Microsoft Store edition, Windows removes Yaazh's app-data folder (settings, saved templates and presets, downloaded assets and the cached plan) when you uninstall; sign out first to remove the saved sign-in as well. In other editions, local settings and downloaded assets may remain. Settings provides access to the projects and app-data folders; close Yaazh before removing local data. Disconnect Google and other external services before uninstalling, or revoke their access directly with the provider afterward.

The same notice is in the Yaazh app under Settings, Privacy and data.