Privacy policy
Privacy policy
Updated November 14, 2026.
ScreenClip is a macOS menu bar app. You capture a region you select, optionally annotate it and add a note, and hand that report to a coding agent you configure. This policy describes what the app stores on your Mac, what can leave it, and what this website does.
What stays on your Mac
Reports, screenshots, notes, annotations, project settings, questions, and activity are stored on your Mac under ~/Library/Application Support/ScreenClip. The queue is a SQLite database plus image files. Agent work runs in a Git worktree under that same folder. Your own project checkout is not the working directory.
A diagnostics log in that folder records build and API error metadata. It does not include screenshots, notes, browser URLs, or window titles.
If you save a Grok Bot webhook URL and Authorization header, they are stored in the macOS Keychain under com.screenclip.app.external-assistant. They are not written into the queue database.
ScreenClip does not create an account with ScreenClip. The app does not include analytics, advertising, or a crash reporter that sends data to ScreenClip. There is no ScreenClip server that receives your reports.
Screen capture and optional context
Screen Recording permission is used to capture the region you select. ScreenClip does not record the screen continuously, and it cannot reconstruct actions you never captured.
Each capture can include the source app name and bundle ID so the report can be routed to a project. If you turn on Read the active browser URL for project matching, ScreenClip may ask for Safari or Chrome automation and store the browser URL and window title with that capture. When that setting is off, those two fields are not collected.
Redaction
Redaction is a rectangle you draw with the redact tool. ScreenClip flattens those rectangles to opaque black in the screenshot it saves. Arrows, pen strokes, shapes, and text do not hide the pixels underneath.
When a capture has a redaction, the unredacted crop is not kept. It is not passed to an agent, pushed to GitHub, or included in a webhook.
Codex and Claude Code
Codex and Claude Code run on your Mac. ScreenClip passes the approved screenshot, your note, and the prompt to that local agent. ScreenClip does not upload those reports itself.
The agent uses the account you signed into: Codex through its app-server, Claude Code through its own login. That agent may send the prompt and images to its own provider under that account’s terms. ScreenClip starts these agents without GitHub tokens in their environment. ScreenClip, not the agent, pushes branches and opens pull requests for them.
GitHub
Pull request automation uses the GitHub CLI you install and the GitHub account that CLI is logged into. ScreenClip pushes a screenclip/ branch, and for Codex and Claude Code it opens the pull request. It reads check status, and it merges only when automatic merge is enabled for that project and the checks and review rules pass.
The pull request body includes the agent’s summary, the project’s validation command with secret-like values redacted, and the report reference. The body states that screenshots and source context remain in ScreenClip. Screenshots are not attached to the pull request by default.
Grok Bot
Nothing is sent to Grok Bot until you save a webhook URL and Authorization header, and you turn on Allow sending screenshots to the external assistant for that project. The opt-in stays off until you enable it, including for private repositories.
ScreenClip then pushes the approved PNGs and a report.json file to a screenclip/ branch in the project repository, and sends a small JSON webhook. The webhook does not contain image bytes. It includes the report number, issue id, revision, title, notes, later context notes, source app name, bundle ID, project name, repository, base branch, validation command, and the evidence branch, commit, and file paths. The browser URL and window title are included only when Read the active browser URL for project matching is on.
Anyone who can read that GitHub repository can read those files until they are removed. On a public repository, that includes anyone on the internet. Grok Bot opens the pull request from that branch. Cancel in ScreenClip stops the local record only. It does not stop Grok Bot. Questions from Grok Bot stay in Grok Bot’s chat, not in ScreenClip.
A redirect of the webhook to a different host does not include the Authorization header.
Deleting data
Delete a report in ScreenClip to remove its local screenshots and notes. That does not delete the agent’s own conversation history, or a pull request already opened on GitHub. Removing the app does not by itself delete ~/Library/Application Support/ScreenClip or the Keychain item.
GitHub, and the provider behind the agent you signed into, keep what they received under their own terms.
Tips
ScreenClip is free. The app can show an optional tip window, and the same window is available from the menu and from Settings. Choosing a tip opens GitHub Sponsors in your browser. ScreenClip does not process the payment and does not receive card or payout details. You can dismiss the window or turn the prompt off. This website does not link to a payment page.
This website
screenclipai.com is a static website. Pages on this site set no cookies and load no third-party scripts, fonts, or analytics. The host that serves the site receives ordinary connection data, such as IP address and user agent, in order to deliver the page.
The download button goes to a GitHub Release of the Mac app. Other links, such as the repository and a donation link if one is configured later, leave this site for that destination.
Contact
Questions about this policy go through the support page.
Changes
Material changes to this policy will be posted on this page, with an updated date.