Privacy Policy

Article 1Purposes of processing personal information #

The Operator processes personal information for the following purposes. Personal information that is processed is not used for any purpose other than the following, and if the purpose of use changes, the Operator will take necessary measures, such as obtaining separate consent in accordance with Article 18 of the Personal Information Protection Act.

1. Membership registration and management: identification and authentication of members through social login (Kakao, Google, Apple), maintenance and management of membership, various notices and notifications, and processing of account deletion
2. Provision of the Service: posting and playback of jam posts, tracks, and Its; automatic sync correction of tracks and compositing of Its; features for saving Its to a device and sharing them externally; display of profiles; delivery and storage of chats between members (one-on-one chats and chat rooms with multiple participants) and display of read status; determination and display of achievements and levels; and display of rankings by part (instrument)
3. Sending notifications: sending push notifications related to use of the Service, such as joining a jam or publishing an Its
4. User protection and operation of the Service: receiving and handling reports (when a message is reported, the Operator checks the reported message and, from the same chat room, up to 5 member-written messages exchanged before it and up to 5 after it, including deleted messages — Terms of Service Article 13(3)), prevention of and sanctions against objectionable content and fraudulent use, provision of the block feature, handling of disputes, identification of service errors, and analysis of usage statistics and quality improvement
5. Service improvement using content: the Operator internally views and analyzes tracks and Its posted by users to the Service (including video and audio such as faces, voices, and musical performances) and uses them to improve the quality of recording, sync correction, and Its compositing, and the usability (UX) of features. This viewing is limited to the Operator’s internal personnel involved in operating the Service, and any use that exposes the content outside the Service, such as promotion of the Service, requires separate consent in accordance with Terms of Service Article 13(2).
6. Personalized recommendations: using the preferred genres and part (instrument) information registered by a member to order the list of posts on Home, and using part (instrument) information and Its viewing history to order the Its feed, in an order closer to the member’s interests; and collecting records of post views and genre filter selections to improve the quality of those recommendations. The order of the Its feed also reflects popularity, which combines the view counts and like counts of many members, and a member’s viewing history is added to it only as a number from which it cannot be identified whose history it is. Preferred genres are optional, and not registering them does not restrict your use of the Service. Who viewed what is not shown to other members, and this processing does not constitute an automated decision that has legal effects or similarly significant effects on users.

Article 2Personal information collected and methods of collection #

1. The Operator collects the following personal information.

   Personal information collected at each point of collection, and whether it is required or optional

   Category	Point of collection	Items collected	Required/Optional
   Membership registration	Kakao login	Social account unique identifier, nickname, profile photo, email	Required
   Membership registration	Google login	Social account unique identifier, name, profile photo, email	Required
   Membership registration	Apple login	Social account unique identifier, name, email (may be a private relay address)	Required
   Profile settings	Onboarding, My page	Nickname, profile photo, part (instrument) information	Required (nickname)/Optional
   Profile settings	Onboarding, My page, immediately after re-consenting to the terms	Preferred genres (selected from the genres presented)	Optional
   Content upload	Recording and uploading tracks, creating Its	Video and audio (may include the user’s face, body, voice, and musical performance)	Required (when using the relevant feature)
   Chat	One-on-one, group, and Space chat rooms	Content of messages exchanged between members and the sender and time sent, identifiers of posts, Its, and tracks shared in messages, the number of the last message read in a chat room, and names a member has given to a chat room (not visible to other members)	Required (when using the relevant feature)
   Notifications	App launch, login	Device push token (FCM token), device platform (iOS, Android) and language setting	Required (when receiving notifications)
   Automatic collection	In the course of using the Service	Service usage records, access logs, device information (model name, OS version, app version), error logs, the number of times the app was opened on each date (attendance records — used to determine achievements)	Automatically collected
   Automatic collection	Viewing posts, selecting genre filters, viewing Its	Identifiers and times of posts viewed and Its watched, genre filters selected and the screens on which they were selected, and how long an Its was played (playback duration) and the length of that video Used for personalized recommendations (Article 1, subparagraph 6) and determination of achievements (Article 1, subparagraph 2), and not shown to other members	Automatically collected
   Automatic collection	Recording a track in the app	Recording diagnostic information — recording mode (recording along with the original song video, or recording along with another member’s track), device information (model name, OS version, app version), the type of connected audio output device (speaker, wired, Bluetooth, or other external output) and the Bluetooth connection type and product family (e.g., AirPods Pro; the name the user has given the device is not collected), audio latency, buffer, and sample rate settings, the result and time of the app’s “Calibrate sync” measurement, the automatic sync correction value applied to the recording, the number of times the audio device changed during recording and the number of interruptions such as incoming calls, when recording along with another member’s track the number of times and duration that track’s playback stopped, the device’s thermal and low-power state, camera orientation, and the recording length and take number Used to identify the cause when a track is out of sync (Article 1, subparagraphs 2 and 4); visible only to the Operator, and retained and destroyed together with the relevant track	Automatically collected
   Automatic collection	In the course of using the app	Google Firebase Analytics — a randomly generated app instance identifier (on iOS, including the identifier for vendor (IDFV)), usage events automatically collected by Google Analytics such as app installation, launch, and sessions, and usage events designated by the Operator (login, sign-up, tab view, track registration, Its publication, message sending) and their associated items (login method, track registration path), push notification receipt and open records, device information (model name, OS version, app version, language, screen information, etc.), access IP address and the country and region estimated from it	Automatically collected
   Reports and inquiries	Receipt of reports, customer inquiries, sync fix requests	Information contained in the report or inquiry, the track for which a sync fix was requested, and the time of the request Sync fix requests are used by the Operator to check and correct the sync of tracks (Article 1, subparagraphs 2 and 4); they are visible only to the Operator, and are retained and destroyed together with the relevant track	When applicable
   Pre-registration	Signing up for launch notifications on the website	Email	Optional
   Website use	Visiting the website (jamit.kr)	Visit records, on-screen movement (navigation, clicks, scrolling), cookies, browser and device information	Automatically collected

   You can scroll the table sideways.

2. Methods of collection: personal information is provided by the relevant platform (Kakao, Google, Apple) at social login, entered or uploaded directly by the user in the course of using the Service, or automatically generated and collected in the course of using the Service.
3. The privacy policy of each platform also applies to the processing of personal information in the social login process.
   • Kakao: policy.kakao.com/kr/privacy
   • Google: policies.google.com/privacy
   • Apple: apple.com/legal/privacy/kr
4. The Operator does not collect resident registration numbers or sensitive information (such as ideology, beliefs, or health).

Article 3Processing and retention periods of personal information #

1. The Operator processes and retains personal information within the retention period prescribed by law or the retention period to which the data subject has consented.
2. Personal information, other than the app usage statistics information in paragraph 6, is retained until the member deletes their account. When you delete your account, we destroy without delay the information that can identify you — your email, nickname, profile photo, and social login linkage information — and a destroyed account cannot be restored. However, the following items are preserved only for the periods in the table below, to the minimum extent necessary to prevent fraudulent use and to handle disputes. A deleted account cannot be restored using these items.

   Items preserved even after deletion or account deletion, and their grounds and periods

   Item preserved	Ground for preservation	Preservation period
   Server logs (request and error records)	Operation of the Service and response to failures, identification of fraudulent use	Up to 14 days
   Identifiers for checking re-registration, and the end date of the re-registration restriction and the type of reason (ordinary account deletion or account deletion during a suspension) A one-way hash of the social account identifier — the original identifier cannot be restored, and it can only be used to check whether the same account is re-registering. The reasons for and details of a suspension are destroyed upon account deletion	Preventing recurrence of fraudulent use and abuse of account deletion to evade use restrictions or to re-register (Operator’s legitimate interest)	30 days after account deletion. If the account is deleted during a suspension, until the end date of the suspension (up to 1 year)
   Content of deleted chat messages Invisible to other members as soon as you delete them; after 30 days, the body, the shared item, and the item a notice refers to are deleted. So that read positions in the chat room do not shift, the message number, sender, time sent, and the type of message (text, track, notice, etc.) remain	Maintaining the read position of the other participants, and preventing a reported message from being deleted first by the person concerned so that it cannot be reviewed (Operator’s legitimate interest)	30 days from the date of deletion or account deletion
   Records of receipt and handling of reports	Handling of disputes, operational records for Apple App Review Guideline 1.2	1 year from the date handling is completed
   Deleted content (tracks, Its, posts) and its video and audio files Not displayed in the Service, and viewed by the Operator only to check whether it is content that has been reported	Preventing reported content from being deleted first by the person concerned so that it cannot be reviewed (Operator’s legitimate interest)	30 days from the date of deletion or account deletion

   You can scroll the table sideways.

3. Content uploaded by a member who deletes their account (tracks, posts, Its) and messages they exchanged are handled as follows.
   1. Tracks uploaded and Its created by the member become invisible in the Service as soon as the account is deleted, and are not shown to other users again. However, they are kept for 30 days for the review of reports and then destroyed, including the video and audio files, by a method that makes recovery impossible. Even during this period, the Operator views them only to check whether they are content that has been reported. The account information that can identify the member has already been destroyed and is not linked to this content, but because the video and audio themselves contain faces and voices, the retention period is limited to 30 days.
   2. Its created by other members are maintained on the basis of the consent in Terms of Service Article 14(4). A member who has deleted their account may request suspension of processing or deletion of such Its in accordance with Article 37 of the Personal Information Protection Act, and the Operator will act on legitimate requests without delay. Even in this case, the member’s email, nickname, and profile photo are destroyed upon account deletion, so the member’s identity is not displayed in such Its.
   3. Posts written by the member are maintained with the author shown as “Unknown” if tracks or Its of other members remain, provided that a reference video uploaded by the member (meaning a video that the member recorded and uploaded directly to serve as the basis of the jam; an original song designated by a YouTube link is not included) is separated from the post and handled in the same way as subparagraph 1. Posts with no content from other members are handled in the same way as subparagraph 1.
   4. Chat messages sent by the member become invisible on the other participants’ screens as soon as the account is deleted, and their content is deleted after 30 days. What the other participants wrote remains on their screens. If no one remains in a chat room with multiple participants, the messages in that room, including those written by other members, are handled under the same procedure.
4. Content is also kept for 30 days when it is deleted without the member deleting their account. This includes cases where a member deletes tracks, Its, or posts themselves; where a member leaves or is removed from a Space shared by multiple members and the tracks and Its they uploaded to that Space are deleted; and where the last member leaves a Space so that the Space ceases to exist and the content in it is deleted. In any of these cases, the content becomes invisible in the Service immediately and can no longer be seen by other users. However, to prevent reported content from being deleted first by the person concerned so that it cannot be reviewed, it is kept in a state accessible only to the Operator for 30 days from the date of deletion and then destroyed, including the video and audio files.

   If you leave or are removed from a Space, the posts you wrote in that Space are not deleted; the author is shown as “Left user,” and they remain visible to the remaining members. A reference video you uploaded to such a post also remains with it, and when the Space ceases to exist, they are deleted as described above and destroyed 30 days later.

   If another user was using the member’s track in their own Its, that participation record is deleted at the same time as the deletion. This means the member’s nickname and profile photo disappear from the list of participants in that Its. However, faces and voices contained in a jam video that has already been made are part of the video itself and cannot be removed.

   On the other hand, likes and viewing history left by other users on a deleted Its are not deleted as soon as the Its is deleted. These records are not information about the member who deleted the content but information about the other users who left them, and they are used to check how far the content was exposed when a report is received and to determine the achievements of the users who left those records. Viewing history is also used for that user’s own personalized recommendations (to move songs they have already watched further back). These records are destroyed together with the Its when it is destroyed (30 days from the date of deletion), or, if the user who left them deletes their account before then, at that time. Separately, viewing history is deleted automatically after 90 days.

5. Personal information of data subjects who are not members is handled as follows. Emails submitted for pre-registration (launch notifications) are destroyed without delay after the launch notification is sent, and are destroyed immediately upon request, even before then, through the contact in Article 12. Website usage analysis information is collected in accordance with Article 10 and kept for 1 year from the date of collection. If you complete social login but do not finish signing up because you do not agree to the Terms of Service and the Privacy Policy, the information received through social login (social account identifier, email, profile photo) is kept so that you can log in again and finish signing up, and is destroyed immediately upon request through the contact in Article 12.
6. App usage statistics information (Article 10) is not linked to member accounts and therefore cannot be destroyed upon account deletion; it is deleted after up to 14 months from the date of collection in accordance with the maximum of the Google Analytics data retention setting. Aggregate statistics that cannot identify individuals are retained even after that.
7. Records of post views, genre filter selections, and Its viewing history are deleted automatically after 90 days from the date of collection, and if you delete your account before then, they are destroyed upon account deletion. These records are used for personalized recommendations (Article 1, subparagraph 6) and determination of achievements (Article 1, subparagraph 2), and are not shown to other members.
8. As the Service is free of charge with no payment feature, the obligation to preserve transaction records under the Act on the Consumer Protection in Electronic Commerce, Etc. does not apply.

Article 4Provision of personal information to third parties #

1. The Operator processes the personal information of data subjects only within the scope of the purposes in Article 1, and provides it to third parties only in cases falling under Articles 17 and 18 of the Personal Information Protection Act, such as with the consent of the data subject or under special provisions of law.
2. The Operator currently does not provide personal information to any third party. If provision to a third party becomes necessary, the Operator will notify you of the recipient, the purpose of provision, the items provided, and the retention period, and obtain separate consent.
3. However, personal information may be provided when requested by an investigative agency or other authority in accordance with the procedures and methods prescribed by law.
4. Note on the nature of the Service: the profile (nickname, profile photo) and content (tracks, Its, etc.) posted by a user are made public to other users within the Service, and tracks that take part in a jam may, in accordance with the functions of the Service, be combined into other participants’ Its and saved to a device or shared externally. Detailed conditions for this are governed by Terms of Service Article 13 and Article 14. In addition, in the rankings by part (instrument) (overall, monthly, and weekly), the member’s nickname, profile photo, experience points (XP), level, tier, and rank are shown to other users, regardless of whether either user has blocked the other.

Article 5Entrustment of personal information processing #

1. For the smooth provision of the Service, the Operator entrusts personal information processing tasks as follows.

   Trustees of personal information processing and entrusted tasks

   Trustee	Entrusted tasks	Notes
   Amazon Web Services, Inc. (AWS)	Operation of service infrastructure, storage of data (including content)	Region: Asia Pacific (Seoul)
   Google LLC (Firebase)	Sending push notifications (FCM), app usage statistics analysis (Firebase Analytics) — error collection tools such as Crashlytics are not used	See Article 6 Cross-border transfer
   Microsoft Corporation	Website (jamit.kr) usage analysis (Microsoft Clarity) — does not apply to the app	See Article 6 Cross-border transfer
   HubSpot, Inc.	Receipt and storage of website pre-registration (launch notification) sign-ups	See Article 6 Cross-border transfer
   Slack Technologies, LLC	Work messenger (Slack) used to notify the Operator of receipt of reports	See Article 6 Cross-border transfer
   Raintank, Inc. (Grafana Labs)	Monitoring of service failures and performance (Grafana Cloud) — querying and displaying server logs and metrics	See Article 6 Cross-border transfer

   You can scroll the table sideways.

2. When entering into an entrustment contract, the Operator specifies in the contract documents (including each company’s data processing agreement), in accordance with Article 26 of the Personal Information Protection Act, matters such as the prohibition of processing personal information for purposes other than performing the entrusted tasks, technical and managerial safeguards, and restrictions on re-entrustment, and supervises whether the trustee processes personal information safely.
3. If the entrusted tasks or the trustees change, the Operator will disclose the change through this Privacy Policy without delay.
4. The social login providers (Kakao, Google, Apple) are independent personal information controllers that process authentication under separate agreements between the user and each company, and the Operator receives the items in Article 2(1) as a result of authentication.

Article 6Cross-border transfer of personal information #

To provide and operate the Service, the Operator transfers personal information overseas (by entrustment or storage) as follows. Data subjects may refuse the cross-border transfer by making a request to support@jamit.kr. However, app usage statistics information and website usage analysis information are not linked to member accounts and cannot be singled out upon request, so you can stop them by the methods in Article 10 (deleting the app, refusing cookies in your browser). If you refuse, use of all or part of the Service (such as push notifications) may be restricted, or the handling of reports may be delayed.

You can scroll the table sideways.

Article 7Procedures and methods for destroying personal information #

1. When personal information becomes unnecessary, such as upon expiry of the retention period or achievement of the purpose of processing, the Operator destroys that personal information without delay.
2. Information that must be preserved under law is moved to a separate database (DB) or storage location and stored separately. Deleted content preserved for a certain period under Article 3 is excluded from the Service’s retrieval paths so that it is not shown to other users, and is viewed only to check whether it is content that has been reported. In either case, it is destroyed without delay once the preservation period expires.
3. Methods of destruction: information in the form of electronic files is deleted using technical methods that make recovery or reproduction impossible, and paper documents are shredded or incinerated. Destroyed information remains in the database’s automatic backups for up to 7 days before being deleted on a rolling basis, and backups are not used for any purpose other than recovery from failures.
4. Upon account deletion, the social login linkage information held by the Operator is destroyed, and disconnection from each platform is also handled. For Apple, the Operator’s server requests disconnection, and account deletion is processed only once the disconnection from Apple has been completed (if the disconnection request fails, account deletion does not proceed, and you may try again). For Kakao, the app requests disconnection; for Google, the iOS app requests disconnection, while the Android app only clears the sign-in state on the device. Even if a disconnection request to Kakao or Google fails due to a network error or the like, the linkage information held by the Operator is destroyed, and you may disconnect any remaining connection directly in each platform’s account settings.

Article 8Rights and obligations of data subjects and legal representatives, and how to exercise them #

1. Data subjects may at any time request the Operator to provide access to, correct or delete, or suspend the processing of their personal information, or withdraw their consent.
2. These rights may be exercised in the following ways, and the Operator will act without delay (within the statutory time limit).
   1. In-app features: editing your profile (correction), deleting content, turning off notifications for each chat room or Space (all notifications can be turned off in your device settings), deleting your account (withdrawal of consent, deletion)
   2. Email: support@jamit.kr

   When you delete content or your account in the app, it is no longer displayed in the Service immediately. However, deleted content is kept for 30 days for the review of reports and then destroyed, as described in Article 3. If you have reason to require destruction without waiting 30 days, you may request it at the email address above. However, content that has been reported and is under review is destroyed after the review is completed, and the Operator completes the review within 7 business days from the date the report is received (Terms of Service Article 16(3)).

3. These rights may also be exercised through the data subject’s legal representative or a person delegated by the data subject. In this case, a power of attorney in the form annexed to the Enforcement Rule of the Personal Information Protection Act must be submitted.
4. Requests for access or suspension of processing may be restricted under Articles 35 and 37 of the Personal Information Protection Act, and deletion of personal information that other laws specify as subject to collection cannot be requested.
5. Only persons aged 14 or older may sign up for the Service (Terms of Service Article 5). Because the Operator does not collect dates of birth or ages, age is not verified at sign-up; if it is confirmed, through a report, inquiry, or otherwise, that personal information of a child under the age of 14 has been collected, the Operator will destroy the relevant account and personal information without delay, together with the tracks, Its, and posts uploaded by that child. Destruction of video and audio files may take up to 30 days, and during that period they are not displayed in the Service.

Article 9Measures to ensure the security of personal information #

The Operator takes the following measures in accordance with Article 29 of the Personal Information Protection Act.

1. Managerial measures: minimizing personnel who handle personal information (individually operated), establishing and reviewing internal processing procedures
2. Technical measures: encryption in transit (HTTPS/TLS), encryption of stored data (the database is stored with cloud-managed keys and uploaded files with server-side encryption), no collection or storage of passwords owing to the use of social login, granting of minimum access rights and management of authentication tokens, cloud access control, and retention of server logs (up to 14 days)
3. Physical measures: use of the physical access control environment of the cloud provider (AWS)

Article 10Installation, operation, and refusal of automatic personal information collection tools #

1. The app itself does not use web browser cookies (although the YouTube player used to play original songs may use YouTube’s cookies — paragraph 5) and does not collect advertising identifiers (IDFA) for targeted advertising. However, it uses Google Firebase Analytics to understand which screens and features are used and how often, in order to improve the Service. In this process, a randomly generated app instance identifier (on iOS, including the identifier for vendor (IDFV)), usage events automatically collected by Google Analytics such as app installation, launch, and sessions, and usage events designated by the Operator (login, sign-up, tab view, track registration, Its publication, message sending) and their associated items (login method, track registration path), push notification receipt and open records, device information (model name, OS version, app version, language, screen information, etc.), access IP address and the country and region estimated from it are transmitted to Google (Article 2·Article 6). This information is not linked to member accounts (email, nickname, etc.) and is not used for advertising purposes. Error collection tools such as Crashlytics are not used.
2. This collection cannot be turned off separately within the app, and it stops when you delete the app. The app instance identifier is deleted with the app and a new one is created if you reinstall it. Information already transmitted is kept for the period in Article 3, paragraph 6. Because this information is not linked to member accounts and the data of a specific user cannot be singled out, individual requests for deletion or suspension of processing cannot be accommodated. Other inquiries may be sent to support@jamit.kr.
3. The website (jamit.kr) uses Microsoft Clarity to understand how its pages are used, in order to improve its screens. In this process, visit records and on-screen movement (navigation, clicks, scrolling) are collected and cookies are stored. This information is not linked to member accounts or pre-registration emails.
4. If you do not want cookies to be stored, you can refuse cookies or delete stored cookies in your web browser settings. However, refusing cookies may make it difficult to use some features of the website.
5. The Service uses the YouTube player to play original songs, and the YouTube Data API to check information about original song videos (title, channel, topics) (YouTube API Services). While an original song is playing, Google may collect information such as your IP address, device information, and cookies directly from your device, and the Google Privacy Policy applies to this. The Operator sends only the video identifier to the YouTube Data API and does not send any member information.

Article 11App access permissions #

The Service uses the following smartphone access permissions. Even if you do not allow optional access permissions, you can use the Service other than the relevant features, and you can change them at any time in your device settings.

You can scroll the table sideways.

Article 12Chief Privacy Officer #

1. The Operator takes overall responsibility for work related to the processing of personal information and has designated a Chief Privacy Officer as follows to handle data subjects’ complaints and provide remedies for damage related to the processing of personal information.

   Chief Privacy Officer and contact information

   Category	Details
   Chief Privacy Officer	Minjae Kim (김민재) (individual operator)
   Contact (email)	support@jamit.kr

   You can scroll the table sideways.

2. Data subjects may contact the Chief Privacy Officer regarding any inquiries, complaints, remedies for damage, and other matters related to personal information protection arising in the course of using the Service, and the Operator will respond to and handle them without delay.

Article 13Remedies for infringement of rights #

To obtain remedies for infringement of personal information, data subjects may apply to the following organizations for dispute resolution, counseling, and the like.

1. Personal Information Dispute Mediation Committee: (no area code) 1833-6972 / www.kopico.go.kr
2. Personal Information Infringement Report Center (Korea Internet & Security Agency): (no area code) 118 / privacy.kisa.or.kr
3. Supreme Prosecutors’ Office: (no area code) 1301 / www.spo.go.kr
4. Korean National Police Agency: (no area code) 182 / ecrm.cyber.go.kr

Article 14Changes to this Privacy Policy #

1. This Privacy Policy applies from its effective date, and if its content is added to, deleted, or modified due to changes in laws, policies, or the Service, the Operator will give notice through this page and in-app notices from 7 days before the change takes effect (30 days before for material changes such as changes to the items collected or purposes).
2. The revision history can be found in the Addenda to this document, and if you need a previous version of the Privacy Policy, you may request it at support@jamit.kr.

AddendaEffective date #

1. This Privacy Policy takes effect on August 25, 2026.
2. Revision of September 1, 2026 — We corrected wording that was inconsistent with actual processing. We deleted “verification of whether a person is under the age of 14,” which was not being performed, from Article 1, subparagraph 1; clarified in Article 8 that age is verified only after the fact; added the selection of videos and photos to the purposes of the photos/media access permission in Article 11; and corrected the means of notice and the guidance on previous versions in Article 14 to reflect the actual channels. There are no changes that increase the items collected or broaden the purposes of processing. This revision takes effect on September 1, 2026.
3. Second revision of September 1, 2026 — We specified the retention period for deleted content and content of deleted accounts. To prevent reported content from being deleted first by the person concerned so that it cannot be reviewed, tracks, Its, and posts that are deleted or belong to deleted accounts are kept for 30 days and then destroyed (Article 3, paragraphs 2 to 4). Information that can identify a member, such as email, nickname, and profile photo, is destroyed immediately upon account deletion, as before. In addition, we corrected the methods of destruction and the wording on disconnecting social logins in Article 7, and the guidance on exercising rights in Article 8, to reflect actual processing. There are no changes that increase the items collected or broaden the purposes of processing — video and audio were already items collected (Article 2), and receiving and handling reports was already a purpose of processing (Article 1, subparagraph 4). This revision takes effect on September 1, 2026.
4. Third revision of September 2, 2026 — We reflected the use of an app usage statistics analysis tool (Google Firebase Analytics). The app uses this tool to see which screens and features are used and how often, but the previous policy stated that “the app has no analytics tools,” which was inaccurate. We added the app instance identifier, usage events, and other items to the Key points and to the automatically collected items in Article 2; added usage statistics analysis to Article 1, subparagraph 4; added the retention period for that information (paragraph 6) to Article 3; added app usage statistics analysis to the scope of entrustment to and cross-border transfer to Google in Article 5 and Article 6; and rewrote Article 10 to describe what is collected and how to stop it. We also corrected the Terms of Service article number referred to in Article 8, paragraph 2 (Article 17 → Article 16(3)). This revision increases the items collected. The added information is for statistical purposes and is not linked to member accounts, and advertising identifiers continue not to be collected. However, because this revision was made before the launch of the Service and no users had consented to the previous policy, it takes effect on September 2, 2026 without the 30-day advance notice procedure in Article 14, paragraph 1.
5. Correction of September 16, 2026 — We reflected in Article 6 the fact that the items transferred to Google (Firebase) to send notifications include the title and body of notifications. Depending on the type of notification, the notification banner contains another member’s nickname and the title of the relevant post or the name of a Space, but the previous table listed only the device push token and device information. This does not change what is processed; it corrects a statement that did not match the facts, and does not increase the items collected or the purposes of processing. This correction applies from September 16, 2026.
6. Fourth revision of October 20, 2026 — We reflected personalized recommendations and chats between members. We added subparagraph 6 (personalized recommendations) to Article 1 and added chat to subparagraph 2 (provision of the Service); added preferred genres, chat messages, and records of post views and genre filter selections to the items collected in Article 2 and specified Its viewing history there; added to Article 3 the retention period for records of post views and genre filter selections (90 days from the date of collection) and the retention period for deleted chat messages (30 days from the date of deletion or account deletion), and clarified how messages are handled upon account deletion. We added the beginning of message content included in chat notifications to the items transferred to Google in Article 6. We also updated the Key points. To identify the cause of tracks that are out of sync, we added track recording diagnostic information to the automatically collected items in Article 2; this information is retained and destroyed together with the relevant track. In the same Article, we specified records of sync fix requests in the items for reports and inquiries; these records are also retained and destroyed together with the relevant track. We added message sending to the usage events designated by the Operator in Article 2, Article 6, and Article 10. To match the names used on the app screens, we changed the Korean term for posts from “게시글” to “모집글”; they refer to the same thing. Also corrected — In Article 1, subparagraph 2, we listed achievements and levels, which have been provided since before, and rankings by part (the items shown in rankings are set out in Article 4, paragraph 4); in Article 5 and Article 6, we listed Slack (United States), which has been used to notify the Operator of receipt of reports, and Grafana Labs (Japan), which has been used to monitor service failures; and we added the contacts of the recipients to the table in Article 6. In Article 3, we corrected the statements that likes and viewing history remaining on a deleted Its are destroyed together with that Its and are also used to determine achievements, and that if a member leaves or is removed from a Space, the posts they wrote in that Space and the reference videos remain; and in Article 7, we corrected the statements that account deletion is processed only once the disconnection from Apple has been completed, and that for Google accounts the Android app only clears the sign-in state on the device. In addition, we specified attendance records and the device platform and language setting in Article 2; the handling of cases where sign-up is not completed and the scope of the re-registration check information that remains after account deletion in Article 3; the backup retention period in Article 7; how to turn off notifications in Article 8; the use of YouTube API Services in Article 10; the identifier for vendor (IDFV) on iOS in Articles 2, 6, and 10; and the Android nearby devices permission in Article 11. This does not change what is processed; these had been omitted or did not match the facts. However, Slack report notifications previously also included the member’s nickname; they now include only the member’s identifier, and the earlier notifications that included nicknames have been deleted. This revision increases the items collected and the purposes of processing; we gave advance notice of it on this page from September 18, 2026, and this revision takes effect on October 20, 2026. However, for members who agree to the revised Privacy Policy in the app before then, it applies from the time they agree. Track recording diagnostic information, records of sync fix requests, and the message sending event were not included in that notice, and we are informing you of them together with this revision. The above correction of September 16, 2026 was actually posted on this page on September 18, 2026.

   Some of the content we gave advance notice of will not take effect. The notice of September 18, 2026 included transferring the title, channel name, and description of videos and the title and tags of posts to Anthropic (United States) in order to infer information about the songs linked to posts. Since then, we changed genres to a method in which the author selects them directly, making that processing unnecessary; therefore, this transfer will not take effect and is not included in this revision. Because this means processing less than what was notified, it takes effect without a separate notice period.

   Its viewing history is a record whose retention period (90 days) has been stated in Article 3 of the previous policy; in this revision, we specified it as an item collected in Article 2, and we also use it to order the Its feed. The same notice did not separately describe the viewing history used for Its recommendations or the part (instrument) information used to order the two lists, but both are items that have been collected since before (Article 2) and are used within the notified purpose of “recommending posts and Its to match your interests.”