Privacy Policy
Last updated: October 11, 2026
In short: Pitwall processes agent activity on your Mac and stores its collected data locally. The current app and collector do not upload this data, and we do not operate a server that receives it. You can choose to share information with us when asking for support.
This policy covers the Pitwall app for macOS, its event collector, and this website (pitwall.oasislab.dev). Pitwall is provided by oasislab.dev ("we"). Questions: support@oasislab.dev.
What Pitwall reads on your Mac
To show what your coding agents are doing, Pitwall reads, on your Mac only:
- Event files in
~/.pitwall/events/, written by the collector hooks you install into each agent. They contain event names, times, session and task identifiers, paths, tool names, status, terminal hints and short text excerpts. These include the request's first non-empty line (truncated to 80 characters), and, for Claude Code and Pi, waiting details such as a command, path or dialog title (truncated to 120 characters) and the final reply's opening text (truncated to 160 characters). Some status, notification and error text is also retained. The collector is open source; the fields are documented in the event format. - Session files the agents keep themselves (for example session logs and transcripts), read to determine task status and match sessions for navigation. Pitwall does not copy these files into its history.
- Local Git metadata, read to display the current repository, branch and worktree.
Pitwall stores selected fields and excerpts rather than complete conversations or tool output. Excerpts, paths, error messages and configuration backups may contain sensitive information from the source. Truncating text does not remove all personal information or secrets.
What Pitwall stores, and where
- Collected event files in
~/.pitwall/events/. These are appended to and currently have no automatic rotation or expiry. - Task history in
~/Library/Application Support/Pitwall/, including identifiers, paths, terminal hints, status, times, request summaries and, for Claude Code and Pi, reply excerpts. History normally keeps the latest 1,000 tasks; unfinished tasks may temporarily exceed that limit. Waiting details are not written to this history. Repository and branch information is read when displayed, rather than stored in history. You can delete entries or clear the history in the app. - Your settings, in the standard macOS preferences for the app.
- Backups of agent config files before the collector installer changes them, in
~/.pitwall/backups/. These are copies of the original files and may include sensitive settings. The installer keeps the latest 10 backup groups.
These files and settings stay on your Mac; Pitwall does not upload them. Clearing history does not delete collected events, config backups or the agents' own records. Uninstalling the collector removes its hooks or extension and leaves event files and backups in place. To remove Pitwall's local files, stop the app and uninstall the collector first, then delete ~/.pitwall/ and ~/Library/Application Support/Pitwall/ (or your custom collector directory). App preferences are stored separately by macOS; deleting the app does not itself clear them. Copies made by your own backup or sync tools are managed by those tools.
Network
The current app and collector do not make network requests or upload collected agent data. They do not include telemetry, automatic crash reporting or usage analytics. Agent software, website hosting, downloads and information you choose to share for support are separate from this local collection.
This policy describes the current release. If future features such as automatic updates or license activation require network access or change how data is handled, we will explain their purpose, the data involved and the available controls, and update this policy before those features ship.
Permissions
- Notifications, to tell you when an agent waits for you, fails or finishes. Notifications leave out your request text unless you turn on task summaries in Settings.
- Automation (controlling your terminal app), only to bring the terminal tab of a session to the front when you ask Pitwall to return to it.
- Folder access, which macOS may request when Pitwall reads Git metadata in protected folders such as Documents, Desktop or Downloads. If declined, repository and branch details for those folders may be unavailable.
These permissions can be declined; the affected features may be unavailable while the board remains usable. The current app doesn't ask for Accessibility, Screen Recording or Full Disk Access.
Diagnostics you choose to share
"Copy diagnostics" in Settings copies a report of app and system versions, source health, session counts and settings to your clipboard. It is designed to omit request and reply text and session identifiers, and is not automatically sent to us. Review it before sharing, especially if you add screenshots, logs or other files. Anything you choose to paste into an issue or email is shared through that service.
When you contact us
If you email us or open an issue, we use what you send only to reply and to fix the problem. We keep support email only as long as needed for that. GitHub issues are public and governed by GitHub's privacy statement.
This website
The current site does not set cookies or include analytics or third-party scripts in its own code. Your language choice is saved in your browser's local storage. Our hosting provider may process standard request data, such as IP address and browser type, to deliver the site and protect it from abuse. Downloads are served by GitHub, under GitHub's privacy statement.
Payments
Pitwall is free during the beta and we don't process any payments. If paid features are introduced, payment will be handled by a third-party reseller, and we'll update this policy first to explain what they receive.
Children
Pitwall is a developer tool and isn't directed at children under 16.
Your rights
Collected agent data is stored on your Mac, where you can inspect and delete it as described above. We cannot access or delete those local files remotely. For anything you've sent us, email support@oasislab.dev to ask for a copy or deletion.
Changes
If this policy changes, we'll update the date above. For significant changes, we'll also note them on the home page.