Ingtalk Privacy Policy

Effective date: November 8, 2026

Itembus processes personal information for Ingtalk as follows.

1. Data and purposes

When you choose Kakao sign-in, Kakao and Supabase Auth process your app-scoped Kakao user ID and authentication session. We do not request your Kakao nickname, profile photo or email. App accounts use a keyed hash of the Kakao ID across devices; Kakao profiles are not copied to public Ingtalk profiles.

When you choose Google sign-in, Google and Supabase Auth process your Google account identifier, email and its verification status, and basic profile information for authentication. Google names, emails, and photos are not automatically copied to your public Ingtalk profile. App accounts use a keyed hash of the stable Google identifier across devices, not email matching. Points and chats are not automatically merged with phone accounts or other sign-in methods.

When you request linking, recent verification of the current account, verification of the additional method, and the registered device are required. Both methods then reference one internal account ID. Similar phone numbers, emails or devices alone never grant another account's data. One-time linking requests expire after 5 minutes and remain for retry-limit enforcement until scheduled cleanup one day after expiration.

Phone numbers and SMS verification records support signup, login and abuse prevention; numbers are not shown to other users. A random device credential is saved in secure device storage; the application database keeps its hash, a keyed phone-number hash and account bindings. Reinstall recovery uses a hash derived from the Android app-scoped device identifier or iPhone Keychain credential. The server stores a further keyed hash until account deletion, never the raw Android device identifier. Supabase Auth processes the actual phone number for SMS authentication. Internal user ID, nickname, age, and gender support profiles, age restrictions, and matching. Talk cards, posts, comments, reactions, chat activity, reports, and blocks support the service, disputes, and safety. Installation ID, app and OS version, push token, access records, and error records support same-number and same-device account verification, notifications, diagnostics, and abuse prevention. Photos and location are processed only when selected. The Google Mobile Ads SDK may automatically collect and share an approximate location inferred from IP address, app interactions such as launches, taps, ad views and video views, SDK diagnostics, and device identifiers such as the advertising ID and app set ID for ad delivery, measurement, analytics, and fraud prevention. Ad completion, ad transaction identifiers, and point-reward records support the 50-point reward, the 24-hour limit, and duplicate-reward prevention.

When you purchase points, RevenueCat and Apple App Store / Google Play process the internal app account ID, product, transaction and receipt identifiers, purchase time, amount, currency, country and refund information to verify purchases, credit points, prevent duplicate grants and handle refunds. Ingtalk does not directly collect card or bank account numbers. The internal app account ID recorded at purchase is retained separately as a payment-audit identifier without a phone number, email, or nickname, and remains after account linking or deletion for the period required for payment audits, refunds, legal obligations, and disputes.

Google Analytics for Firebase measures Android and iOS installs and advertising performance using first launches, sessions, app and OS versions, and app-instance identifiers. Measurement starts after you acknowledge this privacy policy. Phone numbers, email addresses, nicknames and chat content are not sent as analytics events. This measurement integration does not use AAID, IDFA, Android ID (SSAID), IDFV or personalized advertising signals. Google processes the analytics data, which is connected to Google Ads for install measurement.

Android releases with AppsFlyer measurement enabled process install, launch and session records, the AppsFlyer installation identifier, available Android advertising identifiers, app/SDK/OS versions, device, network, diagnostic and performance information, IP-derived approximate location, and advertising and install-referrer information for attribution, advertising analytics and install-fraud prevention. This integration does not directly send phone numbers, email addresses, nicknames, profile photos, chat content, precise location, internal member IDs. Measurement starts after the app privacy acknowledgement; there is currently no separate AppsFlyer opt-out control in the app.

iOS releases with SKAN measurement start AppsFlyer after acknowledgement of the revised privacy notice. With ATT authorization, IDFA, installation identifiers, install/launch/session records, app, device, network, diagnostic and performance information, IP-derived approximate location and advertising attribution data may be used and linked with Meta and X advertising data. Without ATT authorization, we disable IDFA and IDFV collection, apply SDK user anonymization and restrict advertising-partner sharing while processing installs, launches and events for Apple SKAdNetwork (SKAN) aggregate attribution. Anonymization removes or hashes identifying information at AppsFlyer; it does not mean no data leaves the device. Apple sends delayed, privacy-limited attribution reports, including copies to AppsFlyer. This integration does not collect IDFV or Apple Search Ads data. Core app functions remain available without ATT authorization. Change ATT in iOS Settings > Privacy & Security > Tracking. We recheck permission on return to the app and before event transmission. Previously transmitted data requires a separate deletion request. This notice applies to new iOS versions with SKAN measurement.

2. Retention

Each 50P check-in, rewarded-ad, talk-card, post and comment reward is available once per rolling 24 hours per account and device. To prevent repeat claims after switching accounts, deletion or normal reinstallation, a device hash and the last grant time per reward are retained separately from accounts and cleaned up after seven days. Opaque ad-claim tickets are valid for 24 hours and cleaned up seven days after expiry. Tickets do not contain phone numbers or raw device identifiers.

Kakao authentication records are deleted after all device accounts linked to that Kakao identity are deleted. The keyed Kakao identifier used to prevent repeat welcome grants remains while linked accounts exist, then for up to one year after last use or deletion before scheduled cleanup.

Google authentication records are deleted after all device accounts linked to that Google identity are deleted. The keyed Google identifier used to prevent repeat welcome grants remains while linked accounts exist, then for up to one year after last use or deletion before scheduled cleanup.

Keyed device hashes, welcome-reward usage and registration cooldown timestamps are retained separately to prevent repeat registration and duplicate rewards. After all accounts on that device are deleted, these records remain for up to one year after last use or deletion before scheduled cleanup. Internal authentication identifiers for deletion retries are cleaned up after 30 days once deletion is complete; failed deletions retain the records necessary to finish processing.

General service profiles and data are kept until account deletion. Talk cards are limited to the latest 30 per account; older cards are deleted. Linked chat requests and conversations follow their own retention policies. When a card is reported or designated as problematic by an operator, its text, author ID, creation time and reason are archived for authorized administrators for one year from that report or designation, independently of card or account deletion. Expired evidence is removed by scheduled cleanup. Previously deleted ordinary cards cannot later be restored. After account deletion, the account ID, nickname, birth year, gender, region code, registration date and withdrawal date are stored separately for one year from withdrawal for dispute handling and lawful investigative requests. Direct-message text and attached photos are retained for one year from each message date, without restarting the period on withdrawal. Access is restricted to authorized administrators. Records under a separate preservation hold follow that hold period, then scheduled deletion. The provider, verified phone number, provider account identifier, provider-verified email if available, internal authentication ID and link date of login methods linked immediately before withdrawal are archived for the same period as the member record. These are not a complete login history or a definitive record of the initial signup method. Original details of changed authentication bindings are not inferred. Passwords, authentication tokens, profile photos and precise location are not copied. User-accessible chats are kept up to 30 days; closed support inquiries and error logs up to 90 days; safety and enforcement evidence up to one year; and device-wallet and repeat-registration prevention records up to one year after last use or withdrawal. Phone authentication records are deleted when all device accounts linked to that number have been deleted. A keyed phone hash prevents duplicate welcome grants while linked accounts exist, then is retained up to one year after last use or deletion and removed by scheduled cleanup. The same linked Google or Kakao account can restore the account across devices. Phone recovery also requires a registered device. Losing access to the required method or device identity may prevent restoration. Legally required or disputed records may be isolated for the necessary period and then irreversibly deleted.

AppsFlyer retains end-user data for up to 24 months under its default policy, subject to separate instructions or legal exceptions. Aggregate report availability and retention may differ from deletion of individual data. Account deletion does not immediately and automatically delete AppsFlyer or advertising-partner records.

3. Processors and international processing

RevenueCat, Inc. and the app stores process purchase verification, receipts and refunds. Purchase information may be processed in the United States or other provider infrastructure locations, transferred over encrypted networks when purchases or refunds occur, and retained for legally required periods or dispute handling. RevenueCat privacy policy: https://www.revenuecat.com/privacy/.

Kakao sign-in is optional. Kakao and Supabase Auth process account authentication when selected. Kakao privacy policy: https://www.kakao.com/policy/privacy. You can choose another sign-in method.

Google sign-in is optional. Google's authentication service and Supabase Auth process account authentication information when you choose it. Google's privacy policy is available at https://policies.google.com/privacy. You may choose phone verification instead.

We use NAVER Cloud SENS to send verification texts to South Korean numbers and supported international numbers. When you request a verification text, NAVER Cloud and the carriers involved in delivery process the recipient phone number, message content and delivery status. For international numbers, the message is routed through SMS intermediaries and carriers in the destination country. Supabase processes authentication, database, storage, and realtime communications in Seoul. Expo/650 Industries, Sentry/Functional Software, Google Firebase, and Google AdMob may process app, device, push-token, error, advertising-interaction, and identifier data in the United States or other infrastructure locations for builds, updates, push delivery, diagnostics, ad delivery, measurement, and fraud prevention. Transfers use encrypted networks. Google's privacy practices are available at https://policies.google.com/privacy. Refusing or restricting related processing may limit push, diagnostics, advertising, or ad-reward features.

AppsFlyer Ltd. and its affiliates process the installation and advertising-measurement information described above. Data is transferred internationally over encrypted networks during installation and launches. Its published subprocessor list identifies the EU as the data-hosting region and support/maintenance affiliates in Germany, China, Hong Kong, India, Japan, the United Kingdom, the United States and Israel. This describes the provider's published processing scope, not confirmation that each user's data is processed in every country. Provider contact: privacy@appsflyer.com. Processing and retention details: https://www.appsflyer.com/legal/services-privacy-policy/ and https://www.appsflyer.com/legal/subprocessors/. Connected Meta and X advertising partners may receive device identifiers and installation/advertising-interaction information needed for attribution and advertising measurement. Advanced matching is not used. Releases with in-app event measurement enabled send registration completion, login method, point-purchase completion, product ID and quantity to AppsFlyer after the revised privacy acknowledgement. iOS requires the revised privacy acknowledgement; without ATT authorization the anonymization and sharing restrictions described above apply. Transaction IDs are used only locally to prevent duplicates; this integration does not send purchase amounts, receipts, payment credentials or internal member IDs. Separate in-app event forwarding to Meta or X is not enabled. Partner policies: https://www.facebook.com/privacy/policy/ and https://x.com/en/privacy. Requests for access, deletion or restriction can be sent to itembus@itembus.com or 1555-1645; identifying the installation and following provider procedures may be necessary. Deletion or immediate transmission suspension is not automatic; we will communicate the outcome.

4. Optional permissions

Location supports distance-based cards; precise coordinates are not shown to users. Notifications announce chat requests and messages. Only photos selected through the system picker are processed. Refusal limits only the related feature.

5. User rights

Users may edit profiles, withdraw permissions, or delete their account under My Info. Requests for access, correction, deletion, suspension, or withdrawal may be sent to itembus@itembus.com or 1555-1645.

6. Minors

Ingtalk is limited to users age 19 or older. Accounts and content may be restricted or deleted when use by a minor is identified.

7. Security and deletion

Protections include encryption in transit, row-level security, separated administrator access, audit logs, reporting, blocking, and enforcement. Electronic files are deleted to prevent recovery; legally retained data is isolated.

8. Privacy contact

Email: itembus@itembus.com

9. Changes

Changes will be announced in the app or on a public webpage before taking effect.

10. Map talk location processing

Optional map posting processes device location, accuracy and measurement time into an approximately 100m-scale public coordinate linked to the account and talk. Lists, maps and distance calculations use the same processed coordinates. Automatically acquired device coordinates are coarsened before transmission and again on the server to regional cells approximately 100m across; raw device coordinates are not separately stored. Precise foreground location is preferred; a recent valid location is used if a precise fix is delayed or unavailable. Approximate-only permission remains supported. Distances and areas are estimates, not exact locations. Eligible signed-in members can see the publication area. List-only posting remains available without map publication consent. For a confirmed one-time location correction, the coordinate the user selects on the map within 1km of the original talk location is used without grid snapping for the map and list distances. This manual selection does not require an additional device location fix. Edits and republication retain the one-time correction limit. Ordinary posting, editing and republication deactivate the previous talk and start a new publication period. A location correction alone preserves the creation and expiry times of the talk being moved.

Map location is cleaned up separately when its publication purpose ends. Talk originals are subject to a one-year-from-creation and latest-30 limit. User-deleted talks are hidden, including from personal history. User-deleted talks are retained within the same limits to establish facts when reports or disputes arise after deletion. Deletion does not restart a one-year period, and the latest-30 limit may cause earlier deletion. Hiding alone does not satisfy separate personal data erasure requests.

Google Maps SDK may process device, request, connection and diagnostic information. See the existing Google external-processing disclosures and https://policies.google.com/privacy. Revoking device permission does not automatically remove an existing publication. Request withdrawal of map consent, access, correction, erasure or suspension at 1555-1645 / itembus@itembus.com. The location information manager is 조용일.

11. Distance location and map SDK

Google's South Korea user terms identify Google LLC (1600 Amphitheatre Parkway, Mountain View, California 94043, USA) as the provider of services including maps embedded in third-party apps. The Maps Platform terms distinguish information users provide directly to Google through normal service operation from information supplied by the app operator. This identifies the user-service provider, not a guarantee that every Ingtalk processing route or billing entity is the same. Terms: https://policies.google.com/terms?gl=kr&hl=ko / https://cloud.google.com/maps-platform/terms

Google Maps Platform's infrastructure reference lists the United States, Chile, Belgium, Finland, the Netherlands, Taiwan and Singapore. Google explains that actual processing locations vary with traffic origin and that processing may occur in the EEA, UK or other countries. This reference list does not guarantee that all Ingtalk SDK data is processed only in those locations. Source: https://developers.google.com/maps/security/compliance/security-compliance

Google's published Maps policy retains request-log user data while needed for legitimate operational, support, security or improvement purposes and deletes it when no longer necessary for its collection purposes. Anonymized aggregate statistics may be retained longer. This is not a single fixed retention period for all map data. Google's privacy policy covers Google LLC and its affiliates; this does not establish that the billing entity and actual processing entity are identical.

Other members' publication areas, profiles and talk text are retrieved from Ingtalk and displayed in an on-device app layer. Their coordinates, images and text are not passed to Google map markers or map projection APIs; the app calculates their screen positions. Background map requests, the viewed area and current-location centering are separate processing paths. Choosing to open the map or granting device location permission does not replace cross-border transfer consent where separate requirements apply.

Before opening the map, you can review the SDK disclosure and choose to open it, or continue using the list. This choice is separate from consent to publish a talk's location. The acknowledged notice version is stored per account on this device, so restarting the app or signing in again to the same account does not repeat the notice. Material processing changes or withdrawal require confirmation again. Another device or cleared storage may also require confirmation. Use Google map notice and settings on the map screen to review the notice or withdraw this choice. Withdrawal stops subsequent map use but does not automatically erase information already transmitted. On map entry or when you select move to my location, the app checks location permission and obtains one current fix, displayed as a blue dot only on your screen. This action does not track you continuously or store the fix on the Ingtalk server. A location used as the map center may be reflected in Google map requests. The map remains usable if permission is denied or the fix fails. Existing talks retain their published locations.

Distance calculation stores the latest account location, accuracy and update time. New values replace older values without building a movement history. The latest location is retained for 30 days from its last update, then erased by a five-minute cleanup job. Failed jobs are retried, so erasure at the exact 30-day instant is not guaranteed. Linked-account deletion also removes it. Disabling device permission does not immediately erase saved data; contact support to request erasure or suspension. Distance display may be unavailable until location is updated again.

List talks may separately retain publication coordinates for distance calculation. These use the same approximately 100m-scale regional grid as map coordinates; raw device coordinates are not stored or disclosed. Distance coordinates are erased separately on talk deactivation or user deletion; remaining coordinates for expired talks are cleaned up periodically. The one-year/latest-30 limit for talk originals and independent conversation retention are separate.

Google Maps SDK displays the map and may process device, OS and SDK information, IP addresses, SDK identifiers, errors and usage information. Map requests and viewport information are processed to provide the service. The app does not send talk text as map search queries or analytics events. This processing is separate from existing advertising SDKs. The bundled iOS map SDK privacy declarations include user identifiers, device identifiers, crash and performance data, and product interactions for analytics or app functionality. User identifiers are declared as linked to the user. This describes SDK declarations and does not establish that Ingtalk sends its internal account ID directly to the map SDK. Account-linked publication location processed by Ingtalk is assessed separately.

Google may process information on global infrastructure, without a domestic-only storage guarantee. Retention varies with data type, purpose and business or legal needs; Ingtalk's one-year talk retention does not apply to all Google SDK data. Avoiding the map feature avoids these map requests, but separate existing features may continue processing data. See https://policies.google.com/privacy and https://policies.google.com/technologies/retention.

The standard Google Maps agreement includes terms under which each party determines its own purposes and means of processing personal data associated with the service. Google may process information to provide and improve its services under that agreement and its privacy policy. Deleting a talk or reaching Ingtalk's retention limit does not mean that Google immediately deletes SDK data. Information about Google's processing and ways to exercise privacy rights is available at https://policies.google.com/technologies/partner-sites and https://policies.google.com/privacy.

12. Location sharing for map board posts

Enabling the board map does not publish existing or list-only posts on the map. New posts default to list display. A post appears on the map only when the user selects map display and has valid shared map-location consent. Valid consent already given for talks or rooms is reused.

For each map post, the location at publication is processed into an approximately 100m-scale regional coordinate and stored. Authorized signed-in members receive the public coordinate, post title, per-post anonymous name and gender. Map bubbles do not display the actual profile name or photo. Aliases and regional processing do not guarantee that the author cannot be identified. The purpose is nearby-post discovery, not live tracking; a separate movement history is not accumulated.

Multiple posts can be published independently. Creating a new post does not change older posts' locations. Each post permits one move to a selected point within 1km. The current public coordinate is updated; editing text or photos does not reset the alias, creation time or move allowance. Public coordinates are retained while the publication purpose continues and are deleted on post deletion, shared-consent withdrawal or account deletion. Withdrawing map consent preserves list posts and comments. Renewed consent alone does not republish old posts.

Consent and provision records contain account and post identifiers, recipients, time, purpose and delivery status, but no coordinates, and are regularly removed six months after occurrence. Withdrawal or account deletion removes the corresponding records and pending notices. Retry identifiers, content comparison values and result post identifiers used to prevent duplicate creation are regularly removed after 25 hours. The per-post move-use record remains while the post exists.

Provision notices share the room-map delivery and history system. The default is a notice to the registered device for each provision; aggregation within up to 30 days requires a separate choice. If notices cannot be received because of notification permissions or logout, users can review the history or request redelivery to their current device. Shared consent for talks, rooms and board posts can be withdrawn in My Info → Permission Settings → Map location sharing. Turning off OS location permission alone does not remove existing publications. The preceding Google Maps processing disclosures also apply to the board map.