CrystalEngine Privacy Policy
General Provisions
The Company collects nothing from users directly.
(1) BS Planet (hereinafter the "Company") establishes and publishes this Privacy Policy (hereinafter this "Policy") with respect to the processing of personal information in CrystalEngine (hereinafter the "App").
(2) The App is a completely private app that finds and opens the files, photos, music, and records on the device. All processing happens on the user's device, and the contents of the user's files are never sent to a server.
(3) The Company does not collect even device information directly. There is no account or login in the App, and accordingly the Company holds no user information.
(4) Provided that, where a user watches an ad for a "one-day ad pass," Google AdMob may collect an advertising identifier. The boundary between the Company's direct collection and such collection shall be set out in Article 4.
Definitions
For the purposes of this Policy, the following terms shall have the meanings set out below.
1. "Company" means BS Planet, the developer that develops and distributes the App.
2. "App" means CrystalEngine, which the Company distributes.
3. "User" means a person who installs and uses the App.
4. "Device" means the terminal on which the user has installed the App.
5. "Index" means the database that the App creates within the device for unified search.
6. "Optional feature" means a feature that operates only where the user has turned it on. Its principal examples shall be as set out in Article 3 (1).
7. "Trail" means the record of the user's activity that the App leaves within the device and shows on the activity timeline, the composition of which shall be as provided in Article 7.
Article 1 (Information the Company Collects Directly)
(1) There is no information that the Company collects directly from users. The Company collects no information from users directly.
(2) The Company does not collect device information, and it does not collect information that could identify a user.
(3) There is no sign-up or login in the App.
(4) Google's collection through ads shall be set out separately in Article 4.
Article 2 (Processing Carried Out Only on the Device)
(1) The information set out in each of the following subparagraphs is stored only in an index on the user's device and is not sent to any server. Provided that, where the user has turned on an optional feature under Article 3, a photo's location coordinates in subparagraph 2 are sent to the relevant provider to the extent that feature requires, and Article 3 sets out that extent and who receives them.
1. The file and document contents read for search
2. The metadata of photos and music
3. Contacts, calendar, and messages, only when the user turns them on (messages are SMS and MMS messages read from the device's message store; their scope and handling are set out in Article 5, paragraph (5), and the scope and handling of contacts are set out in Article 5, paragraph (6))
(2) The index database is encrypted on the device (SQLCipher).
(3) Provided that, where the App fails to open the encrypted index, the index may be stored unencrypted. That happens where the device keystore (Android Keystore) cannot supply the encryption key, where the encryption library cannot be loaded, where storage is unavailable, or where the cause cannot be determined. The App tells the user when that happens.
(4) The network is on by default, and the user may turn it off at any time under "Network Access" in Settings. Turning it off means the App does not connect to the internet. Core features such as search, indexing, document viewing, and lyrics display keep working while it is off, and only model downloads, map display, and the check with Google Play for a newer version stop. Provided that, in the Google Play edition that carries ads, the ad consent check and the ad requests made after the user taps to watch an ad are not subject to this switch; they take place at the time set out in Article 4, paragraph (5). The purchase check that Google Play handles is not subject to this switch either. The App's network status notice says so as well.
(5) Speech transcription and text recognition (OCR) run on the device with an engine that comes with the App or that the user has downloaded. The user can start them directly with "Transcribe now" and "Read text in photo", and when the speech engine has been downloaded, scanning also transcribes recordings within the size and period set in Settings, which the user can turn off in Settings. The recordings, the photos, and the results are not sent off the device, and the results are stored in the index described in paragraph (1) and used for search.
(6) Photo editing (cropping, rotating, straightening, and adjustments) takes place only on the device, and the photo being edited is not sent off the device. When an edited photo is saved as a copy, the photo's location information (GPS coordinates) is left out by default and is included only when the user turns on "Include location" on the save screen. When the original is overwritten, the original location information is kept by default because the same photo has been corrected, and the user can turn this off as well. Before it is overwritten, the original is first placed in the App's trash.
(7) In photo classification, a model on the device that comes with the App counts only the number of faces and the amount of text; face images and feature values are neither stored nor sent.
(8) When the user turns on "Auto-scan when files change" (off by default), the device's system reports changes to the file list, so the App adds new files to the index on the device even while the App is closed, and it does not connect to the internet when it does so. Music and video have a service and a notification that keep playback going after the user leaves the screen.
Article 3 (Optional Features the User Turns On)
(1) Optional features include those set out in the following subparagraphs. This enumeration is given by way of example and does not limit the optional features in their entirety.
1. Converting a photo's location to an address
2. Voice recognition
3. Maps
4. On-device model downloads
5. Cast and DLNA output
(2) Only when the user turns on and uses an optional feature is the minimum query needed for that feature sent to the relevant provider. Converting a photo's location to an address sends the location coordinates to the device's system geocoding service, and maps send the tile coordinates of the map area being viewed to the OpenStreetMap tile server. On-device model downloads fetch model files from the Hugging Face and Google repositories when the user requests them. Cast and DLNA output discovers devices on the same network by multicast and opens a temporary server on the device to deliver the file being cast to the device the user chose; the file does not leave the user's network. Voice search uses the on-device recognizer first, but on devices where it is unavailable it falls back to the system recognizer, and the voice the user spoke then leaves the device through the device's system.
(3) Even in that case the contents of the user's files are not sent to any server, and the Company neither receives nor stores those queries. Files served by the temporary on-device server during casting go only to the device the user chose within the user's own network.
(4) These features are enabled in two different ways. Maps follow the “Network Access” switch in Article 2(4); that switch is on by default, so they operate without the user turning them on separately. Converting a photo's location to an address, voice recognition, on-device model downloads, and Cast and DLNA output operate only when the user starts them each time they are used. To stop the former, turn off “Network Access”.
(5) The user may turn off "Network Access" in Settings. Turning it off stops any communication the app makes on its own. Communication by the voice-recognition fallback, which the device's system recognizer performs on the app's behalf, follows the device settings rather than the app's switch.
Article 4 (Advertising, Payment, Updates, License)
(1) With respect to advertising, payment, updates and license as well, the Company still collects nothing from users directly.
(2) The user may use the app free of charge for 14 days from the first launch, and the free trial ends when the 14 days have passed. The current edition does not offer the "one-day ad pass" and the app code does not start the ad SDK, so no ad is played and no ad consent check is made. The library of the ad SDK remains inside the app, so paragraphs (3) to (6) of this Article apply to an edition that offers the "one-day ad pass" again, in which a rewarded ad is shown when the user chooses to watch one and that ad is served by Google AdMob.
(3) AdMob may collect and use the advertising identifier (AD_ID), the IP address, device and app information, and ad-interaction data for ad delivery and measurement, and it may process them outside the country. The ad SDK works only when the user taps to watch an ad, so this collection starts at that moment, and before the tap the ad SDK does not fetch ads in advance. During the ad consent check under paragraph (5), however, Google's consent tool communicates with Google to find out whether the user is in a region that requires consent. This is processing that Google performs under its own privacy policy.
(4) The Company neither receives nor stores that information, and the user's file contents, search terms, and index are not used for advertising nor passed to the ad provider.
(5) Ads do not appear automatically and play only when the user chooses to watch them. Users who purchase the lifetime edition are not shown ads. The ad consent check takes place when the App is opened in the Google Play edition after the user has agreed to the Terms on the first-run screen and while no lifetime purchase has been confirmed; on a device where a lifetime purchase has been confirmed it does not take place. On the first launch right after a purchase, before the App has reflected it, it may take place once. The ad SDK itself does not work during this check either and works only when the user taps to watch an ad.
(6) Where consent is required (such as in the EEA), personalized-ad consent is obtained before the first ad, and the user can change or withdraw it at any time under "Ad privacy options" in Settings.
(7) The conditions of use shall be as set out in the following subparagraphs.
1. The user may use the app free of charge for 14 days from the first launch. The free trial ends when the 14 days have passed, and it is not limited by the number of runs or the time of use.
2. After that the user can keep using it with a lifetime purchase (a one-time purchase) or a 3-month pass (a prepaid plan that does not renew automatically). The "one-day ad pass" is not offered in the current edition.
3. There is no separate per-use limit on document viewing, search, music, photos, or video.
4. There is no automatically renewing subscription and no license key.
5. "Tell a friend" only opens the sharing sheet and hands an introductory line and the Google Play link to the app the user picks; the Company and the app do not know what the user picked and receive nothing.
(8) Payment is handled by Google Play and made anonymously, so the Company cannot know who paid; all the Company can see is a purchase identifier (purchase token and product ID). The app checks the Google Play signature on that purchase record on the device with its own public key and does not send the purchase record to the Company or anywhere else. From the confirmed purchase record the app calculates whether the lifetime edition is owned and the expiry time of the 3-month pass, signs these values and keeps them only on the device; it does not send them out of the device. The app writes only on the device whether the "Tell a friend" prompt has been shown. The app writes the time the free trial started on the device and, so that the free trial does not start over when the app is reinstalled under the same Google account, also stores it in Block Store, a storage area provided by Google Play services and tied to the user's Google account. What the app stores in Block Store is limited to three values: the trial start time, the number of the trial rule that applies, and a check value. It does not store the account, device identifiers, purchase information, or usage records. The Company does not receive these values. Because these values are restored on reinstallation or on setting up a new device only if the user has turned on Google backup, the free trial may start again after reinstallation when Google backup is off. The app includes these values in Google's cloud backup only when the device has a screen lock and end-to-end encryption is available. So that turning back the device clock does not lengthen the free trial, the app also writes only on the device the time the app was last opened.
(9) Updates are handled by Google Play. When it starts, the App only asks Google Play whether a newer version exists (at most once every 6 hours, and the user can turn this off in Settings) and, if one does, shows a notice banner inside the App; the App does not download or install an installation file by itself.
(10) The ad SDK of the Google Play edition also declares Android's ad-services permissions (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_TOPICS, ACCESS_ADSERVICES_ATTRIBUTION). The latter two belong to Android Privacy Sandbox, which handles interest topics and ad conversion measurement on the device instead of the advertising identifier; they work only on devices where Google has enabled that feature, and the user can turn them off under Privacy in the device settings. When requesting ads the App does not tag them as child-directed and limits the ad content rating to PG.
Article 5 (Permissions and Their Purposes)
(1) The permissions the Company uses and their purposes are set out in the table below, and nothing read with any permission is used for advertising, analytics, or profiling.
(2) The table lists every permission the user has to grant. Normal permissions granted automatically at installation, such as internet access and network state, are not listed, and where communication actually happens is set out in Article 3 and Article 4.
(3) Some permissions differ depending on where the user obtained the app, and the table says so for those.
| Permission | Purpose |
|---|---|
| All files access | Searching and managing all files (the core feature) |
| Photos, videos, music | Media listing and playback |
| Photo location | Reading where a photo was taken (when address conversion is on) |
| Calendar | Unified search index |
| Contacts | Adding the names, phone numbers, email addresses, and company names of the device's contacts to the unified search index on the device, and showing a name next to a message sender's number. Requested only when you turn on Contacts in Search Targets, and only after the in-app consent sheet has been shown; it is not granted in advance. What is read and how it is handled are set out in paragraph (6) |
| SMS and MMS messages | Adding messages in the device's message store to the unified search index on the device. Requested only when you turn on Messages in Search Targets or message records in the trail, and only after the in-app consent sheet has been shown; it is not granted in advance. What is read and how it is handled are set out in paragraph (5) |
| App usage history | The activity timeline |
| Location (current location) | Recording the route on the activity timeline - your current location is sampled only while you are using the app (no background collection). Requested only when you turn on "location history" in the timeline; the app as distributed does not have this permission, so the feature is turned off. Any sampled coordinates are stored only in the activity records on the device |
| Microphone | Voice search and spectrum display |
| Camera | Taking a photo to find similar images |
| Notifications | Showing indexing progress (can be hidden in Settings) and playback controls for music and video |
| Biometric authentication | Unlocking with a fingerprint or similar when app lock is on. Biometric data is verified by the device's system, and the App receives only whether it succeeded |
| Wi-Fi multicast | Discovering devices on the same network when Cast or DLNA output is started |
(4) The app works even if the user does not grant a permission; only that feature is unavailable.
(5) SMS and MMS messages are handled as follows.
1. Each time the user turns on Messages in Settings > Search Targets or turns on message records in the trail, the app first shows a consent sheet describing what is read, the cautions, and how the data is handled, and only after the user agrees does it show the device's permission dialog. If the user has refused the permission so that it is no longer asked, the app directs the user to the app info screen in the device settings.
2. The app reads the sender address, body, and time of SMS messages and whether each was received or sent, and the text parts of MMS messages. For this the app uses only the permission to read messages (READ_SMS).
3. For attachments to MMS messages, such as photos, videos, and files, only the file name (or a name the app derives when there is none), the format (MIME type), the size, the time, the sender, and the conversation ID are added to the index. The contents of attachment files are not copied into the app's storage; each time the user opens an attachment, the app reads it from the device's system message store. When the user opens an attachment in another app, the app grants read-only access only to the app the user chose.
4. Indexing and searching take place entirely in the index on the device (Article 2, paragraphs (2) and (3)), and the contents of messages and of attachment files are not sent off the device.
5. The app classifies messages on the device into ordinary and advertising and shows the facts confirmed in each message (diagnosis); it does not send messages to the Company or anywhere else for this classification or diagnosis. When the user changes the category of a message directly or creates a rule that hides messages the user does not want to see, those values are stored only in the index on the device and, as set out in Article 7, paragraph (8), are not included in backups or device-to-device transfers.
6. The app does not send messages or receive them for processing, and it does not modify or delete messages. It therefore does not use the permissions to receive SMS (RECEIVE_SMS) or send SMS (SEND_SMS), and it does not take the role of the default SMS app.
7. The app reads the message inbox while at least one of Messages in Search Targets and message records in the trail is on, and stops reading messages from the moment both are off. When the user turns both off, the app asks whether to delete the indexed messages, and if the user chooses to delete, it deletes the messages and attachment information in the index. The message records in the trail, the hide rules, and the categories the user changed directly are not deleted and remain, and the app says so in the same dialog. Message records in the trail are erased with Delete permanently under Article 7, paragraph (3), item 2. The user can withdraw the message permission in the device settings at any time, and messages in the index are also deleted together with the app when it is uninstalled.
8. Message previews kept on the trail timeline are stored with numbers such as verification codes, amounts, and account numbers, and with links, masked. The sender and the time remain as they are.
9. On screens where message bodies are visible (the message list, the message preview, and search results and the trail that contain messages), screenshots and screen recording are blocked regardless of the app lock setting.
10. An earlier edition also read messages from message backup files (XML), but the current edition does not, and on update, messages indexed from backup files are removed from the search index. Message records left in the trail remain until the user erases them by the method in Article 7, paragraph (3), item 2.
11. Messages contain the personal information of people other than the user (senders and recipients). The app uses that information only on the device of the user who has already received or sent those messages, for the user's own searches and warnings; the Company does not receive it and does not provide it to third parties. Accordingly, no provision to a third party of the kind that Article 17 (Provision of Personal Information) of the Personal Information Protection Act of the Republic of Korea makes subject to the data subject's consent takes place (original text at the National Law Information Center: https://www.law.go.kr/lsInfoP.do?lsId=011357).
12. Text drawn on the screen (messages, calendar notes, excerpts from notes, documents, and recording transcripts, recent search terms, and share previews) has numbers in the form of resident registration numbers, card numbers, and account numbers masked. The masking happens on the screen only; the index, search, copying, and sharing use the original text.
13. The App does not open links in messages. Copying a verification code, copying the body, making a call, adding to the calendar, and opening in the messages app work only when the user taps them, and pass only the value needed (the number, the body, or the conversation) to the app concerned.
(6) Contacts are handled as follows.
1. Contacts are one of the switches in Search Targets and are off by default, and the app does not ask for the contacts permission when it starts. When the user turns on Contacts in Search Targets, the app first shows a consent sheet, and only after the user agrees does it show the device's permission request. The consent sheet states what the app reads (names, phone numbers, email addresses, and company names), what it uses them for (building a search index on the device and showing a name next to a message sender's number), that the app never changes or deletes contacts and does not send them off the device, and that turning the switch off deletes the indexed contacts.
2. The app reads the names, phone numbers, email addresses, and company (organization) names of contacts. So that it can apply only what has changed, it also reads each contact's ID and last-modified time, and the list of deleted contacts (their IDs and deletion times). It does not read other items such as photos, notes, postal addresses, or birthdays. For this the app uses only the permission to read contacts (READ_CONTACTS); because it never changes or deletes contacts, it does not use the permission to write contacts (WRITE_CONTACTS).
3. The app uses the contacts it reads for these two purposes only. First, it adds them to the index on the device so that the user can search contacts and see contact cards. Second, it shows a name next to a message sender's number and lets the user find messages by that name. It also matches the numbers of contacts on the device for the contacts filter and the diagnosis, and does not send the numbers anywhere for this.
4. Contacts are not sent off the device. The app does not pass them to the Company, to third parties, or to the advertising SDK. Indexed contacts are kept in the encrypted index described in Article 2, paragraph (2), and, as set out in Article 7, paragraph (8), they are left out of backups and device-to-device transfer.
5. When the user edits or deletes a contact in the default contacts app, the app receives the device's change notification the next time it is opened, or while it is open, and applies only the changed and deleted contacts to the index. It therefore does not reread all contacts every time something changes.
6. When the user turns off Contacts in Search Targets, the app states in a confirmation dialog what will be deleted (the indexed contacts and the sender names shown next to message senders' numbers), and deletes them once the user confirms. If the user revokes the contacts permission in the device settings, the next time the app is brought to the foreground it turns the Contacts switch off, tells the user so, and deletes the indexed contacts. In either case, message senders are shown by number again instead of by name. Indexed contacts are also deleted when the app is uninstalled.
7. Contacts contain the personal information of people other than the user (data subjects). The app uses that information only on the user's device, for the user's own searches and message display; the Company does not receive it and does not provide it to third parties. Accordingly, no provision to a third party of the kind that Article 17 (Provision of Personal Information) of the Personal Information Protection Act of the Republic of Korea makes subject to the data subject's consent takes place (original text at the National Law Information Center: https://www.law.go.kr/lsInfoP.do?lsId=011357).
(7) The App does not start the installation of an installation file (.apk) and does not use the permission to install unknown apps (REQUEST_INSTALL_PACKAGES). The file list only shows the name, size, and location of an installation file and can send it to the trash.
Article 6 (Children Under 14)
(1) The Company does not knowingly collect the personal information of children under 14, and there is no path by which it collects personal information from children.
(2) The application market's target age is 13 and older.
Article 7 (Retention and Deletion)
(1) The Company holds no user data.
(2) The on-device index, settings, and records are deleted together when the user deletes the app. The user can also erase them from inside the app. Files in the App's trash, however, remain after the app is deleted, as set out in paragraph (9).
(3) The ways of erasing them from inside the app shall be as set out in the following subparagraphs.
1. The file index is handled from Settings > Storage scan: Clean up removes files deleted or changed by other apps from the index, and Full rescan deletes the index and rebuilds it from scratch. Delete index removes the index and leaves it empty; an emptied index is rebuilt when the user scans again or automatic scanning runs.
2. The trail consists of records of photos, searches, call recordings, messages, app usage, the screen turning on and off, unlocking, focus mode, and the installation and removal of apps, and it is erased from Settings > Trail (Delete permanently). The app does not delete the trail automatically by default. If the user chooses 30 days, 90 days, or 1 year in Settings > Trail > Keep trail for, the app automatically deletes entries older than that period on the device. Every source other than photos and searches is off by default and records only while the user keeps it on. Location cannot be turned on in the edition distributed today, as the table in Article 5 states, and messages are recorded only when the user has turned on message records and granted the permission under Article 5, paragraph (5).
3. Search history can be deleted in full from the search history sheet on the home screen, and Settings > Auto-delete history can automatically delete entries older than 7 or 30 days. Auto-delete is off by default.
4. Usage history (documents opened, songs, videos and recordings played, and menus visited) is erased with Clear all on the History screen. "Pick up where you left off" on the home screen and the personalized ranking of search results also use this history, so they are emptied as well. "Frequently Used Apps" on the same screen is part of the trail and is erased with the permanent deletion under subparagraph 2.
(4) Cleaning up or rebuilding the index does not erase the trail. In that case the trail has to be deleted separately with the permanent deletion under subparagraph 2 of paragraph (3).
(5) In the case of either deletion, no separate deletion request is needed.
(6) The only thing the Company holds is the email the user sends of their own accord when contacting it, together with the reply. The Company keeps it as a consumer complaint handling record for 3 years from the day the reply was completed and then deletes it (the period set by Article 6(1) of the Enforcement Decree of the Act on the Consumer Protection in Electronic Commerce of the Republic of Korea; original text at the National Law Information Center: https://www.law.go.kr/lsInfoP.do?lsId=009338), and the user may request its deletion earlier through the contact set out in Article 8.
(7) If the app closes unexpectedly, a record of it remains in the app's storage on the device. That record leaves the device only when the user sends it themselves with Share log under Settings > Diagnostics, and file names, links, email addresses, text in quotation marks, and numbers of five or more digits are masked in it.
(8) App data (index, settings, history) is set to be left out of backup tools such as Google backup and device-to-device transfer. There is no backup or restore feature that exports or imports app data, and on a new device the app indexes from scratch. The same applies to message hide rules and to categories the user changed directly, because they are kept in the index. The same applies to indexed contacts. The free trial start record in paragraph (8) of Article 4 (the trial start time, the number of the trial rule that applies, and a check value) is an exception to this setting, because it is stored in Block Store as that paragraph states.
(9) A file deleted in the App is first moved to the App's trash (the hidden folder .CrystalEngineTrash in the storage where the file was) and kept for 30 days; within that time the user can restore it or empty the trash, and items past the period are emptied when the trash screen is opened. This folder is not app data, so it remains after the app is deleted. Media files that cannot be put in the App's trash are sent to the device's system trash with the user's consent.
Article 8 (Inquiries and Amendment of the Policy)
(1) Inquiries about personal information and the exercise of rights under Article 9 are received by email (support@bsplanet.app).
(2) If this Policy changes, it is reflected in both "Settings > Privacy Policy" in the app and the public URL above.
- Developer: BS Planet
- Email: support@bsplanet.app
Article 9 (Rights of Data Subjects and How to Exercise Them)
(1) The user may at any time demand access to, correction or deletion of, or suspension of processing of the personal information the Company holds about them. Since the only thing the Company holds is the inquiry email under Article 7, paragraph (6), such demands concern that email and its reply.
(2) Demands are received by the email set out in Article 8, and the Company gives notice of the result within 10 days of receipt in accordance with article 41 of the Enforcement Decree of the Personal Information Protection Act of the Republic of Korea (original text at the National Law Information Center: https://www.law.go.kr/lsInfoP.do?lsId=011468). Where a demand is refused, the reason and the way to object are given together.
(3) The legal representative of a child under 14 may exercise these rights on the child's behalf in the same way.
(4) The index, settings, and records on the device are not held by the Company and are therefore not the subject of demands under this Article; the user erases them directly by the methods in Article 7. Google holds the originals of Google Play orders and reviews, so demands about them are best made through the user's Google account, and the advertising identifier can be reset or deleted in the device settings.
Article 10 (Destruction of Personal Information)
(1) When the retention period of an inquiry email (Article 7, paragraph (6)) has passed, the Company deletes the email and its reply in a way that cannot be recovered.
(2) Data on the device is deleted when the user deletes the app or erases it by the methods in Article 7; the Company holds no copy, so there is nothing further for the Company to destroy.
Article 11 (Measures to Ensure Security)
(1) The Company operates no server that stores users' personal information. Only the representative has access to the inquiry email account and the Google Play Console.
(2) The on-device index is encrypted with SQLCipher (Article 2, paragraph (2)), and the app uses HTTPS when it communicates with external servers. Casting, however, delivers files to the device the user chose within the user's own network, so that leg is plain HTTP.
(3) The user can require device lock or biometric authentication when opening the app with App Lock in Settings, and while App Lock is on, the App's screen is also hidden in the recent apps list and in screen captures.
Article 12 (Personal Information Protection Officer)
The Company is a small business run by a single representative and, under the small-business exception in article 32 of the Enforcement Decree of the Personal Information Protection Act of the Republic of Korea (original text at the National Law Information Center: https://www.law.go.kr/lsInfoP.do?lsId=011468), does not designate a separate personal information protection officer; in that case the representative acts as the protection officer and handles personal information protection and related grievances. The contact is the email set out in Article 8 (support@bsplanet.app).
Article 13 (Remedies for Infringement of Rights)
The user may seek advice on or report infringements of personal information to the following bodies. All are institutions of the Republic of Korea; users residing outside Korea may also report to the supervisory authority of their country of residence.
| Body | Contact |
|---|---|
| Personal Information Dispute Mediation Committee | 1833-6972, https://www.kopico.go.kr |
| Personal Information Infringement Report Center (KISA) | 118, https://privacy.kisa.or.kr |
| Supreme Prosecutors' Office, Cyber Investigation Division | 1301, https://www.spo.go.kr |
| Korean National Police Agency, Cybercrime Reporting System | 182, https://ecrm.police.go.kr |
Article 14 (Transfer of Personal Information Abroad)
While the app is in use, the information in the following table may be sent to businesses outside the country. The Company does not receive this information; each recipient processes and retains it under its own privacy policy.
| Recipient (country) | Information transferred | When and how | Purpose |
|---|---|---|---|
| Google LLC (United States) | Advertising identifier, IP address, device and app information, ad interactions | The current edition does not play ads or run the ad consent check because the app code does not start the ad SDK; the following transfer takes place only in an edition that offers the "one-day ad pass" again: The ad consent check when the App is opened in the Google Play edition after agreeing to the Terms, and the ad SDK's network transmission after the user taps to watch an ad | Ad delivery, measurement, fraud prevention (https://policies.google.com/privacy) |
| Google LLC (United States), Google Play | Purchase information tied to the Google account (the App receives only a purchase identifier), the app package name, the installed version number | When paying; when the purchase check and the check for a new version run as the App is opened | Payment processing, notice of a new version |
| Hugging Face, Inc. (United States), Google LLC (United States) | IP address, name of the requested model file | When the user requests a model download | Downloading the speech recognition and image embedding models |
| OpenStreetMap Foundation (United Kingdom) | Tile coordinates of the map area being viewed, app package name, IP address | When maps are turned on and viewed | Displaying map tiles |
| Provider of the device's system services (usually Google LLC, United States) | Photo location coordinates; voice during the voice-recognition fallback | When address conversion is turned on and used; when voice search is used on a device without an on-device recognizer | Address conversion, voice recognition |
| Google LLC (United States) | Trial start time, number of the trial rule that applies, check value | Stored in Block Store tied to the user's Google account when the app is opened; included in Google backup if the user has turned on Google backup and the device has a screen lock that makes end-to-end encryption available | Keeping the free trial from starting again under the same Google account (https://developer.android.com/identity/block-store) |
Addendum
(1) This Policy takes effect from 2026-09-01.
(2) The last revision date of this Policy is 2026-10-28.
(3) The revisions of 2026-10-25 and 2026-10-26 describe the handling of messages and contacts, message classification and diagnosis, and when the ad SDK works. They contain nothing unfavourable to users and therefore took effect on the date of revision.
(4) The revision of 2026-10-28 states that the free trial is 14 days from the first launch, that the app code does not start the ad SDK while the "one-day ad pass" is not offered, the 3-month pass, the values signed and kept on the device, and "Tell a friend" (Articles 4 and 14, the table). The same revision also states that the app does not start an installation, the transcription of recordings by scanning, counting faces, the background operation of auto-scan, the check with Google Play for a new version, the masking of numbers and the handling of links in messages, the App's trash, and the scope of masking in crash records (Articles 2, 5, and 7). This revision takes effect on 2026-10-28.
(5) The revision of 2026-10-28 states that the free trial start record (the trial start time, the number of the trial rule that applies, and a check value) is stored in Block Store tied to the user's Google account, and that the time the app was last opened is written on the device so that turning back the device clock does not lengthen the free trial (Articles 4 and 7, and the table in Article 14). This revision takes effect on 2026-10-28.