Privacy Policy

Effective October 20, 2026

Mirage is developed by Faux Fox, Inc. in the United States. This policy explains what information Mirage handles, why it is needed, and the choices available to you.

Which Version of Mirage This Policy Covers

This policy covers Mirage, its website, and account services. The Mirage 2.0 section also applies to beta builds with these features and takes precedence over the older-version descriptions below. Features and service providers depend on the version you use.

Mirage 2.0 and Account Services

Accounts and Sign-In

Mirage uses WorkOS to authenticate customer accounts. We receive your email address, name when provided, and sign-in identifier. WorkOS also receives your IP address and browser information during sign-in. If you use Sign in with Apple, Apple may provide your name and a private relay email address; Mirage does not receive your Apple password.

We store account identifiers, device names, platforms, installation identifiers, public authentication keys, session activity and expiry, and security records to manage access and prevent abuse. Device credentials are stored securely on your device. Nearby and saved private-network connections remain available without a Mirage account; managed connections away from home require sign-in.

Website Sessions

The website uses essential cookies for sign-in, sessions, and request protection, and local storage for your language preference. You may approve website sign-in in the Mirage app or use browser sign-in. App approval expires after five minutes and creates a separate browser session without sharing the app's credentials. Hosting and authentication providers process connection information needed to serve and secure requests. Some public pages load fonts from Google, which receives your IP address and browser request information.

Remote Connections and Connected Apps

Mirage 2.0 streams and connected-app service content are encrypted between authorized devices. A saved address is a connection route, not permission to access a device.

Our connection directory stores encrypted discovery records and opaque identifiers, revisions, and expiry times so your devices can find each other. Account services associate directory access with your account and device. These services do not relay your screen, audio, files, or other session content.

When you authorize a connected app, Mirage processes its publisher, app and installation identifiers, public keys, approved permissions, and activation and revocation records. Our services use your account and purchase entitlement to enforce access and plan limits. The app receives a publisher-specific identifier and authorized access; content you share with it is also subject to its developer's privacy policy. You can revoke connected-app access in the account portal.

Files, Terminal, Workspaces, and AI

Features you use may access files, terminal commands and output, clipboard history, workspace details, and task conversations on your devices. Workspace and task records can be replicated to authorized devices and cached for offline use. Transferring task execution can transfer workspace changes and required portable credentials to the destination device. Disconnecting or signing out does not erase copies already stored on devices.

AI features send prompts, selected context, tool results, and attachments to the model provider you choose. On-device models process requests on the execution device; a configured remote model endpoint receives those requests. If you connect ChatGPT, OpenAI processes that content under its own terms and privacy policy. Peer-to-peer streaming does not prevent content you deliberately send to an AI provider or connected app from reaching that provider.

Glance Beta Cloud Intelligence

When you enable Use Cloud Intelligence, Mirage sends requests and relevant context for your queries, proactive widget updates, agent coordination, and computer-use tasks through Mirage's authenticated services and OpenRouter to Claude Haiku 5.5. Context can include task conversations, retrieved emails and file contents, calendar information, memories, canvas and widget state, selected text, interaction details, and screenshots or image attachments available to the feature. The configured route uses Google Vertex to serve Anthropic's model. Enabled proactive features may make requests without a new message from you. Cloud processing is separate from optional training-data collection; leaving Improve Glance off does not prevent the cloud processing needed for features you enable.

Optional Improve Glance Collection

Improve Glance is off by default. If you enable it, we collect raw inputs and outputs from covered beta model calls, including supplied context and images, candidate actions, model and provider identifiers, configuration, validation results, recorded action outcomes, and thumbs-up or thumbs-down feedback. These records are linked to your Mirage account and device and stored in our database. They can contain personal or sensitive information about you and other people. We do not anonymize or redact this information before collecting it.

We use these records to investigate failures, evaluate models, replay scenarios, and develop training datasets. Training use depends on the applicable model-provider terms; collection does not mean every provider's responses are eligible for training. Later redaction or filtering does not make the initial collection anonymous. Access is limited to authorized personnel and service providers supporting these purposes.

You may turn off Improve Glance to stop new collection without turning off Cloud Intelligence. You can separately choose Delete Collected Training Data to remove your collected records and ratings from our live database and disable collection. If your device is offline, the deletion request remains pending until it can reach our service. Turning off Cloud Intelligence stops new beta cloud model requests on that device. Our scheduled cleanup removes raw collection episodes older than 90 days together with their associated model calls, outcomes, and ratings; account deletion also removes them. Backup copies may remain for a limited period. Requests already transmitted may finish processing under the provider's policies.

We configure the beta route to require endpoints identified by OpenRouter as not collecting data for training and supporting zero data retention. These controls do not replace the providers' terms, exceptions, or your separate consent to Mirage's own collection. Other optional AI integrations, including Anthropic and OpenAI, have their own processing, retention, and training policies and settings. Your Improve Glance choice does not change those providers' settings.

Analytics in Current Builds

Usage Analytics is on by default and can be turned off at any time in Settings. When enabled, Mirage uses a pseudonymous installation identifier to measure active users, app and platform versions, paid or free status, sessions, and feature usage. Analytics does not use your account or support-ticket identity.

Privacy-filtered crash and error reports are always sent to operate and improve Mirage. They can include app, operating-system, and device details plus recent technical activity, but exclude screen contents, input, and account identity. Feature flags continue after analytics opt-out using only minimum operational app, device, distribution, and subscription-status details evaluated on your device.

In current builds, diagnostics attached to a support ticket are uploaded as a separate ticket-specific snapshot, without connecting the ticket to your earlier analytics or diagnostic history.

Account Retention and Deletion

We keep account and device records while needed to provide access. Native sessions expire after 90 days without a successful renewal. Expired sign-in requests are periodically removed; revoked browser sessions are eligible for cleanup after 30 days. Security, deletion, connected-app, and purchase records may remain as needed for their operational or legal purposes.

You can manage devices and browser sessions in the Faux Fox account portal, and sign out or delete your Mirage account in the app. Deletion removes Mirage sign-in identities, device records, connection permissions, and product links, clears your name and email from the Mirage account, and revokes sessions. Limited deletion and security records remain. This does not automatically delete the upstream WorkOS identity, a separate Cove account, support tickets, purchase records, connected-app records, or data already on your devices. Contact us for access, correction, export, or deletion requests covering those records. Account deletion does not cancel Apple subscriptions.

Account deletion does not cancel Apple or Stripe subscriptions. Cancel Stripe subscriptions in the billing portal before deleting your account.

Mirage 1.3.x

Mirage 1.3.x uses Cove for private support tickets, diagnostics, first-party usage analytics, notifications, referrals, and Apple-signed purchase-history reporting. Cove runs on Cloudflare-hosted infrastructure. RevenueCat evaluates subscription entitlement and offering metadata. Usage Analytics is off until you enable it in Settings, and diagnostics default to Errors.

Versions Before 1.3.0

Earlier Mirage releases continue to use Sentry for crash and error reporting and PostHog for analytics and configuration. Those releases may send the pseudonymous identifiers and technical context described in the version of this policy that shipped with them. PostHog analytics in those releases may be enabled by default, including in TestFlight. RevenueCat continues to process subscription entitlement and offering data for those releases.

Your Streams Stay Between Your Devices

Video, audio, clipboard content, and input are sent directly between your devices. Mirage does not route your stream through its servers and does not record or store your screen content.

Connections made through a saved address are encrypted. Some free local sessions may send media without encryption; Mirage Pro includes controls for encrypting local sessions.

Purchases and Subscriptions

Apple handles App Store purchases, billing, cancellations, and refunds. Mirage does not receive your payment-card details or Apple Account password.

For the direct Mac version, Stripe processes Mirage Pro payments and billing. Stripe receives the payment details you enter; Mirage and Cove receive customer and purchase identifiers, billing status, and purchase, refund, and subscription dates to provide account access. Mirage does not receive your full payment-card details.

Mirage receives purchase information from Apple, such as the product purchased, purchase and expiration dates, subscription status, offers, and refunds.

Legacy RevenueCat purchase identifiers may remain on your device only to migrate existing access or rewards. Current builds use Cove purchase identifiers, which are separate from support-ticket access keys and usage analytics. Current builds may associate purchase identity with your Mirage account as described above.

Referrals

If you use referrals, Mirage processes the referral code, claim and reward status, available credits, and related purchase or refund information. Your App Store purchase history is checked to determine eligibility and to restore rewards across your devices.

App Store referral checks do not provide your Apple Account name, email address, or password. Referral codes and pending rewards are stored securely, and your referral history shows only part of a code.

Support

When you contact support in Mirage 1.3.0 or later, Mirage collects what you submit, including your ticket title, description, and attachments. A ticket also includes app and device details and a short history of recent technical activity to help explain what happened. This technical history does not include screen images, typed text, clipboard content, passwords, or payment details.

Attach Logs is selected by default and can be turned off before sending a ticket. Logs and attachments may contain information about your device, settings, connections, and connected Mirage hosts. Please do not submit passwords, payment information, private documents, or unrelated personal information.

Support tickets are private and do not require an account or email address. In Mirage 2.0, submitting while signed in links the ticket and any logs or attachments you include to your Mirage account, so authorized support staff can assist with account access and entitlements. Tickets submitted while signed out remain separate from your account. This link does not link your account to general Usage Analytics or automatic crash and error reports.

Mirage stores a secure ticket key on your device. For account-linked tickets, signing in can restore fresh ticket keys on your other devices. Authorized Cove team members can access tickets and attachments to investigate problems. In-app support conversations are unavailable in Mirage 1.3.0; ticket submission and status remain available.

You can choose whether to receive notifications about a ticket status change or verified App Store update. You can turn these notifications off in Mirage. Deleting a ticket also removes its ticket notification registration.

When Mirage publishes a release that fixes a ticket, it deletes the ticket's logs, attachments, diagnostic details, device information, and notification records. The ticket's minimized resolution and release history remain so you can track the outcome.

Analytics

Usage Analytics is on by default and can be turned off at any time in Settings. When enabled, Mirage collects information about how the app is used, such as launches, onboarding progress, button taps, connection results, streaming outcomes, and session length. This may include your pseudonymous installation identifier, device model, operating system, app version, and paid or free subscription status.

Analytics does not include your screen content, typed text, clipboard content, passwords, or payment details. Mirage does not record your screen or your interactions with other apps.

Crash and Error Reports

Mirage always sends privacy-filtered crash and non-fatal error reports. Reports may include the app and operating-system version, device model, crash details, recent technical activity, and other information needed to diagnose a problem. They exclude screen contents, input, and account identity.

Mirage may also keep a limited local history that is included only if you later choose to attach logs to a support ticket.

How We Use and Share Information

We use information for the optional evaluation and model-development purposes described above and to operate Mirage, provide support, manage purchases and referrals, improve reliability, understand product usage, prevent abuse, and meet legal or accounting obligations.

Mirage 1.3.x used Apple for App Store purchases and notifications, RevenueCat for subscription entitlement and offering management, and Cove for support, diagnostics, analytics, referrals, and Apple-signed purchase-history reporting. Current Mirage builds use Cove for subscription entitlement and offering management, along with support, diagnostics, analytics, referrals, and Apple-signed purchase-history reporting. Cloudflare provides Cove Cloud's service compute, routing, queues, and object storage. PlanetScale initially hosts Cove Cloud's managed PostgreSQL data. WorkOS authenticates authorized support team members and, separately, Mirage customers. It does not receive ticket access keys. Cloudflare and PlanetScale also host Mirage account and connected-app services. AI providers receive content when you use their features, as described above. Earlier releases also use Sentry and PostHog as described above. We require service providers processing Mirage data for us to protect it consistently with this policy and applicable platform requirements. Authorized support team members can access information only when needed for these purposes.

We do not sell personal information, use advertising SDKs, or share information for advertising or cross-app tracking. We do not request precise device location. Service providers receive IP addresses when handling network requests.

How Long We Keep Information

Summary statistics that no longer identify an installation may be kept longer. Purchase, financial, fraud-prevention, and referral records may also be kept as needed for accounting, tax, security, disputes, or legal obligations. Backups may remain for a limited time after information is deleted from the live service.

Settings, caches, secure keys, and pending uploads may remain on your device until they expire or are removed. Legacy RevenueCat purchase identifiers may remain only to migrate existing access or rewards. Deleting Mirage clears its app data, but some secure purchase or reward information may remain so it can be recovered after reinstallation.

Your Choices and Rights

You can control Use Cloud Intelligence and Improve Glance separately, request deletion of collected Glance data, turn Usage Analytics on or off, manage notifications, delete support tickets, remove Mirage's local data, and manage subscriptions through Apple. Referral participation is optional.

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a copy of your personal information, or to object to or withdraw consent for certain uses. EU and UK users may also complain to their local data protection authority.

To make a privacy request, open Mirage, go to My Support Tickets, and submit a private ticket stating that it is a privacy request, or email ethan@fauxfox.io. See Mirage Support for instructions.

Legal Bases for EU and UK Users

Where EU or UK law applies, we process information as needed to provide Mirage, purchases, support, and requested rewards; for legitimate interests such as security, product improvement, support, fraud prevention, and accounting; with consent where required; and to meet legal obligations.

International Transfers

Mirage is operated from the United States. Apple, Cove, Cloudflare, PlanetScale, WorkOS, Google, and any AI provider you use may process information outside your country. RevenueCat may process information from earlier Mirage releases, and Sentry and PostHog may process information from versions before 1.3.0. Where required, we rely on the safeguards provided by those companies for international transfers.

Third-Party Services

Children's Privacy

Mirage is not directed at children under the age of 13. We do not knowingly collect information from children.

Changes to This Policy

We may update this privacy policy from time to time. Material changes will be announced through the app or this page before they apply where required.

Contact

Mirage is offered by Faux Fox, Inc. If you have questions about this policy, open Mirage and submit a private ticket from My Support Tickets, or email ethan@fauxfox.io. See Mirage Support for instructions.