Legal
Privacy Policy
Rushes is local-first by design. Your media never leaves your machine, and transcription and alignment run locally, on-device. We built Rushes this way deliberately — and this policy explains the limited data we do handle to operate the service, run AI analysis, and manage your account and billing.
This Privacy Policy describes how Beastly, Inc. ("Beastly," "we," "us") collects, uses, and shares information in connection with Rushes, a macOS application. Beastly, Inc. is the data controller for the purposes of this policy. If you have any questions, contact us at support@getrushes.com.
The local-first principle
Your interview footage and other media files never leave your machine. Rushes does not upload, transmit, or store your video or audio files. Transcription and alignment run locally and on-device — turning speech into text, and checking where each word starts and ends, happen entirely on your Mac, with no media sent to us or to any third party.
B-roll is found and sorted into bins entirely on your Mac too. The picture model runs locally, in a process that only your Mac can reach; no frames, pictures, thumbnails, or file names are sent anywhere. B-roll adds nothing to what the analysis sends.
The only project content that leaves your device in normal use is text, sent when you run the analysis: the transcript text, the subject labels you typed, and your brief, so that quotes can be organized by concept and theme. Never your footage, audio, file names, or folder paths. Scripted projects are analyzed entirely on your Mac; nothing from them is sent for analysis. The one other time project content leaves your Mac is if you click Send to support, which sends us an encrypted report about an export (see "What we collect" below). Your media itself is never part of either.
What we collect and why
Ingest, sync, and transcription need no account. They run on your Mac without an email or a sign-in. Running the analysis on an interview project requires an email sign-in. The first time you run it, Rushes asks for your email and sends you a magic link. Scripted projects are processed entirely on your Mac and send nothing to our server until you subscribe to export, so Rushes does not ask for your email until then. Ingest, sync, transcription, and analysis are free to use; free analysis runs are counted per account, using a hashed form of your email, and rate limits tied to your device identifier and a short-lived hash of your IP address prevent abuse of the free trial. We also collect your email if you subscribe, or if you separately ask us to send you a download link or product updates from our website.
- Email address — to sign you in with a magic link when you first run the analysis on an interview project, including during the free trial, or when you subscribe; and, if you subscribe, to manage your subscription and handle billing. To count free analysis runs we use a hashed form of your email, not the email itself.
- Device identifier — a random identifier Rushes generates the first time you use it and keeps in a file on your Mac. It is not derived from your hardware. It is sent with analysis requests, subscription checks, crash reports, the launch check-in, and support diagnostics, to prevent abuse, control service costs, and operate the service reliably. Once you sign in, it is associated with your account. It stays on your Mac if you sign out. A subscription works on one Mac at a time, so while a Mac is signed in to a subscription, our server stores that Mac’s device identifier with the subscription record, alongside a one-way hash of your account email, not the email itself, and the dates it was first and last seen.
- Analysis-run counts and request timestamps — to apply the free-run limit and rate limits, and to keep the service reliable. These counters are all we keep from an analysis; our server stores neither the request nor the response.
- IP address — our servers receive your IP address whenever Rushes connects to them. We do not store it. We keep a shortened hash of it for at most 24 hours to rate-limit requests and to limit free analysis runs from one network. Our hosting, download, sign-in, and payment providers also see the IP address of each connection, as any web service does.
- Subscription token — when Rushes confirms your subscription online, our server issues a token signed by us and stored in the macOS keychain on your Mac. It contains a hashed form of your email, your device identifier, the subscription status, the times it was issued and expires (14 days later), and a version number and signing-key ID. It does not contain your email itself, your plan, or any payment details. Rushes checks it each time you export, which is what lets export keep working offline for up to 14 days after Rushes last confirmed your subscription. We do not store issued tokens.
- Crash reports — only if you say so. If Rushes quits unexpectedly, the next time it opens it asks whether to send the crash report to us; nothing is sent until you choose Send, and you can choose "always send" there or in Account. A crash report is the report macOS writes, sent unedited: it typically holds the app's stack traces, its location on disk, the list of loaded system libraries, a numeric macOS user ID, the app version, the macOS version, the Mac model identifier (such as "Mac16,5"), and Apple's crash-reporter identifier for your Mac. macOS removes your user name from these reports before they are written. Rushes encrypts the report on your Mac so that only Beastly can open it. Alongside it we receive, unencrypted, your device identifier, the crash file's name, the app version, and the time. A crash report never contains your footage, your transcripts, your project or file names, or anything you typed.
- Launch check-in — only if you have turned on automatic sending ("Always send crash reports and basic device details" in Account, or "Always send" in the crash dialog). Rushes then sends one short check-in per app version, holding the app version, the macOS version, the Mac model identifier, and your device identifier. It contains no email, no account information, and nothing about your projects. If you send a single crash report without choosing always send, that one send also includes the check-in for the version you are running.
- Support diagnostics — only when you click Send to support on the export page; nothing is sent until you click it. After a successful export it sends that export's internal report; after a failed export it sends a failure record. These reports contain project content so we can see what went wrong: subject names, concept titles, quoted soundbites and other transcript excerpts, unanswered brief questions, clip and audio file names, and, for scripted projects, slate and take names and their lines. A failure record instead holds the time, the app version, the project name, the export's full destination folder path (which usually includes your macOS user name), the last step reached, and the error message. Rushes encrypts the report on your Mac so that only Beastly can open it; our servers and storage provider cannot read it. Alongside it we receive, unencrypted, your device identifier, the project's export name (which includes the project name), the export date, and the app version. Support diagnostics never contain your footage or audio.
- Update check — each time it launches, Rushes requests getrushes.com/version.json to see whether a newer version is available. The request carries no identifiers; like any web request, it reaches our host with your IP address.
- Model downloads — at first launch, Rushes downloads three open-source models from the Rushes download server (downloads.getrushes.com), about 2.8 GB in all: one for transcription, one for checking where words start and end, and one for sorting B-roll by what is in the picture. Like any download, that request shows our server your Mac's IP address; it carries nothing about you or your projects: no device identifier, no account, and no project data. If the download from our server fails, Rushes fetches the same files from Hugging Face (huggingface.co), which then sees the same IP address. After that, Rushes downloads a model again only if its file goes missing from your Mac. All three run entirely on your Mac.
- Analysis content — when you run the analysis on an interview project, Rushes sends our server, which passes it to our AI analysis provider (Anthropic): every transcript line's text, including the interviewer's lines, with line numbers; each subject's label (the short code you gave it, or the first six letters of the name you typed); and your brief as typed (the project brief, interview questions, and thematic anchors). Each request also carries your sign-in session, which identifies your account, your device identifier, a run identifier, and the app version. It never includes your footage, audio, file names, folder paths, or timecodes. Scripted projects are analyzed on your Mac and send nothing for analysis.
- Payment details — handled entirely by Stripe, which acts as merchant of record. We never see or store your card number or other card data. Invoices, tax, and transaction records are held by Stripe under its own privacy policy; we keep only the Stripe customer and subscription identifiers, your plan, its status and dates, and a log of Stripe event identifiers.
What we do not collect
- Your footage and media — never transmitted, never uploaded, never stored by us.
- Request and response content bodies — we do not log the content of your analysis requests or responses. Only metadata (device identifier, a hash of your IP address, run counts, and timing) is kept for service operation and abuse prevention.
- Your IP address — never stored as-is; see above.
Our legal bases
Where the GDPR or the UK GDPR applies, we rely on these legal bases:
- To provide Rushes and your subscription (performance of a contract) — signing you in, running the analysis you ask for, confirming and billing your subscription, keeping it to one Mac at a time, the subscription token, the update check, and the model downloads.
- Our legitimate interests — keeping the free trial from being abused and the service secure and reliable (free-run counts, rate limits, the hash of your IP address, the device identifier, and server logs); answering your support email and the support diagnostics you send; and measuring, in aggregate and without cookies, how our website is used. We have weighed these interests against your rights, and you can object to them (see "Your rights").
- Your consent — crash reports and the launch check-in, which Rushes sends only when you choose to, and our email list (download links, release notes, and product updates). You can withdraw consent at any time: turn off automatic sending in Account, or unsubscribe using the link in any email.
- Legal obligations — billing and tax records, which Stripe keeps as the law requires.
Your email address is needed to run the analysis on an interview project and to subscribe; without it we cannot provide those. Ingest, sync, and transcription work without it.
People in your footage
The transcripts you send for analysis can include personal data about the people you filmed, such as what they said and the labels you gave them. For that data, you decide what is processed and why, and we process it only on your behalf: to return your analysis, as described above. It is not stored by us and is not used for anything else. If your organization needs a data processing agreement with us for this, email support@getrushes.com.
Subprocessors
We rely on a small set of third-party providers to operate Rushes. Each processes only the data needed for its function. None of them ever receives your footage, audio, or any media file — that data never leaves your machine at all.
- Anthropic — AI analysis of transcript text, subject labels, and your brief (organizing quotes by concept and theme). Privacy policy
- Stripe — payments, merchant of record, and billing. Privacy policy
- Supabase — sign-in (your email), subscription records, and storage of the crash reports, launch check-ins, and support diagnostics you choose to send. Crash reports and support diagnostics are stored encrypted. Privacy policy
- Resend — transactional email (such as sign-in magic links), and internal alerts to our support inbox: when a crash report arrives (with your device identifier and the crash file's name), when support diagnostics arrive (with your device identifier and the project name), and about refunds and disputes (with your email). Alerts carry no attachments. Privacy policy
- Help Scout — our support inbox. It holds the email you send to support@getrushes.com (your email address, your name if your email includes it, and anything you write or attach), our replies, and the internal alerts described under Resend. Privacy policy
- Vercel — hosting for our website (including the update check and website analytics), backend, and analysis proxy. Its server logs, which can include your email and device identifier, are kept for a short period. Privacy policy
- Cloudflare — serves our download server (downloads.getrushes.com): the Rushes installer you download from our website, and the three open-source models Rushes downloads at first launch. For these downloads it sees the IP address of each request and nothing else; no identifiers or project data are sent. It also forwards the email you send to support@getrushes.com to our support inbox. Privacy policy
- Hugging Face — the fallback host for the same three open-source models, used only if the download from our server fails. It sees the IP address of the download request and nothing else; no identifiers or project data are sent. Privacy policy
- Redis Cloud (Redis Ltd.) — free-run counts and rate limits (a hashed form of your email, your device identifier, and a hash of your IP address). Privacy policy
- Kit (formerly ConvertKit) — the email list behind our download links and product updates. Website only; the app does not use it. Privacy policy
International data transfers
Beastly, Inc. is in the United States, and most of our providers process data there. Supabase, which runs our sign-in and database, contracts through Supabase Pte. Ltd. in Singapore, so the data it holds can also be processed in Singapore. If you use Rushes from outside the United States, including from the European Economic Area or the United Kingdom, your information (such as your email and transcript text sent for analysis) is processed in those countries. Each provider's data processing terms include the European Commission's Standard Contractual Clauses, with the UK Addendum, and some providers are also certified under the EU-U.S. Data Privacy Framework and its UK Extension. Email us for a copy of these safeguards.
Data retention
- Trial accounts — if you signed in to run the analysis but never subscribed, your account and its free-run count are deleted after 12 months without use. Use includes Rushes quietly refreshing your sign-in when it opens, so an account that is still in use is never deleted. Deletion completes within 90 days, when the record of it leaves our sign-in log. If you come back later, you simply sign in again.
- Subscriber accounts are kept while your subscription is active. 12 months after cancellation or after your last sign-in, whichever is later, we replace the email on your subscription record with a placeholder. Your sign-in account and its free-run count then follow the trial-account rule above. We keep the Stripe customer and subscription identifiers, the plan, its status and dates, and a log of Stripe event identifiers. These are pseudonymous: they link only to Stripe's own records. Stripe keeps payment and tax records as the law requires, under its own privacy policy.
- The Mac on a subscription — the device identifier stored with your subscription record is deleted when that Mac signs out, when support frees it at your request, when the subscription ends, and after 12 months in which that Mac has not been seen.
- Crash reports, launch check-ins, and support diagnostics you send are deleted 30 days after we receive them.
- Rate-limit records — the hash of your IP address is kept for at most 24 hours, and per-device request counters for 7 days.
- Server request logs at our hosting provider (Vercel) and at Cloudflare, which serves our model downloads, are kept for a short period.
- Analysis content (transcript text, subject labels, and your brief) is processed to return results and is not stored by us; our AI provider processes it under its own terms.
- Outside our automatic deletion — the support inbox (Help Scout), database backups, Stripe's own records, and server request logs are not covered by our nightly deletion job. How long each is kept is described in this list.
- Support email — the email you send us, our replies, and the internal alerts above are deleted from our support inbox (Help Scout) 2 years after the conversation's last message. Alerts also stay in our email provider's logs under its own retention.
- Email list — your address stays on our list until you unsubscribe or ask us to remove it. After you unsubscribe, Kit keeps a record that you did, so that you are not emailed again.
- Sign-in records (sign-ins, session refreshes, sign-ups, and account deletions, each naming your email) are kept for 90 days.
- Backups — deleted data can remain in our providers' backups until those backups expire on their normal schedule.
- On your Mac — the subscription token stays in the keychain until it expires. Signing out removes your sign-in and subscription token from this Mac's Keychain. The device identifier file, local copies of diagnostics, and receipts stay on your Mac until you delete them.
Your rights
If the GDPR or the UK GDPR applies to you, you have the right to:
- Access your personal data and get a copy of it;
- Correct it if it is wrong or incomplete;
- Delete it;
- Restrict how we use it;
- Port it: receive the data you gave us in a machine-readable format;
- Withdraw your consent at any time, where we rely on it. This does not affect what we did before you withdrew it;
- Complain to the data protection authority where you live or work.
Your right to object. You can object at any time, on grounds relating to your situation, to our use of your personal data based on our legitimate interests. We will then stop, unless we have compelling legitimate grounds that override your interests or need the data for legal claims. You can object to our product-update emails at any time, without giving a reason, and we will stop sending them.
If you live in California or another U.S. state with a privacy law, you have similar rights, including to know what we hold about you, to correct it, and to delete it, and we will not treat you differently for using them. We do not sell or share your personal information, as those laws define those terms.
To exercise any of these rights, email support@getrushes.com. We may ask you to confirm the request from the email address on your account. We respond within one month; for complex requests that can extend by up to two more months, as the GDPR allows, and we will tell you if it does.
Rushes does not make decisions about you by automated means that have legal or similarly significant effects. The analysis organizes the transcripts you send; it does not evaluate you.
Cookies and analytics
These apply to our website only. The Rushes application itself contains no advertising and no third-party analytics or tracking. The only usage information it sends on its own is the launch check-in described above, and only when you have turned on automatic sending or send a crash report; crash reports and support diagnostics are sent only when you choose to send them.
- Vercel Web Analytics — aggregate website traffic measurement: the page viewed, the referring site, country, browser, operating system and device type, and a few on-page actions (which download button was clicked, whether a download was started, which FAQ questions were opened, and whether the pricing and how-it-works sections were reached). It sets no cookies and stores no IP address; to count a visit once, it uses a hash of the request that is discarded after 24 hours. It is not used to build advertising profiles, and it is not present in the app. Privacy policy
- Kit (formerly ConvertKit) — the email signup and download-link forms on our site. May set cookies. Privacy policy
- Google Search Console — domain verification only; no visitor data.
If we add other analytics or tracking in the future, we will disclose it here and update the effective date.
Security
We take reasonable measures to protect your information. Sign-in is passwordless — we use a magic link sent to your email and never collect or store passwords. Authentication tokens and your subscription token are stored in the macOS keychain on your device. The subscription token is signed by us, so Rushes can tell if it has been altered. Crash reports and support diagnostics are encrypted on your Mac before they are sent, and only Beastly holds the key that opens them. Data in transit is protected with TLS. As noted above, we do not log the content of your requests or responses — only operational metadata.
Children's privacy
Rushes is a professional tool and is not directed to anyone under the age of 16. We do not knowingly collect personal information from children under 16. If you believe a child has provided us with personal information, contact us and we will delete it.
Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will revise the effective date at the top of this page. If a change materially affects how we use your personal data, we will tell you before it takes effect, by email if we have your address and on this website. Where a change needs your consent, we will ask for it.
Contact
Beastly, Inc., 111 NE 1st Street, 8th Floor #327, Miami, FL 33132, USA — support@getrushes.com
Governing law: This Privacy Policy is governed by the laws of the State of Florida, without regard to its conflict-of-laws principles. Venue for any dispute lies in the state and federal courts located in Miami-Dade County, Florida. This does not limit any right you have under the law of the country where you live, including to complain to your data protection authority or to bring a claim in your local courts.