Privacy Policy
Last updated: July 29, 2026
This privacy policy applies to the Sumo app for iOS, developed by Guillermo Rodríguez Delgado. Sumo is a math practice game with a virtual pet, made for children. This page explains, in plain language, what stays on your child's device and the one kind of technical data the app sends out: crash diagnostics.
The short version
Sumo has no accounts and no servers of mine. Everything your child does in the game — their age setting, pet, math progress, coins and items — stays on the device.
The one exception is crash reporting. Sumo includes Firebase Crashlytics, a Google service that sends me technical reports when the app crashes or hits an error, so I can fix it. Those reports contain device and app diagnostics plus identifiers generated by Firebase, so I do not describe them as anonymous. The section below lists exactly what they contain.
On-device data
The following information is created and stored on your child's device only. It is not uploaded, not backed up to any server of mine and not shared with anyone. It exists so the app can cap the difficulty of the math to the chosen age and remember game progress between sessions:
- the selected age (4–12), used to set the difficulty range;
- the name given to the virtual pet;
- math progress and accuracy, and the current streak;
- coins earned, and the pet's state (such as hunger, mood or life stage);
- inventory and customization choices for the pet and its home;
- reminder and notification preferences.
If you turn on Apple's device backups, this data may be included in your own iCloud or computer backup. Those backups are managed entirely by Apple under your Apple Account — I have no access to them.
Crash reporting with Firebase Crashlytics
When the app crashes or runs into a handled error, Firebase Crashlytics collects and transmits a diagnostic report. These reports are tied to identifiers generated by Firebase, so they are best described as pseudonymous technical data rather than anonymous. A report can include:
- crash and non-fatal stack traces;
- exception details and the timestamp of the event;
- the app version and the state of the app at the time;
- device model and architecture, and the operating system version;
- RAM and disk information (for example, memory and storage available);
- a Crashlytics installation UUID, a Firebase installation ID and a session ID — identifiers Firebase generates for the app installation, so repeated crashes can be grouped together;
- a limited amount of diagnostic context that I add myself to make a crash understandable: the screen or flow the app was in, an internal pet-record ID, the pet's life stage, the type of care action, the ID of a selected item, a reward amount, and generic error or lifecycle events.
The developer-provided context above is deliberately narrow and technical. The internal pet-record ID is a local record number for the app's own data — it is not an account, and it does not identify your child. Crash reports do not include the pet's name, the selected age, names, contact details, messages or anything else typed into the app.
What Sumo does not use
Sumo does not use:
- Firebase Analytics or any other product analytics;
- behavioral analytics or advertising analytics;
- attribution or install-measurement SDKs;
- ads or ad networks of any kind;
- the Identifier for Advertisers (IDFA) or App Tracking Transparency prompts;
- cross-app or cross-site tracking, or any linking of app data to data from other apps or websites.
Crashlytics is the only third-party SDK in the app that transmits data, and it is used for crash diagnostics only.
How crash data is used and shared
Crashlytics data is sent only to Google Firebase, acting as my service provider, and is used for a single purpose: diagnosing crashes and improving the stability of the app.
It is not sold, not shared with advertisers or data brokers, and not used for profiling, behavioral analysis, advertising or tracking. I do not combine it with any other source of data, because there is no other source — Sumo has no accounts and no backend of mine.
Where the data goes and how long it is kept
Firebase processes crash data on Google's global infrastructure, which means it may be stored and processed on servers outside your country. Google encrypts the data in transit and at rest.
Firebase retains crash traces and the associated identifiers for approximately 90 days, after which the deletion process begins. Some aggregated crash statistics, which do not identify an individual installation, may be kept for longer by Google.
You can read Google's own documentation here: Privacy and Security in Firebase and Firebase iOS App Store data collection details.
Information Sumo never collects
Sumo has no user accounts, no sign-in, no social or chat features, and no servers operated by me. I never collect, and have no way to receive:
- email addresses or phone numbers;
- precise birthdates (only an age between 4 and 12, kept on the device);
- contacts, photos or the camera and microphone;
- location data, including precise or coarse location;
- health, fitness, payment or financial information;
- school, class or teacher information.
Data retention and deletion
- Local game data stays on the device until you reset the pet inside the app or delete the app.
- Deleting the app removes the locally stored data from the device. Copies may still exist in Apple-managed device backups until those backups expire or you remove them — those backups are controlled by you and Apple, not by me.
- Crashlytics data follows Firebase's retention process described above, with deletion beginning after approximately 90 days.
- If you have a question about privacy, or want to ask about crash data associated with your installation, email me at gelemias@gmail.com and I will help.
Children's privacy
Sumo is made for children and is distributed in Apple's Kids Category, so it follows the stricter rules that apply there. There are no ads, no third-party advertising SDKs, no analytics SDKs, no social or chat features, and no behavioral targeting of any kind.
Firebase Crashlytics is present only for technical diagnostics: to tell me that the app crashed and why. No information from a child is used for advertising, profiling, behavioral analytics or tracking, and none is sold or shared with data brokers.
Sumo does not ask a child for personal details. The age selection (4–12) stays on the device and is used only to set the difficulty of the math questions. Parents who want the app's data removed can delete the app; see the retention section above, or contact me with any question.
Changes to this policy
If the app's data practices ever change, this policy will be updated here before the change takes effect, and the "Last updated" date above will be revised.
Contact
If you have any questions about this privacy policy, contact me at gelemias@gmail.com or visit the Sumo support page.