Mood Summon Maker - Privacy Policy
Effective Date: Effective Date: July 1, 2026.
This Privacy Policy explains how Mood Summon Maker handles information when you use the app.
Mood Summon Maker is an Android creative and entertainment collectible mood card app. Users generate mood cards locally, may keep cards in a local gallery, may optionally personalize the display name shown on cards, and may choose to save or share card images.
Developer / Legal Entity: Jotaku
Developer type: Individual / natural person
Developer jurisdiction: Peru
Privacy contact email: jotartist_420@outlook.com
Support contact email: jotartist_420@outlook.com
Public Policy URL: https://sites.google.com/view/mood-summon-maker-privacy
Language: English
Availability: intended for global distribution, including the United States, Europe, the United Kingdom, Switzerland, and other ad-supported markets.
Current App Behavior Summary
No account or login is required or supported.
No backend server is used to store user accounts, user profiles, card history, or cloud saves.
The app is local-first. Core app data is stored on the device.
Generated cards are created locally on the device.
Users may optionally change the display name shown on a generated card. This card personalization text is local app data.
Save exports a card image to the device photo library after the relevant platform permission/use flow.
Share opens the Android share sheet, and the user chooses where to send the image.
Local notifications are opt-in and local-only.
The current build does not use remote push notifications, does not fetch an Expo push token, does not fetch an FCM token, and does not use any remote push provider.
Reset app data deletes local app-owned data, but does not delete images already saved to the device photo library or already shared outside the app.
Information We Handle
Local app data
The app may store the following data locally on your device for app functionality:
generated mood cards
My Gallery / kept cards
equipped Summon Title and local title progress
theme, audio, haptics, and local notifications preferences
onboarding and other app-state flags
local reminder schedule/state for local notifications
optional display name / card personalization text shown on cards
This local app data is used to make the app function on your device. It is not sent to a backend operated by Jotaku because the app does not currently use a backend service.
User-provided card personalization text
If you enter a custom name for a card, that text is used locally to render the name shown on the generated card.
For the current build:
this text is local app data
it is not sent to Firebase Analytics
it is not sent to Firebase Crashlytics
it is not sent to Firebase Performance Monitoring
it is not sent to Firebase Remote Config
it is not sent to a backend server
Images you choose to save or share
When you choose to save a card, the app exports an image to your device photo library. When you choose to share a card, the app opens the Android share sheet and you choose the destination app or service.
These actions are user-initiated. Once an image is saved to your device photo library or shared to another app or service, that image is outside the app's direct control and must be managed through your device or the receiving app/service.
Active Services
The following third-party services are installed and active in the current app state.
Firebase Analytics
Firebase Analytics is installed and active to measure core app interactions.
Based on the current repo state, Analytics is used for core loop event measurement such as summon, keep, save, share, and gallery activity. The app is designed not to send card text, optional card personalization text, mood text, personal identifiers, or user account data to Analytics.
Firebase Analytics may process data such as:
app interactions / app activity
session information
app instance or device-related identifiers used by the SDK
technical analytics information related to app usage
Firebase Crashlytics
Firebase Crashlytics is installed and active for stability monitoring and bug investigation.
Crashlytics may process data such as:
crash reports and stack traces
device and app version information
timestamps
installation or app instance identifiers used by the SDK
technical diagnostics related to app crashes
The app is designed to exclude card text, optional card personalization text, mood text, gallery item identifiers, share URIs, raw file paths, user IDs, and other personal identifiers from Crashlytics breadcrumbs and custom attributes.
Firebase Performance Monitoring
Firebase Performance Monitoring is installed and active for app performance diagnostics.
Performance Monitoring may process data such as:
app start and rendering performance data
technical performance diagnostics
app instance or installation identifiers used by the SDK
privacy-safe custom performance traces related to app flow timing
The app is designed to exclude card text, optional card personalization text, mood text, user IDs, gallery item identifiers, share URIs, and personal identifiers from custom trace data.
Firebase Remote Config
Firebase Remote Config is installed and active to fetch remote configuration values.
Remote Config may process data such as:
app instance / installation information
technical device/app metadata needed to fetch config values
In the current app state:
behavior-changing defaults are safe/off in source
the app continues to work if Remote Config is unavailable
no user IDs are configured
no account system is used
no ad personalization audience system is active
a sharing kill switch is the only documented flag currently connected to visible behavior
Advertising
Current app state
Google AdMob test architecture is installed in the app, but production ads are not currently active.
In the current app state:
the Google Mobile Ads / AdMob SDK is installed
the app is configured with the Google sample/test App ID and Google test ad unit IDs only
default ad-related flags are safe/off
no production/live AdMob App ID is configured
no production/live ad unit IDs are configured
no production ads load or show with the current defaults
no visible production rewarded ad UI is active
no production reward grant is active
Planned production ads
Real ads are planned for first publication readiness, but they remain blocked until separate work is completed.
Production ads remain blocked until the project completes and verifies items such as:
Consent / UMP decision
final Play Console Data Safety review against final manifest and actual SDK behavior
AdMob Console content-control configuration
live/prod AdMob ID switch plan
visible rewarded opt-in UI if rewarded ads launch
production ads launch checklist
When production ads are enabled in a future release, Google AdMob may collect or process data such as:
advertising identifiers
device or other identifiers
app interactions
diagnostics
approximate technical/device information
fraud-prevention and abuse-prevention data
The intended first production ads path is non-personalized/contextual ads unless and until consent/UMP requirements are separately resolved and implemented.
This policy does not mean production ads are active today.
In-App Purchases and Payments
For the intended first publication:
no in-app purchases are active
no payments are active
no remove-ads purchase is active
no supporter purchase is active
no billing flow is active
Google Play Billing / IAP may be evaluated in the future, but it is not active for the current first-publication plan described by this policy.
Notifications
The app currently supports local notifications only as an optional opt-in feature.
For the current build:
local notifications are controlled on-device
no remote push notification provider is active
no Expo push token is fetched or stored
no FCM token is fetched or stored
no remote push backend is used
Children and Audience
The app is not directed to children under 13 and is intended for a general teen and adult audience.
Store listing, screenshots, metadata, and positioning should avoid child-directed presentation. If the audience strategy changes in the future, this Privacy Policy and the Play Console answers should be reviewed again before publication or update.
Third-Party Services
Active:
Google Firebase Analytics
Google Firebase Crashlytics
Google Firebase Performance Monitoring
Google Firebase Remote Config
Installed test-only / planned production:
Google AdMob - installed as test architecture only in the current app state; production/live ads are not active
Planned / not active at first publication:
Google Play Billing / IAP
Not active:
remote push notifications
Data Retention and Deletion
Local app data
You can delete local app-owned data by:
using Settings -> Reset app data
uninstalling the app
Reset app data is intended to remove app-owned local data such as local gallery data, local title progress, equipped title, local preferences, and local reminder state.
Saved or shared images
Reset app data does not delete:
images already saved to the device photo library
images already shared to another app, service, or destination outside the app
Those copies are outside the app's control and must be managed through your device or the receiving app/service.
Third-party provider retention
Data processed by Firebase services, and by AdMob once production ads are active in a future release, is handled according to the applicable provider's own policies and retention practices.
Security
Local app data is stored on-device using app storage.
Data transmitted to active Firebase services relies on those providers' standard transport/security practices.
The app does not currently provide a user account system or backend database operated by Jotaku.
International Availability
The app is intended for global distribution, including the United States, Europe, the United Kingdom, Switzerland, Peru, and other markets where the app may be made available. Data practices may therefore be relevant across multiple jurisdictions depending on where the app is distributed and which SDK/provider services are active.
Changes to This Privacy Policy
This Privacy Policy should be updated or rechecked:
before first Google Play publication
whenever the public policy URL changes
whenever the effective publication date becomes known
whenever SDKs, permissions, manifests, or third-party services change
before enabling production ads
before enabling Google Play Billing / IAP
before enabling any remote push notification provider
whenever Play Console Data Safety answers or store disclosures need to change
Contact
For privacy questions, support, or privacy-related requests, contact:
Developer / contact: Jotaku
Email: jotartist_420@outlook.com
Jurisdiction: Peru
This Privacy Policy is not attorney-reviewed and must be kept in sync with the actual app, SDK behavior, Play Console answers, and release configuration.