Privacy Policy
Effective: October 25, 2026
Bird registration and preparation choice
After signing in, you register a bird or explicitly choose that you do not have a bird yet and are preparing. We store that choice and its save time in your account settings so it persists across visits and devices. Past registration deferrals alone do not establish this choice. Registration steps and preparation selection and save outcomes use existing product-interaction records, not advertising or cross-app tracking. Existing retention and account-deletion rules apply. Browsing as a guest without an account remains available.
Sign-in and first care usage analysis
We record requests to browse without signing in and displays of alternative sign-in methods using the existing random visitor identifier, so browsing choices can be distinguished from abandoned sign-in. First care notices record the number of selected items after selection changes and when the notice closes in existing feature events. We also record actual exposure of the first-record button on Home and requests to reopen the notice. Opening the notice or selecting an item alone does not save care. This analysis adds no bird names, care dates, email addresses, authentication details or free-form input. Member events follow the existing account-linking and account-deletion rules.
Feedback reply read receipts
When an operator reply is displayed in a signed-in user's feedback conversation, we store the account, reply ID and first confirmation time so the team can see whether the reply was viewed. Fetching the conversation alone does not mark it read. Receipts are not public and are deleted with the message or account. They are not used for advertising or tracking across apps.
International lost and found bird alerts
We index public RSS feeds and listings from ParrotAlert and Japan’s Inkosuki, storing country, region, bird species, event date, report category, source URL and check times. We do not store reporter names, contact details, ring numbers, precise coordinates, full post text or image files. A new visit starts in the connection country, with domestic reports for Korea or an unknown country. A selected search country lasts only while that screen is open; earlier searches and community country filters are not used as defaults. Regions and search terms are excluded from feature telemetry. We request no current location or new permission. Photos and contact methods remain on the source site, whose policy applies when you open its link. This public index is also available in the United States. The US restriction on lost-bird flyers refers to moimoi’s own reporting, flyer and location features.
Places we visited · private trip memories
Members store trip dates, country and region, optional place names and coordinates, companion bird IDs and name/species snapshots, and optional notes and photos on their account. Photos use private storage and ownership-checked access; records are not automatically posted to the community. Guest records stay on the device and are saved to an account only after explicit import and bird matching. Removing a bird profile preserves its name/species in past trips; account deletion removes trips and photos. Current location is requested only when chosen.When a member starts a trip from photos they pick, the shot date and location are read on the device only to fill in the form and are not sent to the server; uploaded photos are re-encoded and keep no location data. When a country and region are filled in from a photo location, only approximate coordinates rounded to two decimals are sent to the map provider (Google); exact coordinates and photos are not sent. The map provider may process coordinates to display selected places. Members can add one video of up to 30 seconds and 50 MB per trip (the length is checked on the device). The video and its preview image are sent straight from the device to private storage; to play it we check ownership and issue a temporary address that is valid for one hour. The video is stored as is, so the file may still contain shooting location and time metadata. When you delete the video, the trip or your account it can no longer be played right away, and the storage files are removed within two hours and five minutes. Trip content, photo URLs and coordinates are excluded from feature telemetry.
Public community authors
Author names on public posts and comments link to author pages that can be read without signing in and by search engines. These pages show only the name already displayed in the community and that author's public posts. Account IDs, email addresses, private group posts, bird profiles and private records are not displayed. No additional account identifiers are collected or published.
Guest community questions
You can post text questions without signing in. The title, body, topic and posting time are public in the community and on shared pages. You choose a management password immediately before posting; the server stores only an irreversible verification value. Protected cookies and a server-stored writer verification value let you return, edit and delete in the same app or browser. A signed cookie recovery credential is kept in that browser for up to one year. On another device, verifying the question's password grants access to that question only; the management cookie lasts up to one year. Writer and password verification values are never public. Question content, passwords and recovery credentials are excluded from feature telemetry. Deleting a question removes it and its verification values. Guest questions are not automatically linked to a member account, so account deletion does not replace deleting the question separately. To limit excessive requests, we process a keyed transformation of the IP address and remove rate-limit records older than one day during subsequent requests. Raw IP addresses are not stored in the rate-limit table.
Guest connection-country and return-visit analytics
When guest-entry and sign-in requests arrive, we store only the connection-country code with the existing random visitor identifier to analyze country-level usage and return visits. This analysis does not store IP addresses, cities or precise locations. Connection country does not mean nationality or country of residence. Clearing storage, reinstalling or using another browser can change the identifier. Missing countries in historical records are not filled retrospectively.
International public community posts
We use AI (OpenAI) to publish brief paraphrases of companion-bird questions from public feeds and official public APIs and retain source URL, site, language and feed timestamp. We do not import authors’ accounts, photos or private posts, or infer their country. Device language settings are used locally to choose the community translation target.
Public-post translation quality correction
We do not request automatic translation for same-language posts or when a user in Korea reads a Korean user's domestic post. Verified translations are reused. For public posts and comments that fail translation checks, the title and body may be sent to one or both of OpenAI (United States) and Anthropic (United States, Claude) at the time of the request for language conversion and meaning correction. Account identifiers, coordinates and authentication tokens are not sent separately, but information you wrote in the public text may be included. Private groups are excluded. If the corrected result also fails validation, the original is shown. See openai.com/policies/privacy-policy/ for OpenAI's processing policy and anthropic.com/legal/privacy for Anthropic's.
Country and region priority and public-post translation
We save your chosen home country and consented coarse area to your account to show public posts from the same area and country first. We do not infer residence from interface language. New public posts may record the country and coarse area at posting time. When translation is enabled, translations of posts and comments are stored separately, invalidated or deleted when the source is edited or deleted, and can be switched to the original. Private group posts are excluded from this public-post translation feature.
1. Information we collect
When you use the iOS app without an account, we do not collect login identifiers. Depending on how you sign up (sign in), we process the following. Kakao: [Required] Kakao member ID and nickname; [Optional] profile image (if you consent). Apple: [Required] Apple member ID, name (Apple provides it only on your first sign-in), and email address (an Apple relay address if you choose Hide My Email). Google: [Required] Google member ID, name, email address, and profile photo. Email sign-up: [Required] email address. The nickname or name and the profile image or photo we receive are only the starting values of your profile, and you can change them in the app. If no name is provided, the part of your email address before the @ becomes your starting nickname. The email address used for Apple, Google, or email sign-in is stored with your account so that another sign-in method using the same email address connects to the same account. Kakao sign-in does not use Kakao's email consent item, so we do not receive an email address from Kakao. When you sign up, we read sign-up source details from that request and record them with your account: app or web, device type (iPhone, iPad, Android, or desktop), the referring app (the in-app browser marker of Instagram, Threads, Facebook, KakaoTalk, NAVER, LINE, and similar apps) or referring website domain, and the connection-country code. These are separate from the test sign-up source in section 1-5. For every sign-up method, [Optional] gender and age group: you can choose them yourself after agreeing on the first screen of an account with no birds yet (Sign-up details) or in Edit your profile (☰ Menu > My birds > Your account > Edit), or Kakao can provide them if you give optional consent when signing in with Kakao. Accounts that start by registering a bird or by accepting a family invitation do not see that first screen and can enter them in Edit your profile. Age is received only as a range such as 20s, and we do not collect your exact birth date. Values from Kakao only fill empty fields and never overwrite values you changed or deleted in the app. You can sign up and use every feature without agreeing or choosing. We also process bird information you enter (name, species, sex, birthday, date you started living together, optional weight and measurement date, leg band details (whether banded, engraving, color, which leg, and type), rainbow-bridge status, and optional date), session start and end times, time spent by screen, page views, button clicks, and save results. Even without an account, we may collect a random session ID, the stage reached in new features (view, attempt, success, failure), error categories, and app or web and operating-system categories. These feature events do not include the keeper’s age range or gender, bird names, weights, dates, or draft text. When you use moimoi without an account or the sign-in screen is shown, we store a random visitor ID in your browser or app storage and record, with that ID, when the sign-in screen is shown, which sign-in method you chose (Kakao, Google, Apple, or email), and the sign-in result (success, or a cancelled, error, or timeout category). When you sign in, that record includes your account, which links your pre-sign-up use to the account. These records do not include email addresses, names, authentication tokens, or raw error text. The visitor ID is removed when you clear browser storage or delete the app, and the record that links it to your account (the sign-in success record) is deleted when you close your account. In the signed-in native app, we process a random installation ID, operating system, app version, and last check time for update notices and compatibility checks. When you upload a photo or video, we process the media file, format, size, dimensions, and purpose. The microphone is used only when you record a video directly in the app, and the sound in that video is uploaded with it. We do not collect keystrokes or the text of posts you are still writing as activity records. When you request moimoi × mereal physical stickers, we process the recipient name, phone number, shipping address, depositor name, memo, and the original print-quality photos you attach (including your bird's moimoi character image if you choose to send it).
Location request diagnostics
If a location request fails, we add only the failing step (permission check, permission request, or position lookup) and a predefined native error code to existing feature usage records. Coordinates, place names, and raw device error messages are not stored in these diagnostics.
1-1. App-store redirect information
When an app install link sends you to an app store, we process only the link-source code, operating-system category, and aggregate click total by UTC date. We do not store IP addresses or user, device, or installation identifiers, and do not connect these clicks to a signed-in account or an actual install or sign-up. Repeated taps by the same person may each be counted.
1-2. Pre-launch Android notification requests
Before the Google Play release, we processed an email address when you explicitly requested a launch notification. We no longer accept new requests. Existing request information is deleted after one public-launch notice is sent or a withdrawal request is handled, and a request linked to a signed-in account is also deleted with that account.
1-3. Community post views and saves
When a signed-in member opens a post, we record the account, post ID and first-view time to display a count of unique viewers. Viewer identities are not public. Saving a post records the account, post ID and save time to show a private saved-post list. Unsaving deletes the save record. Deleting the post or account deletes its associated view and save records.
1-4. Optional reason for using the app
After sign-in, you may choose multiple reasons why you are using moimoi: bird care and records, food and health information, vets and bird cafés, community, or exploring. You may skip. We use responses for product-use analytics. No free text is collected and an answer is not required to use the app. Responses are stored in account preferences and feature-use records and deleted with the account, except that the deletion record in section 3 keeps them for one year after the account deletion date.
1-5. Saved test results and sign-up source
Web test answers and results are kept in the same browser for 7 days so you can continue after signing up or signing in. Retaking the test or clearing browser storage removes them. When you press sign up or sign in on a result screen, a cookie keeps the test type and whether you started from a share link for 7 days. If you first create an account during that window, we record those categories as its sign-up source. Existing-member sign-ins are not counted as new sign-ups. Raw answers and results are not included in sign-up-source analytics logs. Account-linked source information is deleted with the account.
1-6. Food browsing and diet analytics
We record visible food sections and product cards, visible time, catalog product IDs and categories, result counts, add/remove actions, amount entry status and validity, composition counts, check/save outcomes and the last activity step. These records are linked to signed-in accounts or guest sessions for product improvement. Food search terms (up to 200 characters), selected or custom food names (up to 100 characters), exact daily grams and per-product composition on diet check/save are also recorded for analytics. The editable diet stays in your browser. Across the service we record navigation, visible time, scroll depth, button/link/form actions, whether fields are filled, data API paths, status, latency and error occurrences. Passwords, authentication tokens and API request bodies are not collected in these analytics.
1-7. Family care sharing
Accepting an invitation shares the selected bird’s food and water records, family-only photos, videos and notes, author names and times, and lets you add records. Rooms can share records and chat messages for multiple selected birds. Pinned care guides and record comments are also shared; comments inherit the parent record’s visibility. Temporary caregivers can access today’s food/water status, records, photos and comments shared for care within their assigned period, and guides explicitly shared by the owner, only from the start until before the end. Family-only records remain private. Invitations, the relationship chosen when inviting (family, partner, friend or temporary caregiver), the start and end times, record visibility, permissions, notification preferences and read status are stored with accounts. Unselected birds, location, leg-band inscriptions and documents are not shared by this feature. Family photos and videos use private storage and each retrieval checks current membership. Leaving or revoking sharing ends access, while the food/water records, photos and notes you added stay on that bird with your name. While sharing you can delete your own photos and notes, and the owner who registered the bird can delete remaining ones. Your photos, videos, notes, comments, chats and membership are deleted when you close your account. Factual food/water records on another caregiver’s bird may remain without your account identity. File cleanup follows immediate access removal. System notifications contain no photos or note text.
1-8. iOS and Android care widgets
To improve the widget, existing feature usage records include whether a care widget is configured, its size when the app opens, and the result of opening feeding records from the widget. These statistics exclude bird names and identifiers. We do not collect widget impressions.
1-9. Report and block records
When you report a post we store the reporting account, the post and the reason; when you block a user we store the blocking and blocked accounts. We use them to handle reports and blocks and to hide blocked users’ posts. A report record is deleted together with the reporting account or the reported post, and a block record is deleted when either the blocking or the blocked account is deleted.
2. How we use information
We use information for sign-up and member management (identifying members and registering member details), profile display, per-bird record management, community reports and blocks, error investigation, and service safety. Optional gender and age group are used only to register and manage the optional member details you provide and, within that scope, to analyze usage and churn by age group and gender. They are not used for ad targeting, shared with third parties, or used to make age-restriction decisions. Physical-sticker request details are used by mereal (ttukttak company, the same business entity as moimoi) to make the stickers, confirm the deposit, ship the order, and answer inquiries.
Diet account storage
For signed-in users, bird diets (products and entered amounts) and up to 20 saved checks are stored in Supabase with the account. They can be restored on another device and reviewed by operators for support. Deleting a check syncs to the account; account deletion removes these records.
3. Retention and deletion
Gender and age group are stored in Supabase while your account remains active, and you can delete them or withdraw consent at any time in Edit your profile (☰ Menu > My birds > Your account > Edit). Deleting removes the values and keeps only a mark that you deleted them so that the next Kakao sign-in does not fill them again. When you delete gender or age group in the app, we ask Kakao to withdraw consent for that item. Even if that request does not go through, the app does not save those values again, and you can withdraw optional consent given through Kakao sign-in yourself in your Kakao Account's connected services settings. If you withdraw consent in your Kakao Account, the next time you sign in with Kakao we delete the values of fields that came from Kakao rather than ones you chose yourself in the app. The consent record keeps the time and screen of your consent (Sign-up details or Edit your profile), the notice version, and whether you chose each field's value yourself in the app, records the time and screen of a withdrawal separately, and when you consent again, keeps up to the 10 most recent earlier records with it. The consent record is kept with your account and deleted when you close your account. Activity events and session records are stored in Supabase for service improvement and security checks. Profiles, photos, and care records kept for a bird that has crossed the rainbow bridge are retained until you permanently delete that bird or your account. Other image files and file details are kept until the linked content or account is deleted, and your coarse area until you update it or delete your account. When you close your account, account, raw activity, session, device-version, location, and image information with no legal retention requirement is deleted promptly. However, to understand why people leave and to improve the service, we keep the following deletion record and delete it one year after the account deletion date: user ID, nickname (if you never changed it, the nickname or name received at sign-up or the part of your email address before the @), bird profile summary (name, species, rainbow-bridge status, registration time), sign-in provider name, sign-up and deletion times and length of use, number of birds, posts, and comments, last access time, sign-up source details (app or web, referring in-app browser or website domain, connection country), whether it was an internal or test account, whether the app was installed (push device registration history), the visit reasons you chose, age-group and gender categories (including the deleted mark), a deletion-reason code, counts by event type, screen tab, and feature with their stages (view, attempt, success, failure) and the last operation type and stage per feature for the seven days before deletion, the sequence of the 20 most recent features (feature, operation type, stage, error code, app or web, operating system, time before deletion), and the last event and feature (including operation type and stage) with their times. We do not keep email addresses, provider member IDs, session IDs, profile photos, post or comment text, or raw input from feature usage records. Signed-in users can delete their account and saved records from ☰ Menu > My birds > Notifications and privacy > Delete account. Original photos and shipping details from sticker requests are kept in private storage and deleted once they are no longer needed for production, shipping, and dispute handling; contract and payment records are retained for five years under the E-Commerce Act.
4. Third-party sharing
We share information only with the service providers that help us run moimoi, such as hosting, database, crash and install analytics, push delivery, map, weather and advertising providers, each described in this policy (see sections 7 to 8-1 for what is sent to each), and when required by law or with your consent. Information you choose to make public, such as a lost-bird flyer, is visible as described in the section about that feature. We do not otherwise provide personal information to anyone else.
5. Your rights
You may request access, correction, deletion, or withdrawal of consent for your personal information.
6. Location information
Nearby stories and clinic features update your current location only while you view the map after giving consent, showing your position and distance-sorted results. Updates stop when you leave the map. In Community, coordinates are converted to a region name only when you tap My location and consent. For this feature, exact coordinates are not stored in the database or shown to other users. The point you choose in a missing-bird report follows section 6-1. We store state or province, city or district, neighborhood, and a coarse map center; the admin view shows only state or province and city or district.
6-1. Missing and found-bird flyers
You can post without signing in. Guest ownership uses a protected first-party browser cookie (up to one year) and its server-stored hash, not advertising tracking or a member account. A signed writer recovery credential is also kept in this browser’s local storage for up to one year, allowing the original writer’s access to be restored if the cookie is lost; no device serial number is used. New lost and found reports are notified to all eligible devices that allow app and lost/found notifications, with a link to the report. Guest management passwords are stored only as salted hashes. Guests can use the flyer link and password to edit, delete or mark a reunion on another device. After verification, a signed management cookie lasts up to one year. To limit repeated attempts, we retain a keyed hash of the connection IP and attempt counts, regularly removing records older than one day; raw IPs and passwords are not stored or sent to usage analytics. For an older report without a password, the original app or browser can set one. If you lose the password, writer cookie and saved recovery credential, contact support with the flyer link. When you post a missing-bird report or a found-bird notice, we store the bird’s name, species and appearance, leg-band details, photos and videos, when it went missing or was found, a place name and note, optional contact details (phone number and open-chat link; missing-bird reports also store a reward note), and the coordinates of the point you pick on the map. Coordinates are stored as exact values; for found-bird notices they are rounded to two decimal places when shown. Signed-in users can see the point and distance of flyers that are still searching in the app’s list and map. Contact details of flyers posted by other people are not included in the app’s list and appear only on the flyer page (you can see the contact details of your own flyers). The leg-band number on a found-bird notice is hidden in public views and lists. Anyone with a flyer’s share link (moimoi.space/lost/ followed by the flyer code) can open it without signing in. While a flyer is searching or looking for the owner, the contact you entered is public as the flyer’s contact buttons, and flyers that users post as missing may appear in search engines. The data behind a public flyer page does not carry exact coordinates, and contact details are removed from flyers that have returned home or ended. Contact details can be left blank (a found-bird notice needs either a phone number or an open-chat link). When someone leaves a sighting, its note, photos, place name and sighting time are public on the flyer, while the reporter’s name and contact are visible only to the flyer’s author. If a map point is chosen when reporting, its coordinates are also stored and are not shown in public views. A sighting made while signed in is linked to the account, and the nickname is used as the name if the name is left blank. When a sighting arrives, the flyer’s author gets a notification that includes the bird’s name, the place and part of the sighting. A flyer is deleted together with its author’s account. A sighting left on someone else’s flyer can remain on that flyer, with the link to the reporter’s account removed, even after the reporter deletes their account, and the name and contact written in the sighting can still be shown to the flyer’s author; contact us under section 9 to request deletion.
7. External map and weather services
We use Google Maps Platform for community and veterinary maps and OpenStreetMap Nominatim to convert location into a region name. To reflect weather on the home screen, only inside the Korea Meteorological Administration forecast area (the Korean Peninsula and nearby waters), we send an approximate location (coordinates rounded to about 10 km) to the Korea Meteorological Administration public data service, never your exact coordinates. Outside that area, including in the United States, your location is not sent for weather. Device, location, and usage information may be processed under each provider's policy while loading maps and resolving regions. Accounts, activity, and images are stored in Supabase databases and storage.
7-1. Crash diagnostics (Firebase Crashlytics)
If the Android app closes unexpectedly or stops responding (ANR), we send the time of the event, the code location (stack trace), app version, device model and OS version, app state such as memory usage, a random installation identifier generated by Crashlytics, and the Firebase installation ID and session ID to Google through Firebase Crashlytics, to investigate the cause and keep the service stable. This data does not include raw user input such as names, email addresses, or post text, and it is not linked to your sign-in account. Because it is not linked to your account, it is not deleted when you close your account; Google keeps it for 90 days before starting deletion (firebase.google.com/support/privacy).
7-2. App install and removal analytics (Google Analytics for Firebase)
We use Google Analytics for Firebase to process the Android app's first launch after installation (first_open), app removal (app_remove), and basic app-use information such as app version and operating system, so we can analyze install and removal trends and app quality. The install metric is recorded when the app is first opened after installation, not when it is downloaded, and app removal is an Android-only statistic. We do not set your signed-in account's user ID in Google Analytics, and we disable advertising ID collection and personalized-advertising signals for this analytics use.
7-3. Web analytics (Google Analytics 4)
On the web used in a browser (moimoi.space), we use Google Analytics 4 to analyze visit and navigation statistics to improve the service, and we entrust this analytics processing to Google LLC. It is not used in the app or on operator screens. On your first visit, analytics cookies (_ga and cookies starting with _ga_, up to 2 years) are stored in your browser. Together with the random identifier in these cookies, we process the page URL and title you visit, the previous page URL, usage records such as navigation, scrolling, outbound link clicks, file downloads, embedded video plays, and form starts and submissions (excluding what you type), browser, operating system and device type, screen size, language, and an approximate country- or city-level location inferred from your IP address. Google Analytics 4 does not log or store IP addresses. We do not send your signed-in account's user ID, name, or email address, we do not use Google signals or ad personalization signals, and analytics is not loaded on a screen whose address contains sign-in credentials. This information is sent over the network to Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA) each time you use a web page, processed in the United States and other countries where Google has servers, and user- and event-level data is deleted after 14 months under our Google Analytics settings (aggregated statistics that do not identify you are excluded). Because it is not linked to your account, it is not deleted when you close your account. You can refuse this collection and transfer abroad by blocking or deleting cookies in your browser settings and installing the Google Analytics Opt-out Browser Add-on (tools.google.com/dlpage/gaoptout); refusing does not limit your use of the service. See Google's privacy policy (policies.google.com/privacy) for how Google processes data and how to contact Google.
7-4. Community AI helper replies
New community posts may receive a reply written by the “AI helper”, labeled “AI”. It is not written by a person and is not a diagnosis or prescription. To write a reply we send the post’s category, title and body, the comments already on it, the name and species of birds linked to the post, and frames taken from attached photos and videos to Anthropic (United States) for processing with Claude. We do not separately send account identifiers, sign-up email addresses or authentication tokens, but anything you wrote yourself in posts and comments is included as written. While a reply is being written, photo and video frames are stored temporarily in a working folder on moimoi’s operating device and are deleted when the task ends. See anthropic.com/legal/privacy for how Anthropic handles data.
7-5. Other external services
We use Vercel for web hosting, and Firebase Cloud Messaging (Android) and the Apple Push Notification service (iOS) to deliver push notifications. If you allow notifications, we link your device’s notification token, platform (iOS or Android), app type, whether it is active and when it was last seen to your account and send notifications with it; these are deleted when you leave the service. We use Kakao’s Daum postcode search for sticker addresses and Coupang Partners affiliate links for food shopping. Tapping a Coupang link takes you to Coupang, where your information may be processed under Coupang’s policies. Depending on where these services’ servers are, information may be processed outside Korea.
8. Advertising
The web (care guides and app screens used in a browser) may show Google AdSense ads, and the app may show Google AdMob banner ads, rewarded ads that you choose to watch, and a short interstitial ad right before a test result opens. Rewarded and interstitial ads are requested in non-personalized mode, and other ads are non-personalized if you decline app tracking; while an ad loads, device, browser, approximate location, and usage information may be processed under Google's policies. Web ads are never shown inside the app, and no ads appear on lost-bird reports, veterinary screens, or emergency and toxicity guides. Rewards for completed rewarded ads are limited to in-app digital items such as one bird-collection card you don't own yet or one extra throw in a wild-parrot encounter; we never grant cash or Moi points as payment for watching an ad (the completion reward you receive when an ad card completes your collection is a collection reward that does not depend on how the card was obtained). To enforce the daily limit, we record on your account the date you watched the ad and the card you received for it. Interstitial ads are not shown on the first test result you see and are limited in daily count and spacing; to do this, the times and number of interstitial ads shown are stored only on this device. See Google's privacy policy (policies.google.com/technologies/ads) for details on ad data.
8-1. For users in the United States
If you open moimoi from the United States, the app first asks for your birth year and month. We use the answer only to place you in an age range (under 13, 13 to 17, or 18 and over) and we do not store your birth date. The age range alone is kept in a signed cookie named moimoi_age_band for 365 days, and in your account record if you create an account. Under 13: you cannot create an account or sign in. Visitors under 13 can look around in a read-only guest mode in which photo, video and audio uploads and location features are turned off. Like any website, our hosting provider receives technical information such as your IP address and device type when your device loads a page, and we use it to run and secure the service. If you are a parent or guardian and believe your child under 13 has given us personal information, contact us at the address in section 9 and we will review your request and delete the child's personal information we hold, except what we must keep to meet a legal obligation. Analytics: before the age question is answered, and for users under 13, we do not run our own usage analytics or advertising. We also do not run our own usage analytics or app ads for users aged 13 to 17, and we do not turn on Firebase analytics or crash reporting in the Android app for them. In the United States we do not use Google Analytics 4 or Google AdSense on the web. App ads: in the United States, app ads are shown only to users aged 18 and over and are requested as non-personalized ads, we do not offer ads you watch for rewards, and where Google's consent tool requires it you can reopen your ad choices from the app menu under Ad privacy settings. Ages 13 to 17: the app does not request high-precision or continuous location. Notifications: we do not send promotional push notifications to accounts created through the United States age check. Features offered in Korea only: the community, lost-bird flyers, trip memories (Places we visited), the AI helper replies in the community, and Coupang shopping links are not offered in the United States. If this section says something different from another section of this policy, this section controls for you in the United States.
9. Contact
Privacy questions and harmful-content reports: jaehwankim07120@gmail.com