Who this covers
The file you are reading targets only the YumePet mobile build for Android and iOS obtained from Google Play or the Apple App Store. If a label on the storefront disagrees with anything informal here, trust the publisher name printed beside the install button.
Categories of information
- Creative inputs: stills, selections, or bundles you import or capture so the AI pipeline can render previews, transformations, or exports you asked for.
- Device fingerprints & health signals: handset profile, OS build, build number of YumePet, crash dumps, latency hints—anything that helps us reproduce bugs and block misuse without naming you personally in every log line.
- Help-desk payloads: free-text complaints, compliments, or attachments routed through the feedback form or mailto channel.
Sole processing and storage
Personal information that YumePet collects is processed and retained only by us, on systems and infrastructure that we operate and control ourselves. We do not use third-party processors to handle it for us, and we do not store it with external storage or hosting vendors acting on our behalf.
Downloading the app from an app store or completing an in-app purchase may create records that the marketplace operator holds for billing or delivery under its own terms—that is outside YumePet’s own data pipeline. Aside from those unavoidable storefront artifacts, nothing in this policy is processed or stored by a third party on our instructions.
Purposes behind processing
- Rendering the creative flows, timelines, and credit mechanics you trigger inside the UI.
- Spotting broken builds, tuning model quality, and summarizing trends in aggregate so individuals rarely need identifying.
- Guarding infrastructure from scripted attacks, payment fraud, or policy violations.
- Answering tickets, tracing outages, and throttling runaway usage.
- Meeting subpoenas, tax obligations, or other compulsory instruments we cannot ignore.
Camera roll, still imagery, and faces in frame
- Why pixels move through our stack: Visual bits exist solely to honor the edit, filter, or render you started. We do not recycle them into ad-targeting graphs or face databases unrelated to that moment’s task.
- How long they linger: Retention tracks engineering necessity—finish the job, satisfy bookkeeping, then scrub or anonymize on rolling timers described to ops.
- Commercial resale: We are not in the business of packaging your profile rows for unrelated marketers.
When information is disclosed
Apart from day-to-day operation inside our own environment, we only release information when:
- A law, regulation, court order, or formal government request obliges us to respond.
- We must protect life, health, or public safety in an urgent situation.
International footprints
Because processing and storage stay on infrastructure we control, any cross-border dimension comes only from where we choose to locate our own equipment or personnel, not from shipping copies to outside service providers. When that still implicates transfer rules in your region, we follow the safeguards the law requires.
Protective measures
Access reviews, encryption where sensible, and least-privilege tooling are part of the routine. Still, the public internet introduces residual risk—treat highly private scenes accordingly before they leave your handset.
Controls available to you
Many jurisdictions let residents pull copies, fix mistakes, demand erasure, freeze certain uses, or export machine-readable bundles. Email the address in the next section; expect lightweight identity checks so strangers cannot impersonate you.
Younger audiences
The experience is aimed at teens and adults, not kids below 13. Should we confirm we gathered records from someone younger without verifiable guardian approval, we erase what we can as soon as practical obligations allow.
Future revisions
Product pivots or new privacy statutes can force wording swaps. The live HTML timestamp wins; loud changes might also surface through push notes or modal banners when regulators expect more than a silent edit.
Where to send questions
Privacy desk: [email protected]
Prefer tapping inside the app? Use the same feedback surface you would for product ideas—just mark the topic as privacy-sensitive so it routes correctly.