Skip to content
AI

Raycast AI Privacy & Security

At Raycast, we prioritize your privacy and security in all our AI features. With this document, we aim to provide clarity and transparency about how AI works in Raycast and our commitment to privacy and security.

You should know when and how AI is used and activated in Raycast. You should always be in control of your interaction with AI and have the ability to opt-out at any time. We will be transparent and open about how your data and AI inputs/outputs are used. We believe consent is crucial and aim to provide the best, most transparent AI user experience.

Raycast AI only runs when you explicitly trigger it; meaning, you ask AI a question, run an AI command, or otherwise interact with AI directly. There are two opt-in exceptions: Emoji Search, which requires your consent, and Automations, which run a prompt you wrote on a schedule you set.

Raycast AI does not monitor your activity. An automation runs only the prompt you gave it, at the times you chose, and nothing else; you can disable or delete it at any time. Your data is not used to train AI models. If you choose to send feedback, your data may be used to improve our AI system; this is strictly opt-in and you will be prompted to consent before data is sent.

  • Your AI interactions are not recorded
  • We do not collect or store sensitive information
    • We do not log or retain any user prompts. We do store some basic metadata, such as the number of completion tokens, for operational purposes only.
    • Cloud Sync: when enabled, the client sends content such as Snippets, AI Chats, etc. to our backend. We store this information encrypted in our databases.
    • AI attachments: Image attachments are securely uploaded to our servers for AI processing, enabling you to access them later. If you delete a message or chat that includes attachments, those attachments will be deleted from the server.
    • AI Feedback: If you choose to report feedback, the full chat thread — including AI Extension tool calls and results — will be sent to us. This is entirely opt-in and you must give explicit consent before any data is sent. Please be mindful of any sensitive data the thread might contain. We may use this information to improve the reliability of our AI System.
  • All models provided by Raycast AI are Zero Data Retention (ZDR). Providers do not keep your prompts or outputs after the request completes. Two exceptions apply:
    • Mistral AI: Retains data for a rolling 30-day window to monitor abuse. Data is deleted after that window
    • xAI: Retains data for 30 days before automatic deletion

When enabled, Raycast AI can build a memory summary from your conversations to personalize future responses. Memory is stored locally and encrypted at rest and in transit when synced via Cloud Sync. It follows the same privacy and security standards as all AI features. Your data is never used to train models. You can view, edit, or delete your memory at any time. You can learn more on the Personalization page.

Dictation is designed to be private by default. Your voice is never used to train AI models, and we don't store your audio or transcriptions on our servers.

  • Your audio is sent to our speech‑to‑text partner solely to produce a transcription, and isn't retained on Raycast servers after the request completes. Our partners are contractually prohibited from using it to train their models.
  • Every transcription is saved to your local app's database on your device, not in our cloud, so you can find and reuse it later. You can delete individual transcriptions or wipe the entire history at any time in the Dictation History command.
  • Your dictation statistics are computed on‑device from your local history and are never sent to Raycast as analytics or telemetry.
  • If App Context is enabled, nearby text and app details are used only for that single transcription request and discarded as soon as the transcription is complete. Nothing is stored.
  • Raycast AI features are powered by AI model providers, including OpenAI, Anthropic, Perplexity, and more (see the complete list of AI providers we use and their Terms below)
  • Raycast-provided model requests use secure server infrastructure to protect our API keys
  • When using Raycast-provided models, our agreements with providers prohibit them from using any AI interactions to train their models. When you use our AI features, we:
    • Forward your input to the AI provider's API
    • Exclude any personal information when doing so
    • Only share the minimum necessary data
  • BYOK (Bring Your Own Key):
    • Anthropic, Google, OpenAI: Requests are processed through our servers in order to unify the model APIs, integrate fallback behaviors, and do some final prompt management. This helps to maintain the quality and consistency of output when using your own API key vs. ours.
    • OpenRouter: Requests are routed directly from your device to OpenRouter's servers.
    • Custom API keys are stored locally on the user’s computer, not in our backend
    • When using BYOK, you maintain the contractual relationship with the AI provider. Please consult their privacy policies and terms for more details.
  • AI input and output is encrypted during transmission

When you supply the model yourself, your prompts don't go through Raycast's servers and Raycast's provider agreements above don't apply. Instead, the terms and privacy settings of the provider you connected govern how your data is handled. In every case, your chat history is still stored by Raycast, and synced if you have Cloud Sync enabled, the same as any other chat.

  • Connected Subscriptions: With Bring Your Own Subscription, your prompts go from Raycast to Claude Code or the Codex CLI on your computer, and from there directly to Anthropic or OpenAI. Raycast never sees or stores your provider credentials; those stay with the provider's tool.
  • Custom Providers: With Custom Providers, requests go directly from your device to the endpoint you configured. Your API keys live in the providers.yaml file on your device and are never sent to Raycast. If the endpoint is a gateway or team proxy, its operator's policies apply too.
  • Local Models: With Local Models, requests go from Raycast to the Ollama server on your machine, or to a remote Ollama host you configured. Nothing is sent to Raycast or to any third party.

A Project's instructions and memory are only shared with chats inside that project. A project's working directory is stored on the device where you set it and is never synced. Automations are device-local too: the schedule and prompt stay on the device where you created them and don't sync through Cloud Sync. The chats an automation produces are ordinary chats, so they follow your chat history and Cloud Sync settings.

  • AI features are optional and user-controlled. Users can completely disable AI.
  • Before using Raycast AI, you will be prompted to read and accept our Terms of Service if you haven’t accepted them in the past. AI does not run in the background and you must actively consent before AI can be activated. The only thing that runs unattended is an automation you scheduled yourself, and disabling or deleting it stops any future runs.
ProviderTerms of Service
OpenAIServices Agreement, Usage Policies
AnthropicCommercial Terms
PerplexityAPI Terms of Service
GroqTerms of Use
Mistral AITerms
Google GeminiGemini API Terms
xAITerms of Service (Enterprise)
ReplicateTerms
BasetenTerms and Conditions
CerebrasTerms of Service

As a company that believes in the value and importance of open source software, Raycast has a rich and expansive extension ecosystem. Note that third-party extensions may use their own logic for AI. As all extensions are open source, you can refer to an extensions’ README or source code for further information.


Raycast continuously review and update its privacy practices to maintain the highest standards of data protection while delivering powerful AI capabilities. If you have questions or suggestions, you can contact us via privacy@raycast.com.