moon made me ← Back to home

日本語 · ภาษาไทย · 한국어 · Bahasa Malaysia

moon made me — Privacy Policy

Effective Date: October 1, 2026
Last Updated: October 1, 2026
Version: 2.0


The short version (plain language)

moon made me is built around minimal data collection. Here's what matters most. We wrote this part in simple words so that younger users can understand it too.

What we DON'T collect

What we DO collect

What we DO with it

What we DON'T do

If you are under 18 (or under 20 in Thailand)

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.

Who is responsible for your information (the "controller"): Hasia Co., Ltd., 108-1, Gasan Mobius Tower, 169-23 Gasan digital 2-ro, Geumcheon-gu, Seoul, 08504, Republic of Korea. Contact and Data Protection Officer: contact@hasia.ai (see §15).

This Policy covers all versions of the App. The same feature can have a different name depending on the version of the App you use:

In this Policy Also called in the App, depending on the version Event name in our database (all versions)
Daily note note or whisper whisper_viewed
Mood grid mood or vibe vibe_grid_impression
Product pick product pick or talisman draw talisman_drawn

Taps on product cards are recorded as rows in our product_clicks table rather than as a named event.

We do not treat your use of the Service as consent. We process your information on the legal bases set out in §3.1. Where we rely on consent, we ask for it separately, and you can withdraw it at any time.

Part of this Policy applies only in certain countries — see §13 Region-specific privacy information (United States, EEA/UK, Japan, Philippines, Malaysia, Thailand, India, Switzerland, Hong Kong, Pakistan, Sri Lanka, South Africa, Nigeria, Kenya, Republic of Korea). This Policy is available in English, Japanese, Thai, Korean, and Bahasa Malaysia. If a translation conflicts with the English version, the English version prevails, except where local law requires the local-language version to prevail.

2. Information We Collect

Where it comes from: (a) you, when you type it in; (b) your device and the app, automatically, while you use the Service; and (c) your sign-in provider (Apple, Google, or Firebase magic link), which passes us an identifier and, if it returns one, your email address. We do not buy information about you from anyone, and the stores you visit through product cards do not send us your purchase or account data.

2.1 Information You Provide

During onboarding and in Settings, you may provide:

Field Purpose Retention
First name or nickname (≤16 chars) Personalization (shown in greetings, push notifications) While account active
Guide selection (avatar ID + name ≤16 chars) Delivery persona for daily notes While account active
Tone preference (Spark / Calm / Witty) Select daily-note 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
Sealed letter note (free-text, ≤100 chars, optional — written when you seal a letter in the Echo Well) Held unopened until the arrival date you chose (1 month to 1 year out, a random date, or a date you pick), then shown back to you in the Echo Well. Stored alongside a snapshot of the daily note you sealed it with and your guide's name at that moment, so the letter reads the same when it arrives. No other user can read it — it is never shown to other users, never used for analytics, and its text is never placed in a notification. Only authorized staff can technically access it, and only where needed to operate and maintain the system. While account active; deleted on account deletion

Please don't put sensitive information in free text. Feedback and sealed-letter notes are free text. Please do not include health information, religious or philosophical beliefs, other sensitive information, or other people's personal information. If you do, we store it only to give it back to you (letters) or to read it (feedback); we do not analyze it or use it for any other purpose.

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 note; persisted to your account record so reset works consistently across devices While account active
Display language (English, Japanese, Thai or Korean, from device settings) Choose the language of the app and of the daily notes; stored on your account record so that notifications we send from our server (for example, a sealed letter's arrival) use your language 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
Daily note interaction history (which note/whisper ID viewed, date, tone) Prevent repetition within 365 days 365 days rolling, then auto-deleted
Mood grid impression events (vibe_grid_impression: the four moods/vibes shown, note ID, tone, primary mood) Understand which mood combinations users see per daily note; inform curation quality and pool sizing 365 days, then auto-deleted
Product pick events (talisman_drawn: mood selected, note ID, tone, product ID, the Amazon ASIN for Amazon products — for other stores this field holds our own product ID, primary-mood flag) Record which product you pick per mood per day; ensure same-day idempotence and 7-day product variety; inform affiliate analytics 365 days, then auto-deleted
Product click events (product ID, note ID, tone, and an internal click ID that is never sent outside our database) Count clicks per product; understand which products resonate with each daily note 180 days, then auto-deleted. Aggregated anonymized counts may be retained longer.
Product return events (product ID, seconds elapsed before returning from the store, 1–300 s window) Measure engagement depth with linked products 365 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 in-app events in our events table (not to product click records) Diagnose performance regressions across versions; understand device and locale segments Same retention as the event it is attached to: 365 days
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.
Country for store selection (Android only — see §2.4) Choose the online store for your region Not stored on our servers. Cached on your device for 24 hours

2.3 Information We Do NOT Collect

To be explicit, we do not collect or access:

2.4 Country lookup and store links (how store links work)

Which store you see. We choose the store by region, not by language (see Terms §6.1).

Because each product in our catalog belongs to one store, your product click records show which store you were sent to.

What the link carries. When you tap a product card, the app records the click in our database and opens our redirect at moonmademe.com/r/{product_id}. The redirect adds only our own affiliate identifiers (for example our Amazon tag) and sends you to the store or affiliate network. We do not send any identifier of you or of your individual click — no name, email address, account ID, or per-click reference. Sales reports we receive from affiliate programs therefore show totals by product and date, not by user. We do not receive your purchase details, order contents, or store account information.

Separately from anything we send, when your device opens a store link the affiliate network and the store receive what any website receives — for example your IP address and browser/user-agent information at their redirect pages — and may set their own cookies. If you are signed in to a store, the store may connect your visit to your store account under its own privacy policy. See §4 and §10.

2.5 What you must provide, and what is optional

Information Required or optional If you don't provide it
Sign-in identifier (Apple / Google / magic link) and the email your provider returns Required to create an account You cannot create an account or use the Service
First name or nickname, guide, tone Required to finish onboarding. Any nickname works — it doesn't have to be your real name You cannot finish onboarding
Timezone, daily note history, and product pick records (talisman_drawn) Collected automatically; needed to run the Service The Service cannot work as described (daily reset, no-repeat notes, product variety)
Usage analytics: session identifier, other in-app events (app opens, onboarding steps, share taps, mood-grid views, note views, return time from stores), and their event metadata Collected automatically to improve the Service; not needed for it to work. In the EEA, the UK and the Republic of Korea, collected only if you opt in on the App's first screen, and you can switch it on or off at any time in Settings → Usage data. Elsewhere there is no in-app switch None. Outside the EEA, the UK and the Republic of Korea, you may object by contacting us (§6.2); we will then delete the analytics events recorded for your account and exclude your account from our analytics
Country for store selection (Android) Automatic when the product feature is shown The app uses your device's language-region instead, which may pick the wrong store
Notification time and push token Optional You won't receive daily notes or reminders as notifications
Feedback message Optional None
Sealed letter note Optional You can't seal letters; the rest of the Service works normally

3. How We Use Information

We use your information to:

Automated choices and profiling. The app automatically chooses which daily note and which products to show, based on your tone, the day's mood, and your region. This does not produce legal effects or similarly significant effects for you, and we do not build a profile of you for advertising.

If we want to use your information for a new purpose that is not reasonably related to the purposes above, we will tell you first and, where the law requires, ask for your consent.

3.1 Legal bases for processing

Where the law of your country requires a legal basis (for example the GDPR/UK GDPR, the Philippine Data Privacy Act, the Malaysian PDPA, or the Thai PDPA), we rely on the following. We do not make consent a condition of using the Service for anything that is not necessary to provide it.

Purpose Legal basis
Account, sign-in, daily notes, Echo Well letters, preferences, account deletion Performance of a contract — providing the Service you asked for under the Terms
Push notifications (daily note) Consent — the operating-system permission prompt; withdraw any time in device or app settings
Return reminders ("Reminders") Legitimate interests in inviting inactive users back, balanced by an easy in-app switch-off
Product cards, click counts, affiliate commissions Legitimate interests in funding a free Service through affiliate commissions
Analytics events, crash reports, security logs Legitimate interests in keeping the Service working, secure, and improving. In the EEA, the UK and the Republic of Korea, analytics events rely on your consent instead (§13.2, §13.11)
Country lookup for store selection (Android) Legitimate interests in showing a store that can deliver to you
Feedback Legitimate interests in reading and answering your message, or contract where it is a support request
Responding to legal requests, keeping records the law requires Legal obligation

Malaysia's PDPA uses a different, consent-centred structure; see §13.5. For the Republic of Korea, see §13.11.

4. How We Share Information

We share information only with the following service providers and partners, for the specified purposes and in the minimum amount necessary. Service providers process data for us under each provider's terms of service and standard data processing terms, which limit their use of it to providing services to us and require them to protect it. Independent companies (sign-in providers, affiliate programs, and stores) handle information under their own privacy policies.

Recipient Role What they see Location
Apple Sign In (iOS only) / Google Sign In Identity provider (independent) 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) Service provider — identity, 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's global infrastructure
Firebase Crashlytics (Google) Service provider — crash reporting and breadcrumb logs to diagnose stability issues Crash stack traces; non-fatal exceptions; breadcrumb logs (analytics event names; we do not attach your account ID); installation and session identifiers generated by the Crashlytics SDK; device + OS version Google's global infrastructure
Supabase (PostgreSQL) Service provider — backend database. Stores user profile, daily note history, product pick history, sealed letters (including the note you wrote), product clicks, and all in-app analytics events (app_open, onboarding_step, whisper_viewed, vibe_grid_impression, talisman_drawn, product_click_return, share_tapped; product clicks are kept in a separate product_clicks table). All events include your Firebase UID so that your data can be located and deleted on account removal. Sealed letters are protected by row-level security so that no other user can read them. Encrypted storage of the fields in Section 2 United States — AWS US East (N. Virginia, us-east-1)
Resend (operated by Resend, Inc.) Service provider — 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; we do not track opens or clicks) United States — AWS US East (us-east-1)
Amazon (Associates Program) — Amazon.com (US), Amazon.co.jp (Japan) Affiliate program and store (independent) Your click on a product link and our affiliate tag. No identifier of you or of your click from us (§2.4). On its own site Amazon also receives your IP address and browser information and uses its own cookies United States, Japan, and other countries where Amazon operates
Involve Asia (Involve Asia Technologies Sdn Bhd) — Philippines, Malaysia, Thailand only Affiliate network (independent) Your click on a product link (through its redirect link, e.g. invl.me), including your IP address and user agent at its redirect, and our affiliate identifiers. No identifier of you or of your click from us Malaysia, and wherever Involve Asia processes data under its own policy
Lazada and, where available, Shopee (Philippines, Malaysia, Thailand) Stores (independent) Your visit through the affiliate link — IP address, user agent, and cookies they set under their own policies. We do not receive your purchase or account data from them The country where the store operates, and wherever it processes data under its own policy
Expo / Expo Application Services (EAS) Service provider — app build infrastructure and over-the-air updates Build metadata, crash diagnostics (no PII) United States
Expo Notifications (wraps APNs and FCM) Service provider — push notification delivery Push token and notification payload Apple / Google / Expo infrastructure
Cloudflare (Pages, Workers, KV) Service provider — (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 the affiliate program for the product's region, and 302-redirects to the store or network; (c) (Android) country lookup at moonmademe.com/geo Source IP and user agent (transient, in standard edge access logs); requested product UUID; redirect timing; for /geo, the country code Cloudflare derives from your IP (returned to your device, not stored by us) Cloudflare global edge

We do NOT:

When you leave the app for a store. Tapping a product card takes you to an affiliate network and a store. Those companies collect information on their own sites (for example cookies, IP address, and pages you view) under their own privacy policies, and may collect it over time and across websites. We don't control that collection and don't receive what they collect, other than sales reports that show totals by product and date.

4.1 Legal disclosures

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 Things you can do yourself, at any time

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

6.2 Rights you can ask us to act on

Depending on the law where you live, you may have the right to:

We offer these rights to all users, whether or not a particular law requires it of us, to the extent they are technically and legally possible.

How to ask: email contact@hasia.ai with the subject line "Privacy Request". We will verify your identity using the email address associated with your sign-in before acting. There is no fee. We aim to respond within 30 days, and sooner where the law of your country requires (for example within two weeks as our target in Japan, and within 10 days in the Republic of Korea). If we need more time where the law allows, or if we cannot fulfil a request, we will tell you why. A parent or guardian may make a request for a minor.

7. Children

moon made me is not directed at children under 13 years old. We do not knowingly collect personal information from children under 13. In the EEA the minimum age is the local age of digital consent — 16 in Germany, the Netherlands, Ireland and Luxembourg, 14 in Austria and Cyprus, and 13 in the other EEA countries where the Service is available. In the UK and Switzerland the minimum age is 13. In the Republic of Korea the minimum age is 14 (§13.11). In India, South Africa, Nigeria and Kenya you must be 18 or older, and we do not knowingly process the personal data of anyone under 18 in those countries (§13.7, §13.10). Where a minimum age above 13 applies, the App asks you to confirm your age on its first screen.

Users who are minors in their country — under 18 in Japan, the Philippines, and Malaysia, and under 20 in Thailand — should use the Service with the consent of a parent or guardian (see Terms §2.2). Where we rely on consent for a minor's information, that consent must be given or authorized by the parent or guardian where the law requires it. The "If you are under 18" part of the short version at the top of this Policy is our plain-language summary for younger users.

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.

The App carries an age rating in each app store and, where a minimum age above 13 applies, asks you to confirm your age on its first screen; we do not otherwise verify age. If we later discover an existing user is under the minimum age, we will terminate the account and delete associated data. For the U.S. Children's Online Privacy Protection Act (COPPA), see §13.1.4.

8. Security

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

No system is perfectly secure. If a security incident affects your personal information, we will notify the relevant regulator and you as required by applicable law, including:

9. International Data Transfer

We are based in the Republic of Korea, and our main servers are in the United States (AWS US East, N. Virginia, via Supabase). Wherever you use the Service, your information will be transferred to, stored, and processed outside your country. Data protection laws in those countries may differ from those in your country.

Where your information goes:

Destination Who What
United States Supabase (AWS US East), Resend (AWS US East), Expo; Amazon.com Everything in §2 (Supabase); sign-in email (Resend); build data (Expo); store visit (Amazon US)
Google's global infrastructure Firebase Authentication, Firebase Cloud Messaging, Firebase Crashlytics (Google) Sign-in, notifications, crash data
Cloudflare global edge network Cloudflare Request data for the website, product redirects, and country lookup, at the Cloudflare data center nearest to you
Japan Amazon.co.jp (users in Japan) Store visit
Malaysia Involve Asia (users in PH, MY, TH) Redirect visit
The countries where each store operates Lazada and, where available, Shopee (users in PH, MY, TH) Store visit
Republic of Korea Hasia Co., Ltd. (our staff) Access for operating and supporting the Service, and answering your requests

How we protect transferred information. We do not rely on "by using the Service you consent to the transfer." Instead:

On request, we will give you more information about the safeguards for your country, including a copy or summary of the relevant clauses where the law requires.

Country notes:

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.

Store and affiliate sites. When you tap a product card, the page opens outside the app (in your browser or the store's app). The affiliate network (such as Involve Asia) and the store (such as Amazon, Lazada, or Shopee) may set their own cookies or similar technologies there, under their own policies. We don't control them; you can manage them in your browser or the store's app settings.

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. Stores and affiliate networks you visit through product links have their own practices (§10).

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 from ad networks. We do not use advertising SDKs and do not process advertising identifiers. Affiliate product cards are described in §2.4 and Terms §6.

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

13. Region-specific Privacy Information

The following sections add to the rest of this Policy for people in the named regions. Where they conflict with the rest of this Policy, the region-specific section applies to people in that region.

13.1 United States

13.1.1 California (CCPA / CPRA)

We provide the following rights to California residents whether or not the CCPA applies to us.

Categories collected in the past 12 months: identifiers (sign-in ID, email address, push token); internet or other electronic network activity (in-app events, product clicks); approximate location at country level only (Android store selection, not stored); inferences — none beyond the day's mood-to-product matching.

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 sign-in before acting, and respond within 45 days as the CCPA provides. You may also contact the California Attorney General or the California Privacy Protection Agency (cppa.ca.gov).

13.1.2 California Online Privacy Protection Act (CalOPPA)

13.1.3 Other U.S. states

If you live in a U.S. state with a comprehensive privacy law, you may have rights similar to those above (access, correction, deletion, portability, and opting out of targeted advertising, sale, or profiling). We honor these requests for all U.S. residents using the process in §6.2. If we decline your request, you may ask us to reconsider by replying to our response, and you may contact your state Attorney General.

13.1.4 Children (COPPA)

The Service is intended for a general audience aged 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13; if we learn we have, we delete it and terminate the account (§7). We keep a written retention schedule (Section 5) and security program (Section 8).

13.1.5 Data breaches

We will notify affected residents and authorities as required by applicable state breach-notification laws (§8).

13.2 European Economic Area and United Kingdom (GDPR / UK GDPR)

If you are in the European Economic Area or the United Kingdom, you have the rights of access, rectification, erasure, restriction of processing, data portability, and objection, and the right to withdraw consent at any time. Contact us at contact@hasia.ai to exercise these rights. You also have the right to lodge a complaint with the data protection supervisory authority in your country (in the UK, the Information Commissioner's Office).

Legal basis for processing: see the table in §3.1. In summary:

Minimum age: 16 in Germany, the Netherlands, Ireland and Luxembourg; 14 in Austria and Cyprus; 13 in the other EEA countries where the Service is available and in the UK (§7).

Controller: Hasia Co., Ltd. (details in §15) is the controller of your personal data.

Response time: we respond to rights requests within one month. If a request is complex, we may extend this by up to two further months, and we will tell you why within the first month.

Transfers: your data is transferred outside the EEA/UK (mainly to the United States and the Republic of Korea; §9).

13.3 Japan

A complete Japanese-language privacy policy (プライバシーポリシー), prepared under the Act on the Protection of Personal Information ("APPI"), is available at moonmademe.com/ja/privacy. The key items are summarized below. They supplement — and do not replace — the rest of this Policy.

13.3.1 Business operator

Item Detail
Name Hasia Co., Ltd.
Address 108-1, Gasan Mobius Tower, 169-23 Gasan digital 2-ro, Geumcheon-gu, Seoul, 08504, Republic of Korea
Representative Hyeman Lee
Contact contact@hasia.ai

13.3.2 Transfer to third parties in a foreign country

Your data is stored and processed outside Japan.

Destination country: primarily the United States. For Cloudflare, traffic may transit equipment in other countries.

Data protection regime of that country: the United States has no comprehensive, cross-sector personal data protection law comparable to Japan's APPI or the EU's GDPR. Protection is provided through sector-specific federal laws (health, finance, children), state laws such as the California Consumer Privacy Act, and the Federal Trade Commission Act §5 prohibition on unfair or deceptive practices. See the country surveys published by Japan's Personal Information Protection Commission for details.

Basis for the transfer: not your consent, but our establishment of a system necessary to ensure the continued implementation of measures equivalent to those required of a personal information handling business operator under APPI, as provided in Article 28(1) of the APPI and Article 16 of its Enforcement Rules.

Measures taken by those recipients: for the vendors we entrust with personal data (Firebase, Supabase, Resend, Cloudflare, Expo), we ensure the continued implementation of those equivalent measures by contract, terms of service, data processing agreement, or other appropriate and reasonable means — covering purpose limitation, restrictions on sub-processing, security measures, and return or deletion on termination. On our side we apply transport encryption, encryption at rest, row-level access control in the database, and least-privilege access (Section 8).

Apple and Google (sign-in) and Amazon (Associates Program) are not vendors we entrust with personal data; each handles personal information independently in its relationship with you. Sign-in happens directly between you and Apple or Google. We send Amazon no identifier of you or of your click (§2.4).

On request we will provide information about these measures, as required by law.

13.3.3 Retained personal data — your requests

Under Articles 32 to 39 of the APPI you may request:

Email contact@hasia.ai with the subject line "Privacy Request". We verify your identity using the email address associated with your sign-in. There is no fee. We aim to respond within two weeks.

13.3.4 Complaints

Please contact us first. You may also file with the Personal Information Protection Commission of Japan (PPC, https://www.ppc.go.jp/).

13.3.5 Security measures

In addition to Section 8, we note for APPI Article 23 purposes that personal data is handled in the United States; the regime of that country and the measures taken by recipients are described in 13.3.2. The Japanese policy §8 lists our organizational, human, physical, and technical measures.

13.3.6 External transmission of information

In the spirit of Article 27-12 of the Telecommunications Business Act, the information this app transmits from your device is:

Recipient Information Purpose
Firebase (Google LLC) authentication identifier, notification token, crash diagnostics sign-in, notification delivery, debugging
Supabase (Supabase Inc.) profile, daily note history, sealed letters, usage records, product clicks operating the Service
Cloudflare (Cloudflare, Inc.) request information when you tap a product link relaying to the product page
Amazon Japan G.K. (アマゾンジャパン合同会社), via our Cloudflare redirect the request information your device sends when it opens Amazon (no identifier of you or of your click from us) measuring affiliate sales

We do not transmit information externally for advertising or behavioural targeting.

13.3.7 Age

Users must be 13 or older. If you are under 18, please use the Service with the consent of a person with parental authority.

13.3.8 Data breaches

If a leak or similar incident occurs that must be reported, we will report it to the Personal Information Protection Commission and notify you, as required by the APPI (§8).

13.4 Philippines (Data Privacy Act of 2012)

This section applies to data subjects in the Philippines under the Data Privacy Act of 2012 (Republic Act No. 10173), its Implementing Rules and Regulations, and issuances of the National Privacy Commission (NPC).

13.5 Malaysia (Personal Data Protection Act 2010)

This section applies where the Personal Data Protection Act 2010, as amended by the Personal Data Protection (Amendment) Act 2024 ("PDPA"), applies to our processing of your personal data.

A Bahasa Malaysia version of this Privacy Policy is available on our website at https://moonmademe.com/ms/privacy/. The language rule in §1 applies.

13.6 Thailand (Personal Data Protection Act B.E. 2562)

This section applies to data subjects in Thailand under the Personal Data Protection Act B.E. 2562 (2019) ("PDPA") and notifications of the Personal Data Protection Committee (PDPC).

13.7 India (Digital Personal Data Protection Act, 2023)

This section applies to Data Principals in India under the Digital Personal Data Protection Act, 2023 ("DPDP Act") and the Digital Personal Data Protection Rules, 2025.

13.8 Switzerland (Federal Act on Data Protection)

If you are in Switzerland, the revised Federal Act on Data Protection (FADP) applies.

13.9 Hong Kong, Pakistan and Sri Lanka

13.10 South Africa, Nigeria and Kenya

13.11 Republic of Korea (Personal Information Protection Act)

This section applies to data subjects in the Republic of Korea under the Personal Information Protection Act ("PIPA") and its Enforcement Decree. A complete Korean-language privacy policy (개인정보 처리방침), including every item PIPA requires a privacy policy to disclose, is available in the App and at moonmademe.com/ko/privacy. The key items are summarized below. They supplement — and do not replace — the rest of this Policy.

14. Changes to This Policy

We may update this Privacy Policy from time to time, in accordance with applicable law. When we do, we will tell you what is changing and when it takes effect, before it takes effect, in the App or by another appropriate method. In particular, we will:

Where a change needs your consent under applicable law (for example a new purpose unrelated to the original ones, or new consent-based processing), we will ask for it and will not treat continued use as consent. For other changes, the revised Policy applies from its effective date; if you do not agree, you may stop using the Service and request account deletion.

15. Contact Us

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

moon made me
Operated by: Hasia Co., Ltd.
Address: 108-1, Gasan Mobius Tower, 169-23 Gasan digital 2-ro, Geumcheon-gu, Seoul, 08504, Republic of Korea
Email: contact@hasia.ai

Data Protection Officer (Philippines, Malaysia, Thailand): contact@hasia.ai

Chief Privacy Officer (Republic of Korea): Hyeman Lee (이혜만), CEO — contact@hasia.ai

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