Privacy policy

Last updated: 12 September 2026

1. Who we are and how to contact us

Muster is an AI-agent workforce platform built by Tharun Ramagiri at Orazen. This policy explains how Muster handles information on https://muster.today and https://muster.orazen.online, and how local or self-hosted installations differ. For privacy questions, access requests or deletion requests, contact ramagiritharun@gmail.com.

When you connect to someone else's self-hosted Muster server, that server's operator manages the data stored there. Contact that operator about its retention, hosting and security practices.

2. Information we collect

• Account information. Accounts store your name, email address, authentication records and sessions. Google sign-in supplies a Google account identifier, email address, name and profile picture. OAuth access and refresh tokens are stored to support authorized Google features without asking you to sign in on every request.
• Workspace content. We process the agents you configure, tasks, conversations, uploaded files, notes, memories, settings and integration credentials you provide. The connected Muster server stores workspace records and may keep model request and response logs.
• Google Drive data. The workspace-backup feature uploads an encrypted workspace bundle to Muster's private Google Drive app-data folder and reads it when you request restoration. That feature uses the drive.appdata scope, not access to your general Drive files. Separately configured integrations, such as Vault Drive backup, can read other Drive files if you provide credentials with those permissions.
• Technical data. Server request and diagnostic logs, connection information and feature-usage events help operate and troubleshoot the Service. Authentication uses session cookies; local application storage also keeps preferences and drafts.
• Billing information. Where you purchase a paid service, payment providers process payment details. Muster may receive customer, subscription and transaction identifiers and payment status, rather than your full card number.

3. How we use information

• Authenticate users and maintain accounts and sessions.
• Run the tasks and integrations you request, generate agent responses and display workspace history.
• Back up and restore supported workspace data when you invoke those features.
• Operate, troubleshoot and secure the Service, manage billing where applicable, and respond to requests.

We do not sell personal information or Google user data. We do not use Google user data for advertising or to train generalized AI or machine-learning models. Selecting an external AI provider can send task content to that provider, as described below.

4. Google user data and Limited Use

Muster's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

• Permissions and purpose. Google sign-in requests basic profile access and the Drive app-data permission for workspace backup. Requesting permission is not the same as running a backup. Workspace backup and restore are currently manual features for local installations, not automatic cloud-account synchronization.
• Scope of backup access. The workspace-backup integration accesses only its app-data folder. This restriction does not apply to other Drive integrations that you separately configure with broader permissions.
• Sharing. Google data is used for the user-facing features you authorize, not advertising, sale to data brokers or generalized model training. Transfers are limited to providing those features, permitted security purposes, legal obligations or other transfers allowed by Google's Limited Use requirements. Human access to Google data is limited to the circumstances permitted by that policy, such as your affirmative consent to review specific data or a security investigation.
• Revoking access. You can remove Muster's authorization in your Google account connections. Revocation prevents further authorized access; it does not automatically erase credentials or copies already stored by Muster. The workspace backup interface currently has no Drive-disconnect control. Request removal of stored account credentials from the operator and manage existing app-data backups separately in Google Drive.

5. AI model providers and local processing

Prompts and relevant context pass through the connected Muster server and are sent to the model endpoint you configure. Hosted providers process that content under their own policies. Review those policies before including sensitive information in a task. Connected tools may also send data to services you authorize.

A local model runs on the machine hosting its endpoint, which may not be your browser or phone. Using a local model does not prevent server-side logging or transfers through other enabled integrations. For a fully local workflow, both the Muster server and model endpoint must be local, with external integrations configured accordingly.

6. Sharing and service providers

Data may be processed by the hosting infrastructure supporting your deployment, the model and integration providers you select, and payment or email providers when those functions are used. We disclose data as necessary to provide the requested functions, protect the Service or comply with applicable law. Processing locations depend on the operator and providers involved and may be outside your country.

7. Retention and deletion

Account records, workspace content, credentials and diagnostic records can remain on the connected server until removed by its operator; the application does not currently enforce a single automatic expiry period for all of these records. Signing out does not erase them. Self-service account deletion is not currently available in Settings.

To request deletion of hosted account data, workspace content or stored Google credentials, contact ramagiritharun@gmail.com. We may need to verify account ownership and identify the affected deployment. Any legally required retention or limitations on the request must be considered separately. We do not promise that revoking Google access or deleting an individual agent also deletes all related logs, backups or account records.

For a local or independently hosted installation, its operator controls deletion of stored files and databases. Backups in your Google Drive are separate copies; removing server data does not remove those backups. Manage them separately through Google Drive.

8. Security

The public Muster websites use HTTPS. Local and self-hosted connections depend on the deployment and may use HTTP. Muster encrypts workspace backup bundles and hosted per-user provider-key vault entries. Other application records are stored in files and databases without uniform application-level encryption. Session and OAuth tokens are not uniformly hashed or encrypted in storage. Host access controls, disk encryption and backup protection depend on the operator. No system can guarantee absolute security.

9. Children

Muster is not intended for children under 16. Contact us if you believe a child has provided personal information so that we can investigate and address removal.

10. Your rights and choices

Depending on your jurisdiction, you may have rights to access, correct, erase or restrict processing of personal data, obtain a portable copy, object to processing, withdraw consent, or complain to a data-protection authority. Send requests to ramagiritharun@gmail.com. Applicable legal requirements govern how requests are handled.

Settings provides limited profile controls. Local workspace export is a partial backup of supported workspace records, not a complete personal-data or conversation export. For other access, correction, export or deletion requests, contact the operator rather than relying on Settings alone.

11. Changes to this policy

Updates will appear on this page with a revised date. Where required by law, material changes will be accompanied by additional notice or a request for consent. This policy does not limit your statutory privacy rights.