Skip to content

Privacy Policy

Effective date: April 27, 2026

Mouse is a mobile command center for cloud coding agents. This Privacy Policy explains what we collect when you use the Mouse website, mobile app, relay, waitlist, hosted agent features, and connected integrations.

For privacy questions or deletion requests, email hello@mouse.app.

1. Information we collect

Account information. When you sign in, we collect account identifiers from Apple, Google, or another supported authentication provider, such as your user ID, email address, and display name when the provider makes them available.

Waitlist and support information. If you join the waitlist, request support, report a bug, or send feedback, we collect the contact information and message content you provide.

Device and notification information. We collect device identifiers needed to keep you signed in and Expo, Apple, or Google push tokens so Mouse can notify you when an agent needs attention, finishes a run, opens a pull request, or hits an error.

Provider credentials. If you connect providers such as Cursor, Anthropic, OpenAI, OpenRouter, or similar services, we store the credentials you choose to provide so the relay can make requests on your behalf. Provider credentials are encrypted at rest and are not logged in plaintext.

GitHub information. If you install the Mouse GitHub App or connect a repository, we receive the repository metadata, installation metadata, branch names, commit and pull request events, webhook payloads, and file paths needed to show agent work, plan handoffs, and code review context. We only request the access needed for the product features you enable.

Agent and workspace content. Mouse stores thread titles, prompts, messages, normalized agent events, tool events, permission requests, diffs, generated artifacts, transcripts, and related metadata so the app can show a durable history across your devices.

Hosted usage and billing data. If you use Mouse-hosted runs or paid features, we collect usage records, spend limits, subscription state, invoice and checkout identifiers, and billing events from Stripe. We do not store full payment card numbers.

Technical and diagnostic data. We collect logs, device and app version information, request metadata, crash reports, error traces, performance data, and abuse-prevention signals to operate and secure Mouse.

2. How we use information

We use information to:

  • provide the app, website, relay, push notifications, waitlist, support, hosted runs, and billing features;
  • authenticate users and keep sessions secure;
  • route prompts and follow-up messages to the providers and repositories you connect;
  • sync agent status, transcripts, diffs, plan artifacts, and approval requests across devices;
  • enforce usage limits, spend caps, fraud controls, rate limits, and acceptable use rules;
  • debug issues, monitor reliability, improve performance, and develop product features;
  • communicate with you about access, support, security, billing, and important service updates;
  • comply with law and protect Mouse, users, providers, and the public.

We do not sell personal data. We do not use your prompts, repository content, transcripts, or provider credentials for advertising.

3. Third-party services

Mouse works by connecting services you choose. When you connect a third-party provider, your use of that provider remains subject to its own terms and privacy policy. Examples include:

  • Cursor and other cloud coding agent providers;
  • Anthropic, OpenAI, OpenRouter, and other model providers;
  • GitHub for repositories, pull requests, webhooks, and app installation flows;
  • Apple, Google, Expo, and EAS services for authentication, builds, and push delivery;
  • Stripe for subscriptions, invoices, checkout, customer portal, and metered billing;
  • infrastructure, database, storage, logging, email, analytics, and error-reporting vendors used to operate Mouse.

If you bring your own provider key, requests routed to that provider may include prompts, repository context, tool results, diffs, and other content needed to complete the task you asked Mouse to run.

4. Security

Mouse uses technical and organizational safeguards designed to protect user data, including encrypted transport, encrypted provider credentials at rest, restricted secret handling, webhook signature verification, and access controls for operational systems.

No online service can guarantee absolute security. You are responsible for protecting your devices, accounts, repository permissions, and provider keys. If you believe your Mouse account or a connected provider key has been compromised, contact us at hello@mouse.app and rotate the affected credentials.

5. Retention and deletion

We keep information for as long as needed to provide Mouse, maintain security, comply with legal and tax obligations, resolve disputes, and enforce agreements.

You can revoke provider keys, uninstall the GitHub App, delete threads where the app offers that control, or contact us to request account deletion. Some records may remain for a limited time in backups, audit logs, billing records, security logs, or legally required records. Aggregated or de-identified data may be retained when it no longer identifies you.

6. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, or restrict the use of your personal information. You may also have the right to object to certain processing or appeal a privacy decision.

To make a request, email hello@mouse.app. We may need to verify your identity before fulfilling a request.

You can also:

  • disable push notifications in your device settings;
  • revoke Apple, Google, GitHub, Cursor, Anthropic, OpenAI, OpenRouter, or other provider access in those services;
  • rotate or delete provider keys in Mouse settings where available;
  • leave the waitlist by asking us to remove your email.

7. International use

Mouse may process information in the United States and other countries where we or our service providers operate. Those countries may have data protection laws different from where you live. When required, we use appropriate safeguards for cross-border transfers.

8. Children

Mouse is built for developers and is not directed to children under 13. If you believe a child has provided personal information to Mouse, contact us and we will take appropriate steps to delete it.

9. Changes to this policy

We may update this Privacy Policy as Mouse changes. If changes are material, we will provide reasonable notice through the website, app, email, or another appropriate channel. The updated policy will show the effective date above.