Legal
Privacy
Rooster edits video on your Mac. Your recordings, transcripts and projects stay in your own files and are never uploaded to us. We do not operate a server that receives your media, so there is nothing on our side to hand over, sell or lose. This page is mostly a list of the few things that do cross the network, so that the claim above can be checked rather than taken on trust.
Last updated: 22 September 2026
1. Who we are
Rooster is operated from 25 Wilton Road, Pimlico, London SW1V 1LW, United Kingdom. For anything on this page, including any request about your own data, write to support@rooster.cam. We are the data controller for the limited personal data described below.
2. What never leaves your Mac
Video and audio you record or import, the transcripts Rooster produces from them, your projects and edit history, and any media you export. Transcription and the Studio Sound, Eye Contact and Green Screen effects all run in the application on your own hardware. None of it is sent to us, and Rooster has no account to sign in to.
3. What does cross the network
There are six cases, and they are the complete list.
Downloading transcription models
Rooster transcribes with a model that it downloads the first time you need it, from Hugging Face. That request necessarily discloses your IP address to the host serving the file, in the same way as visiting any website. No recording or transcript is involved: the traffic runs in the other direction. Once the model is on disk, transcription works with networking switched off.
Checking for a Rooster update
The copy you download from this site can update itself. Asking whether a newer version exists fetches a small file from rooster.cam, which discloses your IP address and the version you are running to the host serving it, in the same way as visiting any website. If there is an update and you accept it, Rooster downloads it from github.com, where our signed releases are stored - that request discloses your IP address to GitHub, and nothing else about you. Nothing about your recordings, transcripts or projects is involved in either request, and no hardware or usage profile is sent with them. Rooster will not check on its own until you have said it may: it asks once, on an early launch, and if you decline you can still check by hand from the Rooster menu. The copy sold through the Mac App Store will not do this at all, because Apple updates that one.
Sending feedback from the app
Rooster has a Send Feedback box. When you press Send - and only then - what you typed is posted to rooster.cam, together with your email address if you chose to give one and four facts about the build: the Rooster version, the build number, how you got the copy and your macOS version. The box shows you those facts in a sentence before you send. Nothing else goes with it: no media, no transcripts, no project names, no file paths and no identifier for you or your Mac. As with any request, it discloses your IP address to the host serving it. The message is relayed straight to our support inbox, delivered by Resend in the same way as the support form below, and nothing is stored on this site: there is no database, no ticket and no log of what you wrote. Your address is used to reply to you and is never added to a mailing list. Opening the box, typing in it and closing it again send nothing.
Transcription with your own API key
If you choose to supply a key for an OpenAI-compatible service, audio from the file you are transcribing is sent to that provider so it can be transcribed, and your key is stored on your Mac. This is off unless you turn it on and provide a key. Your relationship in that case is with the provider you chose, under their terms and their privacy policy, not ours.
Generating B-roll with your own fal.ai key
If you choose to save a fal.ai key and generate a B-roll clip, the prompt you typed and the settings you chose - the model, the clip length, the aspect ratio and the resolution - are sent to fal.ai so it can generate the clip, and the finished clip is downloaded from fal.ai’s storage into Rooster’s own folder on your Mac. Nothing else is sent: not your recording, not your transcript, not your project. Your key is stored in the macOS Keychain and is sent only to fal.ai. Rooster does not meter, record or see these requests, and there is no Rooster server in the path. This is off unless you supply a key. Your relationship is with fal.ai under their terms and privacy policy.
Buying Rooster
Rooster is not on sale yet, so nothing described here happens today. When it is, the direct download will be sold through a merchant of record, which acts as the seller: it processes the payment, issues the invoice and handles refunds, and we never receive or store your card details. Activating a licence will send your licence key and an identifier for the Mac you are activating, so that one licence can be limited to a small number of machines. Where Rooster is later sold through the Mac App Store, Apple processes that purchase instead and tells us only what it reports to any developer, which does not include your payment details. If you have turned on Apple’s sharing of crash reports with developers, Apple may pass us diagnostic reports; that setting is yours and lives in macOS, not in Rooster.
4. This website
The site loads analytics only if you choose “Allow analytics” in the privacy choices. We remember that choice in your browser’s local storage. It is used only to remember the choice, and you can change it at any time with the Privacy choices button in the footer.
If you allow analytics, the site counts page views using Google Analytics and Vercel Web Analytics. Google Analytics uses first-party analytics cookies to distinguish visits and reports pages, approximate location, device and browser information to us. Advertising storage, ad personalisation and ad-user data are disabled. We do not run Google Ads or use these analytics to advertise to you. The cookies are named _ga and _ga_<container-id>. Google gives both a default lifetime of up to two years, subject to browser limits; withdrawing consent removes them from this site. Google explains the processing in its privacy policy.
Vercel Web Analytics records the page you opened, the site that referred you, the country, region and city the request came from, and your browser, operating system and device type. It writes no cookie or analytics identifier to your device. Repeat views within a day are recognised by a hash Vercel derives from the request itself, and that hash is discarded after 24 hours. It tells us which pages are read. It does not tell us who read them. If you decline analytics, neither analytics service loads.
The video player on the homepage is served by Livid. Its analytics and viewer tracking are disabled, so it creates no Livid viewer cookie or analytics identifier. Loading or playing the video still sends Livid the ordinary request details needed to deliver it, including your IP address and browser information. The player may keep playback preferences, such as whether it is muted, in your browser’s local storage. Those preferences stay on your device and are not analytics.
The site is hosted by Vercel, which also processes requests on our behalf and keeps short-lived operational logs that include IP addresses, as any web host must in order to serve and protect a site.
The support page has a form. What you type into it - your name, your email address, the topic and your message - is emailed to our support inbox, and so, when Rooster opens the page for you, is a line naming the Rooster version, how you got it and your macOS version, which the page shows you before you send. None of it is stored anywhere else: there is no helpdesk, no database and no ticket. The email is delivered by Resend, which acts on our instructions and handles the message in transit. Your address is used to reply to you and is never added to a mailing list. You never have to use the form; writing to support@rooster.cam from your own mail client reaches the same inbox and involves us no differently.
Blog posts carry a launch waitlist form. If you use it, three things are emailed to that same inbox, delivered by Resend in the same way: the address you give, your answer to the optional “how did you hear about Rooster” question, and the page you signed up from. There is still no database - the inbox is the list. Your address is used to send one launch announcement and nothing else, and it is not shared or added to anything further. To come off the list before then, write to support@rooster.cam and we will delete the email that holds your address.
None of this touches the application. Rooster itself has no analytics and reports nothing about your editing back to us. If we add anything to this website that collects more than the above, we will describe it here before it ships.
5. Legal basis and your rights
For the website analytics described above, our basis is the consent you give in the privacy choices. You can withdraw it at any time with the Privacy choices button in the footer. For other personal data, our basis is our legitimate interest in operating and securing the website and in supporting people who write to us. Under UK GDPR you have the right to ask what we hold, to have it corrected or erased, to object to processing, and to receive a copy. In practice we hold very little beyond the emails you send us. Write to support@rooster.cam and we will respond within one month.
If you are not satisfied, you can complain to the Information Commissioner’s Office at ico.org.uk. We would rather you told us first so we can put it right.
6. Keeping and sharing data
We keep support correspondence for as long as it is useful to the person who sent it and then delete it. We do not sell personal data, and we do not share it except with the providers named on this page acting on our instructions, or where the law requires it.
7. Children
Rooster is not directed at children under 13, and we do not knowingly collect their personal data.
8. Changes
If this policy changes we will update the date above. Where a change materially affects what leaves your Mac, we will say so in the application as well, because a website nobody revisits is a poor place to hide a change of that kind.