개인정보처리방침 1.7

Privacy Policy — English Summary

Version 1.7 · Publication and effective date: October 29, 2026 · Applies to the first public app release, version 1.0 (build 44 or later).

Notice before the first public release, without retroactive effect. Future changes remain subject to the advance-notice commitments in section 12. Previous policy 1.6 · Changes at a glance

This English summary is provided so English-speaking users can understand the material privacy terms. The complete Korean notice above is the governing text if the two versions differ, to the extent permitted by applicable law. Read the complete Korean notice.

Version 1.7 also describes purchase-date verification, signed public-schedule retrieval, hosting connection metadata, and local schedule and entitlement storage for the launch gift. The app has not yet been publicly released. Its actual first-public-release time and gift purchase cutoff have not been set; publishing this notice does not activate the gift.

Public gift schedule and hosting

The app retrieves a signed public document using a fixed HTTPS GET to https://bunyek.com/launch-gift/grimoire-v1.json. This may occur during app launch, Settings, skin preview, or restore only when the current Apple purchase lookup verifies a production App Store transaction and no verified final schedule is on the device. A previously cached purchase result alone does not trigger this request. Sandbox (including TestFlight) and Xcode environments, failed or unverified purchase lookups, and unknown transaction environments make no schedule request. Every user receives the same schedule. Only a final document with valid dates and signature is cached; pending or invalid responses are not stored as final.

The hosting provider receives or processes connection and HTTP metadata such as the IP address, request time, requested address, and common User-Agent (BunyekLaunchGift/1). This User-Agent is not a per-user identifier. The app adds no purchase or transaction information, Apple Account information, source text, translations, or history; no request body, query parameters, cookies, or credentials to this request. This does not send content away for translation.

Cloudflare Pages hosts the document. Cloudflare may process IP and network data to provide and secure its services and compile traffic aggregates. Pages Web Analytics is currently disabled and the domain has no Logpush subscription; domain-level unique-visitor and request aggregates remain available to Beek. Those hosting aggregates are separate from an in-app behavioral analytics SDK. See sections 2, 4, and 11 of Cloudflare's Privacy Policy. Retention depends on processing purposes and legal obligations; we do not promise one fixed number of days here.

Collection and support inquiries

• The app does not require a name, email address, phone number, payment details, login, or account.
• The app does not send app-generated device identifiers or advertising identifiers and includes no behavioral analytics, advertising, or third-party crash-report SDK. Public-document hosting metadata and aggregates are described separately below.
• If you contact support, your sender address, display name, message, and attachments are delivered through email services and used only to answer the request or handle a dispute. Do not include unnecessary source text, photos, audio, passwords, or other sensitive data.
• Beek's support mailbox is provided through Gmail by Google LLC in the United States. Support data is normally deleted within 30 days after the request is completed. A consumer complaint or dispute record may be separated and retained for three years when Korean law requires it.

On-device and device-to-device processing

• Translation, OCR, and supported speech recognition run on the user's device or paired Apple devices. A first translation or a new language may require Apple to download a language pack. Bunyek does not send source text or translated text to its own server or a cloud translation provider.
• Optional refinement is available on supported devices running iOS, iPadOS, or macOS 26 or later when Apple's on-device Foundation Models are available. For translations into English, the model processes the source text again if that source is no longer than 300 characters. Mac capture translations apply this limit to each text region separately. Refinement is off by default and can be enabled in Settings. Accepted results follow the same history-saving and iCloud-sync choices described below. Source text and results are not sent to Bunyek or an external translation server for refinement.
• Watch voice requests and user-made recordings are sent through WatchConnectivity to the user's paired iPhone for on-device recognition and translation. Safari sends only selected text to its native extension on the same device; Chrome sends selected text to Bunyek's native host on the same Mac.
• In Face-to-Face Conversation, the app sends original and translated text directly to the other device only after both users verify the displayed number. The peer connection uses one-time encryption keys and does not pass through Beek's server. Audio, photos, and device identifiers are not sent. Received text may be saved under the recipient's history settings.
• Apple states that its Translation framework may collect service usage and performance metrics, such as the app bundle ID and language pair, but not the content of source or translated text. Beek does not receive or view those metrics.

Optional iCloud history sync

• The feature is off by default. If you explicitly enable it in Settings, Bunyek merges saved history through container iCloud.com.bunyek.app in your private CloudKit database across iPhone, iPad, and Mac signed in to the same Apple Account. It does not use the public or shared database. Apple states that private-database content is accessible only to the user by default and is not visible in the Developer Portal.
• Synced fields are the source and translated text, target language, date, favorite status, deletion markers, and history limit and retention setting. Vocabulary, photos, audio, Watch recovery files, and unrelated settings are not included. Translation, OCR, and speech recognition remain on device.
• Sync runs when the main app opens or returns to the foreground, after a saved-history change, or when you choose Sync Now. Bunyek disables CloudKit's automatic background sync and does not give CloudKit access to its Watch, Share, Widget, or Safari extensions.
• Local additions, edits, and deletions made while sync is off are not queued as CloudKit operations. Re-enabling under the same Apple Account performs a full merge that carries new local records and local edits to existing records. A record deleted only locally while sync was off can still return from the private database.
• If the Apple Account changes, Bunyek clears confirmed history, edits, and sync cache linked to the previous account and turns sync off. Never-uploaded records created while sync was off are kept. New records whose previous-account server acknowledgement is uncertain are also kept in quarantine on this device, but are not sent to the new account until Bunyek rechecks its fingerprint and you explicitly approve the merge. Existing-record edits bound to the previous account are not carried over. Vocabulary is not part of this account-bound history cleanup.

Local storage and retention

• Translation history: stored in the local app group and, only when iCloud history sync is enabled, in the user's private CloudKit database. The default limit is 200 recent items; the user may select 50, 200, 500, or 1,000 and a retention period of no expiry, one day, one week, one month, or three months. The store has a hard ceiling of 2,000 items and 8 MB of text.
• Favorites: stored with history and prioritized within its item limit, but favorites are also deleted when the selected history retention period expires.
• Content-free deletion markers: after a synchronized deletion, Bunyek first clears source text, translated text, language, date, and favorite values from the CloudKit record, then requests deletion of that record. Its record ID, generation, and deleted flag may remain temporarily until the deletion request succeeds. Apple's own service retention and backup policies may also apply.
• Vocabulary: a separate local store of up to 5,000 entries per device. History retention does not apply; entries remain until the user deletes them. Vocabulary is not included in iCloud history sync.
• Apple Account binding fingerprint: Bunyek hashes the Apple-provided user record name with SHA-256 and stores only that hash in the local history store and sync cache. It is not sent to Beek. It can remain while sync is off so the app can detect an account change, and is removed when account-bound history is purged or the relevant local app data is deleted.
• Images and microphones: a Photo Library input is read and downsampled through a protected temporary copy. That copy is deleted when the actual photo-preparation task ends. If the operating system is still reading or downsampling after the interface is cancelled or times out, the copy may remain until that task ends. The current image stays in memory while results are shown and is discarded when replaced or the screen is exited. Mac screen captures are discarded after OCR. iPhone, iPad, and Mac microphone input is held in memory until recognition completes or is cancelled. Only an export the user chooses to save remains in Photos or Files.
• Watch recovery data: a Watch recording awaiting transfer has a 15-minute retention rule; an unfinished iPhone-side job has a seven-day rule. Expired data is removed on a later launch, resume, status check, or retry. A compatibility copy of a completed Watch result has a 24-hour retention rule from its first completion time.
• Selected web text and results: processed in extension and same-device native-app memory. Request-processing memory is released when the actual work ends. A result bubble remains visible after the request completes; the translation and, in Safari, the selected source text can remain in memory until the bubble is dismissed, replaced by a different selection, or the page is left. These extensions do not save source text or results to files or translation history.
• App preferences: remain locally until changed or the relevant app is deleted.
• Home Screen and menu bar icon choices: On iPhone and iPad, you can choose the Home Screen icon independently of the appearance; the operating system manages the selected app icon. On Mac, the menu bar icon preference is stored in the app preferences on that device and follows the selected appearance by default. These icon choices are not part of iCloud history sync or translation-history deletion.
• Purchase confirmation and skins: confirmation of a production app purchase and its original purchase date are cached in the device Keychain. Confirmed skin product IDs and the selected skin are stored in local App Group preferences. StoreKit confirmations update the owned product list; choosing a skin or a change in ownership can update the selected skin. The app-purchase confirmation cache has no automatic expiry. These values are separate from translation history and can remain after that history is deleted. Skin purchases and restores use Apple's StoreKit. To determine ownership, the running app processes product and transaction IDs, signing dates, verification and revocation states, and family-sharing status in memory; those transaction details are not saved in the skin-ownership cache. Bunyek does not send purchase-confirmation information to its own server.
• Launch-gift verification: when the gift is enabled, the running app processes the original app-purchase date, app-purchase revocation date, app transaction identifier, Apple signing date, verification result, and production/test environment supplied by StoreKit. The app transaction identifier is not an Apple Account email address or password. These details are kept in memory to check eligibility, distinguish purchase records, and reject older results; they are replaced by new verified information or cleared when the app stops running. They are not written to the gift-entitlement cache. The separate app-purchase Keychain cache described above may retain the original purchase date.
• Signed final-schedule cache: the app stores only a verified final public schedule in local App Group preferences. It contains the campaign, app, and skin identifiers, common start/end times, and signature, not per-user information. It supports eligibility checks after relaunch or while offline. A verified final schedule is not replaced by pending or failed responses, has no automatic expiry, and is removed with the relevant local app preferences. It is separate from the gift-entitlement marker below and is not part of history/Vocabulary deletion or iCloud history sync.
• Launch-gift entitlement cache: only a gift confirmation from the production environment is stored in local App Group preferences, as a campaign identifier separate from the list of paid skin products. This permits previously confirmed access to the Starlight Grimoire Cat skin and its icons while offline. The marker has no automatic expiry. A verified ineligible purchase record or app-purchase revocation updates or removes it; a temporary verification failure does not erase the previous confirmation. Deleting translation history does not clear this marker. It is removed if the relevant local app preferences are removed. Test-environment gift access lasts only for that run and is not retained as a production cache.
• Gift checks and restoration: the app rechecks the Apple-verified purchase when the app starts, when Settings or a skin preview is opened, and during a user-requested restore. The original purchase date can establish eligibility even if a qualifying customer first opens or reinstalls the app after the campaign ends. Paid skin purchases and their restoration remain separate from the gift entitlement. Bunyek does not send these purchase details or the gift marker to its own server or include them in iCloud history sync; each device checks Apple's purchase information independently. No separate account server or device-to-device gift-entitlement sync is added. In production, a verified signed final schedule is required for a new grant. If eligibility remains unknown, purchase of this skin is held back; translation remains available.

Deletion, permissions, and user choices

• Delete individual history items or all history in the History tab. Turning off history prevents new saves and lets you keep existing history or erase it, including favorites. Vocabulary entries can be deleted individually or cleared in Settings. Previous/Next Translation on iPhone, iPad, and Mac keeps up to 20 screens temporarily in process memory only, capped at 240,000 characters and 1 MiB (1,048,576 bytes) of UTF-8 text. It works with history saving off, without writing these screens to files or iCloud. Clear input, clear all history, or quit to discard them; deleting a saved history item also removes its related temporary screens.
• Turning iCloud sync off or deleting the app does not delete an existing iCloud copy. To delete synchronized source and translated text from the private database and other devices, leave sync on, clear all history, choose Sync Now, and wait for the up-to-date status before turning sync off or uninstalling. If the app has already been removed, reinstall it under the same Apple Account and complete those steps. A content-free deletion marker described above may remain temporarily until its CloudKit record deletion request succeeds.
• Local companion apps and extensions can have separate containers. Use the app's clear-history control before uninstalling if you also want to remove local copies.
• Camera, Photos, microphone, speech recognition, screen recording, clipboard, and website access are used only for the feature the user invokes, except for the clipboard auto-paste settings described below.
• iPhone and iPad clipboard: Auto-Paste on Open is on by default and can be turned off in Settings. When the Translate screen is selected with no Settings sheet open over it, and the input field is empty, Bunyek reads the copied text as the app opens or returns to the foreground, when you switch to the Translate screen, or when you close Settings over the Translate screen. It places the text in the input field and translates it on device. It does not read the clipboard while another screen, such as Camera, Conversation, or History, is showing, or while Settings is open over the Translate screen. When Bunyek is opened through its paste link (bunyek://paste), such as the widget's Paste button or the Translate control in Control Center, on the Lock Screen, or on the Action Button, it closes Settings, opens the Translate screen, and, for that request only, reads the clipboard even when the input field has text. Even for a paste-link request, Bunyek does not automatically read (1) items marked confidential, transient, or auto-generated by password managers (ConcealedType, TransientType, AutoGeneratedType); (2) text copied with Bunyek's own copy buttons or the share extension's Copy Translation button, which add a Bunyek marker; or (3) copies it has already handled, meaning copies it tried to paste automatically, copies you pasted yourself with the Paste button, and copies made while Bunyek was in the foreground (while you were using Bunyek). Because of (3), text copied inside the Bunyek app with the long-press menu or share sheet is not pasted automatically when you return from another app or switch to the Translate screen, and this record is kept when the app is relaunched. A copy from another app that was already on the clipboard when Bunyek became active is not recorded under (3) even if it was not read then (for example, because the input field had text or another screen was showing), so it can be read later when the conditions above are met.
• Limits: some copies without the Bunyek marker can still be read automatically. Text copied by long-pressing the result in the share extension is made while Bunyek is not in the foreground, so it is covered by neither (2) nor (3) and can be read when you open the app. When Bunyek does not read the clipboard automatically, or the setting is off, text enters the input field only when you paste it yourself with the Paste button.
• Clipboard text read this way is translated on device and is not sent to Beek's or a third party's server for translation. Like typed text, the source and translated text are saved to translation history unless history saving is turned off; if you enabled iCloud history sync, that history is sent to your private CloudKit database and synced. iOS may ask whether to allow pasting from other apps; if you decline, Bunyek does not receive the content. You can set Paste from Other Apps to Ask, Deny, or Allow under Bunyek in the iOS Settings app.
• Mac keyboard shortcuts: When the default Shift/Option gesture is selected and the global shortcut is enabled, Bunyek detects it without requesting Input Monitoring permission. You can turn the shortcut off or choose Set a Key Combination in Settings. Passive monitors observe modifier-key states, their key codes, and mouse clicks. Bunyek does not subscribe to ordinary key-down events from other apps; it checks only the system-provided numeric session-wide key-down count and latest key-down time to cancel an in-progress gesture when typing intervenes. It does not read or store typed text, block events, or change them. A custom key combination uses macOS hotkey registration.
• Mac clipboard: Auto-Translate Clipboard on Open, which translates copied text when the popover is opened with the shortcut or menu bar, is on by default and can be turned off in Settings. Using the shortcut again while the popover is open closes it without reading the clipboard. During the same app session, an already handled copy is not placed in the input again. Copying the same text again in another app is treated as a new copy. Results copied by Bunyek are not automatically pasted back; after the app is relaunched, text still on the clipboard can be placed again. Clipboard items marked confidential by password managers are not read. Translations follow the same history settings as typed text.
• To request access, correction, or deletion of information sent directly to support, email sont0729@gmail.com. Beek is operated by Taeseop Son, 28 Yeokjeon-ro, Unit 403, Jeungpyeong-eup, Jeungpyeong-gun, Chungcheongbuk-do, Republic of Korea.
• Children under 14 should not send personal information by support email without a guardian's consent. Beek deletes such information promptly if it learns that it was submitted without consent.

↑ 한국어 전문으로 돌아가기 / Back to the complete Korean notice