Privacy Policy

Last updated: 14 November 2026

Abhinav Soni, a sole proprietor trading as Sonah, of Link Road, Sadar Mahavir Ward, Betul, Madhya Pradesh 460001, India (“we”), is responsible for the personal data that reaches us through Sonah Team, payments and this website. For questions or requests, write to abhinav@sonah.dev.

The command-line tool

The sonah command runs on your computer and keeps its files there, under ~/.sonah, readable by you only. It sends:

  • your agent's session and, with the code review, files of your repositories, to the AI model you choose, through your own login or API key: Anthropic by default, or OpenAI with Codex;
  • the change of a branch (the repository's name, the commit messages, the changed files' paths and the changed functions' code) to Anthropic, through your Claude login, when it draws the graphs page (plain sonah, sonah visual, sonah review --format html unless you add --no-visual, and the review of each push where you turn on the push hook);
  • the review on that graphs page to Sonah Team, when you press “Save online” or “Invite your team” on that page or run sonah share and, in a repository where you turn on the push hook (sonah hook add --push), at each push from it, with no button press. It is the page and its data, which hold the repository's owner and name, the branch, the commits' ids and messages, the changed files' paths and line counts, the changed functions' code, the story of the change, the findings with the lines they quote, and the run's calls, models, times and cost. They also hold code from outside the change: the places elsewhere in the repository that call each changed function (their paths, lines and function names, and the line that starts each of those functions), and the paths of the test files that call it. sonah share and the push hook add each agent session that the commits name: its id, the ids of the commits that name it, the paths those commits changed that are among the review's files, and the ids of the review comments that sonah fix started it to answer, never what the sessions hold. A copy of the page that you share holds that review too, and its buttons work for whoever opens it: they save it to their own account;
  • calls to Sonah Team that send no recording, code or path of yours: from its team commands, only when you run them (sonah connect, which names its token after your computer when you give it a code, sonah status, sonah disconnect, sonah hook add --push, sonah fixes, and sonah fix, which sends the comment's id, the id of the Claude Code session it starts and the id of any session that one forks); at each push from a repository where you turn on the push hook, a check that sends the repository's owner and name and asks for the comments that wait for you there, before its review and after it, even when it sends no review; and, once you run sonah remind on, the same check when Claude Code starts;
  • once you say yes to sonah fix, the prompt it starts Claude Code with: the comment and the thread it answers (who wrote each, how and on what day, and your teammates' words in full), the item, the repository, the pull request, the branch, the range's two commits and the review's link, as in the review page's “Fix in Claude Code” (below). When it starts Claude Code as a copy of an earlier session, the one that wrote the change or your last fix of that comment, as it tells you before you answer, that session's conversation goes with the prompt, secrets included. Claude Code sends them to Anthropic, as in any session of yours, on your Claude Code login or, when your shell sets an ANTHROPIC_API_KEY, on that key's account, which may not be the account that ran the earlier session;
  • a check for a new version to npm, at most once a day, which holds nothing about you or your work;
  • requests to GitHub's API, only when you name a pull request; and the review of a push, sonah share and sonah fix may make git ask your git remote about its branches or commits, as git fetch does.

It sends nothing else to us: no telemetry, no analytics. Privacy for the command-line tool lists exactly what each request holds.

Sonah Team

Each review is made on its author's laptop, through their own Claude login, as with the command-line tool: Sonah Team's servers never call an AI model. The command-line tool is Sonah Team's laptop client: a review reaches Sonah Team only when “Save online” or “Invite your team” is pressed on its graphs page, when you run sonah share, or, once you connect it to Sonah Team and turn on its push hook in a repository, after each push from there. Those buttons work on a copy of the page that you share too, for whoever opens it. We keep:

  • Your account: your email address and a handle made from it, to sign you in and show who did what.
  • Your team: your company's email domain, the team's name, its members (with each one's role and seat, paid or free), invites (email addresses), requests to join it (who asked and when, and who approved, denied or withdrew each one, kept 30 days after it ends), who was removed from it or left it and when, and its plan with the billing references Paddle gives us. When we change a team's owner, we keep a record of it: the owner before and after, why, and when. That record is only added to, and it stays after the accounts it names are deleted.
  • The reviews you share: the review page and its data, which hold the repository's name, the branch, the commits (ids, subjects and messages), the changed files' paths and code, the names and paths of the code that calls or tests it, with the line that starts each function that calls it, the ids of the agent sessions behind the commits, the review's text and findings, which quote your code, and the run's models, times and cost. They do not include your agent sessions' recordings. Sonah masks nothing, so a secret in your code is in the review too. A review the laptop client uploads is kept with your account and handle, the id of the token that sent it and the time, and with each agent session its commits name: the commits that name it, the review's files those commits changed, and the comments it was started to answer.
  • What your team does on a review: each decision, question, comment and fix, with its note, and when someone takes a fix to Claude Code with sonah fix, and when a review they then upload, from a push or with sonah share, answers it, with the Claude Code session's ids and the commits that answer it. This log is only added to, never edited.
  • Notices: your notice settings and the address they go to, your browsers' push subscriptions, and your team's webhook addresses, with what was sent to each, for up to 30 days.
  • How Sonah is used: a line for each sign-up, laptop connected with a code, upload, view of a review (one a day per person and review), action, share and checkout, with its time, your account, your team and, where it has one, the review. This log is only added to, never edited.
  • For security: the tokens and codes that connect a laptop, kept only as hashes, with each token's name (when you connect with a code, sonah connect names it after your computer) and when it was made, last used and revoked; and sign-in attempts, reviews sent with “Save online” or “Invite your team”, codes tried, the calls a laptop makes with its token, and invites and requests to join a team, counted per email address, IP address, token and account, as hashes kept for a day. Supabase, which runs sign-in, also receives your IP address in full each time a sign-in code is sent to your email address or you use a code or link, for its own limits on sign-ins.
  • Logs: the server's own log names people by handle, never by email address. It notes each laptop that connects with a code or revokes its token, and the repository and the first 7 characters of the commit of each review that is uploaded, saved or waits to be saved. Google Cloud's request log holds each request's path and query (such as a repository's owner and name), its IP address and the browser or program that sent it. Google Cloud keeps both for 30 days.

We use this to run Sonah Team for you (our contract with you), to keep it secure and see how it is used (our legitimate interest), and to meet legal duties.

Who can open a review: the person who saved it and, while your team has Sonah Team and that person has a paid seat, your team's other paid seats. A free seat's reviews are opened only by that person. The reviews of someone who leaves your team stay readable to its paid seats. Webhooks your team's admins set up receive your team's events, free seats' reviews included. Otherwise, no one outside your team. We open a review only to help you, to keep Sonah safe, or when the law requires it.

Fix in Claude Code: on a comment on your review, Sonah Team can give you, the review's author, a prompt to take it up in your own Claude Code. The prompt holds the comment and the thread it answers (who wrote each, how and on what day, and their words in full), the item, the repository, the pull request, the branch, the range's two commits and the review's link. “Open in Claude Code” puts it in Claude Code's box. “Open in VS Code”, offered when Sonah Team knows the session that wrote the change, puts it in that session's box in VS Code. “Copy the prompt” copies it. Once you send it, Claude Code sends it to Anthropic, with the earlier session when it continues one, on your Claude Code login or API key, as in any session of yours.

Where it is kept: in the United States. The database is at Supabase, and the server and its files at Google Cloud, both in Northern Virginia. If you are outside the US, your data is transferred there. Google Cloud may keep the logs above outside the United States.

Fonts: Sonah Team's pages, its sign-in and review pages included, take their fonts from Google Fonts, so your browser asks Google for them, which gives Google your IP address.

How long: your account until you ask us to delete it, and the reviews your team shares until your team asks us to delete them. A review sent with “Save online” or “Invite your team” waits up to an hour for you to sign in; if you do not, it is deleted. To delete your account, write to us from the address you sign in with; what you did and wrote on your team's reviews stays in their log under your handle, with the Claude Code session ids and commits of the fixes you took to Claude Code, and the log of how Sonah is used keeps its lines.

Payments

Paddle.com, our reseller and merchant of record, takes your payment. It collects your payment details, billing address and tax information under its own privacy policy. We never see your full card number. Paddle gives us what we need to provide Sonah Team and help you, such as your email address, your country and what you bought. We use it only for that, and never for marketing without your consent.

This website

sonah.dev has no analytics and sets no cookies. Netlify hosts it and sees each request, including your IP address, as any web host does. Its fonts come from Google Fonts, so your browser asks Google for them. What you send through a form here goes to us through Formspree, and we use it only to reply.

Cookies

Sonah Team's cookies only sign you in, keep you signed in, and hold a review you are saving while you sign in. No analytics or advertising cookies.

Who handles data for us

ServiceFor
SupabaseSonah Team's sign-in and database
Google CloudSonah Team's server, its files and logs
ResendSonah Team's emails: sign-in codes and notices
PaddlePayments, as merchant of record
NetlifyHosting this website
FormspreeThis website's forms
GoogleThe fonts of this website and of Sonah Team's pages, and our sonah.dev mailbox (Google Workspace)

We do not sell personal data. We share it only with these services, to run Sonah, or when the law requires it.

Your rights

You can ask us for a copy of your data, or to delete it: write to us. You can also complain to the data protection authority where you live.

Changes

We will post changes here with a new date, and email account holders before a change that matters takes effect.