Privacy Policy

The Company collects the following personal information.

a. Required items

• Account: email address, password (stored encrypted), or Apple/Google account identifier
• Nickname (auto-generated, changeable)
• Date of birth (to verify users are at least 14 years old)
• Device identification: push notification token, operating system type

b. Optional items

• Profile photo, short bio
• Location (when attaching weather to a record): latitude and longitude. Relayed through the efilog server for a weather lookup only and never written to our database. To reduce repeated lookups, coordinates rounded to about 1 km (two decimal places) are held in server memory for up to 10 minutes and then discarded. Of the results, the weather condition, temperature, and city name are stored as part of that record.
• Contacts (when sending a Time Letter to someone who has not signed up yet): processed on-device only, never stored on our servers
• Phone verification result (when subscribing to efilog premium): only whether verification succeeded and when it occurred is stored; the phone number itself is not stored.
• Microphone (when attaching a voice recording — premium only): used only at the moment the user explicitly starts a recording. No always-on listening or background use. Recorded data is handled as an attachment under Section 1-c of this policy

c. User-generated content

• Records you write, comments, inspirations, follow relationships, and reports or blocks you create
• Time Letter delivery information: the users you designate as recipients, the users you invite as co-senders, the scheduled arrival time, and the time it was opened
• Attached photos (JPEG): EXIF metadata (GPS, device, capture time) is automatically removed before upload
• Attached videos (MP4) — efilog premium only: compressed on the client (720p) at upload → metadata atoms (udta, meta, ilst) removed on the server and creation/modification timestamps reset to 0. No GPS, device, or capture-time exposure.
• Attached voice recordings (M4A/AAC) — efilog premium only: recorded directly via the microphone (up to 60 seconds each, up to 3 per record). On upload, the server removes the same atom metadata as videos and zeroes timestamps. We perform no analysis of recorded voices (recognition, transcription, speaker identification, voiceprint extraction, etc.), and access is possible only through a private bucket with signed URLs.

d. Automatically generated and collected information

• Service usage records, access logs, error logs (excluding personally identifiable information)
• Push notification delivery and receipt records

e. Payment information (when using efilog premium)

• In-app purchase receipt information from the App Store or Google Play: payment platform, product ID, subscription plan, purchase token, order number, subscription status, and start and expiry times
• Payment credentials such as card or bank account numbers are handled directly by Apple and Google; efilog neither collects nor stores them.

f. Collection methods

• Entered directly by users during sign-up and use of the service
• Collected automatically through the mobile operating system (iOS/Android) and the SDKs bundled with the app (push notifications, location, contacts, photo picking, voice recording, in-app purchases)

• Member identification, authentication, and sign-in
• Providing core features such as writing, storing, and scheduled publishing of records
• Time Letter delivery: delivering a record to the person you designated at its arrival time
• Sending notifications (record arrivals, comments, inspirations, follows, and other notifications the user has consented to)
• Use of date of birth: verifying that the user is at least 14 years old, and computing the upper bound of the scheduling range (preventing schedules beyond the user's 80th birthday). Date of birth is never shown to other users.
• Managing efilog premium subscriptions: verifying payment receipts, checking subscription status, and determining feature entitlements
• Service operation and incident response (reviewing access and error logs)
• Preventing fraudulent use, responding to illegal activity, and resolving disputes

• Deleted immediately upon account deletion (unrecoverable)
• However, where retention is required by applicable laws, information is kept for the relevant period:
  • Protection of Communications Secrets Act: sign-in records, etc. — 3 months
  • E-Commerce Act: records on contracts and withdrawal of subscription — 5 years
  • E-Commerce Act: records on payment and supply of goods — 5 years
  • E-Commerce Act: records on consumer complaints or dispute resolution — 3 years
• Block records kept for fraud prevention are retained for 1 year and then destroyed

The Company does not provide users' personal information to external parties, except in the following cases.

• When the user has given prior consent
• When required by law (e.g., a lawful request from an investigative agency)
• Content the user has explicitly set to public

The Company outsources the following tasks to provide a stable service.

a. Amazon Web Services, Inc. (AWS)

• Outsourced tasks: server and database hosting, storage of attached files
• Outsourced items: all items collected under this policy
• Processing location: Seoul region, Republic of Korea (ap-northeast-2)
• Retention period: until account deletion or termination of the outsourcing contract

b. Apple Inc. (APNs)

• Outsourced tasks: iOS push notification delivery, Sign in with Apple, App Store in-app purchases and receipt verification
• Outsourced items: device token, Apple account identifier, payment receipt information
• Retention period: until token expiration, disconnection, or the end of the subscription

c. Google LLC (FCM)

• Outsourced tasks: Android push notification delivery, Google Sign-In, Google Play in-app purchases and receipt verification
• Outsourced items: device token, Google account identifier, payment receipt information
• Retention period: until token expiration, disconnection, or the end of the subscription

d. OpenWeather Ltd.

• Outsourced tasks: looking up the weather to attach to a record
• Outsourced items: latitude and longitude (called on your behalf by the efilog server; never written to our database)
• Retention period: discarded immediately after the lookup (held in server memory for up to 10 minutes)

Contracts with processors require compliance with applicable laws, security safeguards, and restrictions on sub-outsourcing so that personal information is not processed beyond its intended purpose.

Users may exercise the following rights at any time.

• Request access to personal information (app → Profile/Settings)
• Request correction or deletion of personal information (app → Edit Profile)
• Request suspension of processing (app → Settings → notification toggles)
• Withdraw consent and delete your account (app → Settings → Delete Account — all data is permanently deleted immediately)

These rights can be exercised directly through in-app features; for further inquiries, contact the privacy officer listed below.

• Encryption in transit: all communication is encrypted with HTTPS (TLS)
• Protection at rest: passwords are stored as one-way hashes; authentication tokens are kept in device secure storage (iOS Keychain / Android Keystore)
• Access control: every read request is answered only after the server checks the visibility scope, arrival time, and block relationships; sensitive information such as date of birth and notification settings is kept in a separate table accessible only by the owner
• Scheduled record protection: until the publication time arrives, no one but the author can read the content
• Media metadata removal: EXIF in uploaded photos and atoms (udta, meta, ilst) plus timestamps in videos and voice recordings are automatically deleted — blocking exposure of GPS, device, and capture time
• Media storage control: private bucket + signed URLs with 1-hour expiry — external access is automatically blocked even if a URL leaks
• Access log management: system logs are retained and abnormal access is monitored
• Least privilege: even operators cannot arbitrarily view users' private content; access is limited to legitimate grounds such as report handling or legal compliance

efilog is available to users aged 14 and older. Age is verified via the date of birth entered at sign-up, and registrations by children under 14 are blocked. If we learn that information of a child under 14 has been collected, we destroy it immediately.

As a mobile application, efilog does not use web cookies, but collects information through the following automatic mechanisms.

• Operating system SDKs: push notification token, device identifier (renewed when the app is reinstalled)
• Authentication token storage: secure storage used to keep you signed in

Users can decline permissions such as notifications in their device settings; declining may limit the corresponding features (e.g., receiving notifications).

efilog does not collect advertising identifiers and bundles no third-party advertising or behavioral analytics SDKs in the app. Usage records are reviewed only within the scope of server logs kept for service operation and incident response.

• Required consent: the Terms of Service and the collection and use of personal information strictly necessary to provide the service. If refused, sign-up and use of the service are not possible
• Optional consent: marketing communications, location use. Refusal does not affect use of the core service

For inquiries, complaints, or remedies regarding personal information processing, please contact the officer below.

• Name: Hyojun Park
• Title: Privacy Officer
• Email: support@efilog.app

If you need to report or consult on a privacy infringement, you may contact the following organizations (Republic of Korea).

• Personal Information Infringement Report Center (KISA): privacy.kisa.or.kr · 118 (no area code)
• Personal Information Dispute Mediation Committee: www.kopico.go.kr · 1833-6972
• Supreme Prosecutors' Office Cyber Crime Investigation Unit: cybercid.spo.go.kr · +82-2-3480-3573
• National Police Agency Cyber Bureau: ecrm.cyber.go.kr · 182 (no area code)

If this policy changes, we will notify users through in-app notices starting 7 days before the effective date. For changes that materially affect user rights, we will give notice starting 30 days before the effective date and, where necessary, obtain users' explicit renewed consent.