Reference

Data and privacy

Reviews live in your project folder. Settings live in ~/.ferret/, and keys and accounts in the OS user-data folder. Only crash reports reach the developer, through Sentry, and you can turn them off. Feedback you choose to send from the app becomes a public GitHub issue. Videos you post to YouTube or TikTok go from your computer to that service, only when you press OK to post. Last updated: October 18, 2026.

#Inside .ferret/reviews/

<project>/.ferret/reviews/20261003-104500/
├── feedback.md      # what the agent reads
├── 01.png, 02.png…  # one or more images per finding
├── session.json     # review state and edit history
├── events.jsonl     # action log (built-in browser only)
├── recording.webm   # the video
└── work/            # intermediate audio and frames

Reviews made before the rename live in .ade-movie/reviews/. They are still listed and opened, and new reviews go to .ferret/reviews/.

When recording starts, .ferret/ is appended to .git/info/exclude. Worktrees and submodules are handled. .gitignore is never modified. An interrupted review can be recovered from history if its records survived. The app then warns that the last seconds may be missing.

#Retention

Keep recordings (7 days by default, 30 days, or Forever): on startup, completed reviews older than that lose recording.webm and work/. feedback.md and the finding images are kept. Incomplete reviews are never pruned. Pruning runs at launch, for the last opened project.

#What leaves your machine

WhenDestinationData
Transcription: On device (free)none—
Transcription: OpenAI / compatibleOpenAI or your Base URLaudio chunks
Model downloadHugging Facefile request
Organizeyour Claude Code / Codex CLI, or the LLM endpoint you set in organizertext and action log only (no images, audio, or video)
Acceptance check (decision model, off by default)your agent, through the local relay, to Ollama / Cloudflare / AI Gateway / TypeSafe / OpenAI / your URLwhat the agent sends: finding text, "Done when", and BEFORE/AFTER screenshots (image models only)
Rating imported meeting findings (decision model, only when it is turned on)Ferret, through the local relay, to the decision model you seteach candidate's title and request, the remarks it came from, and its video frame (image models only)
Share links (only when you make one)share.ferretade.dev (a Cloudflare Worker run by the developer)the title, the URLs and titles of the pages it opens, the memo (encrypted when you set a password; the password itself is never sent), and the random install ID (used only, as a keyed hash, to limit how many links one install can make). Reviewers' recordings, text notes, drawings and optional names are sent to the same server, and anyone with the link can see them (see Share links). Everything is deleted after 7 days
Create private GitHub repo (only when you click Create)GitHub via your ghcreates a private repository with the name and description you chose and pushes the folder's commits (a first commit made by Ferret leaves out files ignored by .gitignore and files that may hold secrets)
Send to Agentthe agent in your terminalone instruction pointing at feedback.md
Footer usage (Claude Code and Codex only)Anthropic, ChatGPTusage request with your own login
GitHub star promptGitHub via your ghchecks whether you starred the repo, and stars it only if you click Star on GitHub
Updates (when Ferret starts, every 6 hours, and Check for Updates)download server (Cloudflare R2)requests for latest.json and that version's SHA256SUMS (on macOS also UPDATE-SHA256SUMS); when a newer version is found, the update file for your computer (only when you click Download if Update automatically is off)
Connecting and posting to YouTube (only when you connect your Google account and press OK to post)Google (YouTube Data API)sign-in on Google's own page; the video, thumbnail, title, description, tags and privacy setting you approved; reads the connected channel's name and the upload status (see YouTube)
Connecting and posting to TikTok (only when you connect TikTok and press OK to post)TikTok (Login Kit and Content Posting API). The sign-in code and token refreshes go through the developer's token relay at ferretade.dev/oauth/tiktok/the video and caption you approved; reads your TikTok display name. The relay passes the code or token on and stores nothing (see TikTok)
Sending feedback from the app (only when you send it)the developer's feedback relay (a Cloudflare Worker), which opens a public issue in JapanMarketing-Dev/ferretyour text, bug or idea, app / OS version and CPU, and up to 3 screenshots you attach. Keys, tokens, email addresses, and home-folder paths are masked. The relay does not store your IP address (see Feedback from the app)
A crash or error (Send crash reports on)Sentrystack trace and OS / CPU / app versions (see Crash reports)
  • The app has no analytics, no performance tracing, and no session replay. The only data it sends without you asking is crash reporting: errors, one session per launch, and slow-startup and freeze warnings, all described below and all controlled by Send crash reports.
  • Secret-looking values in URLs (tokens, keys) are redacted before they are written to feedback.md.
  • Text captured from the page is marked as data in feedback.md, so the agent is told not to follow instructions found in it.
  • This website (not the app) counts page views with Cloudflare Web Analytics: cookie-free, with no cross-site tracking and no personal data.

#Feedback from the app

You can send a bug report or an idea from inside Ferret without a GitHub account (Send Feedback at the bottom of the sidebar). It is sent only when you send it, and it becomes a public issue in JapanMarketing-Dev/ferret (opens in a new tab), labeled from-app. Do not include anything you would not post in public.

  • The app sends it from your computer to a small relay (a Cloudflare Worker run by the developer), which opens the issue with its own GitHub token. Apart from share links you make, this relay is the only server of the developer's that receives anything you write.
  • Sent: your title and text, whether it is a bug or an idea, the app version, and up to 3 PNG or JPEG screenshots you attach. The OS name and version, CPU architecture, and the random install ID are sent only if you leave them included. Not sent: your name, email, GitHub account, project files, recordings, or findings.
  • Before the issue is created, the relay masks text that looks like keys or tokens, email addresses, and the user name in home-folder paths, and stops @mentions from notifying anyone. It also removes location and other metadata from screenshots. Check your text anyway: masking cannot catch everything.
  • The relay does not store your IP address. To limit how often one sender can post (5 per hour, 20 per day), it counts a keyed hash of the IP address (and of the install ID, if sent) for up to 24 hours, then deletes it. Neither appears in the issue.
  • Screenshots are kept by the relay in Cloudflare R2 under unguessable names and shown in the issue. To have an issue or its screenshots removed, comment on the issue or open a new one.
  • The relay's code is in workers/feedback-relay in the repository.

#YouTube (YouTube API Services)

Ferret uses YouTube API Services to upload videos to your own YouTube channel. It does so only after you connect your Google account in Ferret and press OK to post a video. By connecting, you agree to be bound by the YouTube Terms of Service (opens in a new tab). How Google handles your data is described in the Google Privacy Policy (opens in a new tab).

  • Access requested: youtube.upload to upload videos, and youtube.force-ssl to set the video's thumbnail and read the name of the connected channel.
  • What is used, and for what: the video, thumbnail and metadata you approved (title, description, tags, privacy and similar settings) are uploaded to your channel, and the upload status is read back so Ferret can show whether it finished. The channel name is read only to show which channel is connected. Ferret does not read, collect or share any other data from your Google account, and does not use it for advertising or analytics.
  • Where it goes: from your computer straight to Google. Nothing from your Google account, your channel or the videos you post is sent to the developer or to anyone else. Crash reports never include tokens, videos, titles or channel names.
  • Where it is stored: the OAuth tokens are kept only on your computer, encrypted with the OS keychain (macOS Keychain, Windows DPAPI or the Linux secret service), in Ferret's userData folder. The connected channel's name is kept next to them to show in the app. The video and its post settings stay in your project folder.
  • How to stop: disconnect your Google account in Ferret's settings at any time. This deletes the tokens from your computer. You can also revoke Ferret's access at Google security settings (opens in a new tab). Videos that were already uploaded stay on YouTube until you delete them there.
  • Ferret's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.

#TikTok

If you connect TikTok, Ferret uses TikTok's Login Kit and Content Posting API only to post the video and caption you approved to your TikTok account, after you press OK. Use of TikTok is subject to TikTok's Terms of Service (opens in a new tab) and Privacy Policy (opens in a new tab).

  • Access requested: user.info.basic to show the display name of the connected account, and video.upload to send the video to your TikTok inbox, where you finish the post in the TikTok app. video.publish (posting directly) is requested only after TikTok approves Ferret for it.
  • Where it goes and where it is stored: the video and caption go from your computer straight to TikTok. The tokens are kept only on your computer, encrypted with the OS keychain in the same way as for YouTube. Disconnecting TikTok in Ferret's settings deletes them. You can also remove Ferret's access in the TikTok app's settings.
  • Token relay: TikTok needs the app's client secret to turn the sign-in code into tokens, and that secret must not ship inside the app. So for that step only, Ferret sends the request to a small Cloudflare Worker run by the developer at https://ferretade.dev/oauth/tiktok/. It accepts only three requests (exchange the sign-in code, refresh a token, revoke a token), adds the client secret, forwards the request to TikTok, and returns TikTok's answer to your computer unchanged. It does not log or store the code, the tokens, your IP address or anything about your account, and it never receives your videos or captions.

#Crash reports

When the app crashes or hits an unhandled error, Ferret sends a crash report to Sentry (opens in a new tab) so the bug can be fixed. It is on by default. Turn it off in Settings → Privacy → Send crash reports, or with Turn off on the notice shown at first launch. Turning it off takes effect at once. Turning it back on takes effect at the next launch. Development builds (pnpm dev) also send, tagged development, so the developers can fix crashes they hit while working. E2E runs and unit tests never send.

SentNot sent
  • Error type and message, with home-folder paths shown as ~
  • Stack trace (where in Ferret's code it happened)
  • For native crashes: which process crashed, why it exited (for example crashed or oom), the app version, the kind of crash and the file name of the module it happened in, and where: the offset inside that module, the module offsets found on the crashed thread's stack (up to 20), the IDs needed to look up that module's debug symbols, and the thread's name. Also Ferret's own last steps from that launch (up to 30, for example quitting or installing an update). Never memory contents, raw addresses or file paths
  • OS name and version, CPU architecture, Electron / Chrome / Node versions, app version, screen size, memory size
  • App lifecycle events right before the error (for example app.ready), and startup failures
  • Which part of the app failed: a screen area that could not render (and its React component names), an IPC call, a terminal that could not start, a crashed or hung process, or a page of the app that failed to load
  • Where you were in the app: editor or feedback mode, the open tab (Browser, Findings, Settings, or just file), and whether a recording was running
  • One session per launch (started, ended normally, or crashed), so the crash-free rate of each version can be measured
  • A random install ID (created on first launch and kept in the app's settings folder), so the number of affected installs can be counted. It is not linked to your name, email, or device
  • For JavaScript crashes only: the last 50 of Ferret's own log lines (such as [startup] and [recording]), shortened and with paths, URLs, emails, and keys removed
  • Your project folder path and file names (replaced with <project>)
  • URLs opened in the built-in browser, and any other web address (replaced with <url>)
  • Terminal output, transcripts, findings, page text, screenshots
  • Email addresses and API keys or tokens (replaced)
  • Your name, device name, IP address (not stored), cookies, local variables
  • Memory dumps of native crashes (minidumps). They can hold anything that was in memory, so they stay on your computer
  • Clicks, network requests, and any log line that isn't one of Ferret's own

The installed app sends at most 10 reports per launch and only half of JavaScript errors (native crashes are always sent). Development builds send every error, up to 50 per launch. The same error is sent only once per launch. Slow startups (over 5 seconds) and long freezes of the app (over 1 second) are sent as warnings, at most once every 10 minutes. No performance tracing or session replay is used. The app uses Sentry's free plan. If it fills up, extra reports are dropped and nobody is charged.

Building Ferret yourself? Set FERRET_SENTRY_DSN (the old name MOVIE_ADE_SENTRY_DSN also works) to your own Sentry DSN, or to an empty string to send nothing. The code is in src/main/telemetry.ts and src/shared/telemetry.ts.

#Contact

Ferret is provided by Japan Marketing LLC. For questions about privacy, or to ask about data the developer holds (crash reports, feedback, share links), open an issue at GitHub Issues (opens in a new tab) or contact Japan Marketing LLC (opens in a new tab). See also the Terms of Service.

Edit this page on GitHub (opens in a new tab)