Security

Your media is safer when we do not have it

Rooster’s security model begins by keeping the core workflow on your Mac. There is no Rooster account, project-sync service or media server for an attacker to reach.

Contained by macOS

Rooster runs inside the macOS App Sandbox. Access to cameras, microphones, screen recording and files is governed by macOS and by the choices you make. Rooster can use Downloads for new recordings and exports under its sandbox entitlement. For other locations, it uses access you explicitly grant.

Original media stays original

Imported and recorded source media is treated as immutable. Rooster records editing instructions in a versioned edit graph and writes rendered effects and exports as derived media. It does not silently rewrite an original recording or overwrite an existing export.

Local work and optional connections

Local transcription, effects, preview and export run on the Mac. Optional third-party services work only when you configure and choose them. API keys you save are held in the macOS Keychain rather than in a Rooster project file.

Security and privacy overlap, but they are not the same page. The privacy policy lists every network flow and the information involved. The local-workflow explanation gives you a practical way to verify what continues working offline.

Report a security problem

If you find a security or privacy issue, email support@rooster.cam with the affected version, what you observed and the smallest safe set of steps that reproduces it. Please give us a reasonable opportunity to investigate and fix it before publishing details. We will credit you if you would like us to.

Release status

Rooster is in active development and has not been released yet. This page describes the security boundaries already built into the product; it does not claim an external audit, certification or bug-bounty programme.