Hangul Moment

User guide

1. Open the app to see a Hangul clock that follows your device's current time and local time zone.
2. Tap the clock face once to open settings. You can change the theme, date and seconds display, text size, and clock display dimming.
3. Use your iPhone in portrait or landscape. Your preferences are kept when you reopen the app.
4. Settings also let you choose flip animation, sound, and whether to keep the screen awake while using the app.

The clock face always shows time and dates in Korean. Settings and guides follow your device's preferred language, with English, Korean, and Japanese supported.

Keep the app open in the foreground to use its flip clock. The clock and its themes work without an internet connection. Version 1.1.0 and later also include Hangul clock and daily calendar widgets.

After updating to version 1.1.0 or later, open the app once. On iOS 17 or later, enable StandBy, connect your iPhone to power, lock it, and place it on its side. Touch and hold the left widget area in StandBy to add the Hangul clock, and add the daily calendar on the right. Edit each widget to follow the app theme or choose one of four looks. iOS manages actual widget update timing.

The time looks wrong

Check your iPhone's current time and time zone under Settings → General → Date & Time. The app follows your device's time zone; it is not fixed to Korean time. After changing the time zone, bring the app to the foreground again.

The app or settings stopped responding

Close the app and open it again. If the issue continues, email us your device model, iOS version, and the steps that cause the issue.

Adjusting brightness and sound

The app's dimming setting changes the appearance of the clock display. To change your device's overall screen brightness, use your iPhone's Control Center. You can turn clock sound on or off in the app's settings.

Privacy policy

Notice updated: October 24, 2026 · Applies to: Hangul Moment for iOS 1.0.0(3), 1.0.1 (build 6), 1.1.0 (build 7), and 1.2.0 (build 8)

This notice describes data handling by version. Version 1.0.0(3) has no advertising or analytics SDKs. Version 1.0.1 (build 6) and released version 1.1.0 (build 7) measure advertising performance through Meta and TikTok after tracking permission; they do not include Firebase usage analytics. Starting with version 1.2.0 (build 8), Firebase usage analytics begins only when you separately enable usage sharing. Earlier preparation builds 1.0.1 (4 and 5) had measurement disabled.

1. Information used by the clock and preferences

The app reads the system's current time and time zone to display the time and date. It does not use location permission. The time and date displayed by the clock are not sent outside your device. Preferences are stored locally. In version 1.2.0 (build 8), enabling usage sharing sends the selected preferences and usage information described below for analytics.

Your theme, date and seconds display, text size, dimming, flip animation, sound, keep-screen-awake preference, and whether the first-use guide has been shown are stored locally on your device in the app's own settings storage.

2. Version 1.0.0(3)

This version has no accounts, app server, advertising or analytics SDKs, or tracking features. The operator does not collect personal information or usage records through this version. It does not request access to photos, contacts, the microphone, location, or notifications.

3. Versions 1.0.1 (build 6), 1.1.0 (build 7), and 1.2.0 (build 8) — advertising measurement after consent

Only after you allow Apple's App Tracking Transparency (ATT) permission, the app starts Meta App Events and TikTok App Events SDKs to measure installations and app launches resulting from our ads. If you initially decline tracking or permission is restricted, the SDKs do not start and advertising identifiers and measurement events are not sent. All clock features work offline regardless of your choice. There are no accounts or in-app ads.

After consent, the following categories of information are sent to Meta and TikTok. This information is processed in connection with device identifiers.

• Device ID: advertising identifier (IDFA), device, installation, and session identifiers
• Product interaction: installation, app launch, and activation activity
• Coarse location: the general area that can be inferred from the IP address used for communication. The app does not collect GPS or precise location or request location permission.
• Other data types: device and request context, such as device model, operating system, language, and network information
• Performance data: SDK performance information, such as request latency
• Other diagnostic data: SDK diagnostic information, such as request errors

Advertising measurement does not collect or send clock time and date content, saved preferences, names, email addresses, phone numbers, user accounts, purchases, screenshots, or crash reports. The app also does not request access to photos, contacts, the microphone, or notifications.

3-1. Version 1.2.0 (build 8) — optional usage analytics

This section applies starting with version 1.2.0 (build 8). Versions 1.0.0(3), 1.0.1 (build 6), and 1.1.0 (build 7) do not include Firebase usage analytics. Analytics uses information from after you enable sharing in this version. Usage from earlier versions or before enabling sharing is not collected retroactively.

Usage sharing is off by default. The app starts Google's Firebase Analytics (Google Analytics) only after you turn on “Share Usage Information” in the app's privacy panel. This choice is separate from ATT tracking permission for the advertising SDKs. All clock features remain available if you do not share.

When sharing is enabled, the following information is sent to Google to improve features and understand app usage:

• Basic activity such as app launches and activation, a pseudonymous app-instance identifier that distinguishes app installations, and clock-session identifiers
• Time the clock screen is active in the foreground, whether a clock session reaches five cumulative active minutes, the theme and screen orientation, and changes to date, seconds, text size, dimming, animation, sound, and keep-screen-awake preferences. Time in settings, while locked, or in the background is excluded; this does not measure time spent looking at the screen.
• Counts of configured clock and calendar widgets observed when the app successfully queries their configuration. This does not measure widget impressions or viewing time.
• Basic context such as device model, operating system, app version, and language, and a general area such as country or region inferred from the connection's IP address. GPS and precise location are not collected.

This information is linked to an app-instance identifier, so we do not guarantee it is anonymous. Usage events do not include names, email addresses, phone numbers, accounts, free-form text, or screenshots. We do not use a screen-recording or crash-collection SDK. This Firebase configuration uses a module without advertising identifier (IDFA) collection capability and disables vendor identifier (IDFV) collection. Ad storage, ad user data, and ad personalization are denied. Separate Meta and TikTok advertising measurement follows the ATT notice above.

In updates that include widget heartbeat collection, widgets on devices with usage sharing enabled send a recent-activity signal during a refresh at most once per UTC day, even when the app is closed. Supabase relays the app-instance identifier, UTC day, and the sending widget type (clock or calendar) to Firebase Analytics. The relay hashes the identifier for deduplication storage. This does not distinguish Home Screen from StandBy or measure impressions or viewing time. iOS scheduling and network failures can prevent a signal; no signal does not prove removal. Turning sharing off stops new requests but cannot cancel information already in transit or delivered. Relay deduplication records are kept for about 35 days and removed by a daily scheduled job. The Supabase Privacy Policy also applies to relay processing.

You can turn off “Share Usage Information” in the same panel at any time. Turning it off stops new usage analytics collection and resets Firebase analytics data and the app-instance identifier on your device. Information already sent and requests already in progress are not automatically deleted, and remote deletion is not guaranteed. Google's processing and retention are governed by the Google Privacy Policy and Firebase Privacy and Security information. Send related requests to the support email above.

4. Purposes and recipients

For advertising measurement, the recipients are Meta and TikTok. Device IDs, product interaction, coarse location, and other contextual data are used for this app's advertising and marketing, third-party advertising services, and analytics, and may be used for advertising tracking by linking information across apps and websites. Device IDs are also used to operate the measurement SDKs. Performance and other diagnostic data are used for analytics and app functionality and are not used for advertising tracking.

Each recipient's policies govern the processing, retention, and deletion of information sent to it. See the Meta Privacy Policy and TikTok for Business Privacy Policy, and TikTok Business Products (Data) Terms. Send privacy requests, including access or deletion requests, to the support email above or through the relevant provider's privacy contact channels.

5. Permission changes, storage, and deletion

You can change tracking permission in iPhone Settings → Privacy & Security → Tracking. Withdrawing tracking permission stops new advertising measurement events sent by the app. Information already received or stored by an SDK, and requests whose transmission began before withdrawal, may still be processed afterward. We cannot guarantee recall of transmitted requests or remote deletion of information held by recipients. Deleting the app or withdrawing permission does not automatically delete information already sent.

Clock preferences remain on your device while you use the app. Deleting the app from your device also removes its local preferences. Device backups and restores follow your iOS settings and Apple's policies.

6. Email support

If you choose to contact us by email, your email address and message are sent through the email service. The operator reads them to respond to your inquiry. The app does not automatically send emails or inquiry content. For requests about information in your inquiry, contact the support address above.

7. This support website

This page is hosted on GitHub Pages and uses no additional analytics scripts or advertising. Information about visits to the website may be subject to the hosting provider's GitHub privacy statement.

8. Changes and contact

Before a future version changes data handling, this notice will be updated to describe that version. The operator and privacy contact are listed in the Contact section above.