Privacy Policy
This is an English translation provided for convenience. If it differs from the Korean version, the Korean version prevails.
Jaewon Kim (김재원, the "Operator"), who operates Danbi (the "Service"), processes users’ personal information in accordance with the Personal Information Protection Act (「개인정보 보호법」). This policy explains what information we process, why, on what legal basis, how long we keep it, and to whom we entrust it. It applies to both the mobile app "Danbi" (iOS and Android) and the website dan-bi.com.
The key point is this: the content of your reflection records is visible only to you, and it is never carried over any channel that reaches other people.
At a glance
- Information we collect — Email and social login information, handle and display name, reflection records, push token, profile photo (if you upload one), access, device and login records (§1)
- Purposes — Identifying members, storing reflection records, companionship, follow and cheers, sending notifications, security and error handling, retention required by law (§1)
- Retention — Until you delete your account. Login records and some other records have separately defined periods, and data remains in backups for up to 90 days (§2, 3)
- Third-party sharing — We do not provide your information to third parties (§4)
- Processors and cross-border transfer — We entrust 8 tasks to 6 companies. Servers and the database are in Korea; backups, email, push notifications, error logs and others are overseas, including in the United States (§5, 6)
- Sensitive information (optional) — Church affiliation, only when you give separate consent (§7)
- Access and deletion — danbi@dan-bi.com. Delete your account in the app or on the web (§8)
The above is a summary of the key points. Please see the full text below for details.
1. Personal information we process, purposes and legal bases
The Service divides its legal bases for processing into three.
- Performance of contract: Information strictly necessary to provide the Service under the Terms of Service. We process it without obtaining separate consent (Article 15(1)4).
- Legal obligation: Information that the law requires us to retain (Article 15(1)2).
- Consent: Processed only when the user has given separate consent (Article 15(1)1, Article 23(1)1).
| Legal basis | Items | Purpose | Collection method |
|---|---|---|---|
| Performance of contract | Email address (verified address) | Identifying members; sending verification emails, account deletion confirmation emails and notices of added login methods | Social login, email verification |
| Performance of contract | Social login account information — Kakao: member identifier, email, nickname, profile photo URL / Naver: member identifier, email, name, nickname, profile photo URL / Google: identifier, email, name, profile photo URL / Apple: identifier, email | Login and account linking; suggesting a default display name (Kakao and Naver nickname; a Google name is shown only as an example in the input field); default profile photo (when you have not uploaded your own) | Exactly the scope the provider sends with the user’s consent at social login. Names and nicknames are stored as received |
| Performance of contract | Handle (cannot be changed after sign-up), display name | Displaying members within the Service; companionship and follow | Entered by the user |
| Performance of contract | Device time zone, app language | Calculating day boundaries (reflection date, streak); choosing the language of notifications and emails | Reported automatically by the app |
| Performance of contract | Reflection record text, emotion (a value the user chooses), selected Bible translation, completion status, streak, XP | Storing and displaying reflection records; tracking habits | Entered by the user; generated during use |
| Performance of contract | Push notification token, notification settings | Sending service notifications (reminders, cheers, companionship notifications) | App |
| Performance of contract | Companionship participation, follow, cheer, block and report records (including the reported member’s handle, display name and profile photo URL at the time of the report) | Providing companionship, follow and cheers; handling reports | Generated during use |
| Performance of contract | In-app notification records (notification type, the member who triggered the notification, values needed for the notification such as the companionship name, read status) | Providing the in-app Notifications screen | Generated during use |
| Performance of contract | Profile photo you upload | Displaying your profile | Uploaded by the user (optional) |
| Performance of contract | Records of consent to terms and policies (item, document version, whether consent was given, date and time) | Confirming and proving consent | Consent screen |
| Performance of contract | Login session information (hash of the token; issue, expiry and last-used times; login method; device type, model and manufacturer; OS; app version) | Keeping you logged in | Generated automatically |
| Performance of contract | IP address and app or browser information at the time of email verification and account deletion requests | Preventing fraudulent requests | Generated automatically |
| Performance of contract | Send-interval records for verification and account deletion emails (recipient email address, requesting IP address, time last sent) | Preventing abuse through sending verification emails too often | Generated automatically |
| Performance of contract | Server access logs (IP address, requested URL, app or browser information), server and app error logs | Incident response, security, fixing errors | Generated automatically |
| Legal obligation | Login records (date and time, type, result, IP address, app or browser information, device type, model and manufacturer, OS, app version) | Retaining communication confirmation data | Generated automatically |
| Consent (sensitive information) | Church affiliation (map place identifier and church name) | Showing your church on your profile; finding members of the same church | Selected directly from Kakao Map search results after separate consent is obtained when you choose a church (device location is not used) |
The Service does not process any personal information other than the items above. We do not collect phone numbers, addresses, device location, contacts or advertising identifiers (ADID/IDFA). If we are to receive information beyond the items above from a social login provider, we will amend this policy before receiving it.
Only people aged 14 or older can sign up for the Service, and we do not process personal information of children under 14. We confirm at sign-up that you are 14 or older.
Information received directly by external services — When you search for a church, your device sends the search term directly to Kakao Map. Kakao then receives your device’s IP address and device information. This information does not pass through the Operator, and Kakao’s privacy policy applies.
When you donate on the website — The "후원하기" (Support) button on the website links to Buy Me a Coffee (United States), an overseas donation service. The name, email and message you enter when donating, and your payment information, are received by Buy Me a Coffee, and its privacy policy applies. This information is not linked to your Danbi account, and the Operator uses the donation history in that service’s admin screen only to send thanks and respond to inquiries.
2. Retention period
| Item | Retention period | Basis |
|---|---|---|
| Member information, social login account information, reflection records, streak and XP, companionship, follow, cheer, block and report records, push token, notification settings, profile photo, consent records | Until you delete your account | Performance of contract |
| Church affiliation | Until you clear your affiliation (withdraw consent) or delete your account | Consent |
| Records of withdrawal of church consent | Until you delete your account | Proof of consent and withdrawal |
| Login records | 3 months from the time recorded. If you leave the Service, the records are unlinked from your account and only date and time, type, result and IP address are kept | Article 15-2 of the Protection of Communications Secrets Act (「통신비밀보호법」); Article 41(2)2 of the Enforcement Decree of the same Act |
| Login session information | 30 days after logout or expiry | Performance of contract |
| Email verification and account deletion request records | Destroyed the day after processing is complete. Requests that expire without being processed are destroyed 7 days after expiry | Performance of contract |
| Send-interval records for verification and account deletion emails | 7 days after the last email is sent | Performance of contract (preventing abuse) |
| In-app notification records | Until the receiving member or the member who triggered the notification deletes their account | Performance of contract |
| Handles of members who have left the Service | 3 months after leaving (reserved so that no one else can use the same handle to impersonate them) | Performance of contract |
| Server access and error logs | 3 months | Performance of contract (security) |
| Server and app error logs sent to the error analysis service (Sentry) | Up to 90 days | Performance of contract (fixing errors) |
3. Destruction procedure and method
- Procedure: Information whose retention period has ended or whose purpose has been achieved is destroyed without delay. An automatic destruction job runs every day. When you delete your account, your information is erased immediately, except for what the table above specifies separately.
- Method: Electronic files are erased irrecoverably by deleting rows from the database. We do not create paper documents.
- Backups: To prepare for outages, we back up the entire database every hour. Backups are kept on the server for 14 days and in Cloudflare R2 for 90 days, and are then deleted automatically. Therefore, deleted information also remains in backups for up to 90 days before it disappears. Backups are used only for recovery from outages, and as a rule, deleted accounts are not restored during recovery.
4. Provision of personal information to third parties
The Service does not provide users’ personal information to third parties, except where laws have special provisions.
5. Entrustment of personal information processing
| Processor | Entrusted tasks |
|---|---|
| Oracle Cloud Infrastructure | Operating servers and the database (Republic of Korea region) |
| Cloudflare, Inc. | Serving the website and visitor statistics, relaying app requests, storing profile photos, storing database backups, forwarding incoming email |
| Google LLC (Gmail) | Sending service emails and storing inquiry emails |
| Expo (650 Industries, Inc.) | Relaying push notifications |
| Google LLC (Firebase Cloud Messaging) | Delivering Android push notifications |
| Apple Inc. (Apple Push Notification service) | Delivering iOS push notifications |
| Google LLC (Cloud Vision API) | Automated screening of uploaded profile photos for harmful content |
| Functional Software, Inc. (Sentry) | Collecting and analyzing server and app error logs |
Entrusted processing follows each processor’s terms of service and data processing terms. However, email is currently sent and received through the Operator’s personal Gmail account, to which Google’s general terms of service apply. If a processor changes, we will amend this policy and give notice.
Kakao, Naver, Google and Apple are login methods. They are not processors to which reflection records are passed.
6. Cross-border transfer of personal information
Servers and the database are located in the Republic of Korea. However, we transfer personal information overseas for the tasks below.
- Legal basis: Article 28-8(1)3a. The transfer is entrustment of processing and storage necessary to perform a contract with the data subject, and it is disclosed in this policy. Therefore, we do not obtain separate consent.
- Timing and method: Information is sent over an encrypted network (HTTPS) when you use the Service. Backups are sent every hour.
| Recipient (contact) | Country | Items | Purpose | Retention and use period |
|---|---|---|---|---|
| Cloudflare, Inc. (privacyquestions@cloudflare.com) | United States and other regions designated by Cloudflare | App and web requests (including IP address), website visitor statistics, profile photo files, database backups, inquiry emails | Relaying requests, visitor statistics, photo storage, backups, email forwarding | Requests: while being processed; photos: until account deletion; backups: 90 days |
| Google LLC — Gmail (googlekrsupport@google.com) | United States and other countries where Google has facilities | Email address, email body | Sending service emails, storing inquiry emails | Sending records and inquiry emails are deleted within 1 year after handling is complete |
| Expo — 650 Industries, Inc. (expo.dev/contact) | United States | Push token, notification title and body (reflection content is not included) | Relaying push notifications | Until delivery (receipts: 24 hours) |
| Google LLC — Firebase Cloud Messaging (firebase.google.com/support/privacy/dpo) | United States and other countries where Google has facilities | Push token, notification title and body | Delivering Android push notifications | Until delivery (up to 28 days if the device is off) |
| Apple Inc. — APNs (apple.com/kr/legal/privacy/contact) | United States | Push token, notification title and body | Delivering iOS push notifications | Until delivery (up to 30 days if the device is off) |
| Google LLC — Cloud Vision API (support.google.com/cloud/contact/dpo) | United States and other countries where Google has facilities | Profile photo images you upload | Automated screening for harmful content | Only during screening (not stored) |
| Functional Software, Inc. — Sentry (compliance@sentry.io) | United States | Server and app error logs, some performance traces (sampled). Configured not to send default personal information such as IP address | Error analysis | Up to 90 days |
| Google LLC — Google Sign-In (googlekrsupport@google.com) | United States | Login identifier, email, name, profile photo URL | Login | Until account deletion |
| Apple Inc. — Sign in with Apple (apple.com/kr/legal/privacy/contact) | United States | Login identifier, email | Login | Until account deletion |
How to refuse, and what happens if you do: To refuse cross-border transfer, delete your account or let us know at danbi@dan-bi.com.
- If you turn off Danbi notifications in your device settings, your push token is not transferred.
- If you do not upload a profile photo, no photo is transferred.
- Other transfers are strictly necessary to provide the Service, so if you refuse them, you cannot use the Service.
7. Sensitive information and information visible to other members
Church affiliation is information about religious belief, so we treat it as sensitive information. When you choose a church, we obtain your consent separately from other consents. Even if you do not consent, you can use every feature except church registration.
While you use the Service, the following information may be visible to other members (Article 23(3)).
| Information | Where it is visible | How to hide it |
|---|---|---|
| Church affiliation | Your profile as seen by people who find you, the list of members who chose the same church, recommendations of members from the same church | If you clear your affiliation, it is not shown anywhere (this is the same as withdrawing consent). If you switch to a private account, you are removed from the list and from search, but it remains visible to followers you have already approved. |
| Handle, display name | Search, follow, companionship, Hall of Fame | If you switch to a private account, you are removed from search, recommendations and lists. Your handle and display name themselves are your names within the Service and cannot be hidden. |
| Profile photo (the photo you uploaded, or your social account photo if there is none) | Places where members are shown, such as companionship and follow | You can take it down with "Remove photo" in the app settings. Your social account photo can be taken down the same way; if both are taken down, your initials are shown. |
The content and emotions of your reflection records are not visible to other members. Other members see only status, such as whether you started together, whether you finished today, and your streak, and if your account is private, only followers you have approved see even that. However, in a companionship, its members can see how many people have read that companionship’s chapter for today. They cannot see who has read it, and this count includes private accounts.
8. Your rights and how to exercise them
Users may at any time request access to, correction of, deletion of, or suspension of processing of their personal information, and may withdraw consent.
- Where to make requests: danbi@dan-bi.com. The Operator acts without delay, and at the latest within 10 days, and informs you of the result.
- Display name, profile photo, church: You can change or delete these yourself in the app settings. Clearing your church affiliation is treated as withdrawing your church consent.
- Account deletion: You can delete your account in the app or on the web (dan-bi.com/delete-account). In the app, the account is deleted immediately; on the web, it is deleted after confirmation through the email address you registered. For accounts that log in with Kakao, the connection with Kakao is also removed on deletion.
9. Security measures
- Managerial measures
- Only one person, the Operator, handles personal information.
- Records of the Operator’s access to the database (who, when, which database, what command) are kept for at least 2 years and reviewed monthly.
- Technical measures
- We manage database access rights.
- All transmission paths are encrypted (HTTPS).
- Login tokens are stored as hash values, not in their original form.
- Error logs are configured not to include default personal information.
- Physical measures: Information is stored at Oracle Cloud Infrastructure (Republic of Korea region) and the facilities of the processors listed above. The Operator does not run a separate server room and has no paper documents.
10. Automatic collection tools and app permissions
- Cookies and tracking: The app does not use advertising identifiers or tracking tools. The website dan-bi.com does not use login cookies. It uses Cloudflare Web Analytics for visitor statistics. This does not leave cookies or device identifiers, and only shows visited page URLs, referring pages, browser and device types, and countries as totals that cannot identify individuals.
- App permissions: There are no required permissions. The two permissions below are both optional, and if you do not allow them, you can still use the Service except for that feature. You can change them at any time in your device settings.
| Permission | Type | Purpose |
|---|---|---|
| Notifications | Optional | Receiving reflection reminders, cheers and companionship notifications |
| Photos (storage on Android 12 and below) | Optional | Choosing a profile photo. On iOS and Android 13 and above, the photo picker is used, so this permission is not requested separately. |
11. Chief Privacy Officer
- Chief Privacy Officer: Jaewon Kim (김재원, the Operator)
- Contact: danbi@dan-bi.com
The Operator bears final responsibility for the processing of personal information. Requests to access personal information, inquiries, complaints and requests for remedies for damage are received at the contact above.
12. Remedies for infringement of rights
If you need counseling about, or need to report, an infringement of your personal information, you can contact the institutions below.
- Personal Information Dispute Mediation Committee (개인정보 분쟁조정위원회) — kopico.go.kr / 1833-6972 (no area code)
- Personal Information Infringement Report Center (개인정보 침해신고센터), Korea Internet & Security Agency (한국인터넷진흥원) — privacy.kisa.or.kr / 118 (no area code)
- Supreme Prosecutors’ Office (대검찰청) — spo.go.kr / 1301 (no area code)
- Korean National Police Agency (경찰청) — ecrm.police.go.kr / 182 (no area code)
13. Measures in case of a personal information breach
If we become aware that personal information has been lost, stolen or leaked, we notify users without delay (Article 34). The notice includes the following.
- The items leaked and how the breach happened
- What users can do to reduce the harm
- The Operator’s response
- Remedy procedures and contact information
Where required by law, we also report to the Personal Information Protection Commission (개인정보보호위원회) and the Korea Internet & Security Agency.
14. Changes to this policy
When we change this policy, we announce it in the app and on dan-bi.com at least 7 days before the effective date. If the collected items increase or the changes are unfavorable to users, we announce them at least 30 days in advance. Versions of documents that users have already agreed to are not overwritten, and when this policy changes, previous versions are also posted on this page.
- Effective date: October 6, 2026
Revision history
- Version 2026-10-06 · Effective · Current