Privacy Policy

Summary

Tiremusu has no network code. It cannot connect to the internet, and it has no account, no telemetry, no analytics, and no crash reporting. Nothing it reads or writes ever leaves your Mac.

What stays on your Mac

Tiremusu keeps its data in one folder: ~/Library/Application Support/Tiremusu. The folder is created with permissions that only your user account can read.

• history.json — a summary of up to 50 sessions: agent name, session id, project folder path, repository and branch, model name, token count, phase durations, and tool names with usage counts and timestamps. No message text, no code, no command arguments.
• identities.json — the colour and shape assigned to each session, kept for 7 days.
• backups/ — copies of your own Claude Code and Codex settings files, taken before Tiremusu changes them. The last 20 of each are kept.
• bin/tiremusu-hook — the small helper program that Claude Code and Codex call.
• hook.sock — a Unix domain socket on your own disk. It is a local file, not a network port, and no other machine can reach it.

What is read but never stored

To show you what a session is doing, Tiremusu reads session metadata and the tail of your agents' transcript files: tool names, permission requests, the model name, and the last assistant message. These are held in memory only while Tiremusu is running. They are written to no file and logged nowhere.

Your preferences

Settings such as sound choices, volume, the Island's style and opacity, and the keyboard shortcut are stored by macOS in your own user defaults for this app. They are not sent anywhere.

No network, no third parties

Tiremusu ships with no third-party analytics, advertising, or crash-reporting libraries. The only communication it performs is over the local socket file described above, between the app and its own helper.

System permissions

Tiremusu requests only two things from macOS, and you can refuse either one:

• Notifications — used to alert you that a session needs you, and only if you turn this on in Settings. Turn it off in System Settings at any time.
• Open at login — used to start Tiremusu when you log in, and only if you turn this on in Settings.

Changes Tiremusu makes to Claude Code and Codex

When you connect an agent, Tiremusu adds its own hook entries to your own agent configuration: ~/.claude/settings.json for Claude Code, and ~/.codex/hooks.json for Codex. Nothing else is touched. Your project-level and machine-local agent config files are left alone.

Before writing anything, Tiremusu shows you exactly which file it will change, which entries it will add, and where the backup will go. If the file is not valid JSON, Tiremusu refuses to write to it.

The hooks run a local helper that forwards an event to Tiremusu over the local socket. They do not block your agent, and if Tiremusu is not running the helper exits immediately and your agent behaves exactly as before.

To undo this, use Disconnect in Settings → Agents. It removes only the entries Tiremusu added and leaves your other hooks in place. Your backup copies stay where they are until you delete them.

Deleting your data

To remove everything Tiremusu has stored, quit Tiremusu and delete the folder ~/Library/Application Support/Tiremusu. If you want the agent config files returned to their original contents as well, restore the relevant backup from the backups/ folder, or use Disconnect in Settings → Agents first.

Children

Tiremusu is a developer tool intended for adults. Because it collects no data from anyone, it does not knowingly collect information from children.

Changes to this policy

If this policy changes, the date at the top of this page changes with it. Tiremusu is provided as is, without warranty; use at your own risk is covered in the Terms of Use.

Contact

Questions about this policy can go to the developer using the contact details on the Support page.