Glaze Privacy & Data

Glaze is local-first. Apps built with Glaze live and run on the Mac, and nothing about them is uploaded or synced silently.

AI is where data leaves the machine, at two points. The agent sends prompts and the parts of a project it's working on to AI model providers to build an app, and an app with a Glaze AI feature sends whatever that feature acts on each time someone runs it. This page covers both, along with what Glaze stores, who it shares data with, and what it measures.

What Stays on the Mac

An author's apps, their data, project files, and chat history with the agent all stay on their Mac. Apps and their code live as files on disk, and chat history lives in a local database. None of it leaves the Mac on its own, and nothing is synced to the cloud in the background.

What's Sent to Build an App

As the agent works, it sends what it needs to the Glaze AI service, which passes it to the model providers: the author's prompt, the conversation so far, the app's description, the files it reads or edits, the output of the commands it runs, and any images or files attached. The project isn't uploaded up front; code reaches the model as the agent opens it. The provider's API key stays on Glaze servers, never on the device.

Glaze doesn't use prompts or content to train or tune its AI models, and inputs aren't kept once a response is generated. Three categories of things are kept, including:

• Uploaded files that an app needs to run, so it keeps working.
• Feedback and issue reports, which can include session context, like conversation history, memory files, and app logs.
• A short summary of prompts, described under Analytics & Improvement below.

What an author builds is theirs. An app's code and content, and the output the models generate, belong to its author, to use, distribute, or sell. The Glaze pieces an app ships with, like the runtime and SDKs, stay property of Raycast Technologies Ltd and come with a licence to use them, which is what lets the app run.

What's Sent When Using Glaze AI

An app with no Glaze AI features sends nothing to AI. When an app does use Glaze AI, whatever that feature acts on leaves the app and goes to a model provider so it can generate a response: the text the user types in, the notes or records it summarizes, the file or image they hand it, and the instructions the app sends alongside them. That data is the user's, and anything the app stores but never sends to Glaze AI stays on their Mac.

The request goes to the Glaze AI service, which passes it to the provider, and is the same path the agent uses. Glaze records only what it needs to meter the user's credits, such as which app ran the request and how much it used, never the prompt or the content sent, and as with the agent those requests aren't used to train or tune the models.

Custom AI Providers

An author can also ask the agent to wire an app up to an outside AI service directly, using their own account and API key with that provider. This is separate to Glaze AI, and the protections above don't apply to it:

• The requests go straight from the app to that provider, not through Glaze. Glaze can't see, meter, or limit them, and they don't draw on anyone's Glaze credits.
• User data is handled under that provider's terms and privacy policy, which set their own rules on retention and training.
• The credentials live in the app rather than on Glaze servers, and every user runs on the author's key. A desktop app can't keep a secret truly private, so treat any shipped key as recoverable and scope it as narrowly as the provider allows.

Publishing & Installing Apps

Publishing changes who's responsible. Once other people run an app, its author handles their data, not Glaze, and Glaze's Privacy Policy doesn't cover what the app does with it. If an app collects, stores, or sends anything about its users, including through a Glaze AI feature, telling them and having a lawful basis for it is the author's job.

App authors are also responsible for making sure a published app carries no credentials, API keys, or personal data it shouldn't. Glaze may run apps through an automated review before publishing that looks for exposed keys, personal data, and other security risks, but it runs without human oversight and its findings and fixes are a safety net rather than a guarantee. Review the app before submitting it to the Store or sharing with others. See Publish Apps.

From a user's side, permissions granted to an installed app go to that app and its author, not to Glaze, and Glaze doesn't monitor or endorse how a published app behaves. An app from the Store deserves the same scrutiny as any other app download.

Sharing & Storage

Glaze shares data only with the vetted service providers it relies on to run, like the AI model providers, cloud hosting, and Stripe, which processes payments so Glaze never sees or stores full card details. Each provider is bound by a contract that limits it to working on Glaze's behalf. The model providers also apply their own terms to the input they receive, which both authors and users accept when they use the agent or Glaze AI.

Personal data is stored primarily on servers in the United States, with safeguards in place whenever it's transferred across borders, and it's kept only as long as it's needed to provide the service or until the account is deleted, whichever comes first. Glaze doesn't sell data or use it for ad targeting.

Connections & Secrets

When an app connects an outside service like GitHub, Linear, or Slack, the access token is stored encrypted on the Mac it's running on, protected by the Keychain, rather than in plain text. Connections can be reviewed or revoked at any time. See Managing Connections.

Analytics & Improvement

To improve Glaze, we collect usage analytics about both the Glaze app and the apps built with it, as described in the Privacy Policy. These are usage metadata only, things like app identifiers, open and usage events, build type, and OS details; they don't include prompts, files, or the content of apps. Separately, Glaze keeps a short, model-generated summary of prompts, linked to the account that sent them, to help improve the service.