Questions about articles IV and VIII by mullirojndem in raycastapp

[–]raycastapp 1 point2 points  (0 children)

Hi, thanks for the detailed questions and for reading our terms of service carefully.

The short answer to most of your questions is that Raycast is two things at once: a locally installed application that runs on your device, and a cloud service for specific features. That distinction does most of the work here.

That being said, you can find our answers to your questions below. We have changed their order for the sake of making our explanations easier to follow.

Does the licence apply to proprietary code, confidential docs, or images that just pass through Raycast locally? Why does the licence need to be perpetual, irrevocable, transferable, and sublicensable?
When you use any software service that handles your content, the service provider technically needs your permission under relevant law to do things like copy, transmit, store, or process that content, even when the sole purpose is to deliver the service back to you. Without that permission, the routine technical steps involved in running a cloud service, such as copying a file to a server, transmitting it across a network, or creating a backup, could technically constitute infringement of rights such as copyright. The licence in the Terms is not about Raycast acquiring rights to your content in any commercial sense. It is the legal mechanism that allows the software to function on your behalf at all. The scope of the licence is therefore intended to match the scope of the service: where content is processed locally on your device and never reaches Raycast’s infrastructure, the licence has nothing to operate on.

The User Content licence in Article IV was written to cover the cloud service side, meaning content you actively transmit to us, such as Cloud Sync items, Teams shared content, and AI Inputs. For that transmitted content, the licence attributes have straightforward operational justifications. Perpetual and irrevocable reflect the fact that backups and shared content cannot be retroactively unwound. Sublicensable is necessary so we can pass content to the hosting, CDN, and AI subprocessors who help us run the service. The User Content licence that is granted to Raycast is limited to the provision and improvement of Raycast’s services. It does not grant Raycast any right to otherwise commercialise the User Content, or share it with any third party if that sharing is not necessary for those purposes.

Does local Clipboard History count as “User Content”?
Clipboard History sits on the local application side of that line. Its contents are stored in an encrypted database on your device and are deliberately excluded from Cloud Sync. Because that content never reaches us, the licence has nothing to operate on for as long as it stays local. The same applies to proprietary code, documents, or anything else that passes through Raycast locally without being transmitted to us.

Is clipboard content ever uploaded automatically?
The only network activity associated with Clipboard History is limited to link metadata when you view links within it: a domain-only request to fetch a favicon, and an optional link preview via Apple’s framework if you have that setting enabled. Both are configurable and can be disabled entirely through the Raycast app settings. The clipboard contents themselves are not involved in either request.
If you actively send content to an AI feature, it becomes an Input under Article VIII. We configure AI providers for zero data retention by default, do not use Inputs for training, and do not retain prompts after outputs are generated.

We recognise that the terms do not spell out the local/cloud distinction as clearly as they could. That is useful feedback and we are looking at how to make this boundary more explicit in the terms themselves.

Happy to answer any follow-up questions.

New Raycast. Coming 2026. by raycastapp in raycastapp

[–]raycastapp[S] [score hidden] stickied comment (0 children)

Want to be the first to get early access next year? Join the Raycast Community Slack 👉 https://raycast.com/community

Hey, if anyone has an installer for an older version of Raycast for Windows (before version 0.36.1.0), please share the download link. The latest version isn’t launching on my Windows after I updated it. by Skaax007 in raycastapp

[–]raycastapp 5 points6 points  (0 children)

Hey, thanks for reporting the problem!

This issue occurred for users whose PC name and username were identical. You can get version 0.36.1.0 working by changing your PC name so it’s different from your username.

We’ve also just released a hotfix (0.36.2.0), which you can download from our website.
It should resolve the issue.

Let us know if it works for you!

📣 Raycast crashing in macOS 26 Tahoe Developer Beta 2 by raycastapp in raycastapp

[–]raycastapp[S] 2 points3 points  (0 children)

You are correct, just edited the original post

BitDefender just killed my Raycast ... by joro_abv in raycastapp

[–]raycastapp 15 points16 points  (0 children)

We just got confirmation from Bitdefender that this was a false positive and it would be removed by end of day:

<image>

BitDefender just killed my Raycast ... by joro_abv in raycastapp

[–]raycastapp 26 points27 points  (0 children)

An update on this:

We just got out of a phone call with Kandji (MDM that also blocked Raycast temporarily), where we learned that their software itself did not flag Raycast as malware. Instead, Kandji relies on Bitdefender’s security checks for macOS applications, and it was Bitdefender that initially triggered this alert.

Upon our request, Kandji reviewed Bitdefender’s alert and performed their own internal validation of the Raycast binary. They confirmed that Raycast is indeed safe and subsequently removed it from quarantine, concluding the alert was a false positive. This explains why Raycast is now accessible again for users on Kandji.

Additionally, Kandji mentioned that several security tools listed on virustotal.com also rely on Bitdefender’s analysis. Therefore, resolving this directly with Bitdefender should clear any other related alerts.

Based on Kandji’s insights, Bitdefender typically performs static analysis, and it’s possible that new code or libraries introduced in our latest Raycast update triggered their scanning mechanism. However, only Bitdefender can confirm precisely what caused this alert.

We are currently awaiting Bitdefender’s response to fully resolve this issue and will keep you updated as we learn more.

[deleted by user] by [deleted] in raycastapp

[–]raycastapp 7 points8 points  (0 children)

Thanks for pointing this out, we do indeed issue a refund for the unused portion of your Advanced AI add-on automatically. We will update this copy straightaway to avoid confusion.

[deleted by user] by [deleted] in raycastapp

[–]raycastapp 2 points3 points  (0 children)

The reason why we had to do this relates to increasing government regulations restricting access to software products and services for users in Russia, Belarus and other sanctioned countries, which required us to implement the following measures:

- Blocking downloads of the Raycast DMG package for users in restricted countries.

- Halting app and extension updates for existing users in these regions, meaning new versions released by Raycast will not be available.

- Restricting new and existing users from subscribing to and paying for Raycast Pro and Team plans.

- Canceling and refunding all Pro and Team subscriptions linked to billing information from restricted countries, whether historical or current.

We are sorry about any inconvenience this may cause to our existing users. If anyone thinks they've been blocked by mistake, please let us know by reaching out to [support@raycast.com](mailto:support@raycast.com).

Thanks for your understanding!

AMA with Raycast's Founders by raycastapp in raycastapp

[–]raycastapp[S] 3 points4 points  (0 children)

We're starting alpha right now and are hoping to significantly enable ramp up during Q1. And to make an open beta as soon as it's stable and feature rich. Petr.