Privacy Policy
Menglegi processes only the information it needs to let you create, and lets you manage your own information and content.
This is an English translation. The Korean version (개인정보 처리방침) is the original. If the two versions differ, the Korean version prevails.
1 Information we process and why
The features that run on your device without signing in work without any account information. If you choose to sign in, back up to our server or use community features, we process the information below.
2 How we collect information
- Information the account provider sends when you complete Google or Apple sign-in
- When you enter a profile, upload, post, comment, message, report or inquiry yourself
- Diagnostic and usage information that the Firebase SDK generates automatically so we can check app stability and usage flow
- Advertising, device, diagnostic and consent information that the Google AdMob and Google User Messaging Platform SDKs generate automatically, or that you choose, to provide ads and manage consent
3 Third-party services and processing infrastructure
To the extent needed to provide the service, we use the infrastructure of the providers below. Each provider processes information under its own privacy policy and contracts. Menglegi does not sell personal information.
- Apple, Google, Firebase — sign-in, usage analytics, crash and performance diagnostics
- Google AdMob — serving third-party ads, measuring ad performance, analytics and fraud prevention
- Google User Messaging Platform — asking for consent where local law requires it, storing your consent choices and providing ad privacy options
- Cloudflare — image storage and delivery, DNS and web security
- Oracle Cloud Infrastructure — operating the API and the database
When it serves and measures ads, Google AdMob may process the advertising, device, interaction and diagnostic information listed in the table above, for the purposes shown for each item. The Menglegi app does not ask for AppTrackingTransparency (ATT) permission, and does not use the information it collects to track you across apps or websites owned by other companies.
Where the relevant law requires it, we ask for advertising and privacy consent through Google User Messaging Platform and store your choices.
When these services use their global infrastructure, information may be processed outside the Republic of Korea. Transfers use encrypted connections and are limited to what is needed to provide the service.
4 Retention and deletion
- We keep account information and content you saved on the server while your account remains active.
- If you delete your account in the app under MY → Account → Delete account, we disconnect your sign-in link, anonymize your profile, make your posts, comments and uploaded content no longer visible in the service, and proceed with deleting the original files.
- Information to be deleted that remains in operational backups expires within 30 days at most, depending on the backup cycle.
- Records of reports and abuse prevention are kept for up to 3 years, to the extent needed for dispute response and service safety, and then deleted.
- If the law requires us to keep information for a different period, we keep it separately for that period.
5 Your choices and rights
In the app, you can edit your profile, delete the materials you saved or your posts, and delete your account yourself. You can make your advertising and privacy consent choices when we first ask, and you can manage them again later in the app under MY → Ad privacy settings.
You can send requests to support to access, correct, delete or stop the processing of your personal information. After we confirm that the requester owns the account, we reply without delay.
Make a privacy request6 Website advertising
Google AdMob ads appear only in the Menglegi iOS app. This public information website does not show any ads, including Google AdSense, and does not use any ad SDK.
7 Security measures
- We use encrypted HTTPS connections for sign-in and API communication.
- We store session information in the iPhone Keychain, and we keep original uploads in private storage, not in a public bucket.
- We limit access permissions, upload size and request rates, and we separate the access scope of operational data and backups.
8 Contact and changes
Send privacy questions to the address below. If this policy changes, we update the effective date and the changes on this page.
[email protected]