Privacy Policy

This Privacy Policy explains how Z-Rex Network (“we,” “us,” “our”) collects, uses, stores, shares, and deletes personal information when you use the Milo mobile application and related online services (the “Service”). It is intended to be consistent with Google Play’s User Data and Data safety requirements and with our in-app disclosures.

By creating an account or using the Service, you acknowledge this policy. If you do not agree, do not use the Service. Related documents: Terms of Service, Community Guidelines, and Child Safety Standards.

1. Who we are

• App name (Google Play): Milo
• Android package: net.zrex.milo
• Operator: Z-Rex Network
• Privacy / support email: support@z-rex.net
• Service domains: milo.z-rex.net (API) · support.milo.z-rex.net (this legal site)

2. Information we collect

2.1 Information you provide

• Account identifiers: Email address (for email verification codes). If you choose Google Sign-In, we receive your Google account identifier, email, and display name as provided by Google’s OAuth / ID token flow.
• Profile: Nickname, preset avatar index (in-app artwork only), optional bio, primary language, zodiac, birth decade range (for matching preferences—not a verified date of birth), and gender (you may keep gender private). You may also set whether your pen-pal count is visible to pen pals.
• User content (UGC): Letter text, replies, conversation messages, optional routing preferences (e.g., preferred gender / decade / zodiac for drift delivery), stamp style choices, and whether you allow an optional AI fallback reply on a letter.
• Social actions: Pen-pal requests and responses, blocks, archive/hide actions, and safety reports you submit about content or users.
• Support communications: Emails you send to us (including child-safety reports).

Milo’s primary sign-in methods are email one-time codes and Google Sign-In. Password-based registration may exist as a legacy or alternate path; where a password is set, it is stored only as a one-way hash.

2.2 Information collected automatically

• Service logs: Approximate access times, API request metadata, and error logs needed to operate and secure the Service. When sending verification or account-deletion emails, we may process and rate-limit your IP address to prevent abuse.
• App activity: Check-in history; virtual stamp balances and transactions; letter send/receive and moderation status; conversation and read state; rewarded-ad claim records; last login / last active timestamps.
• On-device tokens: Access and refresh tokens (JWT) and preferences such as language and theme stored locally so you can stay signed in.
• Advertising identifiers (via Google AdMob): When you choose to watch a rewarded video ad, Google’s advertising SDK may process the Android Advertising ID and device/ad performance data under Google’s policies. See Section 4.

2.3 Information we do not collect for core features

Core Milo features are text-based. We do not require precise GPS location, contacts, microphone, SMS, or access to your photo library to write or receive letters. Avatars are selected from in-app presets; we do not currently offer camera capture or gallery upload for profile photos or letter attachments.

2.4 Android permissions

The Android package may declare permissions used by the uni-app runtime, Google Sign-In, and/or Google AdMob, including network access, network/Wi-Fi state, wake lock, vibrate, and (on some builds) camera, accounts, or phone-state related declarations from the framework or SDKs. We request only what is needed for sign-in, networking, optional haptics, and rewarded ads. You can deny or revoke runtime permissions in system settings; some features (especially ads or Google Sign-In) may then be unavailable.

If a permission is declared but not used by a Milo feature you invoke, we still disclose it here because it may appear in the app package. We will update this policy if we add features that actively use camera or media access.

3. How we use information

1. Create and authenticate accounts (email codes or Google Sign-In) and keep sessions secure;
2. Provide drifting letters, delayed delivery, mailbox, conversations, pen-pal matching, and related social features;
3. Apply content safety checks (local sensitive-word filters and automated moderation) and handle reports, blocks, and enforcement;
4. If you opt in to AI fallback replies on a letter, generate a reply using a third-party language model (see Section 5);
5. Issue and manage virtual stamps (new-user grants, check-ins, rewarded ads);
6. Prevent spam, fraud, and abuse (including rate limits);
7. Respond to support and safety requests;
8. Improve the Service using aggregated or de-identified statistics;
9. Comply with law and Google Play policy obligations (including child-safety reporting where applicable).

We do not sell personal information. We do not use your letter content to build advertising profiles.

4. Advertising (Google AdMob)

You may optionally watch rewarded video ads served by Google AdMob to earn virtual stamps. Ads are not required to use core letter features if you obtain stamps another way (e.g., check-in).

• Google may collect and process advertising identifiers, device information, and interaction data as described in the Google Privacy Policy and AdMob documentation.
• On Android, respect the system setting to opt out of Ads Personalization / interest-based advertising. When that setting is enabled, advertising identifiers must not be used to build personalized ad profiles (contextual ads, frequency capping, fraud prevention, and reporting may still apply).
• Milo is intended for users 16+ and is not Designed for Families / child-directed. We do not target children with ads.

5. Content moderation and optional AI replies

5.1 Moderation

When you send a letter or reply, we may:

• Run local / server-side sensitive-word checks; and
• Send the text content to a third-party moderation API (currently OpenAI Moderation) for automated analysis.

Outcomes may include allowing delivery, returning mild violations so you can revise (with stamp refund on eligible send paths), or silently rejecting severe / malicious content without notifying you or refunding stamps. Details are in our Community Guidelines.

5.2 Optional AI fallback (“AI Drifter”)

If you enable the option to allow an AI reply on a specific letter and no human reply arrives within the configured waiting period, we may send that letter’s text to a third-party chat / completions API (configured OpenAI-compatible endpoint) to generate a reply. AI replies are labeled in product, cannot form pen-pal relationships, and are also subject to safety checks. We do not intentionally send your email address or account ID as part of that prompt, but anything you write in the letter may be included.

If you disagree with a moderation or AI-related outcome, email support@z-rex.net for manual review. We will respond within a reasonable time but cannot guarantee reinstatement.

6. Sharing and third parties

6.1 Service providers

• Google: Sign-In and AdMob. Google Privacy Policy
• OpenAI (or OpenAI-compatible API provider): Text moderation and, when you opt in, AI reply generation. OpenAI Privacy Policy
• Resend: Transactional email (sign-in codes, account-deletion confirmation). Limited to delivery metadata needed to send mail.
• Infrastructure: Hosting, MariaDB, Redis, and related cloud providers that process data on our behalf under contractual or operational controls.

6.2 Other users

• Before pen pals: others typically see your virtual identity (generated nickname / preset avatar) and the content you send—not your registration email.
• After mutual pen-pal acceptance: each party may see profile fields the other has chosen to display (e.g., nickname, avatar, bio, language, zodiac, birth decade, public gender, activity counts; pen-pal count only if you enable that setting).
• Recipients see letters and replies you choose to send. Delivery may be delayed by design.

6.3 Legal and safety

We may disclose information when required by law, valid legal process, or when necessary to protect users (including children), the public, or our rights—including reporting confirmed CSAM to NCMEC or equivalent authorities as described in our Child Safety Standards.

7. Storage, retention, and international transfers

• Data is stored on servers we operate or control for the Service. Locations may change as infrastructure evolves.
• Providers such as Google, OpenAI, and Resend may process data in other countries. Transfers are limited to what is needed for the purposes in this policy.
• We retain account and content data while your account is active and as needed for safety, dispute, and legal obligations.
• After account deletion is confirmed and the grace period ends, we anonymize personal identifiers and clear message/letter content as described in Section 8. Structural records (e.g., empty conversation shells, safety action logs, stamp/check-in history without your identity) may remain for integrity, abuse prevention, or legal reasons.

8. Account deletion

You can request deletion in the app (Profile → Delete account) or on our Delete Account web page.

1. We email a confirmation link to your registered address (links expire; we do not reveal whether an email is registered beyond the confirmation flow).
2. After you confirm, the account is blocked immediately (you cannot sign in).
3. After a 7-day grace period, we purge personal data by anonymization: email and Google ID removed/replaced with non-identifying placeholders; profile fields cleared; your letter and message content emptied; virtual-identity nicknames set to a deleted placeholder.

Other users may still see that a conversation once existed, but not your personal identifiers or original text. Content we are legally required to retain (e.g., for ongoing safety investigations) may be kept in restricted form.

9. Security

We use HTTPS in transit, access controls, and hashed passwords where passwords exist. No method is 100% secure. If a breach likely affects your personal information, we will take steps required by applicable law, which may include notice.

10. Your rights and choices

• Access / correct profile data in-app (Profile → Edit);
• Control visibility of certain profile fields and pen-pal list visibility;
• Opt out of AI fallback by not enabling it on a letter;
• Limit ads personalization via Android Ads settings;
• Report / block / archive content or users in-app;
• Delete your account as in Section 8;
• Contact us at support@z-rex.net for privacy requests. We typically respond within 15 business days.

Depending on where you live, you may have additional rights under local law (access, erasure, restriction, complaint to a regulator). We will honor applicable requests after verifying your identity.

11. Children

Milo is for users aged 16 and older only. We do not knowingly collect personal information from children under 16, and the Service is not directed to children under 13 (COPPA) or to “children” as defined in Google Play’s Families policy.

Birth decade on a profile is an optional matching preference, not age verification. If you believe a child under 16 created an account, contact support@z-rex.net; we will disable the account and delete or anonymize associated personal data as soon as reasonably practicable.

CSAE / CSAM standards: Child Safety Standards.

12. Cookies and local storage

The app uses on-device storage for tokens and preferences. This legal website is static HTML and does not set its own tracking cookies. Hosting providers may keep basic access logs.

13. Policy updates

We may update this policy. The current version will be posted here with a new “Last updated” date. Material changes may also be noted in the app. Continued use after the effective date means you accept the updated policy; if you do not, stop using the Service and delete your account.

14. Contact