Privacy / clear boundaries

Your room stays yours.

Green Room runs locally. The public website stays out of your conversations, while your selected cloud model provider receives request content, your provider credential, and associated network metadata under its own terms.

Local rooms. User-owned keys. Direct provider requests. ● No Green Room relay. ●
Policy summary / effective September 14, 2026

The short version.

  • Green Room applicationsRooms, messages, character data, settings, and provider profiles are stored locally on your device.
  • Provider credentialsOn iPhone, provider credentials are stored in the iOS Keychain and are not stored in room data, SQLite, WebKit storage, logs, diagnostics, exports, or character packs.
  • Selected cloud providersWhen you send a message through a cloud provider, the app sends bounded conversation and character context directly to that provider over HTTPS. Green Room operates no model proxy or transcript relay.
  • Current iPhone distributionGreen Room iPhone Alpha 0.1.0 (2) is limited to the owner’s one-member internal TestFlight group. External TestFlight, a public invitation link, Beta App Review, and App Store publication have not been approved.
  • greenroomai.netThe static website has no app accounts, analytics, advertising, cookies, key entry, transcript ingestion, room storage, or model-request endpoint. Serving a page necessarily sends ordinary request metadata, such as an IP address and user agent, to the site’s hosting and delivery provider, which may process it under its own terms.
Model requests / your provider

Provider terms still apply.

Green Room supports a closed list of compatible providers. The app sends requests directly to the provider you select using a credential you obtained independently. The request may include your prompt, recent room context, selected character instructions, model choice, and generation settings needed to produce the reply.

Those cloud providers process and may retain data under their own terms, privacy policies, account settings, and routing choices. Retention can vary by provider and account. Using your own key does not by itself guarantee zero-data retention. Review your provider’s current policy and controls before sending sensitive information.

The desktop source application can use LM Studio on the same machine through a fixed loopback endpoint without a provider credential. A future optional private LM Studio path over the user’s Tailnet is roadmap work, not a feature of the current internal TestFlight build. It will require a separately reviewed network contract and TestFlight approval before iPhone distribution.

The Green Room project does not receive provider credentials, prompts, replies, rooms, transcripts, or model requests from the app.

Controls / local authority

You control local data.

Use the application’s local controls to remove saved provider credentials and delete local rooms or app data where those controls are available. On iPhone, a Keychain credential may remain after the app is uninstalled, so use the in-app credential-removal control first when you want explicit deletion.

Removing the application and its local data does not delete information a selected provider may have retained; provider-side access or deletion requests must be handled with that provider.

Because the project does not receive app room data or provider credentials, the website operator cannot retrieve, export, or delete them for you.

Scope / changes

What this covers.

This policy covers the Green Room applications and the static greenroomai.net website. It does not replace the privacy terms of model providers, Apple, GitHub, the site’s hosting and delivery provider, or other services you choose to use.

If the product adds accounts, analytics, a hosted relay, synchronization, invitations, or another project-operated data service, this policy must be updated before that feature is offered. Material changes will be posted here with a new effective date.

For privacy questions or sensitive reports, use the project repository to request an appropriate private contact channel without posting private information in a public issue.