Privacy Policy

Account information

You sign in to Viddy with Google. We do not offer email and password accounts, so we never receive or store a Viddy password. When you sign in, we store the following from your Google profile:

• Your name
• Your email address
• Your Google profile picture URL
• The account identifier Google uses for you, and the OAuth tokens Google issues so we can keep you signed in
• Account creation and last update timestamps

Session information

For each active sign-in we store a session token, its expiry, the IP address the session was created from and the browser user agent string. This is how we keep you signed in and how we can tell one device apart from another.

Recordings and uploads

For each recording or upload we store the video file itself plus its title, its share link slug, its owner, its file size, its duration, its media type, whether it came from the desktop recorder or a browser upload, and its visibility setting.

Transcripts

If a recording is transcribed, we store the transcript text, its timestamped segments, the detected language, and the name of the engine and model used (whisper.cpp, base.en). See section 3 for where that transcription happens.

Notes and comments

We store timestamped notes people leave on a video, including the note text, the point in the video it is attached to, and which account wrote it.

Teams

If you create or join a team, we store the team name, its owner, its members and their roles, who invited whom, and the team join link token. If you invite someone by email, we store that email address, the invitation token and its expiry until the invitation is accepted or expires.

Playback counts

We count how many times a playback link is issued for each video, per calendar month, and we store an estimate of the bandwidth that implies. This is a spend control on our side. It is a per-video counter. It is not per viewer, it is not tied to any identity, and we do not record who watched or where they watched from.

What we do not collect

• No analytics, product telemetry, advertising or session replay tools run on this site. There is no Google Analytics, PostHog, Segment, Plausible, Mixpanel, Amplitude or similar in the codebase.
• No advertising identifiers and no cross-site tracking.
• No payment card details. We do not process payments today.
• No password for Viddy, because Viddy has no password login.

When you record with the Viddy desktop app, the recording is written to a folder on your own Mac first (~/Documents/Viddy/). Segments are uploaded to our storage as the recording proceeds so the share link is ready when you stop. You can choose to keep the local copy after upload.

Uploaded video is stored in a Backblaze B2 bucket that MUSCLED controls. Playback works by our server issuing a short-lived download authorization to the viewer, after we have checked that the viewer is allowed to see that video. Because the viewer then streams the segments from Backblaze directly, our servers do not see individual segment requests, which is also why we can only count playback sessions and not bytes.

A screen recording captures whatever is visible on the screen or window you selected. If you enable the microphone, it captures your voice. If you enable system audio, it captures what your Mac is playing, which on a video call includes the other participants' voices. If you enable the camera bubble, it captures your camera. You choose which of these are on before you record. Please read section 3 of the Terms of Service regarding your responsibility to tell other people when you are recording them.

Transcription runs on your computer. The Viddy desktop app ships a local copy of whisper.cpp and runs it against the recording's audio on your own machine. Your audio is never sent to OpenAI, Google, AssemblyAI, Deepgram or any other transcription provider, because no such provider is involved.

The one network request the transcriber makes is a one-time download of the open source speech model file (ggml base.en) from Hugging Face, so it can run locally. That request fetches a model. It does not send your audio anywhere.

The resulting transcript text is then uploaded to Viddy and stored with the recording, so it can appear next to the video on the share page and be searched. If you do not want a transcript stored on our servers, do not transcribe the recording.

Every video has one of three visibility settings, which you control:

• Private. Only you, the owner, can watch it.
• Everyone. Anyone who has the link can watch it, with no sign-in required. Treat this as public. If the link is forwarded, posted or indexed, anyone holding it can watch the video and read its transcript and notes. We cannot control who a link reaches once you have shared it.
• Teams. Members of the specific teams you shared it with can watch it. Anyone who joins one of those teams later, including via a team join link, will also be able to watch it.

Whoever can watch a video can also read its transcript and the notes attached to it, and can add notes of their own. Notes you write on someone else's video are visible to the owner and to everyone else who can view that video.

We do not sell your personal information and we do not share it for advertising. We use the following providers to operate the service:

• Google.Sign-in. Google authenticates you and gives us your name, email address and profile picture. Your use of Google is governed by Google's own privacy policy.
• Backblaze B2. Storage and delivery of video files, including the audio inside them. Backblaze stores the file contents.
• Resend. Transactional email only, such as a team invitation or a notice that one of your videos is getting unusually heavy playback. Resend receives the recipient email address and the message. We do not send marketing email.
• Hugging Face. One-time download of the local speech model file to your own computer, as described in section 3. No audio and no account data is sent.
• Our hosting and database provider. Runs the Viddy web application and the PostgreSQL database holding the account, video metadata, transcript, note and team records described in section 1.

Data may be stored and processed in the United States and in other countries where these providers operate infrastructure. If you need the specific storage region for your account's video data in writing, email client@muscled.co and we will confirm it.

We may also disclose information where we are legally required to, or where it is necessary to investigate abuse of the service or to protect our rights or the safety of others.

Viddy can connect to third-party AI tools, including Claude, Claude Code and Cursor, through Viddy's Model Context Protocol endpoint. This only happens when you explicitly authorize it on a consent screen.

When you authorize an app, Viddy issues that app an access token scoped to your account. Every scope below is read only except the last two:

• videos.read: list and read your videos and their metadata
• transcripts.read: read your transcripts, including searching across them
• annotations.read: read the notes on your videos
• tasks.read: read the action items and summaries Viddy extracted from a recording's transcript
• edits.write: suggest parts of a recording to cut. Suggestions are saved separately for you to review and are never applied automatically
• videos.write: upload a new video file to your account and get its share link. Requested only by the Viddy MCP package, which uploads files from the computer it runs on when you ask it to

A connected app cannot record, delete or overwrite anything, and it can only reach content on your own account. edits.write can do exactly one thing: save a suggested list of cuts for you to look at. It cannot change the cuts you made, cannot render a video, and cannot touch the original recording, which Viddy never modifies in place. Applying a suggestion is something only you can do, while signed in. videos.writecan only add new videos: an upload is private unless the app asks for it to be viewable by anyone with the link, and the app cannot rename, re-share or delete videos you already have. Once you authorize an app, the content it reads leaves Viddy and is handled under that app vendor's own privacy policy, not this one.

Access tokens expire after one hour. Refresh tokens rotate on each use and expire after thirty days. We store only a SHA-256 hash of each token, never the token itself. You can see and revoke every connected app at any time under Connected apps. Revoking a connection invalidates every token issued from that authorization.

Viddy sets a session cookie when you sign in. That cookie is what keeps you signed in. It is set with SameSite=Lax, it is marked Secure in production, and it expires after seven days. Sessions refresh once a day while you are active.

We set no advertising cookies, no analytics cookies and no third-party tracking cookies. If you block or clear the session cookie you will be signed out, and signed-in pages will not work.

The desktop app stores its own sign-in state locally on your computer. The Viddy MCP package stores its tokens in a local file on your computer (~/Library/Preferences/viddy-mcp/auth.json on macOS, ~/.config/viddy-mcp/auth.json on Linux).

• Videos, transcripts and notes are kept until you delete them. Deleting a video removes its database record and its stored files from Backblaze B2, and removes its transcript, its transcript segments, its notes and its team shares.
• Account records are kept while your account exists. If your account is deleted, the records that reference it are deleted with it, including your videos, notes, team memberships, sessions and any connected-app tokens.
• Sessions expire after seven days, or immediately when you sign out.
• OAuth authorization codes expire after ten minutes and are single use.
• Team invitations expire seven days after they are sent.
• Backups and provider-side logs may retain copies for a short period after deletion before they age out.

A share link that you already gave to someone stops working once you delete the video. However, if someone downloaded or re-recorded the video while it was shared, we cannot reach or remove that copy.

You can view, rename, change the visibility of and delete your own videos and notes from inside the product at any time. You can leave or delete a team you own, and you can revoke any connected app.

Depending on where you live, you may also have the right to request a copy of the personal information we hold about you, to have it corrected, to have it deleted, to restrict or object to how we process it, and to lodge a complaint with your data protection authority. To make any of these requests, including full account deletion, email client@muscled.co from the email address on your account. We will respond within the time your local law requires, and in any case without undue delay.

If you were recorded in someone else's Viddy video and want it taken down, email us at the same address with the share link. The person who made the recording controls it, so we will contact them, and we will act ourselves where the law requires it or where the recording violates our Terms of Service.

Traffic to Viddy is served over HTTPS. Access to a video is checked on our server before any playback authorization is issued, and those authorizations are short lived. Connected app tokens are stored only as hashes. Authorization uses PKCE with S256, and a reused refresh token revokes the whole grant.

No system is perfectly secure, and we cannot guarantee that a determined attacker will never succeed. If you believe you have found a security issue, please email client@muscled.co rather than posting it publicly.

Viddy is not intended for children. You must be at least 16 years old, or the minimum age of digital consent where you live if that is higher, to use Viddy. We do not knowingly collect information from children. If you believe a child has created an account, email us and we will remove it.

If we change this policy in a way that materially affects what we collect or who we share it with, we will update the date at the top of this page and, where the change is significant, notify account holders by email. Continuing to use Viddy after a change means you accept the updated policy.

This policy is governed by the laws of Ontario, Canada.