Privacy Policy

1. Who we are

MediaOtter is an open-source desktop extension for Adobe Premiere Pro and After Effects (CEP 10, macOS) built and maintained by madebysaira — Sagarika Sultana. The software is distributed under the MIT License at github.com/madebysaira/mediaotter. For privacy questions, contact hi@madebysaira.me.

2. Scope

This policy covers two things:

• The MediaOtter desktop extension — the CEP panel you install in Premiere Pro / After Effects.
• The MediaOtter website — mediaotter.madebysaira.me, which serves this landing page, Privacy Policy, and Terms of Service.

3. No data collected by default

By default, MediaOtter collects nothing. All processing — search, suggestions, metadata lookup, format planning, download, muxing, and import — runs locally on your machine using bundled binaries (yt-dlp and ffmpeg). No account is required to search or download, no data is sent to madebysaira, and no remote server operated by us receives your queries or download history.

If you never use “Sign in with Google” or “Use browser session,” the app makes zero authenticated requests and stores nothing except local settings and download history that you can delete at any time (see §11).

4. What is stored locally

MediaOtter stores the following only on your machine, in standard application storage and in your home directory. Nothing is uploaded.

• Settings — your preferences (quality cap, format preference, download folder, theme) stored in the extension's local storage.
• Download history — a local list of completed downloads (title, URL, file path, time) so you can re-import or drag items to your timeline.
• Auth token — only if you opt in (see §5) — an OAuth access token and refresh token for the YouTube Data API, stored at ~/.mediaotter/auth.json with filesystem permissions 0600 (read/write for you only).

All of these files remain on your computer. Uninstalling the extension and deleting ~/.mediaotter/ removes them.

5. Sign in with Google (optional, opt-in only)

MediaOtter offers an optional “Sign in with your own Google account” feature so you can browse your private YouTube playlists and liked videos inside the panel.

• Scope: youtube.readonly only — read-only access to your YouTube playlists and liked videos. The app cannot upload, edit, delete, comment, or manage your account.
• OAuth flow: Standard Google OAuth 2.0 with PKCE via a local loopback redirect. You create your own Google Cloud OAuth client (a 5-minute setup) or use the build-time client ID included in packaged releases. The consent screen is Google's; we never see your password.
• Where tokens live: The access and refresh tokens are stored only at ~/.mediaotter/auth.json on your machine, with restricted permissions. They are used solely to call the YouTube Data API v3 on your behalf to read your playlists/liked videos.
• What is transmitted: Only direct HTTPS requests from your machine to googleapis.com / youtube.googleapis.com to fetch your playlists. No token or watch history is sent to madebysaira or any other third party.
• Revocation: You can disconnect at any time inside MediaOtter (Settings → Sign out) which deletes ~/.mediaotter/auth.json, or revoke access in your Google Account permissions.

If you do not sign in, this entire section does not apply and no Google API is contacted.

6. Browser cookies (optional, local only)

MediaOtter includes an optional “Use browser session” toggle for private, age-restricted, or member-only videos. When enabled, the app reads cookies directly from your own browser's local cookie store (Chrome, Edge, Brave, or Firefox) on your machine and passes them to the local yt-dlp process so it can fetch the same content your browser can see.

• Cookies are read locally and are never transmitted to madebysaira or any other server.
• They are used only for the duration of that download and are not stored by MediaOtter after the request.
• You can disable this feature at any time in Settings.

7. No telemetry, no analytics, no ads, no tracking

MediaOtter contains:

• No telemetry or usage analytics.
• No crash reporting.
• No advertising, ad SDKs, or affiliate links.
• No fingerprinting, no cross-site tracking, no marketing cookies.

The code is open source — you can verify this at github.com/madebysaira/mediaotter.

8. Third-party services

When you use optional features, your machine communicates directly with these third parties under their own policies:

• YouTube Data API v3 (Google LLC) — only when you sign in. Governed by Google's Privacy Policy and the YouTube API Services Terms. Data fetched is your own YouTube playlists/liked videos.
• yt-dlp and ffmpeg — local, bundled open-source binaries that run entirely on your machine. They make direct HTTPS requests to the video site you choose to download from (e.g., youtube.com, vimeo.com) — the same request your browser would make.

No other third-party SDKs are bundled.

9. Website privacy (mediaotter.madebysaira.me)

The marketing site is a static site served by Vercel.

• The site itself sets no cookies and runs no analytics of its own.
• Vercel, as the hosting/CDN provider, may collect standard web-server logs (IP address, user-agent, requested path) for security and performance purposes under Vercel's Privacy Policy. We do not have access to individual identifiers beyond aggregated logs.
• Fonts are loaded from Google Fonts and icons from cdnjs (Cloudflare) when you visit the site — those providers may receive your IP and user-agent as part of a normal web request. Where possible, system fonts are used as fallback.

10. Data sharing

We do not sell, rent, or share any personal data. Because we do not collect personal data in the first place (see §3), there is nothing to share — except for the direct, user-initiated requests to Google's YouTube API and to video sites via yt-dlp described above, which happen on your machine and under your control.

11. Retention & deletion

All app data is stored locally and retained until you delete it:

• OAuth tokens: Delete ~/.mediaotter/auth.json or click Sign out in MediaOtter Settings. Also revoke at myaccount.google.com/permissions.
• Settings & download history: Stored in the extension's local application storage. Clear them in Settings or remove the extension; to fully wipe, delete ~/.mediaotter/ and the CEP extension folder at ~/Library/Application Support/Adobe/CEP/extensions/MediaOtter (macOS).
• Website logs: Managed by Vercel per their retention policy; we do not retain additional copies.

12. Your rights

Depending on your jurisdiction (including the EEA, UK, and India), you may have rights to access, correct, delete, or restrict processing of personal data. Because MediaOtter stores data only on your device, you can exercise these rights directly by deleting the local files described above. For any request or question, contact hi@madebysaira.me — we will respond within 30 days.

13. Children

MediaOtter is not directed to children under 13 and we do not knowingly collect data from children. The extension is a professional tool for video editors.

14. Changes to this policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page at https://mediaotter.madebysaira.me/privacy.html with a revised effective date. Material changes will also be noted in the GitHub repository's release notes. Your continued use of the software after an update constitutes acceptance of the revised policy.

15. Contact

If you have questions about this Privacy Policy or how MediaOtter handles data, contact:

madebysaira — Sagarika Sultana
Email: hi@madebysaira.me
GitHub: github.com/madebysaira/mediaotter

Effective date: August 17, 2026 · Last updated: August 17, 2026