Korean policy · The Korean policy governs notices to users in South Korea. If a service agreement and this policy differ, the term more favorable to the data subject applies where required by law.
MOADAY Privacy Policy
linqen (the “operator”) provides MOADAY, a project-first schedule service. This policy covers both the Android app and the moaday.site web app.
1. Information, purposes, legal bases, and retention
| Category | Information | Purpose and basis | Retention |
|---|---|---|---|
| Google sign-in and account | Firebase user ID, name, email, Google profile-photo URL, provider data, IP address, user-agent, platform and app identifiers | Authentication, account identification, security, and service delivery; necessary to enter into and perform the service agreement | Until account deletion. Firebase deletion and backup removal may take up to 180 days; authentication IP records may be kept for a few weeks under Google's policy |
| MOADAY profile | Chosen display name, optional cropped and resized profile image stored as a 160×160 WebP file, update time | In-app identity and cross-device sync; contract performance | Until changed or the account is deleted |
| Projects, events, memberships | Project name, color, icon, owner/member IDs; event title, date, time, completion status, author ID; display name and timestamps | Save, share, and synchronize schedules at the user's request; contract performance | Until the item, project, membership, or account is deleted |
| Invitations | Ten-character code, project ID/name, owner/creator ID, active status, creation and expiry time | Invitation and joining requested by users | Becomes unusable after seven days and is deleted no later than the next monthly retention sweep |
| External task links | Private 32-character link token; recipient and requester display names; project and task titles; due date/time; instructions; response status and optional response; creator ID, active status and timestamps | Deliver one task and return progress or results without requiring the recipient to create an account; contract performance and the sender's request | Link access ends when stopped or after 30 days. The record is deleted no later than the next monthly retention sweep, or earlier when its project or sender account is deleted |
| Policy acceptance | Community Guidelines version and acceptance time; per-account device marker | Evidence of UGC safety-policy acceptance and service operation | Until account deletion |
| Safety reports and blocks | Reporter, target user, project and content IDs; target type, reason, optional details, block choice, status and time; blocker/blocked IDs and source project | Moderation, abuse prevention, user protection and terms enforcement; legitimate interests and legal obligations | Up to 24 months from submission or creation, then deleted no later than the next monthly retention sweep. A user's outgoing blocks are deleted earlier when that account is deleted. Only information subject to a legal hold or active dispute is retained separately as required |
| Optional usage and error analytics | General actions and screens, app version/language, app-instance/device data, coarse IP-derived region, fixed error source/class/current screen, synchronization result and duration ranges. No project or event names, email, user ID, raw error messages, stack traces, referrers, or page URL query strings are added | Product improvement, synchronization reliability, and error diagnosis; separate consent | Up to two months under the current Google Analytics user/event retention setting. Withdrawal stops new optional events; aggregate reports may not be affected by that setting |
| Optional public website analytics | Allowlisted English/Korean public page paths, page language, web-app or Google Play button category, browser/device analytics data and coarse IP-derived region. No entered text, account ID, project data, private-link tokens, query strings, fragments, or referrers are added | Understand public page visits and app-download/opening choices; separate browser-level consent | Google Analytics user/event data up to two months. The public-site consent choice and its separate analytics cookies expire after 60 days; withdrawal stops collection and removes those analytics cookies |
| Essential security and access data | Firebase Installation ID, App Check/reCAPTCHA or Play Integrity tokens and limited device/app metadata, web IP and request information | Request verification, abuse prevention, and web delivery; contract performance and legitimate security interests | App Check token up to seven days, replay-protection token up to 30 days; Hosting IP records for a few months under Google's policy; otherwise under provider policy or until account deletion |
| Support, rights, deletion requests | Sender email, request, handling record and reply | Customer support and fulfillment of privacy/deletion rights | Up to 12 months after completion; longer only as necessary for an active legal dispute |
MOADAY does not display in-app advertising; request an advertising ID, contacts, payment data, precise GPS location, camera, or microphone access; or sell personal information. Do not put health, biometric, political, government-ID or other sensitive information in project fields. MOADAY does not require such information, make it public, or separately process pseudonymized data.
2. Collection and choices
- Required account processing begins when you select Google sign-in. You can refuse by not signing in or by deleting the account, but core login and synchronization will not work.
- Profile, project, event, invite, external-task, and report information is collected when you enter it or use the feature. A recipient's response is collected when that person opens a private task link and submits an update.
- Usage/error analytics is denied by default per account and begins only after a separate opt-in. You can withdraw in Profile without losing core service access.
- Public website analytics is off until you accept its separate notice. You can decline and continue, or change your choice using Analytics preferences on a public page. This choice does not grant analytics permission to an app account. We do not reconstruct activity that occurred before consent.
- App Check and web reCAPTCHA v3 may run before sign-in to protect the service.
3. User-directed sharing
| Recipient | Information | Purpose | Duration |
|---|---|---|---|
| Authenticated members of your project | Display name, project/event content and status, internal member/author IDs | Schedule collaboration and sync you requested | While the project or membership exists |
| Signed-in person to whom a user gives a valid invite code | Project name and invite metadata before joining; project data after joining | Invitation confirmation and joining | Until invite expiry/deletion or membership termination |
| Person holding a valid private external-task link | Requester and recipient display names, project/task title, due date/time and instructions. The person may return a status and optional response; no project membership list or other project events are provided | Task delivery and feedback requested by the sender | Until the sender stops the link or 30 days after creation, whichever comes first |
Share codes and private task links only with people you trust. Anyone who receives or is forwarded a still-valid task link can open that one task and submit a response. MOADAY does not sell or disclose information beyond this user-directed sharing except where law requires it or urgent protection of life and safety permits it.
4. Processors
MOADAY's core stack includes Firebase Authentication, Cloud Firestore, Firebase App Check, Firebase Hosting, and Firebase Installations.
| Processor | Task |
|---|---|
| Google LLC, the applicable Google Cloud contracting entity, and published subprocessors | Firebase Authentication, Cloud Firestore, Firebase Hosting, Installations, App Check, reCAPTCHA/Play Integrity: authentication, storage, sync, web delivery, and security |
| Google LLC | Google Analytics for Firebase app/web usage, reliability, error, and public website analytics for users who separately consent |
| Google Asia Pacific Pte. Ltd. and Google Workspace subprocessors | Send and store support, privacy-rights, and deletion-request email at contact@linqen.co.kr |
We contractually limit processing to its purpose and require access controls, safeguards, incident notification, deletion, and subprocessor oversight. See Google's current Firebase and Workspace subprocessor lists.
5. International transfers
| Recipient/contact | Information | Country | Time/method | Purpose/retention |
|---|---|---|---|---|
| Google LLC and applicable Google Cloud contracting entity Privacy contact | Account ID, name, email, photo URL, IP, user-agent and app data | United States | Encrypted transfer during sign-in/authentication | Firebase Authentication; until account deletion, removal up to 180 days, IP a few weeks |
| Google LLC and applicable Google Cloud contracting entity Privacy contact | Profile, project, event, membership, invite, external-task, report, block and request data | United States (Firestore multi-region nam5: Iowa/Oklahoma, witness South Carolina) | Encrypted transfer during storage and sync | Cloud Firestore; periods in section 1, deletion/backup removal up to 180 days |
| Google LLC and published subprocessors Privacy contact | Installation ID, integrity/reCAPTCHA tokens, IP, limited device/app and web-request data | United States and Google global infrastructure countries | Encrypted transfer during access and verification | Hosting, Installations, App Check and reCAPTCHA; essential security periods in section 1 |
| Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA Analytics privacy contact | Optional analytics described in section 1 | United States and countries where Google Analytics processes data | Encrypted transfer after consent when events occur | Product improvement/error diagnosis; user/event data up to two months |
| Google Asia Pacific Pte. Ltd., 70 Pasir Panjang Road #03-71, Singapore 117371 Workspace privacy contact | Email, support/privacy/deletion request and handling record | Singapore, United States, and published subprocessor countries | Encrypted transfer when email is sent or received | Handle requests; up to 12 months after completion, provider deletion up to 180 days |
You may refuse required Firebase transfers by not signing in or deleting the account, but login, storage, and synchronization will be unavailable. You may deny or withdraw optional Analytics transfers without affecting core service.
6. Deletion
We delete information when its period expires or its purpose ends. A least-privilege operator runs a monthly retention tool that calculates legacy and current invitation, external-task, report, and block expiry from creation/expiry timestamps and deletes expired records after a dry-run review. Other Firestore documents and the Firebase Authentication account are removed through deletion APIs; localStorage entries are erased in the app; and the offline cache is scheduled for clearing on the next launch after account deletion. Electronic records are logically deleted so they are no longer available through the service, and provider backups expire through their rotation. Any legally required record is separated and used only for that obligation.
7. Cookies, local storage, and offline cache
- The web app may use cookies or browser storage for Firebase Auth, reCAPTCHA v3/App Check, language, Guidelines, onboarding, and per-account analytics choice. Firestore may use an offline cache of up to about 40 MB.
- Public pages save an optional analytics choice in browser storage for 60 days. Only after consent, Google Analytics uses separate cookies prefixed with moaday_landing for up to 60 days. Analytics preferences lets you withdraw without affecting sign-in, project data, or app-account consent.
- Android may store Firebase Installation/App Check data and app settings. If you enable schedule reminders, their time, title, and project name are scheduled locally on that device and are removed or replaced when schedules change. MOADAY data is excluded from Android cloud backup/device transfer.
- You can block or clear cookies/site data in browser settings or clear app storage in Android. Blocking essential Auth/App Check/Firestore storage can prevent sign-in or sync. Analytics can be declined independently in Profile.
8. Your rights
You may request access, correction, deletion, restriction or cessation of processing, and withdraw optional consent. You can edit your name/photo and delete the account in Profile. If you cannot use the app, email contact@linqen.co.kr from the Google email used for MOADAY. Do not send passwords, invite codes, or private task links. We may verify identity or authority, respond within the period required by applicable law, and explain any lawful limitation and available appeal route. MOADAY is intended for adults aged 18 or older; a lawful representative may be asked to prove authority.
9. Security
Controls include Firebase Authentication and App Check; Firestore rules requiring both project membership records and IDs; high-entropy, time-limited external-task tokens whose rules expose only one task and restrict guest-written fields; denial of ordinary-client access to reports; least-privilege operator accounts with multi-factor authentication; encrypted transport; input type/length validation; signed and hash-verified Android releases; web security headers; operating procedures and periodic review. Operators access only what they need.
10. Privacy contact
Controller: linqen (MOADAY operator)
Privacy and complaints team: MOADAY Privacy
Email: contact@linqen.co.kr
11. Changes
This policy took effect on July 16, 2026. On August 19, 2026, we added external-task link handling. On September 22, 2026, we clarified optional synchronization diagnostics and introduced separately consented public-page analytics, with its fields, 60-day browser storage, and withdrawal controls. The new collection remains off until the relevant consent is given. Material future changes will be announced in the app or web service before taking effect.
Back to MOADAY · Korean policy