Donurim
Privacy policy
Effective date: September 19, 2026
IBRDOS Inc. ((주)아이비알도스, the “Company”) processes information in Donurim as described below. Contact dev@ibrdos.com for privacy requests and support.
1. Information and purposes
| Category | Information | Purpose |
|---|---|---|
| On-device plans | Task titles, notes, dates, times, durations, priorities and repeats; completion and rest records; daily capacity and journal entries; theme, language and reminder preferences | Planning, rearranging tasks, displaying records and decorating your room |
| Email account | Email address, random account ID, authentication request, expiry and attempt information, hashed codes and session secrets | Registration, sign-in, deletion verification and account security |
| Account synchronization | Copies of plans and preferences, modification and deletion times, sync revisions | Account storage, synchronization, recovery and conflict handling |
| Purchases | Product and transaction identifiers, subscription status and expiry, purchase tokens, account association values and verification times | Entitlements, restoration, refunds, cancellations and preventing duplicate ownership |
| Weekly push | Push token, random device ID, language, time zone, notification preferences, associated session and delivery outcomes | Sending optional weekly reflections and preventing duplicate delivery |
| Security and operations | Hashed connection IP values for request limits, request times and outcomes, technical errors | Preventing authentication abuse and operating the service |
| Support | Sender email, message, attachments you choose and replies | Support and privacy requests |
Basic planning works without registration and saves records on your device. Connecting an email account synchronizes its plans and preferences with Company servers. The Company cannot remotely read device records that have not been synchronized. Focus timer state and widget display copies are stored on your device. Your writing is not included in advertising requests or sent to external generative AI services.
2. Email authentication
Registration and sign-in use a six-digit, single-use email code that expires after 10 minutes. Sending and verification attempts are limited. Account deletion requires a new code specifically for deletion. The server stores hashes of codes and session secrets; the app stores sign-in tokens in the operating system's secure storage. API logs are configured not to record email addresses, codes, purchase tokens or request bodies.
3. Calendar, reminders, widgets and files
When you choose calendar import, the app requests system permission and reads the next seven days from your device calendars. Event titles, identifiers, start and end times and all-day status are used to create fixed tasks. It does not import attendees, event locations or notes, or modify the source calendar. Imported tasks are stored like other tasks and are included in cloud synchronization when connected to an account.
Morning, evening and focus reminders are scheduled with the operating system using your chosen times and plans calculated on your device. Enabling weekly reflections while signed in registers your push token, language, time zone and notification preferences with the server. A message containing your weekly completion count is sent through Expo and Apple or Google push services. Push providers do not receive your email, task titles or notes. Turning off weekly reminders or signing out stops delivery for that registration; you can also revoke device permission. Notifications and widgets can display task titles, times and progress. Review your lock-screen and notification-preview settings. You can revoke calendar and notification access in device settings while continuing to use unrelated basic planning functions.
Export creates a JSON file containing your plans and records, then passes it to the destination or sharing app you choose. Import reads your selected file and merges it with saved records. Exported files contain your writing and are not protected with a separate password. Manage exported files and copies on other devices at their respective locations.
4. Service providers and international processing
| Provider | Information and service | Processing location and occasion |
|---|---|---|
| Amazon Web Services | Hosting, storage and operation of accounts, plan copies and purchase verification | Seoul region, South Korea, when account, sync and billing APIs are used |
| Resend (Plus Five Five, Inc.) | Recipient email address, authentication message and delivery outcomes | United States, transmitted securely when you request an authentication email |
| Expo (650 Industries, Inc.) | Push token, notification content including the weekly completion count, and delivery outcomes | United States, transmitted securely when registering or sending weekly notifications |
| Apple and Google | Store payments, purchase and refund verification, push tokens and notification delivery | Countries and infrastructure used by the provider, during purchases, restoration, entitlement checks or notification delivery |
| Google AdMob and UMP | Advertising, privacy choices and the information described below | United States and other Google operating countries when advertising and privacy-choice functions are used |
Resend does not receive your task, note or calendar content. You may use local features without connecting an account if you do not want authentication emails. Deleting your account or requesting that processing stop restricts account authentication and synchronization. Resend describes processing customer data while its service agreement remains active, with deletion within 90 days after the Company terminates its Resend account. The Company works with providers on individual deletion requests. Resend Privacy Policy · Resend Data Processing Addendum
Expo describes holding notification content in memory and message queues for the time needed to hand it to Apple or Google push services. Turn off weekly reminders if you do not want push delivery; basic planning remains available. Expo Privacy Policy · Push service data handling
Store payment processing is also governed by each store's policies. The Company does not receive your card number or bank password. Apple Privacy Policy · Google Privacy Policy
5. Advertising and choices
The native app includes Google AdMob banner ads. Its SDK may process IP addresses and approximate location derived from them, ad impressions and responses, app interactions, diagnostics, performance information and app- or device-related identifiers for advertising, measurement and fraud prevention. The Company does not add your email, plans, notes, calendar content or purchase authentication tokens to ad requests.
The app requests non-personalized ads. On iOS, Apple’s App Tracking Transparency (ATT) system permission is requested before loading the advertising SDK or UMP. If you allow tracking, device identifiers may be used for advertising and measurement, and applicable regional UMP privacy choices are checked separately. If ATT is not authorized or its status cannot be checked, the advertising SDK is not initialized and ads are not requested. If you revoke permission in Settings, ad display stops when you return to the app. Core app features remain available regardless of this choice. The Android app removes the advertising-ID permission to restrict access to the advertising ID on Android 13 and later. On Android 7 through 12L, removing this permission alone does not block access, and the advertising SDK may process the Android advertising ID (AAID), depending on device and Google Play services settings. Even with non-personalized ads, available identifiers may be used for frequency capping, aggregate reporting and measurement, and fraud prevention. These choices do not eliminate all SDK processing.
Where applicable, UMP presents privacy choices; you can reopen advertising privacy choices in Settings when that option is available. Device advertising settings may also offer options such as deleting or resetting the advertising ID. Planning remains available when ads cannot be requested. Information about apps using Google services · About non-personalized ads
6. Retention and deletion
Accounts and synchronized records are retained while you use the service. Once a deletion request is verified, the account is disabled to block access, and its email association, sessions, plans, device registrations and account-level purchase records are removed in stages. Temporary processing failures are retried automatically; the account cannot access records awaiting deletion. Cleanup jobs use a random account ID and hashed association values without the original email or plan content. Codes cannot be used after 10 minutes; expired records are removed through storage cleanup. Expired or signed-out sessions cannot be used. Push registrations have a 90-day validity period after their last refresh and are excluded from delivery after expiry, unregistration or account deletion. Duplicate-delivery and receipt records also use storage cleanup periods of up to 90 days. Operational logs are configured for 14-day retention. Database recovery backups may contain pre-deletion copies for up to 35 days and are not used for routine access.
A deleted account's random ID marker and hashed store identifiers used to prevent duplicate purchase ownership remain as separate security and transaction-protection records. They contain no email address or plan content. They prevent the same purchase from being attached to another app account; related rights requests can be reviewed through support. Where law requires transaction or dispute records, the Company retains them separately for that purpose and the required period. Support information is deleted when its purpose ends unless applicable law requires retention.
Account deletion does not cancel a store subscription. See Account and data deletion for requests inside or outside the app. Local guest records can be removed by clearing app data or uninstalling the app. Exported files, copies on other devices and information independently held by stores or advertising providers are not all erased by deleting a Company account.
7. Your rights and contact
Contact dev@ibrdos.com for applicable rights, including access, correction, deletion, restriction, withdrawal of consent, objection and portability. Only the minimum information needed to verify the request is sought. Authorized representatives may act under applicable law. Any lawful refusal or restriction will be explained. You may also complain to your local data-protection authority.
Processing relies on providing the account and requested service, legitimate interests in security and preventing fraud, legal obligations and consent where required. Users who require parental authorization under applicable law must have it. The Company does not ask children to provide sensitive personal content.
The Company applies access restrictions, encrypted transmission and storage, and session and request validation. Material changes to this policy are announced in the app or on this page before they apply.
Operator: IBRDOS Inc. ((주)아이비알도스) · Email: dev@ibrdos.com · Phone: +82-70-4589-9109
Address: Room 618A, 6F, 326 Wangsimni-ro, Seongdong-gu, Seoul 04709, Republic of Korea