Privacy Policy
This Privacy Policy explains how Meme Studio: Meme Maker (the “App”) accesses, uses, shares, and stores information when you use the App.
Summary: The App does not require an account and does not upload your selected photos, generated memes, or typed meme text to a server operated by the developer. The App uses Google Mobile Ads for banner advertising and may use Google Analytics for Firebase for product analytics when Firebase is configured for the release.
1. Information you choose to provide or access
The App may access images that you explicitly select through Android’s photo picker, document picker, or share sheet. The App accepts user-selected content:// image references so it can create a collage.
The App may read the selected image files while creating the preview and exported image. It does not request broad access to your entire photo library, and it does not collect names, contacts, microphone recordings, camera recordings, precise location, or payment information.
If you add text or adjust a layout, those editing choices are held in the App’s local editing session. The custom analytics events described below do not include the image contents, image URI values, or the text you type.
2. Local processing, export, and sharing
Photo composition, cropping, image positioning, text rendering, and export are performed on your Android device. When you export a meme, Android’s media storage may save the PNG in the device’s Pictures/MemeStudio folder. The saved file remains under your control through Android and your gallery or file-management apps.
When you share an exported image, the App passes the image to Android’s share sheet and the app you choose. The receiving app may copy, upload, or otherwise process the image under its own privacy policy. The developer does not receive a copy through this share action.
3. Firebase Analytics
When a release is connected to a Firebase project, the App uses Firebase Analytics to understand feature usage and improve the App. Firebase may automatically collect information such as an app-instance or installation identifier, app version, device model, operating system, language or locale, approximate region derived by Google, and app usage or diagnostic information. Firebase Analytics may also use identifiers and related data to measure sessions, engagement, and audiences. The precise data handled depends on Google’s SDK behavior, your device settings, and the Firebase project configuration.
The App sends the following custom events and limited parameters:
- App open and screen view events.
- Photos received from sharing, picked, or added, with only a photo count and, where applicable, a source label.
- Selected layout and canvas format.
- Text-layer added and removed actions.
- Photo-add action, export started/completed/failed, and share started.
These custom events do not contain your selected images, generated images, image URI values, photo filenames, typed text, or the identity of people shown in an image. Firebase processes analytics data under Google’s terms and privacy information. See Firebase Privacy and Security and Google Analytics for Firebase.
4. Google Mobile Ads (AdMob)
The App displays fixed-size banner advertisements on the Home and Editor screens using the Google Mobile Ads SDK. Google and its advertising partners may automatically collect and share information for ad delivery, measurement, analytics, and fraud prevention, including:
- IP address, which may be used to estimate general location.
- Android Advertising ID, App Set ID, and other device or account identifiers where applicable.
- Ad impressions, ad interactions, app launches, taps, and other product-interaction information.
- Diagnostic and performance information, such as SDK or app launch and stability data.
- Advertising data and, where applicable, coarse location or signals from Android advertising services.
Google states that data handled by the Mobile Ads SDK is encrypted in transit. Ad personalization, consent, and privacy controls may depend on your region, Android settings, Google account settings, and the consent configuration used by the published release. You can review Google’s information about AdMob data disclosures, the User Messaging Platform, and Google’s Privacy Policy.
The development build currently uses Google test ad identifiers. Those identifiers must be replaced with the developer’s production AdMob identifiers before publication.
5. How information is used and shared
Information is used to:
- Provide photo editing, collage, export, and sharing features.
- Understand feature usage and improve App reliability and design through Firebase Analytics, when enabled.
- Display, measure, and protect banner advertising through Google Mobile Ads.
- Prevent abuse, diagnose failures, and maintain the App and its third-party services.
Analytics and advertising data may be processed by Google and its service providers in countries outside your country of residence. The developer does not sell your selected photos, generated memes, or typed text. The App’s Android share action is user-initiated and is not a transfer to the developer.
6. Storage, retention, and deletion
The developer does not operate an account system or a server that stores your photos, generated memes, or editing sessions. Local images and exported files remain on your device until you delete them using Android or another app that manages your storage.
Firebase Analytics and Google Mobile Ads may retain provider-side data according to Google’s applicable retention settings, policies, and user controls. The developer does not control the exact retention period for data processed directly by Google. For Google-side controls or deletion requests, see Google’s privacy and account tools. You can also contact the developer at gopurajesh@gmail.com; because the App has no user account and does not receive analytics identifiers, the developer may need information from you to identify a request and may need to direct provider-side requests to Google.
7. Security
Photo processing is performed locally on your device. Data sent to Google services by their SDKs is handled under the security practices of those services, including encryption in transit as described by Google. No method of storage or transmission is completely secure, and you should use Android’s device security and keep the App and operating system updated.
8. Children’s privacy
The App is not directed to children under 13 and is not knowingly designed to collect personal information from children. If you believe a child provided personal information through a third-party service used by the App, contact us at gopurajesh@gmail.com so we can review the request.
9. Your choices
You choose which photos to provide to the App and whether to export or share a result. You can delete locally saved images from your device, reset or limit Android advertising identifiers through Android settings, and use Google account or device controls for Google Analytics and advertising where available. In regions where Google requires an advertising consent choice, the published release should present Google’s consent options before requesting personalized ads.
10. Changes to this Privacy Policy
We may update this Privacy Policy when the App, its analytics configuration, or its advertising services change. The updated policy will be posted at this URL with a new effective date. You should review it periodically.
11. Contact
For privacy questions, data requests, or concerns about this policy, email gopurajesh@gmail.com.