Mosika Pets

Privacy Policy

Mosika Pets · Effective November 14, 2026

This policy explains how Mosika Pets and its developer handle information when you use the App and its online features.

You can use local features without sending content for online generation. Generating or refining a character requires processing of the content described below. Please avoid including sensitive personal information or other people’s private information.

Creations saved on your device

Mosika Pets stores character names, personalities, palettes, animation frames, creation dates, rendered images, behavior choices, interaction dates, and shared-moment records on your device. A local shared area makes saved characters and your display choice available to the Widget. The App does not provide an account-based cloud library or iCloud sync. Adopting a bundled companion and interacting with saved companions are local features and do not send generation requests.

Manual companion backups

You can choose to export a companion file containing its name, personality, palette, animation frames, behavior choices, interaction dates, and shared-moment records, then import it on another device. Backups do not include generation balances, purchase entitlements, payment transactions, or authentication credentials. This is a manual file backup, not automatic cloud synchronization. The App does not upload the file to our service. If you use the system share sheet or save it with another provider, the destination you choose handles that copy. Deleting a companion in the App does not delete copies you previously exported; you manage those separately.

Online processing & service providers

When you choose online creation or refinement, the App sends your description, color preferences, requested motion, language and, where applicable, selected pixel size. Image-based animation may first generate a master character image, then upload that image with motion or change instructions for reference-based editing. Legacy pixel refinements also send the existing character's name, personality, palette, animation frames and requested changes. The Widget only displays saved local creations and does not send generation requests.

Requests pass through our service hosted by Cloudflare and OpenRouter. Text requests use available providers of DeepSeek or GLM services; the executing provider may vary with routing and availability. OpenRouter publishes its provider directory and data-handling policies. Only the content needed for your request is sent; these services do not receive unrestricted access to your device. Processing may occur outside your country. Each provider’s policies and applicable service terms govern its own retention and handling. We select these providers for this service and require them to handle your personal data with the same or an equal level of protection as described in this policy.

Classic creation currently uses Black Forest Labs through OpenRouter for its character image, followed by local Still, Bounce or Sway movement. Custom Motion creation uses Google through OpenRouter for a master image and reference-based animation; the actual reference image and requested motion are sent for editing. These are current service choices and may be updated. See Black Forest Labs privacy, Google privacy and the applicable Google service terms.

Character images, animation & local recovery

Static artwork and image-based characters use the online processing chain above. Reference editing sends the actual master or reference image bytes, together with the requested motion or changes, through our online service and OpenRouter to Google (Gemini). The App receives resulting image bytes through our own online service; it does not separately download the result from a model provider's image-hosting address.

Received master images and generated originals, together with their descriptions, preferences, motion requests and creation dates, may be saved automatically in a local recovery area, including when later editing, animation preparation or cancellation prevents a finished character. You can reopen an available original, retry local preparation, export it, or explicitly delete it in the separate “Recent creations” screen. Saving an original does not automatically add it to the Widget. Separate static base-image drafts are saved locally when you choose to save them and can be reopened or deleted from the static artwork screen.

Photos used to make companions

You may choose a photo of yourself or someone who has authorized you to use it. The system picker supplies only the selected item. You confirm a crop locally; the App resizes and re-encodes that crop without copying EXIF/GPS metadata. Before photo creation, a separate disclosure asks for permission to send the selected crop, description and preferences through our Cloudflare-hosted service and OpenRouter to Google Gemini. The service first draws a pixel character from the photo, then uses that generated image as the reference for an animation sheet. Saved companion interactions and Widgets run locally and do not resend the photo.

The selected crop and unfinished creation settings may be kept in a separate local photo draft so you can resume. This draft is excluded from the App’s system-backup area and is separate from generated recovery originals and companion export files. You can remove the selected photo in the creation screen. Removing a local draft or companion does not delete the original photo from your photo library or recall information already sent to providers. Previous permission for text or generated-image requests does not by itself authorize uploading a selected photo.

Permissions & purchases

You may choose a photo with Apple’s system picker; the App receives only the selected item, without full photo-library access. It does not request camera, microphone, contacts, calendar, or precise-location access. Purchases are handled by Apple. The App verifies purchase entitlements with StoreKit and records separate Classic and Custom Motion allowances on this device. We do not receive your full payment-card details.

Service access, security & support

We process anonymous app or device identifiers, service-access records, request times, usage counts, and diagnostic information to provide access, prevent misuse, and investigate failures. Hosting providers may also process IP addresses and network information. Our operational logs do not include your message text or generated content. If you contact us, we receive your email address and the information you choose to send.

We do not sell personal information, show advertising, or use cross-app tracking or third-party advertising analytics in the App.

Retention & deletion

Use the menu in a companion's details to delete it, remove its local creation, companion history and rendered images, and update the Widget's saved data. Saved creations remain available to view or delete if you stop using online generation and refinement. App removal deletes the App's local documents; system backups and secure device credentials may remain under system controls.

Recovery originals and static artwork drafts are managed separately from saved companions. Deleting a companion does not automatically delete its recovery originals; explicitly delete originals in “Recent creations” and static drafts in their own draft screen. If you export or share an original, you manage the exported copy at the destination. Deleting the local original does not remove previously exported copies.

The online service does not provide a saved cloud library of your content. This does not mean online processing has zero retention. Service-access, usage and security records, and data held by OpenRouter or model service providers, may be retained for service operation, safety, legal obligations or their applicable terms. Any permitted use for service or model improvement depends on the relevant provider's policy and service agreement; we do not promise zero retention or a blanket no-training rule for all providers. Contact us to ask about or request deletion of data we hold; we may need limited information to locate an anonymous record. Local deletion does not automatically erase records held by service providers or Apple.

Your choices & privacy rights

Before online creation or refinement of a legacy character sends information, Mosika Pets asks for your explicit permission to share the data described above with our online service and third-party AI providers. You can decline and still adopt bundled companions, view saved creations, interact locally, make manual backups, and use Widgets. Accepting the User Agreement does not turn on AI data sharing.

You can review or withdraw permission in Me > Settings > Online creation & privacy. Withdrawal blocks subsequent online requests, including later stages of a creation already underway. It cannot recall data already sent or automatically delete records held by service providers. A request already sent may finish. Valid paid image results already received in full continue through the local recovery storage described above; withdrawing permission does not erase them or your saved creations. Withdrawal does not cancel an Apple subscription; manage subscriptions separately in Apple settings.

You may contact us to request access, correction, deletion, a copy, or a restriction or objection where these rights apply. You may also complain to your local privacy authority. We respond as required by applicable law and do not deny local features for exercising privacy rights.

Security, children & updates

We use encrypted connections and limit processing to the service’s purposes. No system guarantees complete security. The App is not directed to children under 13 or a higher minimum age required locally. Minors should involve a parent or guardian. Contact us if a child’s personal data has been submitted. We may update this policy as the product changes; the effective date identifies this version.

These legal and support pages use GitHub Pages. Opening them sends ordinary web-request information to the hosting provider. The pages do not add advertising cookies, analytics scripts, or third-party fonts.

Apple purchases and device-local allowances

Apple handles payments. The App uses verified StoreKit purchase records to determine your subscription and expiry on this device. Product, transaction, subscription-period and expiry information may be kept locally for this purpose. Purchase proofs are not sent to our generation service for membership verification. We do not receive your Apple Account password or full payment-card details.

Allowances and creation/request jobs are recorded on this device, including quota periods, operation type, reservations, completion or failure state and a result checksum. The App saves these records to prevent counting the same job twice. They are not a shared account balance and do not sync between devices. Restore Purchases can restore an eligible Apple subscription; it does not reset this device’s usage or retrieve usage records from another device. App removal or device erasure can remove local records; system backups may retain copies under system controls. Our service does not provide a membership cloud ledger or cloud result-recovery library.