Security and privacy
Short enough to forward to the person who has to approve it. Every line here describes the app as it is built; where something is planned rather than built, it says so.
Where your code is
On your Mac. The app opens a folder on your disk, or clones a repository into its own folder on your disk, and runs the product there with the command you approved. The checkout the app edits is its own copy, so your working folder is never touched. No part of the repository is uploaded to BAARS DESIGN.
Setting up a project installs its packages, pinned by the project's own lockfile where it has one, and starts it with the command you approved. Those packages run on your Mac, as they do for any developer who clones the repository.
What the AI sees
The AI engine is yours: a local Claude Code, Codex or Gemini CLI sign-in, an API key you provide, or an endpoint you host. Prompts and the code excerpts they carry go from your Mac to your provider under your agreement with them. BAARS DESIGN has no key in the app and no proxy in the path.
A command-line engine runs as a separate process on your Mac, as your macOS user, with the same access to your files as when you run it in Terminal. Engines are listed under Settings with what each is allowed to do.
What the app talks to
GitHub: the public release feed, to check for updates, and under your own login, to open pull requests and read their state. Your AI provider, through the engine you chose. No other host. When accounts are live, our account service as well, for sign-in and your plan.
The product you open talks to whatever it talks to when a developer runs it locally. That traffic is yours and unchanged. The app sends no analytics and no crash reports.
What the app keeps on the Mac
All it keeps is in one folder in your home directory, ~/.something: its copies of the repository and their branches, the project list, comments, canvases and settings. Sign-ins and API keys are in the macOS keychain, not in files. Remove the app, that folder and the keychain entries and nothing of it remains.
In your repository it adds a small .something folder: the project plan and an index, readable in a diff and correctable in a pull request. The part that changes on every run is kept out of commits.
What reaches BAARS DESIGN
Today, nothing. The app has no account service switched on and sends no usage data.
When accounts are live: your email, name and sign-in provider id, sign-in times, your subscription state and seat assignments, the name and app version of each Mac you sign in from, and, for team admins, a monthly count of pull requests sent per member. Counts only. Not the repository, not file names, not prompts, not screenshots. Account data will be stored in the EU.
Pull requests
Pull requests are made from your Mac under your own GitHub login. You connect GitHub once, inside the app, by approving it in your browser; the sign-in lives in your Mac's keychain. Branch protection, CODEOWNERS and required checks apply as to any pull request. BAARS DESIGNholds no token for your organisation and never has administrative access to it.
Plugins
What an engine or a plugin can do is declared before it runs, and access to the page has a switch. A plugin that changes the page returns its edits as data; it never runs inside your product's page, never writes files directly, and cannot make the page fetch an address of its choosing. Plugins that come with a project are fingerprinted and wait for you to allow them.
One limitation, stated plainly: a trusted plugin runs as an ordinary process with the same access to your Mac as the app itself. Capability declarations document intent; they are not a sandbox.
Updates and signing
The app is signed with a Developer ID certificate and notarised by Apple. It checks for updates from a public release feed, verifies each download against its published checksum, and the system refuses an update that does not carry the same signature. No update installs until you quit or choose Restart to Update.
Your account data
When accounts are live, you can download what we hold about you as one JSON file and delete your account from your account page. Invoices are kept after deletion, because Norwegian bookkeeping law requires it.
Subprocessors
The companies that process account and payment data for us are listed on the subprocessors page.
Enterprise
The Enterprise plan comes with a DPA with standard clauses, a completed security questionnaire, invoicing by purchase order, and a named contact. On request, delivered as part of an Enterprise agreement: SAML or OIDC single sign-on, SCIM provisioning, audit-log export and domain auto-join. Tell us what you need.
SOC 2: not yet. Ask us where we are with it.