PROVIDERS AND SUBPROCESSORS
List updated on: August 3, 2026
This page lists the third parties that receive Mirokami data, and what for. It complements Section 4 of the Privacy Policy, which describes these recipients by category.
About AI model providers: Mirokami accesses AI models through OpenRouter, which routes each call to the provider of the model in use. Which models we use may change based on cost, quality, or availability. This page reflects the providers in use and is updated when that changes — without amending the Privacy Policy, which describes these recipients by category.
OpenRouter
Purpose: AI gateway: routes our model calls to the provider currently in use
Data involved: Photos uploaded in the app and text generated in character interactions
Processing country: United States
Privacy policy: View policy ↗
OpenAI
Purpose: Image analysis (food detection, activity classification) and experience matching
Data involved: Photos uploaded in the app and the text tied to the interaction
Processing country: United States
Privacy policy: View policy ↗
Google (Gemini / Gemma)
Purpose: Text generation: insights, daily recap, tarot readings, and translations
Data involved: Interaction text and character attributes
Processing country: United States
Privacy policy: View policy ↗
Cerebras
Purpose: Inference for the alchemy minigame
Data involved: Only the two words picked in the minigame — no personal data
Processing country: United States
Privacy policy: View policy ↗
Amazon Web Services (S3, SES)
Purpose: Private image storage (S3, us-east-1), transactional email delivery (SES), and backend infrastructure
Data involved: Photos, account data, server logs, and verification codes
Processing country: United States
Privacy policy: View policy ↗
Google Firebase
Purpose: Usage analytics and push notification delivery
Data involved: Analytics events (without user_id for minors) and push notification token
Processing country: United States
Privacy policy: View policy ↗
Google AdMob / User Messaging Platform
Purpose: Rewarded ads and consent management
Data involved: Advertising identifiers and consent state
Processing country: United States
Privacy policy: View policy ↗
Apple (Sign in with Apple, Declared Age Range API)
Purpose: Sign in with Apple and, where available, declared age range verification
Data involved: Apple account identifier and approximate age range — never the date of birth
Processing country: United States
Privacy policy: View policy ↗
Google (Sign-In, Play Age Signals)
Purpose: Google Sign-In and, where available, declared age range verification
Data involved: Google account identifier and approximate age range — never the date of birth
Processing country: United States
Privacy policy: View policy ↗