MiraOne Privacy Policy

1. App and accounts

This policy covers the MiraOne (Mira One) Android app provided by Freya Code. Basic daily tasks can be used without registering an email address, phone number or password. Arena, friends and messaging use a social account with a unique identifier, without requiring an email address.

2. Data processed

Data depends on the features you use. Social data and installation-based usage measurements are processed using Supabase infrastructure.

3. Profiles, messages and visibility

Your handle, display name, built-in avatar and shared profile fields can appear to other MiraOne users in profiles, discovery, friendships or Arena rankings. Profile discovery and social preferences are managed in the app.

In-app message text, sender/recipient relationships, conversation information and read status are stored to provide messaging. User and message reports are processed for safety and moderation. A custom photo you choose from your gallery is kept in the app’s local device storage; the current photo feature does not upload it to a server.

4. Ads and privacy choices

The free version displays Google AdMob ads. The Google Mobile Ads SDK may process IP addresses, app/ad interactions, diagnostics and advertising/device identifiers for ad delivery, analytics and fraud prevention. IP addresses may be used to estimate approximate location.

Google UMP manages ad choices where required. When available in the app, “Ad privacy options” lets you review your choices. Android advertising identifier controls are available in device settings.

5. Google Play purchases

Pro purchases and payments are handled through Google Play. MiraOne does not request card numbers or CVV. Product identifiers, purchase status and, when needed, purchase tokens can be processed to verify entitlement; associated verification and entitlement records may be stored.

Deleting a MiraOne account does not automatically cancel a Google Play subscription. Manage subscriptions in Google Play’s Payments and subscriptions section.

6. Device permissions and sharing

Notification permission is used for your chosen daily reminders. Gallery selection happens when you initiate it. For sharing and invitations, you choose the receiving app in Android’s share sheet. Invitation codes and Google Play install-referrer information can be used to verify invitation rewards.

These MiraOne features do not require reading your address book, SMS or private messages from other apps. Ad-related approximate location data is described in the ads section.

7. Service providers

Supabase is used for social accounts, messaging, Arena, usage measurements and related server functions. Google provides Google Play, AdMob and UMP. Shared profile information may be visible to other MiraOne users. If you email support, your sender address and message content are processed to answer the request.

Provider infrastructure may process data outside your country. Google’s and Supabase’s privacy information applies to their own services.

8. Retention and deletion

Local tasks, XP, streaks, preferences and photos remain until app data or the relevant local data is removed. Social profiles and related social records are retained until account deletion is completed.

Installation-based usage measurements are stored separately from the social profile. Social account deletion does not automatically remove these records; you can include them in a web-based data deletion request. Available identifiers and, when needed, limited additional verification are used to locate records.

Support or security records may be retained while needed for the relevant request/investigation and applicable mandatory retention. If a record must be retained, the reply to your request will explain the data, reason and retention period. Google’s own payment and advertising records follow Google’s retention rules.

9. Request account or data deletion

Use “Delete social account” on the Arena profile screen to start social account deletion. If you cannot access the app, use the email path on this website’s Account and Data Deletion page.

You can request deletion of associated social data and any separately specified usage measurements, rather than only closing an account. Remaining local device data can be managed in Android app settings.

10. Data security

Server connections use HTTPS/TLS. Account operations use session verification and server access controls. Do not send passwords, payment card details or unnecessary identity documents in a support request.

11. Choices, corrections and contact

Edit profile information and social preferences in the app. Contact the address below for data access, correction or deletion requests. Age-group information and community rules are used to support a safer social experience.

12. Updates

This policy is updated when features, providers or data practices change. The current document date appears at the top of the page.