Privacy Policy

Effective August 23, 2026

Mirage is developed by Ethan Lipnik 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

Mirage 1.3.0 and later use the current services described in the Mirage 1.3.0 and Later section. Earlier releases continue to use the legacy services described in the Versions Before 1.3.0 section while they remain installed. The rest of this policy applies to every version unless a version-specific section says otherwise.

Mirage 1.3.0 and Later

Mirage 1.3.0 and later use Echo for private support tickets, diagnostics, first-party usage analytics, notifications, referrals, and Apple-signed purchase-history reporting. Echo runs on Cloudflare-hosted infrastructure. RevenueCat continues to evaluate 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.

Information Stored in iCloud

If you use iCloud features, Mirage stores device names and identifiers, trust information, and basic hardware details in your private iCloud account. This allows your devices to find and trust each other.

Purchases and Subscriptions

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

Mirage receives purchase information from Apple, such as the product purchased, purchase and expiration dates, subscription status, offers, and refunds. RevenueCat evaluates subscription access and offering metadata. Echo also receives Apple-signed purchase history for operational reporting and future entitlement recovery.

RevenueCat and Echo purchase identifiers are stored on your device to keep access and rewards consistent. They are separate from your support tickets and analytics identifier.

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.

Mirage does not receive your Apple Account name, email address, or password from Apple. 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. Mirage stores a secure key on your device so only someone with that key can open the ticket. Authorized Echo 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 off until you enable it 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 device model, operating system, app version, subscription status, a random installation identifier, and a one-way identifier used to recognize related activity across your Mirage devices. These identifiers are pseudonymous, so Mirage does not describe this mode as anonymous.

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

You can choose None, Crashes Only, or Errors in Settings. Mirage defaults to Errors. Reports may include the app and operating-system version, device model, crash details, recent technical activity, and other information needed to diagnose a problem.

Choosing None stops automatic diagnostic uploads. Mirage may still 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 only 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.0 and later use Apple for iCloud, App Store purchases, and notifications; RevenueCat for subscription entitlement and offering management; and Echo for support, diagnostics, analytics, referrals, and Apple-signed purchase-history reporting. Cloudflare provides Echo Cloud's service compute, routing, queues, and object storage. PlanetScale initially hosts Echo Cloud's managed PostgreSQL data. WorkOS authenticates authorized support team members; it does not authenticate Mirage customers and does not receive ticket access keys. 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 collect your location.

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. 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 turn analytics and diagnostics on or off, manage notifications, delete support tickets, remove Mirage's local data, manage iCloud 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 [email protected]. 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, RevenueCat, Cloudflare, PlanetScale, and WorkOS may process information outside your country. Sentry and PostHog may also 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 Ethan Lipnik under the FauxFox name. If you have questions about this policy, open Mirage and submit a private ticket from My Support Tickets, or email [email protected]. See Mirage Support for instructions.