moon made me ← Back to home

moon made me — Privacy Policy

Effective Date: May 14, 2026
Last Updated: May 14, 2026
Version: 1.1


The short version (plain language)

moon made me is built around minimal data collection. Here's what matters most:

What we DON'T collect

What we DO collect

What we DO with it

What we DON'T do

The detailed policy follows. In any conflict between this summary and the detailed sections, the detailed sections control.


1. Introduction

moon made me ("we", "us", "our") operates the moon made me mobile application (the "Service"). This Privacy Policy describes how we collect, use, share, and protect information when you use the Service.

By using the Service, you agree to the practices described here. If you do not agree, please do not use the Service.

2. Information We Collect

2.1 Information You Provide

During onboarding and in Settings, you may provide:

Field Purpose Retention
First name or nickname (≤20 chars) Personalization (shown in greetings, push notifications) While account active
Guide selection (avatar ID + name ≤16 chars) Delivery persona for whispers While account active
Tone preference (Spark / Calm / Witty) Select whisper variant While account active
Notification time (preset: 7am / 9am / 12pm / 6pm / 9pm) Schedule daily local push While account active
Email address (if using Apple Sign In or Google Sign In) — including Apple's private-relay address when "Hide My Email" is selected Returned by your sign-in provider's OAuth flow; stored in your Firebase Authentication record. We do not display it back to you, do not use it for marketing, and do not share it outside the providers listed in §4. While account active; deleted on account deletion
Email address (if using email magic link) Send a single, time-limited sign-in link, delivered via our transactional email provider Resend; retained in Firebase Authentication while account is active for re-login and account recovery While account active; deleted on account deletion
Feedback message (free-text, ≤500 chars, optional via Settings → Feedback) Read your message to improve the Service; respond if you've included contact info Retained for 24 months then auto-deleted; deleted within 30 days of account deletion request

2.2 Information Collected Automatically

When you use the Service:

Data Purpose Retention
Authentication identifier from Apple Sign In / Google Sign In / Firebase email magic link Account login While account active
Authentication provider type (google.com / apple.com / password) Identify sign-in method for account recovery and internal cohort analytics While account active
Device type and OS version Debugging, compatibility Operational logs ≤ 90 days
Timezone (detected from device) Local midnight reset for daily whisper; persisted to your account record so reset works consistently across devices While account active
Last active timestamp Detect stale accounts and inform stale-data cleanup While account active
Session identifier Group analytics events into sessions to understand usage patterns; rotate every 30 minutes of inactivity to limit cross-session correlation UUID generated on device, persisted to local app storage; rotated after 30 minutes idle; not retained after rotation
Whisper interaction history (which whisper ID viewed, date, tone) Prevent repetition within 365 days 365 days rolling, then auto-deleted
Vibe grid impression events (the four vibes shown, whisper ID, tone, primary vibe) Understand which vibe combinations users see per whisper; inform curation quality and pool sizing 365 days, then auto-deleted
Talisman draw events (vibe selected, whisper ID, tone, product ID, Amazon ASIN, primary-vibe flag) Record which talisman you draw per vibe per day; ensure same-day idempotence and 7-day product variety; inform affiliate analytics 365 days, then auto-deleted
Product click events (product ID, whisper ID, tone) Affiliate tracking; understand which products resonate with each whisper 180 days, then auto-deleted. Aggregated anonymized counts may be retained longer.
Product return events (product ID, seconds elapsed before returning from Amazon, 1–300 s window) Measure engagement depth with linked products 180 days, then auto-deleted
In-app behavior events (onboarding step completed, share button tapped, app-open at session start) Understand onboarding completion and content-sharing patterns; no content from these events is shared with third parties 365 days, then auto-deleted
Event metadata (app version, OS version, platform, locale) attached to all in-app events Diagnose performance regressions across versions; understand device and locale segments Same retention as the parent event: 365 days for whisper-view, onboarding, share, and app-open events; 180 days for product events
Push notification token Deliver notifications Retained while account is active; cleared on account deletion. May persist briefly after disabling notifications until next account-state sync.

2.3 Information We Do NOT Collect

To be explicit, we do not collect or access:

3. How We Use Information

We use your information to:

4. How We Share Information

We share information only with the following service providers, for the specified purposes and in the minimum amount necessary.

Recipient Role What they see Location
Apple Sign In (iOS only) / Google Sign In Identity provider Own OAuth flow — we receive a user ID token and, if the provider returns one, your email address (which Firebase Authentication then stores in your auth record) Global
Firebase Authentication (Google) Identity provider, session management, magic-link issuance (delivery is performed by Resend, see below) User ID token, provider, and email address — supplied by your chosen sign-in provider (Apple, Google, or magic link) Google Cloud
Firebase Analytics (Google) Anonymized usage analytics Event data without personally identifying fields Google Cloud
Firebase Crashlytics (Google) Crash reporting and breadcrumb logs to diagnose stability issues Crash stack traces; non-fatal exceptions; breadcrumb logs (analytics event names, no user identifiers); device + OS version Google Cloud
Supabase (PostgreSQL) Backend database — stores user profile, whisper history, talisman draw history, and all in-app analytics events (app_open, onboarding_step, whisper_viewed, vibe_grid_impression, talisman_drawn, product_clicked, product_click_return, share_tapped). All events include your Firebase UID so that your data can be located and deleted on account removal. Encrypted storage of the fields in Section 2 US East (AWS)
Loops (Email Service Provider) Marketing email collection + delivery for landing-page signup, welcome, and launch announcements Email address; subscription timestamp; standard delivery telemetry US (AWS)
Resend (operated by Resend, Inc.) Transactional email delivery (SMTP relay for the magic-link sign-in path) Recipient email address; magic-link message body; standard delivery telemetry (sent / delivered / bounced / opened) US (AWS)
Amazon (Associates Program) Affiliate tracking for product links Your click on a product link + our partner tracking tag — no personal identifier from us Global
Expo / Expo Application Services (EAS) App build infrastructure and over-the-air updates Build metadata, crash diagnostics (no PII) Expo / AWS
Expo Notifications (wraps APNs and FCM) Push notification delivery Push token and notification payload Apple / Google / Expo infrastructure
Cloudflare (Pages, Workers, KV) (a) Static hosting for moonmademe.com and /.well-known/ files. (b) Server-side affiliate redirect proxy at moonmademe.com/r/{product_id} — every product-card tap in the App passes through this Worker, which looks up the product, applies our Amazon affiliate tag, and 302-redirects to Amazon Source IP and user agent (transient, in standard edge access logs); requested product UUID; redirect timing Cloudflare global edge

We do NOT:

We may disclose information if required by law, valid legal process (subpoena, court order), or to protect the safety and rights of users or the public. We will challenge overbroad or improper requests where feasible.

4.2 Business transfers

If moon made me is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you and post a notice in the App if your information becomes subject to a materially different privacy policy.

5. Data Retention

We retain information only as long as necessary for the purposes described. Specifically:

6. Your Rights

6.1 Rights available to all users

At any time you may:

Account deletion removes your personal data within 30 days, subject to the retention exceptions above.

6.2 California residents (CCPA / CPRA)

If you are a resident of California, you have the right to:

To exercise these rights, email us at contact@hasia.ai with the subject line "Privacy Request". We will verify your identity via the email address associated with your Apple/Google sign-in before acting.

6.3 EEA / UK residents (GDPR / UK-GDPR)

If you are in the European Economic Area or the United Kingdom, you have additional rights including access, rectification, erasure, restriction of processing, data portability, and objection. Contact us at contact@hasia.ai to exercise these rights.

Legal basis for processing:

6.4 Other jurisdictions

Residents of other jurisdictions with applicable privacy laws (e.g., Virginia, Colorado, Connecticut, Utah in the US; LGPD in Brazil) have similar rights. Contact us for assistance.

7. Children (COPPA)

moon made me is not directed at children under 13 years old. We do not knowingly collect personal information from children under 13.

If you are a parent or guardian and believe your child under 13 has provided personal information to us, please contact us at contact@hasia.ai. We will delete the information within a reasonable timeframe and terminate the account.

App Store age rating restricts download to age-appropriate users. If we later discover an existing user is under 13, we will terminate the account and delete associated data.

8. Security

We take reasonable technical and organizational measures to protect your information, including:

No system is perfectly secure. If we discover a security incident affecting your personal information, we will notify you as required by applicable law.

9. International Data Transfer

Our servers are located in the United States (AWS US East via Supabase). If you use the Service from outside the US, your information will be transferred to, stored, and processed in the US. Data protection laws in the US may differ from those in your country.

By using the Service, you consent to this transfer. For EEA/UK residents, this transfer relies on standard contractual clauses or other transfer mechanisms as permitted by applicable law.

10. Cookies and Similar Technologies

moon made me is a native mobile app and does not use browser cookies. We use:

We do not use web beacons, pixel tags, fingerprinting, or any cross-app tracking technologies.

11. Do Not Track

The App does not respond to Do Not Track signals, because Do Not Track is a browser-level standard that does not apply to native mobile apps. However, we do not track you across other apps or services regardless of Do Not Track status.

12. Advertising (current state: none)

As of this Policy's effective date, moon made me does not display third-party advertising of any kind — no banners, interstitials, rewarded video, or sponsored content. We do not use advertising SDKs and do not process advertising identifiers.

If we ever introduce advertising or change our data practices, we will:

13. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will:

Continued use of the Service after an update constitutes acceptance of the revised Policy. If you do not agree to the revised Policy, you must stop using the Service and may request account deletion.

14. Contact Us

Questions, concerns, or requests regarding this Privacy Policy or your personal information:

moon made me
Operated by: HASIA Co., Ltd.
Email: contact@hasia.ai

For data access, correction, or deletion requests, include "Privacy Request" in the subject line. We will verify your identity using your Apple/Google sign-in email before acting on the request.