# Team FAQ

Common questions from teams building apps with Glaze at work, including the ones IT, Security, and Finance tend to ask. For everything Glaze collects and stores, see [Glaze Privacy & Data](https://manual.glaze.app/account/privacy-and-data).

## Where Your Data Goes

### Our app connects to a company system. Where does that data go?

The data goes straight from the Mac running the app to that service and back, whether it's a CRM like Salesforce, an ERP like NetSuite, a warehouse, or an internal API. Glaze isn't in the middle: the app calls the service directly, and the results it gets back are held locally, in the app's own data area on that Mac. They aren't routed through Glaze servers, and nothing syncs or backs up to the cloud in the background.

Two things change that, both covered below: a feature that uses [Glaze AI](https://manual.glaze.app/capabilities/ai) or another AI provider to process data, and real data left in the project while the app is being built by the agent.

### What gets sent to Glaze's servers?

- **What the agent needs to build the app**, meaning prompts, the conversation, and the files and command output it works with, which go to the Glaze AI service and on to the model providers.
- **Whatever a Glaze AI feature sends** while someone is running the app, by the same route.
- **Account, billing, and usage metadata**, like which app made an AI request and how many credits it used.
- **The app itself, if it's published**, meaning its source and the built app, not its data.

Business-sensitive information an app fetches and stores locally is not on that list.

## AI Features

### Our app uses AI on company data. What gets sent then?

Whatever the AI feature implemented by the app author acts on. If it turns a set of records into a weekly summary, those records go to the Glaze AI service, which passes them to the model provider that generates the response. They aren't kept once the response comes back, and they're never used to train or tune models.

**Glaze retains only the usage metadata it needs to meter credits, never the content itself.**

### Can we build the same app without sending anything to a model?

Yes. AI is opt-in and implemented per-feature in an app, and an app with no Glaze AI features sends nothing to a model. Charts, grouping, totals, and other everyday analysis are ordinary code that runs entirely on the Mac, so an app can avoid AI altogether unless you want the more powerful analysis or reports that models can provide.

Where an app does use AI, each person running it grants permission for that app individually and can revoke it or cap its daily usage. See [AI](https://manual.glaze.app/capabilities/ai).

## Building & Sharing Apps

### Does the agent see our data while it's building the app?

It sees the project: the code, the files it opens, and the output of the commands it runs, all of which go to the model providers as it works. A real export sitting in the project folder is a file like any other, so the agent can read it and send it along with everything else.

Keep production data out of the project while building. A short sample, synthetic rows, or a few anonymized records are enough for the agent to build against, and the app can connect to the real source when it runs.

### What gets uploaded when we publish to the Team Store?

Two things, for two different reasons. The app's **source**, meaning everything in its project folder, goes to Glaze's private storage so the automated review can scan it for exposed keys, personal data, and other security risks, and so the pipeline can compile it. The **built app** is what teammates download when they install it, and the source isn't shared with them.

What isn't uploaded is the app's data or the credentials on the author's Mac, since everyone connects with their own. Files like `.env` are blocked too. Anything else sitting in the project folder is part of the source, a data file included, so check what's in there before publishing and treat the automated scan as a safety net rather than a guarantee.

Team Store apps are visible only to the team. See [Team Store](https://manual.glaze.app/team/team-store) and [Visibility Levels](https://manual.glaze.app/share/visibility-levels).

### If we share an app across the team, can people see each other's data?

Not by default. Each person installs their own copy, connects it with their own credentials, and its data stays on their Mac. Glaze puts no shared store behind an app holding everyone's records, so sharing an app distributes the app itself, not its contents.

An app author can build that deliberately, by wiring the app to an outside database or service so every copy reads and writes the same records. That's ordinary app code and Glaze isn't part of it: the data lives with whichever service was chosen, under that service's access rules.

## Integrations & Credentials

### Where do the credentials for a connected integration live?

Encrypted on the Mac, not on Glaze servers. Signing in happens in the browser, and the provider hands its response back through a Glaze callback URL that exists only to pass it to the app. For a service connected through [Custom OAuth](https://manual.glaze.app/integrations/custom-oauth), the app exchanges that response for a token on the Mac itself, and Glaze keeps no copy of it. Access can be revoked at the provider or in Glaze at any time. See [Managing Connections](https://manual.glaze.app/integrations/managing-connections).

### Can we configure which integrations are available in Glaze?

Not centrally. There's no team setting that limits which services an app can connect to, so anyone building one can use a built-in connector or any OAuth 2.0 provider they have credentials for. What a team can do is agree on a convention and ask app authors to favour particular integrations or OAuth providers in internal apps, so everyone connects to the same systems the same way.

Connections are also per-project rather than team-wide, and it's the person running an app who signs in, so an app only ever reaches what they've granted it. See [Integrations Overview](https://manual.glaze.app/integrations/overview).

## Storage & Retention

### Where does Glaze store the data it does hold, and for how long?

Personal data sits primarily on servers in the United States, with safeguards 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. Usage analytics are metadata only and never include prompts, files, or app content. See the [Privacy Policy](https://glaze.app/privacy).

## More Questions

For anything about your team, contact [teams@glaze.app](mailto:teams@glaze.app). For privacy and data protection questions, contact [privacy@glaze.app](mailto:privacy@glaze.app), and for security questions, [security@glaze.app](mailto:security@glaze.app). You can also find Glaze's full contractual terms on our website:

- [Terms of Service](https://glaze.app/terms)
- [Privacy Policy](https://glaze.app/privacy)
- [Acceptable Use Policy](https://glaze.app/aup)