Privacy Policy

Effective: October 8, 2026 · Last updated: October 8, 2026

At a glance: Mogshot (formerly Bimax) lets you put a selected person or animal face onto a live camera view, animate its mouth with your expressions, and take snapshots. Face detection, alignment, mouth animation, and rendering run on your device, without sending images to a cloud face-swap service. The app also uses online purchase, analytics, and advertising services. In particular, TikTok's remotely controlled diagnostics can include screen images, as explained below; on-device face processing is not a promise that all app data stays on your device. No account is required.

This policy describes the live face-swap version. If your installed version still offers muscle ratings, style advice, or generated after pictures, read Older versions and legacy data below: those features use different photo processing.

1. Who we are

Mogshot is operated by Massive Interface LLC, a Delaware limited liability company. We are responsible for the personal data we process to provide the service. Contact info@massiveinterface.com for privacy questions or requests.

2. Camera, photos, and face information

You can choose a source image using Apple's photo picker or take a photo with the camera. The picker gives the app the image you select, rather than access to browse your entire library. Apple may retrieve an iCloud-stored image according to your Photos settings. The live effect uses the front camera after you grant camera access. It does not record microphone audio or create a video recording.

The app uses Apple's on-device Vision and Core ML frameworks and bundled face-detection models to locate facial features, including eyes, lips, and face contours. You can also align a source face manually, including an animal face. Temporary facial coordinates and mouth movement measurements position and animate the selected face; the app does not use them to recognize your identity, authenticate you, or create a face-recognition profile.

The face-swap pipeline holds source images, camera frames, facial coordinates, and rendered snapshots in app memory. It does not upload them to our photo-processing server, Google Gemini, or a remote face-swap model, and it does not create a saved photo or face-geometry history inside the app. The camera session stops when you leave the live view, open a snapshot, or the app becomes inactive. A source image may remain available in memory while you adjust or reuse it. This describes face-swap processing; see section 5 for separate SDK diagnostics.

3. Snapshots, saving, and sharing

Taking a snapshot creates an image in the app; it does not automatically publish it or save it to your Photos library. “Save or share” opens the iOS share sheet with the rendered image. If you choose Save Image or a sharing destination, iOS or the selected app receives the image to complete that action. Saved or shared images may contain identifiable faces and the camera background. Your Photos/iCloud settings and the destination's policies govern their subsequent storage, backup, and use. Removing a source photo in Mogshot does not delete your original photo or copies saved elsewhere.

4. Identifiers, purchases, and local preferences

  • Persistent identifier. The app stores a pseudonymous identifier in the iOS Keychain, initially based on Apple's identifier for vendor when available, or a generated UUID. It is sent to Firebase Analytics as a user ID and to RevenueCat as an app user ID. It can persist after uninstalling and is not an anonymous session identifier.
  • Purchases. Apple handles payments. RevenueCat processes your app user ID, transaction and product identifiers, purchase history, subscription or lifetime entitlement status, and restoration information so we can verify access and support purchases. We do not receive payment-card details. The face-swap version offers annual and lifetime access where available; the purchase screen states the actual price, billing period, and any eligible trial.
  • Campaigns and preferences. The app remembers onboarding completion and a campaign identifier from a campaign link in local preferences. That campaign identifier is also sent to Firebase Analytics and RevenueCat for attribution. Purchase SDKs maintain local caches used for access checks.
  • Support. If you contact us, we receive the message, contact details, and any attachments you choose to send. Please do not send sensitive photos or payment-card details unnecessarily.

5. Analytics, attribution, and SDK diagnostics

Google Firebase Analytics: we collect screen views and events such as source selection (camera or library), automatic or manual alignment, camera permission/status, starting and ending a swap, session duration, effect toggles, snapshot creation, and whether a share action completed or failed. Subscription status, campaign identifiers, app/device information, and SDK-generated usage or purchase events may also be processed. Our custom face-swap analytics events do not include image pixels, facial coordinates, or mouth measurements. Google processes analytics identifiers and technical information under its Firebase privacy information and Privacy Policy.

TikTok Business SDK: the app initializes this SDK for advertising measurement after the iOS tracking-permission check. The SDK can process installation, launch, return-use, and automatic purchase events, including product/transaction information, value and currency, plus app/device identifiers, IP/network information, and technical diagnostics. Depending on TikTok's remote configuration, enhanced measurement can include screen names, interface structure, button text, and taps. If remote debug mode is enabled, the SDK can attach screenshots of the displayed app screen to events; those screenshots could include a selected face, camera image, or snapshot visible at that time. These are SDK diagnostic capabilities, separate from local face-swap rendering. See TikTok's Privacy Policy.

Access to Apple's advertising identifier depends on your App Tracking Transparency permission. Denying tracking permission does not disable all analytics or non-IDFA SDK events, and does not prevent using paid face swapping. The app does not currently provide a separate in-app switch to turn off all analytics or SDK diagnostics.

6. Purposes and recipients

We process information to provide the effects you request, verify and restore paid access, understand app usage, measure advertising, diagnose problems, secure the service, respond to support requests, and meet legal obligations. Where applicable, our legal bases include providing the service you request, legitimate interests in operating and protecting it, consent where required, and legal obligations.

Recipients include Apple (distribution, system photo/sharing services, and payments), RevenueCat (purchase and entitlement management), Google Firebase Analytics (usage measurement), and TikTok (attribution and SDK diagnostics). Render hosts this website and may process ordinary web request information, such as IP addresses and requested URLs. These Mogshot legal pages do not load analytics scripts or set analytics cookies; other pages on massiveinterface.com may use Google Analytics and cookies.

Images you deliberately share go to your selected destination. We may also disclose information where required by law, to protect rights and security, or as part of a business transfer. On-device face processing does not require a Google Gemini request or an Amazon Web Services image upload; older versions are described next.

7. Older versions and legacy data

Earlier Mogshot versions send a submitted photo and selected tone or instructions through our Render-hosted API to Google Gemini for muscle ratings, style recommendations, or generated after pictures. The newer rating/plan endpoints process images in memory without saving a photo or feedback record, while retaining aggregate usage counts and operational logs. Google's own content processing and retention are governed by the applicable Gemini API terms, including safety and abuse-monitoring provisions. On-device face-swap processing does not apply to those requests.

Older Bimax upload/evaluation features used Amazon Web Services image storage and stored evaluation records. Prior uploads, analytics (including numeric scores or earlier onboarding attributes), purchase records, and old local app data are not automatically deleted by this product change. The face-swap version stops sending new muscle ratings and clears the retired onboarding properties it previously set in Firebase; that does not erase historical analytics. Contact us about legacy records or deletion.

8. Retention and your choices

The face-swap app does not keep an in-app image history. In-memory images and face data are temporary and are released as app state is replaced or the app process ends; we do not promise immediate secure erasure of device memory. Originals and any images you save or share remain in Photos, backups, or the chosen destination until removed there. Onboarding preferences and SDK caches remain in app storage, and the Keychain identifier can survive uninstalling.

Purchase, analytics, attribution, diagnostic, support, and legacy service records are retained according to their purposes, provider settings, and applicable legal obligations. They are separate from temporary face-swap image processing; there is no single automatic deletion period for all of them.

Manage camera, photo-library, and tracking permissions in iOS Settings. Live face swapping requires camera permission. You can clear the selected source using “Choose a different photo,” decline to save or share a snapshot, and manage saved copies in Photos or the service where you shared them. Uninstalling does not automatically delete provider, server, or Keychain records, and does not cancel an Apple subscription.

9. Privacy rights and requests

Email info@massiveinterface.com to request access, correction, deletion, or information about your data. We may need information to locate the relevant record and verify your request. We cannot delete copies held only on your device or by a recipient you chose; manage those copies through the relevant device or service.

Depending on where you live and which laws apply, you may have rights to access, correct, delete, restrict, object to processing, obtain a portable copy, withdraw consent, or opt out of sale or sharing for targeted advertising. Advertising measurement may constitute sharing under applicable privacy laws. Use iOS tracking controls and contact us to exercise applicable rights. We do not discriminate for exercising privacy rights. EU/UK residents may also complain to their local data-protection authority.

10. Security and international processing

Network services use HTTPS and access controls to protect information, but no system is completely secure. Our infrastructure and providers may process information in the United States and other countries. Where required, applicable data-transfer safeguards govern those transfers.

11. Adults only

Mogshot is intended for adults 18 and older. Do not use images of anyone under 18. Use another adult's likeness only with their permission, including permission for any sharing. If you believe a child has provided personal information, contact us so we can investigate and address it.

12. Changes and contact

We will post updates here with a revised date and provide additional notice when required by applicable law. Contact Massive Interface LLC at info@massiveinterface.com.