Inkling runs on your Mac and nowhere else. It never sees your Claude credentials, your files or your prompts. The only thing it ever sends anywhere is two anonymous pings, described below.
Inkling is a native macOS app. When you drop a piece on something, the app launches the claude command-line tool that you installed, headlessly, as your own user account. The agent's reading, writing and tool use all happen on your machine through Claude Code, exactly as if you had run it in Terminal.
Inkling has no accounts, no login, no cloud sync and no server-side copy of anything you do. It keeps two kinds of files on disk:
~/Library/Application Support/Inkling/.~/.claude/skills/<name>/, where Claude Code can find it. You can open, edit or delete these at any time.Inkling does not ask for, read, copy or store your Claude login or API key. Those live wherever Claude Code keeps them. Inkling only runs the claude binary, which authenticates itself. If you are not signed in to Claude Code, Inkling does not work.
The contents of the things you drop pieces on, the questions you ask and the answers that come back are handled by Claude Code on your Mac. None of it is sent to us. Inkling has no server that receives file contents, prompts, paths, window titles or conversation history.
Inkling sends exactly two events over HTTPS, so that we know roughly how many people installed it and how many got as far as bonding a first piece.
Sent once, the first time the app launches.
Sent once, the first time a piece is dropped on something.
Each event carries a random install ID and nothing else. The ID is generated on your Mac when the app first runs; it is not derived from your hardware, your Apple ID, your Claude account or anything that identifies you, and it is stored locally with the app's other data. There is no account on our side to link it to. The events contain no file contents, no prompts, no paths, no file or window names, no usernames and no Claude account information.
Like any HTTPS request, a ping reaches our server from your IP address. We do not store the address with the event or use it to build a profile.
There is no other telemetry. The app does not phone home on launch after the first time, does not report crashes automatically and does not track what you do with pieces. The install script contains no telemetry at all.
Inkling asks for three permissions under System Settings → Privacy & Security. Each one is used only for the purpose below, and each can be revoked at any time; the corresponding feature simply stops working.
To know where other apps' windows and selections are on screen, so a piece can be dropped on a window and stay attached to it as it moves, and so the fluid can be drawn in the right place.
macOS gates the titles and layout of other apps' windows behind this permission. Inkling needs it to identify what you dropped a piece on, for example which browser tab or document window it is bonded to. Inkling does not record your screen or save screenshots anywhere.
To ask the app under a piece, such as Finder or a browser, for the file path or URL it is showing, using Apple Events. The prompt appears per app, the first time Inkling talks to it.
Everything these permissions reveal stays on your Mac. It is used to give the agent its context through Claude Code and is never sent to us.
Inkling is a front end for your own installation of Claude Code. When an agent reads a file or answers a question, Claude Code sends that content to Anthropic's API using your plan or API key, just as it does when you use it in Terminal. How that data is handled, retained and used is governed by Anthropic's terms and privacy policy for the plan you are on, not by this document. See anthropic.com/legal.
Inkling is an independent tool and is not made by or affiliated with Anthropic.
Everything Inkling creates is in plain folders in your home directory. To remove all of it:
/Applications/Inkling.app to the Trash.~/Library/Application Support/Inkling/. This also discards the random install ID; a reinstall generates a new one.~/.claude/skills/. We leave these in place on uninstall because they are yours and Claude Code can keep using them without Inkling.Because the two telemetry events carry only a random ID, there is nothing on our side we could match to you in order to delete it. If you have a question about this anyway, write to us.
If this policy changes, the new version will be posted here with a new effective date. If a future version of the app sends anything beyond the two events above, that will be stated here and in the app before it happens.
tryinkling.dev uses PostHog for analytics: page views, clicks and which download button was used. It records the page, your browser type and a random visitor ID; it does not receive your name, email or anything from the app. If you block analytics scripts, the site works exactly the same.
Questions: aruntemme@gmail.com