Privacy Policy

Me in a Meme · Effective August 17, 2026

Me in a Meme creates face-swapped meme images using an on-device model. This policy explains what information the app handles and the choices available to you.

Face data and on-device processing

Me in a Meme handles photographs selected by the user; cropped face images; detected face locations and facial landmarks; face orientation and image-quality measurements; numerical face embeddings; target-face geometry in meme images; and generated face-swapped images. This information is used only to let the user select and crop faces, align a selected face with a meme template, generate and preview a face-swapped image, and save or share an image at the user's direction. It is not used to identify or authenticate a person, build a user profile, train machine-learning models, advertise, or track users.

All facial analysis and face-swap generation occur on the user's device. Face photos, facial-analysis data, embeddings, imported images, and generated images are not uploaded to Ash Apps, Superwall, Imgflip, Memegen.link, or another third party. If the user expressly chooses Save or Share, the generated image is delivered to the Photos library or recipient or service selected by the user and is then governed by the user's settings and that destination's privacy practices.

Face data storage, retention, and deletion

The original photograph selected as a face source is held temporarily during import and is not copied into the app's permanent storage. For each face the user chooses to keep, the app stores a cropped face image, a local random identifier, a user-provided name, a face bounding box, and orientation or quality measurements in the app's local container. This information remains until the user deletes that face from the Face Library or deletes the app.

Facial landmarks, numerical embeddings, and other intermediate model outputs are retained only in temporary memory or caches and are discarded when caches are cleared, memory pressure occurs, or the app terminates. Imported custom meme images and generated images in the app remain locally until the app is deleted. Temporary preview caches may be removed or replaced automatically. Images saved to Photos remain there until the user deletes them from Photos. Because Ash Apps does not receive or store face data on a server, Ash Apps has no remote copy to delete.

The app stores on-device performance samples, including generation duration, device and operating-system information, template information, and a local face identifier. These samples do not contain face photos, facial landmarks, or face embeddings, remain inside the app's local container, are limited to the most recent 5,000 samples, and can be removed from Settings or by deleting the app.

Meme catalog and search

The app fetches meme template indexes and images directly over HTTPS from Imgflip and Memegen.link. These services receive standard network information, such as your IP address and the requested resource, when those requests are made. Ash Apps does not receive those requests. The app does not send face data, search text, or its Superwall identifier to these catalog services.

Meme searches are performed on your device using the downloaded catalog indexes. The app does not transmit your search text to Imgflip, Memegen.link, or an Ash Apps search server. It may download a selected template image from the service that supplied it.

Subscription, paywall, and product analytics data

Me in a Meme uses Superwall to display paywalls, determine subscription access, process and restore App Store subscriptions, and understand how people move through the app before and after a paywall. Superwall may receive an anonymous app-user identifier, a device vendor identifier, device and app properties, install and session information, paywall interactions, approximate region derived from an IP address, purchase or subscription status and history, and coarse product-interaction events. Product-interaction events are associated with the anonymous app-user record so a funnel can be measured across a session. Those events include starting or completing a face import, displaying a custom-face swap, completing a custom meme import, saving a result to Photos, and completing a share. They may include a coarse source label, the number of faces added, and the current free-swap count.

Purchase and subscription history is associated with that anonymous app-user record so subscription access can be provided and restored; it is not used to identify you by name or email address.

The app does not provide Superwall with a user's name or email address and does not send face photos, facial-analysis data, face identifiers, template identifiers, search text, file names, imported meme images, generated images, user-provided face names, or the destination selected in the system share sheet to Superwall. This information is used for app functionality and analytics, not advertising or cross-app tracking. Superwall's handling of this information is described in its Privacy Policy.

Ash Apps retains subscription, paywall, and product-interaction information available through Superwall only as long as reasonably necessary to provide subscription functionality, understand product and paywall performance, meet legal or accounting obligations, or resolve support and fraud issues. Deleting the app removes the identifiers and subscription information stored locally but does not automatically delete information already received by Superwall. To request deletion of information that Ash Apps controls through Superwall, contact aaron@ashapps.com. Ash Apps will work with Superwall to locate and delete an applicable anonymous record when reasonably possible and when retention is not legally required.

Analytics and crash reporting

Me in a Meme uses Google Firebase Analytics to measure aggregate app usage and conversion funnels and Firebase Crashlytics to diagnose crashes and improve app reliability. Firebase Analytics receives app launches, sessions, screen views, coarse product interactions, paywall interactions forwarded from Superwall, purchase outcomes, subscription status, device and app properties, and a random per-install app-instance identifier. The app does not set a Firebase user ID. Crashlytics receives crash data and other diagnostic data for app functionality.

Firebase data are used for analytics and app functionality, not advertising or cross-app tracking. The app uses the Firebase Analytics package without advertising-identifier support and disables vendor-identifier collection, ad personalization signals, ad-network registration, and on-device advertising conversion event data. The app does not send face photos, facial-analysis data, embeddings, imported or generated images, file names, user-provided face names, face identifiers, search text, template identifiers, or user IDs to Firebase, and it does not attach custom keys or custom logs to crash reports. Google's handling of these data is described in Firebase Privacy and Security.

The app does not display third-party advertising, include an advertising SDK, or request App Tracking Transparency permission.

Privacy-preserving advertising attribution

Me in a Meme uses Apple's AdAttributionKit and SKAdNetwork system APIs to measure advertising results without identifying or tracking an individual across apps or websites. When the app is opened or a user reaches a coarse conversion stage—such as displaying a first custom-face swap, opening a paywall, starting a trial, or starting a subscription—the app may update an on-device conversion value. Apple may send a delayed, signed, privacy-preserving postback containing limited installation, campaign, and conversion-value information to the registered advertising network whose ad resulted in the installation or reengagement. The amount of detail is controlled by Apple's privacy thresholds.

Sharing

Ash Apps does not sell personal information or face data. The app communicates directly with Imgflip and Memegen.link to load meme catalogs and selected template images, with Superwall for the subscription, paywall, and product analytics purposes described above, and with Google Firebase Analytics and Crashlytics for usage, conversion, crash, and diagnostic reporting. Ash Apps requires service providers that receive user data to use it only for the disclosed purposes and to provide the same or equivalent protection described in this policy. Their handling of information is also governed by their own terms and privacy practices.

Security

Network requests use HTTPS. Face photos and generated face-swap data are processed locally and are not uploaded by the app except when the user expressly chooses a system Save or Share action. No method of storage or transmission can be guaranteed to be completely secure.

Children's privacy

The app is not directed to children under the minimum age required to consent to data processing in their country or region. Questions about children's privacy may be sent to aaron@ashapps.com.

Changes to this policy

This policy may be updated when the app's data practices change. The effective date above will be updated when a revised policy is published.

Contact

For privacy questions, email aaron@ashapps.com.