What data WeaverClip collects, uses, and deletes.

We collect account information you provide, such as your name, email address, authentication details, plan, and support messages. When you use the product, we process the recording picture, the microphone and computer audio tracks enabled in OBS, transcripts, markers, clips, and project settings you choose to store with WeaverClip.

We also collect limited technical information needed to operate and protect the service, including device and helper versions, upload and render status, error records, usage totals, and security logs.

We use information to authenticate you, receive and verify your recording files, create transcripts and clips, provide the AI-assisted features you ask for, provide support, operate billing, calculate and enforce plan usage, prevent abuse, and maintain and improve service reliability.

WeaverClip uses service providers for functions such as hosting, cloud storage, transcription, AI-assisted processing, email delivery, analytics, and payment processing. We give each provider only the information reasonably necessary to perform its function, and each handles that information under its own privacy policy. Our payment processor receives billing information directly; complete card numbers never reach WeaverClip.

Some of that processing, including AI-assisted analysis of transcript text, may take place outside your country, in jurisdictions whose data protection rules differ from your own. Do not process recordings containing information you are not permitted to send to a third-party service provider.

Connecting a YouTube channel is optional and off until you ask for it. WeaverClip requests access to your Google account only when you press Connect on a session's publish screen, and it requests two YouTube permissions and nothing else: youtube.upload, which is what allows WeaverClip to upload a finished video to your channel, and youtube.readonly, which WeaverClip uses for one purpose only — reading the name, identifier, and picture of your own channel so the publish screen can tell you which channel you are about to publish to. WeaverClip does not read your existing videos, analytics, revenue, comments, subscribers, or playlists.

From that connection WeaverClip stores your channel identifier, channel name, and channel picture address, the permissions you granted, the date you connected, and an encrypted Google refresh token. The refresh token is the part that matters: it is what lets a multi-gigabyte upload keep going after you close the browser, and it is stored encrypted, as described in the next section.

WeaverClip uses that data to do the thing you asked for — upload the finished video to your channel with the title, description, tags, privacy setting, and made-for-kids declaration you approved on the publish screen — and to keep an honest record of what happened: the resulting video identifier, the channel it went to, the privacy setting YouTube actually applied, how many bytes transferred, and the specific reason if an upload did not finish. The upload itself is performed by the WeaverClip helper running on your own computer, which sends the finished video directly to YouTube.

WeaverClip does not sell Google user data, does not use it for advertising, and does not use it to train AI models. It is used only to provide the YouTube connection and publishing features described here. Apart from Google itself, the only providers involved are the hosting and infrastructure providers that operate WeaverClip and store its application data. Google user data is not shared with WeaverClip's AI-assisted processing providers: they never receive your Google account details, your channel identity, or any Google credential.

WeaverClip's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Signing in with Google is a separate, also optional choice. If you use it, WeaverClip receives the basic profile information in the Google sign-in token — your name, email address, and profile picture — to create and identify your account. Signing in with Google does not give WeaverClip any access to your YouTube channel; only the Connect step above does that.

Google user data is the most sensitive thing WeaverClip holds, because a YouTube credential can post to a creator's channel. These are the specific measures in place to protect it.

• Encrypted in transit. Every connection is encrypted with HTTPS/TLS: your browser to WeaverClip, WeaverClip to Google's authorization, token, and YouTube upload endpoints, WeaverClip to its database and storage, and the WeaverClip helper on your computer to both WeaverClip and YouTube. The WeaverClip site is served over HTTPS with HTTP Strict Transport Security, so browsers refuse to fall back to an unencrypted connection.
• Google refresh tokens are encrypted before they are stored. Your refresh token is encrypted with AES-256-GCM using a key held only in WeaverClip's server environment, so the value written to the database is not a usable Google credential on its own. The authentication tag means a tampered value fails to decrypt rather than decrypting to something unexpected. If that encryption key is not configured, the Connect button refuses to start the connection rather than storing a channel credential in plain text.
• Short-lived access tokens are never written down. The hour-long access token used to perform an upload is requested fresh for each upload, held in memory for the duration of that upload, and never stored in the database or written to disk.
• Encrypted at rest. WeaverClip's application database and your stored media are held with infrastructure providers that encrypt stored data at rest on their own systems. That is a layer beneath the token encryption above, not a replacement for it.
• Google credentials never reach your browser. The whole OAuth exchange — trading Google's authorization code for tokens, refreshing them, and revoking them — happens in WeaverClip's server code. The screen that shows your connected channel is served by an endpoint that reads only the non-secret columns, so no Google token is ever sent to a web page, and no Google token is ever placed in a link, a web address, or a browser store.
• The Google client secret and encryption key are server-only. WeaverClip's Google client secret, refresh-token encryption key, and database service credential are supplied as server environment variables that are never bundled into browser code and are not kept in the source repository.
• Only WeaverClip's servers can read the credential store. The table holding Google credentials has row-level security enabled with no policy granting access to a signed-in browser session, and the database roles that browser requests run as hold no privileges on that table at all. It is read and written only by WeaverClip's own server processes, using a separate server credential that is never exposed to the browser.
• One account cannot reach another account's channel. Every request that touches a YouTube connection, an upload, or a recording re-establishes who you are on the server and then restricts the query to rows you own. Publishing additionally verifies that the recording and the finished video both belong to you. A connection identifier taken from somewhere else does not give access to someone else's channel.
• Protection against forged connection attempts. Starting a connection creates a random, single-use value held on WeaverClip's servers and valid for ten minutes. The callback from Google consumes that value before it does anything with the authorization code, so a connection cannot be initiated on your behalf by another site.
• Google data is kept out of logs and analytics. WeaverClip does not write Google tokens to its logs or put them in web addresses. Its product analytics record only coarse counters — whether an account is free or paid, how many publishes remain, which control was clicked — and never a channel name, a video identifier, a video title, or any credential. Responses carrying connection details are marked not to be cached.
• Limited access, kept to what the job needs. Access to production systems is restricted to the small number of people who operate WeaverClip and is used only to run and support the service. WeaverClip asks Google for the narrowest permissions that can perform an upload, and stores only the channel details and single credential needed to keep publishing working.

No service can promise perfect security, and WeaverClip does not. What it can say is that these are the actual measures in place, that they are designed to be reasonable administrative, technical, and organizational safeguards against unauthorized access, disclosure, alteration, or destruction of your Google user data, and that if something material changes here this page changes with it.

WeaverClip keeps your Google refresh token and channel details only while your channel is connected. Disconnecting is immediate and complete: choose Disconnect on the publish screen and WeaverClip asks Google to revoke the token, then deletes the stored connection, including the encrypted token, the channel identifier, the channel name, and the channel picture address. You can also revoke WeaverClip's access yourself at any time from your Google account's third-party access settings; WeaverClip detects a revoked grant on its next attempt, stops trying to use it, and asks you to reconnect if you want to publish again.

Deleting your WeaverClip account deletes the stored Google connection with it. The short-lived value created when you begin a connection expires in ten minutes and is discarded whether or not you finish.

Records of videos you published — the video identifier, the channel, the privacy setting applied, and when it happened — are kept as your publishing history for as long as your account exists, so the app can tell you what it did on your behalf. Email the address below if you want that history removed. Deleting an upload record in WeaverClip does not remove the video from YouTube; that is done from YouTube Studio.

WeaverClip automatically deletes source recordings 30 days after a Free recording ends and 180 days after a paid-plan recording ends. The service checks for scheduled deletions every day. When a source is deleted, its transcript and already finished clips can remain while the account is current. You can permanently delete a complete recording project sooner from its session page.

After paid access ends or an unpaid account becomes read-only, you can review or delete stored recordings and download finished clips for 30 days. Remaining content is then permanently deleted unless billing is restored first. Deleting content can require a short operational period to remove active copies and backups. Billing, security, and audit records may be retained when required for fraud prevention, accounting, disputes, or legal compliance.

You can permanently delete recordings from their session pages. You can also email the address below to request access to, correction of, or deletion of personal information. Some records may be kept where law or a valid security need requires it.

For privacy questions or requests, email support@weaverclip.video. For billing questions, see the billing policy.