ConnectionValue Inc. (hereinafter the "Company") establishes and discloses this Privacy Policy in accordance with applicable laws, including the Personal Information Protection Act, to protect users' personal information and to promptly and smoothly handle related grievances.
1. Personal Information Collected and Collection Methods
1.1 Personal Information Directly Collected by the Company
PhotoKip (hereinafter the "App") does not require account registration or login. Collections, spaces, photos, videos, titles, descriptions, memos for photos and videos, and similar content saved by users in the App are stored on the user's device and are not transmitted to the Company's content servers. On iOS, content is also stored in the user's private Apple iCloud database when iCloud Sync is enabled and its requirements are met.
However, if a user directly contacts the Company by email or another method, the following information may be collected.
| Collected Items | Purpose | Retention Period |
|---|---|---|
| Email address, inquiry details, attachments | Customer support, troubleshooting, dispute response | Until the inquiry is handled and for any period required by applicable laws |
1.2 Information Stored on the Device but Not Transmitted to Company Servers
The following information is stored in the user's device internal storage to provide the App's core features. The Company cannot access or restore this information.
| Stored Items | Purpose |
|---|---|
| Collection names, descriptions, spaces | Organizing photos and videos |
| Photos, videos, thumbnails, memos for photos and videos | Collection management and viewing |
| Filenames, MIME types, capture dates, added dates, resolution, file size, video duration, shooting location information when included in photos or videos or recorded because the user turned on the camera's location options, and other metadata for photos and videos | Search, sorting, detailed information display, and managing original photos and videos |
| App settings such as language, theme, camera launch setting, and gallery view setting | Maintaining the App environment |
1.2.1 Optional iCloud Sync
On supported Apple devices, enabling sync sends spaces, collections, photos, videos, previews, names, descriptions, memos, ordering, custom backgrounds and related metadata to the user's private CloudKit database for access from devices using the same iCloud account. It uses the user's iCloud storage quota and is not transmitted to Company content servers. The app uses CloudKit encrypted fields for content and CloudKit asset encryption for files. The local account boundary uses an environment-specific hash of the account identifier; diagnostic events exclude account identifiers.
Device settings, unfinished drafts and review tasks, and locally preserved content after a reset are excluded from automatic sync. Turning sync off stops new transfers and does not delete existing iCloud data. Deletions of synced content are applied to other connected devices. Uninstalling the app does not by itself delete iCloud data; unsent changes and device-only content can be lost. Users can manage cloud content through app deletion actions and Apple's iCloud storage controls.
Apple's policies apply to CloudKit processing. Implementation references:
- Private databases: https://developer.apple.com/documentation/cloudkit/ckcontainer/privateclouddatabase
- Encrypting user data: https://developer.apple.com/documentation/cloudkit/encrypting-user-data
1.3 Information That May Be Automatically Collected During Service Use
During use of the App, the following information may be automatically collected and processed through third-party SDKs or service providers.
| Collected Items | Purpose | Collected/Processed By |
|---|---|---|
| Advertising identifiers (ADID/IDFA), app instance or installation identifiers, app set IDs or vendor identifiers, IP address, device model, OS version, app version, language and region information | Personalized and non-personalized advertising, ad performance measurement, app analytics, fraud prevention | Google AdMob, Firebase Analytics, Amplitude |
| App usage events such as screen views, button taps, feature usage, search and sorting (excluding the raw search query, and including query length and result counts), purchase and restore events, ad clicks | Service improvement, statistical analysis, feature stabilization | Firebase Analytics, Amplitude |
| Aggregate sync outcomes, sanitized error codes, duration and pending-count ranges, app and OS versions | Improving sync reliability | Firebase Analytics, Amplitude |
| App crash logs, error information, performance information, device state | App stability improvement and bug fixes | Firebase Crashlytics |
| Push notification tokens such as APNs/FCM tokens, push subscription status, notification receipt and click information, first and last session time, session count, usage duration, device OS, language, timezone, country, app version, application identifier, carrier, device model, IP address | Sending push notifications and managing notification settings | OneSignal |
| In-app purchase information, product IDs, purchase and restore history, Premium access activation status, RevenueCat anonymous app user ID, advertising and device identifiers such as IDFA/IDFV/Google advertising ID, IP address, Meta anonymous ID, ATT consent status | Managing Premium access, restoring purchases, purchase conversion and ad performance measurement | RevenueCat, Apple App Store, Google Play |
| Firebase installation ID, app version, platform information, remote configuration values | App update notices, maintenance management, feature configuration | Firebase Remote Config |
| Meta anonymous ID, App Events such as app activation, install events and selected feature-use events, advertising identifiers, ATT/ad tracking authorization status | Meta ad performance measurement, purchase conversion attribution, reflecting ad tracking consent | Meta Platforms, RevenueCat |
| Ad consent status, iOS app tracking authorization status | Determining whether personalized ads can be provided and complying with platform policies | Google AdMob, Meta Platforms, Apple App Tracking Transparency |
The App does not upload the actual contents of photos, videos, titles, descriptions, or memos saved by users to Company servers. However, if a user uses a sharing feature to directly send content to an external app or third party, the privacy policy of that external service applies.
1.4 Device Access Permissions
The App uses the following device access permissions.
| Permission | Purpose | Required |
|---|---|---|
| Camera | Capturing photos and videos to add to collections | Optional |
| Microphone | Recording audio when capturing videos | Optional |
| Photos/Gallery | Selecting existing photos and videos, showing the in-app grid of photos and videos, saving to the device gallery, and deleting originals selected by the user | Optional |
| Location (iOS/Android) | Only when the user turns it on: adding a capture-place watermark to captured photos and saving the capture location in captured photos and videos (see Section 1.4.1) | Optional |
| Notifications | Receiving push notifications | Optional |
| Internet | Integration with external services such as ads, app analytics, error collection, remote configuration, push notifications, in-app purchases, and purchase restoration | Required |
Photos and videos selected or captured via camera or gallery, and any shooting location information included in those photo and video files, are stored in the user's device internal storage and may also be sent to private iCloud as described in Section 1.2.1. They are not transmitted to Company content servers.
1.4.1 Capture Location (Place Watermark and Save Location Info)
The camera offers a watermark option that stamps the capture time and place onto captured photos as text, and a Save location info option that records the capture location in captured photos and videos. Both options are off by default, and the App uses the device's current location only when the user turns them on.
- Location is processed only on the user's device and stored in the captured photo and video files (such as EXIF metadata) and in App data. It is not transmitted to Company servers or collected for analytics; App analytics events contain no coordinates or addresses.
- To show the place as an address, the device operating system sends the coordinates to the address lookup service of Apple (iOS) or Google (Android), which is governed by each company's privacy policy. The Company does not receive the coordinates or the address in this process.
- Watermark text becomes part of the photo and cannot be removed after saving. When photos or videos saved with these options are shared externally or exported to the device gallery, the location information contained in the files may be passed along.
- If iCloud sync is on, these files are also stored in the user's private iCloud as described in Section 1.2.1.
- Users can turn the camera options off or revoke the location permission in device settings at any time, after which location is not used for subsequent captures.
1.5 Website
The PhotoKip website stores a photokip-language cookie for up to one year to remember a selected display language. It contains only a language code and can be deleted in browser settings.
These provisions apply only to the six localized main PhotoKip landing pages in development, preview, and production. Privacy-policy, terms, and support pages are outside the tracking scope. They are effective October 7, 2026; technical rollout may occur on or after that date.
Before an Allow or Decline choice, Google Analytics operates in Advanced Consent Mode with analytics_storage, ad_storage, ad_user_data, and ad_personalization denied. It may send cookieless basic page, session, and engagement statistics and, where supported, detailed approximate location and device information. A lightweight bespoke Meta PageView request also operates before a choice, but excludes browser credentials and cookies. This is not a claim of anonymity, strict necessity, legal exemption, or Meta's official consentless mode. Both may receive normal IP and browser headers, sanitized page URL, validated approved UTMs, locale, page type, environment, and mode; GA also receives a safe referrer origin and may use transient request/session identifiers. Before consent, stable first-party cookies are not used for analytics or advertising, and our code supplies no manual User-ID. No click, scroll, FAQ, or language-action tracking occurs before consent.
The interface provides equally prominent Allow and Decline buttons and Cookie settings in each scoped-page footer; declining does not restrict the website or store links. Both choices are stored as essential photokip-tracking-consent version 2 in localStorage for up to 180 days; version-1 choices are requested again. Approved UTM keys are utm_source, utm_medium, utm_campaign, utm_content, and utm_id; utm_term, free-search data, and user identifiers are not used. Safe campaign codes may be sent before consent without browser storage. Only after acceptance, the latest valid campaign is retained for the current tab in sessionStorage as photokip-utm. Website and App identities are not automatically linked.
After acceptance, GA records the same basics plus Company-configured store_link_click, and may automatically record first_visit, session_start, and user_engagement. Meta uses its full SDK for PageView and StoreLinkClick; detailed page/product auto-configuration remains on and auxiliary events such as SubscribedButtonClick may occur. Advanced matching, code-free automatic conversion detection, and automatic advanced matching are off. Company-configured events are only PageView/page_view and StoreLinkClick/store_link_click; a store-link click is not an install, purchase, lead, or subscription. Google Ads performance measurement is permitted, but website ad personalization remains denied, Google signals and user-provided data are off, allow_google_signals is false, and no new audiences, campaigns, budgets, or app-campaign goals are created. Existing App advertising settings are unchanged. No GTM, Meta Conversions API, MMP, or other website analytics is used.
After acceptance, optional GA _ga/_ga_* analytics cookies may be used for no more than 180 days, capped by the remaining consent period on a non-rolling basis. Relevant Google Ads attribution cookies and Meta cookies are used only after consent; their durations are governed by provider policies and browser controls. Accessible such cookies are deleted on withdrawal. Google and Meta may process consented ad-click IDs (fbclid, gclid, dclid, gbraid, wbraid) and cookie identifiers. Meta cookie handling follows Meta policy and is not represented as a universal 180-day period. The existing language cookie is unchanged. Hosting may process basic access logs for delivery and security. App SDK and website processing remain separate.
2. Purpose of Collection and Use of Personal Information
The Company uses collected personal information for the following purposes.
| Purpose | Details |
|---|---|
| Service provision | Managing photo and video collections, maintaining app settings, and providing Premium features |
| Customer support | Responding to inquiries, checking errors, and handling disputes |
| Service improvement | Improving features through analysis of app usage statistics |
| App stability | Resolving issues through analysis of crash logs and error information |
| Advertising | Displaying ads and providing personalized ads through Google AdMob |
| Push notifications | Sending service-related notifications and announcements |
| Purchase management | Verifying Premium access status and restoring purchases |
| Website analytics and advertising measurement | Cookieless basic statistics before a choice, and after acceptance Google Analytics and Meta measurement of scoped landing-page visits and store-link clicks |
| Legal and policy compliance | Complying with App Marketplace policies, ad consent requirements, and privacy laws |
2.1 Subscription and Access Information
Apple App Store, Google Play and RevenueCat may process product and transaction identifiers, purchase history, plan type, billing period, renewal status, expiration dates, billing issues, grace periods and pauses to verify and manage monthly, annual and lifetime purchases, restorations, changes, renewals, cancellations and refunds. RevenueCat links purchase status using an anonymous app user ID; no separate PhotoKip account is required. The device retains the latest Premium activation flag for offline use and the share extension, appearance preferences and acknowledgements of status notices. Payment details such as card numbers are handled by the store and are not collected directly by the Company. This processing does not transmit original photos, videos or notes to RevenueCat.
3. Provision of Personal Information to Third Parties and External Services
The Company does not sell saved content or collect it on Company content servers. Optional iCloud Sync uses Apple CloudKit as described in Section 1.2.1. However, the following third-party services required for app operations may collect and process user information.
For the website processing described in Section 1.5, Google and Meta may process the information described below before or after a choice according to the respective phase; optional cookies and store-link tracking require acceptance.
| Recipient | Items Provided or Processed | Purpose | Retention Period |
|---|---|---|---|
| Google LLC (Firebase Analytics) | Device information, app usage events, app instance or installation identifiers, advertising identifiers | Service analysis and improvement | Per Google's Privacy Policy |
| Google LLC (Firebase Crashlytics) | Crash logs, error information, device state, performance information, Crashlytics/Firebase installation identifiers | App stability improvement | Per Google's Privacy Policy |
| Google LLC (AdMob) | Advertising identifiers, IP address, device/account identifiers, device information, ad consent status, ad impression and click information, user interactions, diagnostic and performance information | Ad display, personalized and non-personalized ads, ad performance measurement, fraud prevention | Per Google's Privacy Policy |
| Amplitude Inc. | Device information, app usage events and event properties, app installation or device identifiers | Product analytics and service improvement | Per Amplitude's Privacy Policy |
| OneSignal Inc. | Push notification tokens, push subscription status, notification receipt and click information, session and usage duration information, device OS, language, timezone, country, app version, application identifier, carrier, device model, IP address | Sending and managing push notifications | Per OneSignal's Privacy Policy |
| RevenueCat Inc. | In-app purchase information, product IDs, purchase and restore history, Premium access activation status, RevenueCat anonymous app user ID, advertising and device identifiers, IP address, Meta anonymous ID, ATT consent status | Premium access management, purchase restoration, purchase conversion and ad performance measurement | Per RevenueCat's Privacy Policy |
| Meta Platforms, Inc. | Meta anonymous ID, App Events such as app activation, install events and selected feature-use events, advertising identifiers, ATT/ad tracking authorization status, purchase conversion events through RevenueCat | Meta ad performance measurement, purchase conversion attribution, reflecting ad tracking consent | Per Meta's Privacy Policy |
| Apple Inc. (iCloud / CloudKit) | Synced content, files and metadata | User-enabled device synchronization | Until user deletion and subject to Apple iCloud policies |
| Google LLC (website Google Analytics and Google Ads measurement) | IP/browser headers, sanitized URL, safe referrer origin, approved UTMs, locale, page type, environment, mode, cookieless page/session/engagement statistics and, where supported, approximate location/device data before a choice; after acceptance the same data, optional Google analytics/Ads cookies and ad-click IDs, and store_link_click; transient request/session identifiers may be used | Basic website statistics before a choice; analytics and Google Ads performance measurement after acceptance | Event detail: 2 months; user detail: 14 months; provider policy and browser controls apply |
| Meta Platforms, Inc. (website Meta) | Before a choice: normal IP/browser headers, sanitized URL, approved UTMs, locale, page type, environment, and mode in a lightweight bespoke PageView request without browser credentials/cookies. After acceptance: full-SDK PageView/StoreLinkClick, Meta/click cookie identifiers, consented ad-click IDs, enabled detailed public page/product information, and possible auxiliary SDK events | Basic PageView measurement before a choice; scoped-page and store-link measurement after acceptance | Per Meta Privacy and Cookie Policies |
| Apple Inc. / Google LLC | In-app payment information, purchase history, purchase status related to App Marketplace accounts | App Marketplace payment processing and refunds | Per each App Marketplace policy |
For details on how each third-party service processes personal information, please refer to their respective privacy policies.
- Google: https://policies.google.com/privacy
- Amplitude: https://amplitude.com/privacy
- OneSignal: https://onesignal.com/privacy_policy
- RevenueCat: https://www.revenuecat.com/privacy
- Meta: https://www.facebook.com/privacy/policy/
- Meta Cookie Policy: https://www.facebook.com/privacy/policies/cookies/
- Apple: https://www.apple.com/legal/privacy
- Google Play: https://policies.google.com/privacy
4. International Transfer of Personal Information
Some third-party services used by the App are provided by overseas companies, and personal information may be transferred internationally during use of the Service.
The website transfer described in Section 1.5 is separate from App SDK processing. It may occur before a choice only for the cookieless basic measurement described there; optional cookies and store-link tracking require acceptance.
| Recipient | Destination Country | Transferred Items | Purpose | Timing and Method | Retention Period |
|---|---|---|---|---|---|
| Google LLC | United States, etc. | Device information, IP address, advertising identifiers, app instance or installation identifiers, app usage events, crash logs, user interaction, diagnostic and performance information, ad information | App analytics, error improvement, advertising, fraud prevention | Network transmission through SDKs while using the App | Per Google's policy |
| Amplitude Inc. | United States, etc. | Device information, app usage events, app installation or device identifiers | Product analytics and service improvement | Network transmission through SDKs while using the App | Per Amplitude's policy |
| OneSignal Inc. | United States, etc. | Push notification tokens, push subscription status, notification-related information, session, device and app information, IP address | Sending and managing push notifications | Network transmission through SDKs when configuring notifications or using the App | Per OneSignal's policy |
| RevenueCat Inc. | United States, etc. | In-app purchase information, product IDs, purchase and restore history, Premium access activation status, RevenueCat anonymous app user ID, advertising and device identifiers, IP address, Meta anonymous ID, ATT consent status | Purchase status verification, purchase restoration, purchase conversion and ad performance measurement | Network transmission through SDKs when launching the App, purchasing, or restoring | Per RevenueCat's policy |
| Meta Platforms, Inc. | United States, etc. | Meta anonymous ID, App Events such as app activation, install events and selected feature-use events, advertising identifiers, ATT/ad tracking authorization status, purchase conversion events through RevenueCat | Meta ad performance measurement and purchase conversion attribution | Network transmission through SDKs or RevenueCat integrations when launching, activating, purchasing, restoring, or measuring ad performance | Per Meta's policy |
| Google LLC (website Google Analytics and Google Ads measurement) | United States, etc. | IP/browser headers, sanitized URL, safe referrer origin, approved UTMs, locale, page type, environment, mode, cookieless basic statistics and, where supported, approximate location/device data before a choice; after acceptance the same data, optional cookies/ad-click IDs and store_link_click | Basic website statistics before a choice; analytics and Google Ads performance measurement after acceptance | Browser transmission on scoped-page view; optional cookies/store-link tracking only after acceptance | Event detail: 2 months; user detail: 14 months |
| Meta Platforms, Inc. (website Meta) | United States and other countries where Meta processes data | Before a choice: normal IP/browser headers, sanitized URL, approved UTMs, locale, page type, environment, and mode in a lightweight PageView request without browser credentials/cookies. After acceptance: full SDK PageView/StoreLinkClick, identifiers, detailed public page/product information, and possible auxiliary events | Basic PageView measurement before a choice; scoped-page/store-link measurement after acceptance | Browser transmission on scoped-page view; optional cookies/store-link tracking only after acceptance | Per Meta policies |
| Apple Inc. / Google LLC | United States, etc. | Payment information, purchase history, App Marketplace account-related purchase status | In-app payment processing and refunds | Transmission through App Marketplace systems during purchase or restoration | Per each App Marketplace policy |
5. Personalized Advertising
The App provides advertising through Google AdMob. Depending on the user's consent status, device settings, App Marketplace policies, and local laws, personalized or non-personalized ads may be displayed.
- Information that may be collected: Advertising identifiers (ADID/IDFA), app usage events, ad impression and click information, IP address, app set IDs or vendor identifiers, device information, diagnostic and performance information, Meta anonymous ID, app activation events, ATT/ad tracking authorization status
- How to opt out of ad personalization:
- Android: Settings > Google > Ads > opt out of ad personalization or reset the advertising ID
- iOS: Settings > Privacy & Security > Tracking > disable "Allow Apps to Request to Track"
- Ad consent management: Depending on region and policy, Google's ad consent form may be displayed.
- Premium access: Active monthly, annual and lifetime plans provide the same ad-removal benefit. Expiry alone does not automatically reactivate currently disabled advertising.
The App may use the Meta SDK and RevenueCat's integration with Meta to measure ad performance related to app activation, installs, and purchase conversions.
6. Retention and Use Period of Personal Information
6.1 Data Stored on Device
Collection data saved by users in the App (photos, videos, titles, descriptions, memos, spaces, metadata for photos and videos, etc.) is kept on the device and, when applicable, in private iCloud. When the App is uninstalled, app data stored on the device may be permanently deleted. The Company cannot access or restore this data.
6.2 Inquiry Information
If a user contacts the Company, the email address, inquiry details, and attachments are retained for the period necessary to handle the inquiry and respond to disputes, and then destroyed. However, such information may be retained for a period required by applicable laws.
6.3 Automatically Collected Data
The retention period for data collected through third-party services follows each service provider's privacy policy or App Marketplace policy.
Sync diagnostics use 15-minute aggregates and daily limits. The on-device pending queue is retained for at most seven days. It excludes photos, text content, file paths, account identifiers and content sync IDs. Contact support opens a reviewable email draft with limited diagnostics; it does not attach files or send email automatically.
6.4 Website Consent and Campaign Data
The photokip-tracking-consent version-2 value is retained for up to 180 days for either choice; version-1 choices are requested again. photokip-utm is retained only for the current tab session and only after acceptance. GA event detail is retained for 2 months and user detail for 14 months, with reset of user data on new activity enabled; aggregate reports may have different retention. GA _ga/_ga_* analytics cookies are limited to 180 days and the remaining consent period on a non-rolling basis. Relevant Google Ads attribution cookies and Meta cookies have durations governed by provider policies and browser controls; they are used only after consent, and accessible ones are deleted on withdrawal. Hosting logs follow existing host practices.
7. Procedures and Methods for Destroying Personal Information
7.1 Data on Device
- App deletion: Uninstalling the App may delete collection data and app settings stored on the device.
- Individual deletion: Users can delete collections or individual photos and videos within the App.
- Original deletion: If a user explicitly chooses to do so, original photos or videos in the device gallery may be deleted after being saved in the App. Users should choose carefully because original deletion may affect device gallery data.
7.2 Inquiry Information
The Company destroys inquiry information whose retention period has expired or whose processing purpose has been achieved in a way that cannot be restored.
7.3 Third-Party Service Data
- Advertising ID reset or ad personalization opt-out: Users can reset the advertising ID or restrict personalized ads in device settings.
- Push notification opt-out: Push notifications can be disabled in App settings or device settings.
- Purchase information: Purchase information stored by App Marketplaces and RevenueCat is managed according to each service's policy.
- Per-service deletion requests: Data collected by third-party services can be requested for deletion according to each service's policies.
7.4 Website Tracking Data
Users may change or withdraw consent through Cookie settings. Withdrawal records the new choice, stops optional cookies and store-link tracking, clears accessible first-party GA/Google Ads and Meta cookies and the photokip-utm session value, but cookieless basic page, session, and engagement statistics continue. It does not recall data already sent to Google or Meta; provider-held data requests follow their policies and applicable law.
8. Users' Rights and How to Exercise Them
Users may exercise the following rights in accordance with applicable privacy laws.
- Request information about personal data processing: Confirm the items of personal information collected and the purpose of use.
- Request correction or deletion of personal information: Request correction or deletion of inquiry information directly provided to the Company.
- Delete data on the device: Delete local data using in-app deletion features or by uninstalling the App.
- Opt out of ad personalization: Refuse personalized ads through device settings or an ad consent form.
- Opt out of push notifications: Refuse push notifications through App settings or device settings.
- Manage App Marketplace purchase information: Manage purchase history and refund requests through Apple App Store or Google Play accounts.
- Manage Website Tracking Consent: Accept, decline, or later change website tracking through Cookie settings without losing access to the website or store links.
Because the Company cannot access collection data stored on the user's device and in the user's private iCloud database, users must view, modify, or delete such data directly in the App or on the device. For exercising the above rights or inquiries regarding personal information, please contact the Privacy Officer below, and we will take prompt action.
9. Measures to Ensure the Security of Personal Information
The Company takes the following measures to securely manage users' personal information.
- Content storage separation: Content is stored on the device and in user-enabled private iCloud, and is not transmitted to Company content servers.
- Minimum collection principle: Only the minimum information necessary for service operation is collected and processed.
- Permission minimization: Camera, microphone, gallery, and notification permissions are requested when needed for a feature.
- Secure communication: HTTPS and other encrypted communication methods are used when communicating with third-party services.
- Access restriction: Inquiry information directly collected by the Company is accessed only within the scope necessary for business purposes.
10. Protection of Children's Personal Information
The App is available to users of all ages, but the Company does not intentionally collect personal information from children under the age of 14. If we become aware that personal information of a child under 14 has been collected, we will take reasonable steps to delete such information.
If a legal guardian has inquiries regarding the processing of a child's personal information, please contact the Privacy Officer below.
11. Privacy Officer
The Company designates a Privacy Officer as follows to oversee personal information processing and to handle user complaints and remedies.
| Item | Details |
|---|---|
| Company | ConnectionValue Inc. |
| Representative | Hyeonseung Kim |
| Privacy Officer | Hyeonseung Kim |
| hello@pollit.kr | |
| Address | 4F, 401-38, 31-11 Yesul-gil, Dong-gu, Gwangju, Republic of Korea |
12. Remedies for Rights Infringement
Users may contact the following organizations for dispute resolution or consultation regarding personal information infringement.
| Organization | Contact | Website |
|---|---|---|
| Personal Information Dispute Mediation Committee | 1833-6972 | https://www.kopico.go.kr |
| Personal Information Infringement Report Center | 118 | https://privacy.kisa.or.kr |
| Supreme Prosecutors' Office Cyber Investigation Division | 1301 | https://www.spo.go.kr |
| National Police Agency Cyber Bureau | 182 | https://ecrm.cyber.go.kr |
13. Changes to This Privacy Policy
This Privacy Policy is effective from the enforcement date. If there are additions, deletions, or modifications due to changes in laws or services, we will notify users through in-app notices or other methods designated by the Company at least 7 days prior to implementation. However, changes that do not materially affect user rights or urgent changes required for legal or policy compliance may be notified after they take effect.
Effective Date: March 27, 2025 Website Section Amendment Effective Date: October 7, 2026
Subscription Provisions Amendment Effective Date: October 26, 2026
Location Provisions Amendment Effective Date: November 6, 2026
Last Updated: November 6, 2026