HeimLog Privacy Policy
HEIMDEX Co., Ltd. (the "Company") establishes and discloses the following Privacy Policy pursuant to Article 30 of the Personal Information Protection Act ("PIPA") in order to protect the personal information of data subjects and to handle related grievances promptly and smoothly.
Date of publication: October 23, 2026 / Effective date: November 22, 2026
Article 1 (Purposes of Processing Personal Information)
(1) The Company processes personal information for the purposes set out below. Personal information processed is not used for any purpose other than these purposes, and where the purpose of use changes, the Company will take necessary measures, including obtaining separate consent pursuant to Article 18 of PIPA.
| Category | Purpose of processing |
|---|---|
| Member management | Provision of membership-based services, identification and authentication, confirmation of intent to register, prevention of registration by children under 14, prevention of misuse, delivery of notices, management of consents and withdrawals of consent |
| Service provision | AI-based automated analysis, selection and editing of video, generation and delivery of Outputs, provision of storage, sharing of Outputs by the method designated by the Member, posting of Outputs to the Member's external platform accounts (YouTube, TikTok, Instagram) at the Member's request |
| Grievance handling | Receipt and handling of inquiries, reports and objections, receipt of error reports and feedback through the feedback widget, verification of facts, notification of outcomes |
| Paid services | Payment and settlement of fees, management of the provision and use of Passes, Credits, Subscriptions and other paid products, processing of renewals and cancellations of recurring payments for overseas payment products, application of promotion codes, processing of withdrawals of subscription, refunds |
| AI quality evaluation and service analytics | Evaluation of the quality of AI drafts (automated editing results) and analysis of service usage using usage records in which account and project identifiers have been pseudonymized (HMAC); diagnosis of upload transmission errors and improvement of service stability |
| Marketing performance analysis | Measurement of sign-ups and conversions by acquisition channel, measurement of advertising performance |
| Marketing (optional) | Notification of event information, transmission of advertising information (limited to Members who have given separate consent) |
(2) The Company sends advertising information only to Members who have consented to receive it. Where advertising information is sent by email, the Company marks the subject line with "(Advertisement)" and does not send it between 9:00 p.m. and 8:00 a.m. the following day without separate consent. The Company confirms every two (2) years from the date of consent whether Members who have consented wish to continue receiving such information, and a Member may withdraw consent at any time through the settings menu within the Service or the unsubscribe link at the bottom of the email.
Article 2 (Categories of Personal Information Processed)
(1) Membership registration and management
- Required: email address, password, nickname, year of birth (for the purpose of confirming that the Member is aged 14 or over)
- Optional: profile image, gender
- Consent records: date and time of consent to the Terms of Service and to the processing of personal information; whether the Member has consented to receive marketing information and to the use of data for training, and the history of changes thereto (dates and times of consent and withdrawal)
- Where social login is used, the items received from each provider
| Provider | Items received |
|---|---|
| Account identifier, email address, name, profile image | |
| Kakao | Account identifier, email address, nickname, profile image |
(2) Content processed in the course of using the Service
- The Company processes video files uploaded by Members in order to use the Service. Video files may contain the following personal information:
| Item | Description |
|---|---|
| Facial images | Faces of the Member and of third parties who appear in the video |
| Voice | Voices and conversations of the Member and of third parties |
| Recording metadata | Date and time of recording, recording device information |
- A video file is itself a file that may contain personal information, and the Company treats it as personal information rather than as an ordinary posting. Location information contained in a video file (EXIF location metadata such as GPS coordinates) is removed from the server immediately upon upload, and the Company does not use or retain it for any purpose. The Company does not provide any feature that uses location information.
- Information generated by the Company in the course of providing the Service: low-resolution copies (proxies) for editing and low-quality export, project editing information, and AI suggestion records (scene selection and arrangement suggestions produced in the automated editing process, and whether the Member adopted or modified them)
(3) Use of paid services
- Payment method information (processed through a payment gateway; the Company does not retain full card numbers), payment approval records, transaction history, records of the purchase and use of Passes, Credits, Subscriptions and other paid products, records of renewals and cancellations of recurring payments (overseas payment products only), records of the use of promotion codes
(4) Use of the external platform posting feature
- Where a Member links an external platform account, the Company receives the following information from the relevant platform or generates it. Access tokens are stored in encrypted form, and the Company uses them only where necessary to post Outputs, within the scope of permissions the Member granted on the linking screen.
| Platform | Items processed |
|---|---|
| YouTube (Google) | Channel identifier, channel name, access token and refresh token, posting records (video identifier, date and time of posting, and title, description and visibility setting entered by the Member) |
| TikTok | Account identifier (open_id), display name, profile image, access token and refresh token, posting records (post identifier, date and time of posting, and description and visibility setting entered by the Member) |
| Instagram (Meta) | Instagram professional account identifier, username, access token, posting records (media identifier, date and time of posting, and caption entered by the Member) |
(5) Use of the feedback widget
- Feedback and error details entered by the Member, screenshots, screen recordings and files attached by the Member, email address, address of the page on which the feedback was submitted, browser and device information
(6) Information collected automatically
| Category | Items |
|---|---|
| Access and device information | IP address, cookies, access date and time, time of last visit, service usage logs, device information (OS, browser, device identifier), error logs |
| Editor usage records | Feature usage events (reuse of unused clips; preview, placement and deletion of background music; number of subtitle edits, splits and merges; opening of panels; export downloads; number of undo actions) and session summaries (number of clicks, intervals between clicks, type of the element last clicked, active time) |
| Upload transmission diagnostics | Browser and device type, transmission result, time taken, error type, online status |
| Acquisition information | UTM parameters (source, medium, campaign), landing path of the first visit, referring site domain, device type at sign-up (mobile / PC or tablet) |
| Information collected by web analytics and session recording tools | Information collected through Google Analytics 4, Microsoft Clarity and the Meta Pixel; the specific items are as set out in Articles 15 and 16 |
Article 3 (Special Notice Regarding the Personal Information of Third Parties Appearing in Video)
(1) The Company recognizes that video uploaded by a Member may contain the face or voice of a person other than the Member. In such case, that depicted individual is also a data subject under PIPA.
(2) The mere fact that a Member possesses a video file does not entitle the Member to exercise the rights relating to a depicted individual's personal information on that individual's behalf. A Member must upload only video for which the depicted individuals have given their consent.
(3) The legal basis on which the Company processes the personal information of third parties appearing in video uploaded by a Member is Article 15(1)6 of PIPA (where processing is necessary to achieve the legitimate interests of the personal information controller and such interests manifestly override the rights of the data subject). The Company processes such information in a manner that does not unfairly infringe the rights of the data subject, as follows:
- 1. The purpose of processing is limited to the generation of an Output at the Member's request, and processing is carried out only to the minimum extent necessary to achieve that purpose.
- 2. The Company does not extract or store feature points for the purpose of linking a depicted individual's face to a specific individual for identification.
- 3. The Company does not use depicted individuals' personal information to train artificial intelligence models.
- 4. The Company does not continuously monitor Members' content; access is limited to matters received in accordance with the principles set out in Article 10 of this Policy.
- 5. A depicted individual may exercise the rights under paragraph (4) at any time even if they are not a Member, and the Company will verify the facts and act immediately upon receipt of a request and notify the requester of the outcome.
(4) A person appearing in video may, even if they are not a Member, request the Company to restrict access to, de-identify, delete or suspend the processing of content containing their face or voice. Requests may be sent to heimlog@heimdex.co, and the Company will verify the facts and act immediately upon receipt of a request and notify the requester of the outcome.
(5) As of the effective date of this Policy, the Company does not extract or store facial feature points for the purpose of linking a face to a specific individual, and does not process voice for the purpose of identifying a speaker as a specific individual. Face detection, processing that groups faces detected within the same video in order to apply blur to them collectively, speech-segment detection and speech-to-text conversion performed by the Company in order to generate Outputs are not processing for the purpose of recognizing a specific individual and therefore do not constitute processing of biometric identification information (sensitive information) under PIPA. Information generated for face blurring is used only for the blur processing of the relevant project, is not compared with information from other projects or Members, and is destroyed together with the Original Content when the retention period of the Original Content ends. Accordingly, the Company does not process sensitive information, and there are no categories of sensitive information that data subjects may disclose.
(6) Should the Company in future introduce a feature that uses facial recognition or speaker identification, such as a feature that automatically groups scenes in which the same person appears, such processing would constitute processing of sensitive information (biometric identification information) under PIPA. In that case, the Company will comply with the following:
- 1. Before introducing the feature, the Company will disclose the purpose of processing, the items processed and the retention period, and will obtain separate consent distinguished from other consents.
- 2. A data subject who does not consent will face no restriction on use of the Service other than the feature concerned.
- 3. Feature-point data will be stored in encrypted form and destroyed without delay upon discontinuation of use of the feature or withdrawal of consent.
- 4. The procedure for exercising the rights under paragraph (4) applies equally with respect to the faces and voices of third parties appearing in video.
Article 4 (Processing and Retention Periods)
(1) The Company processes and retains personal information within the retention and use period prescribed by law or the retention and use period consented to by the data subject at the time of collection.
| Item | Retention period | Basis |
|---|---|---|
| Member information | Destroyed without delay upon withdrawal of membership | PIPA Article 21(1) |
| Consent history (whether the Member has consented to receive marketing information and to the use of data for training, and the dates and times of consent and withdrawal), time of last visit, acquisition information | Destroyed without delay upon withdrawal of membership | PIPA Article 21(1) |
| Original Content | Destroyed without delay from the Service and the operational database when thirty (30) days have elapsed from the date of upload or when the Member deletes it or withdraws; copies remaining in backup storage are destroyed by an irrecoverable method within 60 days in accordance with the backup rotation cycle | PIPA Article 21(1); Terms of Service Article 13 |
| Low-resolution copies (proxies) and project editing information | Destroyed by the same method when sixty (60) days have elapsed from the date of upload or when the Member deletes them or withdraws | PIPA Article 21(1); Terms of Service Article 13 |
| Outputs | Destroyed by the same method when thirty (30) days have elapsed from the date of generation or when the Member deletes them or withdraws | PIPA Article 21(1); Terms of Service Article 13 |
| AI suggestion records | Twelve (12) months from the date of generation; destroyed immediately where the relevant project is deleted or the Member withdraws | PIPA Article 21(1) |
| External platform linking information (account identifiers, access tokens, etc.) and posting records | Destroyed without delay upon unlinking or withdrawal of membership | PIPA Article 21(1) |
| Service usage logs (Amazon CloudWatch) | 90 days from the date of generation | Protection of Communications Secrets Act Article 15-2; Article 41 of its Enforcement Decree |
| Pseudonymized analytics data (Article 6) | Weekly snapshots: 15 days from the date of creation; daily log event files: 89 days from the date of the event (up to 90 days) | PIPA Article 28-2 |
| Web analytics and session recording data | Google Analytics 4: 2 months / Microsoft Clarity: session recordings 30 days, aggregated data such as heatmaps 13 months / Meta Pixel: as set out in Article 16 | Data retention settings of each service |
| Inquiry and dispute handling records (including feedback and attachments received through the feedback widget) | 3 years after completion of handling | Act on the Consumer Protection in Electronic Commerce, Etc., Article 6 and Article 6 of its Enforcement Decree |
| Data access records (Article 10) and records of access to member information in the admin console | 2 years from the date of access | PIPA Article 29; Article 30 of its Enforcement Decree; Standards for Measures to Secure the Safety of Personal Information |
| Misuse records | 1 year; retained for the Company's legitimate interest in preventing misuse | PIPA Article 15(1)6 |
| Settlement information for consideration distribution | Retention period under applicable law following completion of payment (5 years) | Framework Act on National Taxes; Income Tax Act |
(2) Retention required by law
| Governing law | Item | Period |
|---|---|---|
| Act on the Consumer Protection in Electronic Commerce, Etc. | Records on contracts or withdrawal of subscription | 5 years |
| Act on the Consumer Protection in Electronic Commerce, Etc. | Records on payment and supply of goods | 5 years |
| Act on the Consumer Protection in Electronic Commerce, Etc. | Records on consumer complaints or dispute handling | 3 years |
| Act on the Consumer Protection in Electronic Commerce, Etc. | Records on labeling and advertising | 6 months |
| Protection of Communications Secrets Act | Service usage records, access logs, access IP | 3 months |
| Framework Act on National Taxes | Books and supporting documents on transactions | 5 years |
Article 5 (Matters Concerning Artificial Intelligence Training)
(1) The Company does not use Members' Original Content or Outputs for the training, fine-tuning or other training of artificial intelligence models.
(2) The Company uses artificial intelligence technology to analyze and edit video in order to provide the Service; however, this is limited to processing (inference) for the purpose of generating that Member's Output and is not used for training that updates model weights.
(3) Where the Company uses an external artificial intelligence service, it enters into and applies a data processing agreement containing training opt-out terms and data-retention minimization terms so that data transmitted to the relevant service provider is not used to train that provider's models. The services in use are set out in Articles 8 and 9.
(4) Should the Company wish in future to use content for training, it will disclose the purpose, scope and opt-out method in advance and obtain separate consent from the data subject; a data subject who does not consent will face no restriction on use of the Service. The Company records and manages whether the data subject has consented to the use of data for training and the dates and times of consent and withdrawal.
(5) Pseudonymized analytics data under Article 6 is used only for evaluating the quality of AI drafts and for service analytics, and is not used for the training, fine-tuning or other training of artificial intelligence models.
Article 6 (Processing of Pseudonymized Information)
(1) Pursuant to Article 28-2 of PIPA, the Company processes pseudonymized information as set out below for the purposes of compiling statistics and scientific research (including industrial research to improve the Service). This processing takes place regardless of whether the data subject has consented to the use of data for training, and separate consent of the data subject is not obtained.
| Category | Details |
|---|---|
| Purpose of processing | Evaluation of the quality of AI drafts (automated editing results) and analysis of service usage |
| Items processed | Account and project identifiers pseudonymized with HMAC, editor usage records, AI suggestion records and whether the Member adopted or modified them, upload transmission diagnostics, service usage log events (content itself such as video, voice and facial images, and directly identifying information such as email addresses and nicknames, are not included) |
| Retention period | Weekly snapshots: 15 days from the date of creation; daily log event files: 89 days from the date of the event (up to 90 days) |
| Processed by | The Company's AI team (storage and analytics infrastructure: Google Cloud Storage and BigQuery, Seoul region; see Article 8) |
| Provision to third parties | None |
(2) In processing pseudonymized information, the Company takes the following measures to secure its safety:
- 1. The key used for pseudonymization (HMAC key) is stored separately from the pseudonymized information in a repository with separate access rights, and the AI team has no access to the pseudonymization key.
- 2. Access rights to pseudonymized information are limited to designated personnel of the AI team, and access records are retained.
- 3. The Company does not process pseudonymized information for the purpose of recognizing a specific individual; where information that makes it possible to recognize a specific individual is generated in the course of processing, the Company immediately suspends processing and retrieves and destroys that information without delay.
- 4. Pursuant to Article 29-5 of the Enforcement Decree of PIPA, the Company prepares and keeps records of the processing of pseudonymized information, including the purpose of processing, the items processed and the history of use.
(3) Pseudonymized information is not used to train models and is destroyed without delay once its retention period expires.
Article 7 (Provision of Personal Information to Third Parties)
(1) The Company does not provide Members' personal information or content to third parties. However, where a Member requests posting to an external platform, the Company provides information as set out below with the consent of the Member, who confirms the recipient and the items provided on the posting screen and approves the posting.
| Recipient | Purpose of provision | Items provided | Retention and use period |
|---|---|---|---|
| Google LLC (YouTube) | Posting of the Output to the Member's YouTube channel | Output video; title, description, visibility setting and thumbnail entered by the Member | Until the Member deletes the post or unlinks the account (thereafter, in accordance with YouTube's policies) |
| TikTok Pte. Ltd. (TikTok) | Posting of the Output to the Member's TikTok account | Output video; description and visibility setting entered by the Member | Until the Member deletes the post or unlinks the account (thereafter, in accordance with TikTok's policies) |
| Meta Platforms, Inc. (Instagram) | Posting of the Output to the Member's Instagram account | Output video; caption entered by the Member | Until the Member deletes the post or unlinks the account (thereafter, in accordance with Meta's policies) |
(2) Where an Output posted to an external platform includes a depicted individual other than the Member, the Member must obtain that individual's consent in accordance with Article 17 of the Terms of Service. The Member may manage and delete posted Outputs directly on the relevant platform.
(3) The Company may in future operate a program under which content that Members elect to contribute is provided to third parties in the form of a dataset (the "Dataset Program"). In that case, the Company will comply with the following:
- 1. Consent will be obtained on a per-content basis; blanket consent covering all of a Member's content will not be obtained.
- 2. At the time of consent, the Company will specifically disclose the recipient, the purpose of provision, the items provided and the retention period.
- 3. Consent may be refused, and refusal will not result in any disadvantage in the use of the Service.
- 4. Content that includes a depicted individual other than the Member will be provided only where the Company has obtained consent directly from that depicted individual and retains evidence thereof, or where the content has been processed so as to make re-identification impossible.
- 5. The Company will impose on recipients, by contract, obligations not to resell, not to use for other purposes, not to attempt re-identification, and to comply with destruction requests.
- 6. Where the Company comes to process pseudonymized information under the Dataset Program, it will state the purpose, items and retention period of such processing in this Policy and comply with the requirements of Article 28-2 et seq. of PIPA.
(4) Effect and limits of withdrawal of consent: A Member may withdraw consent at any time, and the Company will immediately cease further provision and request destruction by the recipient. However, physical recovery may not be guaranteed with respect to data already provided before withdrawal. The Company clearly discloses this on the consent screen.
(5) The Company may provide personal information where specifically required by law or where an investigative authority so requests in accordance with the procedures and methods prescribed by law, and will notify the data subject of that fact unless prohibited by law.
(6) Matters concerning the collection of behavioral information by Meta Platforms, Inc. through the Meta Pixel installed on the Company's website are set out in Article 16.
Article 8 (Entrustment of Personal Information Processing)
(1) The Company entrusts personal information processing tasks as follows in order to provide the Service smoothly:
| Trustee | Scope of entrusted work | Retention and use period |
|---|---|---|
| Amazon Web Services, Inc. | Cloud infrastructure operation; storage of Original Content, Outputs and Member information; video rendering; storage of service usage logs (Amazon CloudWatch) | Until termination of the entrustment agreement or until the Member's deletion or withdrawal (service usage logs: 90 days) |
| Google LLC (Google Cloud) | GPU-based video analysis computation (processed serverlessly; data exists only during processing and is not stored) | Destroyed immediately upon completion of processing |
| Google LLC (Google Cloud Storage and BigQuery) | Storage and analysis of pseudonymized analytics data (Seoul region) | Retention period for pseudonymized analytics data under Article 4 |
| Google LLC (Google Analytics 4) | Web usage statistics analysis (including pseudonymized account and project identifiers) | 2 months |
| Google LLC (Google Workspace) | Sending of advertising emails to Members who have consented to receive marketing information; sending of service notices and replies to inquiries by email | Until sending is completed or the entrustment agreement terminates |
| Microsoft Corporation (Microsoft Clarity) | Session recording and heatmap analysis (records of on-screen interactions; input values are masked) | Session recordings 30 days; aggregated data 13 months |
| Userback Pty Ltd | Operation of the feedback widget; receipt and storage of feedback and attachments (screenshots, screen recordings, files) | 3 years after completion of handling, or until termination of the entrustment agreement |
| Slack Technologies, LLC | Internal notification of feedback received through the feedback widget | 3 years after completion of handling, or until termination of the entrustment agreement |
| Asana, Inc. | Management of the handling of feedback received through the feedback widget | 3 years after completion of handling, or until termination of the entrustment agreement |
| Aieev | Operation of domestic GPU servers and video analysis computation | Until termination of the entrustment agreement |
| OpenAI, L.L.C. | AI-based video scene analysis and classification, and highlight detection | Destroyed immediately upon completion of processing (or, where the provider has a retention period for abuse-monitoring purposes, for that period, up to 30 days) |
| Eleven Labs Inc. | Speech recognition (speech-to-text conversion) for advanced subtitles | Destroyed immediately upon completion of processing |
| Verifone (2Checkout) | Overseas payment authorization and settlement, and processing of recurring payment renewals | Until termination of the entrustment agreement or for the retention period under applicable law (5 years) |
| Kakao Pay Corp. | Domestic simple-payment processing | Until termination of the entrustment agreement or for the retention period under applicable law (5 years) |
| KG Inicis Co., Ltd. | Domestic payment processing and authorization (credit cards, bank transfers, etc.) | Until termination of the entrustment agreement or for the retention period under applicable law (5 years) |
| Korea PortOne Co., Ltd. | Operation of the payment integration service (transmission of payment requests and results) | Until termination of the entrustment agreement or for the retention period under applicable law (5 years) |
(2) When entering into an entrustment agreement, the Company specifies in the contract or another document, pursuant to Article 26 of PIPA, matters concerning the prohibition of processing personal information for purposes other than performing the entrusted work, technical and administrative protective measures, restrictions on sub-entrustment, management and supervision of the trustee, and liability including damages, and supervises whether the trustee processes personal information safely.
(3) The Company contractually requires trustees to obtain the Company's prior consent before sub-entrusting entrusted work to a third party, and discloses the status of sub-entrustment through this Policy.
(4) Where the contents of the entrusted work or the trustee changes, the Company will disclose the change through this Policy without delay.
Article 9 (Transfer of Personal Information Abroad)
(1) Pursuant to Article 28-8(1)3(a) of PIPA, the Company transfers personal information abroad as set out below for the purposes of entrusted processing and storage necessary to enter into and perform a contract with the data subject, and makes such transfers without separate consent by disclosing in this Policy the matters listed in Article 28-8(2) of PIPA.
| Recipient (contact) | Country | Date/time and method of transfer | Items transferred | Purpose of transfer | Retention and use period |
|---|---|---|---|---|---|
| Amazon Web Services, Inc. (aws-korea-privacy@amazon.com) | United States | Transmitted over an information and communications network at the time of service use | Member information, Original Content and Outputs, access records, service usage logs | Cloud infrastructure operation and data storage | Until termination of the entrustment agreement or until the Member's deletion or withdrawal (destroyed within 60 days, including backups; service usage logs: 90 days) |
| Google LLC (googlekr-privacy@google.com) | Singapore | Transmitted over an information and communications network at the time of a video analysis request | Video frame and audio data from Original Content | GPU-based video analysis computation (scene segmentation, speech recognition, etc.) | Destroyed immediately upon completion of processing (exists in memory only during computation; not stored) |
| Google LLC (googlekr-privacy@google.com) | United States | Transmitted through the Google Analytics 4 script when the website is used | Page view and event records, device and browser information, cookie identifiers, pseudonymized account and project identifiers | Web usage statistics analysis | 2 months |
| Google LLC (googlekr-privacy@google.com) | United States and other countries where Google data centers are located | Transmitted over an information and communications network when emails are sent | Email address, nickname, email content | Sending of advertising and service-notice emails, replies to inquiries | Until sending is completed or the entrustment agreement terminates |
| Microsoft Corporation (https://aka.ms/privacyresponse) | United States | Transmitted through the Microsoft Clarity script when the website is used | Records of on-screen interactions such as clicks, scrolling and mouse movement (input values masked), device and browser information, cookie identifiers | Session recording and heatmap analysis | Session recordings 30 days; aggregated data 13 months |
| Userback Pty Ltd (contact@userback.io) | United States, Australia | Transmitted over an information and communications network when feedback is submitted through the feedback widget | Feedback content, screenshots, screen recordings and attachments, email address, page address, browser and device information | Receipt and storage of feedback | 3 years after completion of handling, or until termination of the entrustment agreement |
| Slack Technologies, LLC (https://slack.com/privacy-policy) | United States | Transmitted over an information and communications network when feedback is received | Feedback content, email address, links to attachments | Internal notification of feedback | 3 years after completion of handling, or until termination of the entrustment agreement |
| Asana, Inc. (https://asana.com/terms/privacy-statement) | United States | Transmitted over an information and communications network when feedback is received | Feedback content, email address, attachments | Management of feedback handling | 3 years after completion of handling, or until termination of the entrustment agreement |
| OpenAI, L.L.C. (privacy@openai.com) | United States | Transmitted via API call at the time of a video analysis request | Video frame and audio data from Original Content and processing request information | AI-based video scene analysis and classification, and highlight detection | Destroyed immediately upon completion of processing (or, where the provider has a retention period for abuse-monitoring purposes, for that period, up to 30 days) |
| Eleven Labs Inc. (legal@elevenlabs.io) | United States | Transmitted via API call at the time of a request to generate advanced subtitles | Audio data from Original Content | Speech recognition (speech-to-text conversion) for advanced subtitles | Destroyed immediately upon completion of processing |
| Verifone (2Checkout) (privacy@verifone.com) | United States and others | Transmitted at the time of an overseas payment request and of a recurring payment renewal | Payment method information, transaction history, email address | Overseas payment authorization and settlement, and recurring payment renewals | Retention period under applicable law (5 years) |
(2) Pursuant to Article 28-8(1)1 of PIPA, the Company transfers personal information abroad as set out below with the consent of the data subject. A Member consents by confirming the following on the external platform posting screen and approving the posting; a Member who does not consent will be unable to use only the external platform posting feature.
| Recipient (contact) | Country | Date/time and method of transfer | Items transferred | Purpose of transfer | Retention and use period |
|---|---|---|---|---|---|
| Google LLC (googlekr-privacy@google.com) | United States | Transmitted via the YouTube API when the Member requests posting | Output video; title, description, visibility setting and thumbnail | Posting of the Output to the Member's YouTube channel | Until the Member deletes the post or unlinks the account (thereafter, in accordance with YouTube's policies) |
| TikTok Pte. Ltd. (https://www.tiktok.com/legal/report/privacy) | Singapore, United States and others | Transmitted via the TikTok API when the Member requests posting | Output video; description and visibility setting | Posting of the Output to the Member's TikTok account | Until the Member deletes the post or unlinks the account (thereafter, in accordance with TikTok's policies) |
| Meta Platforms, Inc. (https://www.facebook.com/privacy/policy) | United States | Transmitted via the Instagram API when the Member requests posting | Output video; caption | Posting of the Output to the Member's Instagram account | Until the Member deletes the post or unlinks the account (thereafter, in accordance with Meta's policies) |
(3) Pseudonymized analytics data stored in Google Cloud Storage and BigQuery is stored in the Seoul region and is not transferred abroad.
(4) A data subject may request suspension of the transfer of personal information abroad (PIPA Article 37). However, because the transfers abroad under paragraph (1) are essential to the provision of the Service, suspending them would make use of the Service impossible; in that case the data subject may cease processing by withdrawing their membership. The transfers abroad under paragraph (2) may be stopped by unlinking the external platform account. Request method: heimlog@heimdex.co
(5) Pursuant to Article 28-8(4) of PIPA, the Company implements necessary protective measures, including encryption of the transfer channel and of stored data, contractual prohibitions on use for other purposes and on onward provision, the imposition of safety obligations on recipients, and the operation of a grievance-handling procedure concerning transfers abroad.
Article 10 (Access to Content for Handling Inquiries and Disputes)
(1) The Company may access a Member's video content to the minimum extent necessary to handle the Member's inquiries, error reports, reports of rights infringement or disputes.
(2) Access is subject to the following principles:
- 1. Limited to matters received: The Company does not conduct continuous monitoring; access is limited to the files necessary to handle a matter for which a request or report has been received.
- 2. Minimum personnel: Only personnel designated in advance and bound by confidentiality obligations have access rights.
- 3. Records: The date and time of access, the person accessing, the subject and the reason are recorded automatically and retained for two (2) years.
- 4. Revocation of rights: Access rights are revoked upon completion of handling.
- 5. Purpose limitation: Information accessed is not used for any purpose other than handling the relevant matter and is not used for artificial intelligence training.
(3) A data subject may request confirmation of the access records relating to their own content by writing to heimlog@heimdex.co.
Article 11 (Matters Concerning Automated Decision-Making)
(1) The Company automatically selects and arranges the segments of a Member's uploaded video to be included in an Output. This is done on the basis of criteria such as image quality, camera shake, scene transitions, the presence of speech, and the arrangement method selected by the Member (chronological or thematic).
(2) The automated processing under paragraph (1) is carried out in order to generate an Output at the Member's request and does not have a material effect on the Member's rights or obligations; accordingly, it is not subject to the right of refusal under Article 37-2(1) of PIPA.
(3) However, a Member may at any time request an explanation of an automated decision pursuant to Article 37-2(2) of PIPA, and the Company will, absent justifiable grounds to the contrary, take necessary measures such as reprocessing with human intervention or providing an explanation. A Member may also manually modify the composition of an Output or request regeneration.
Article 12 (Destruction of Personal Information)
(1) Where personal information becomes unnecessary because the retention period has elapsed or the purpose of processing has been achieved, the Company destroys it without delay.
(2) Method of destruction
- - Electronic files: permanently deleted by a technical method that makes restoration impossible
- - Paper documents: shredded or incinerated
(3) Personal information that must be retained under applicable law is stored separately in a distinct database and is not used for any purpose other than retention.
Article 13 (Rights and Obligations of Data Subjects and Legal Representatives, and How to Exercise Them)
(1) A data subject may exercise the following rights against the Company at any time:
- - Request to access personal information
- - Request to correct errors
- - Request to delete
- - Request to suspend processing
- - Withdrawal of consent (including consent to receive marketing information, consent to the use of data for training, and external platform linking)
- - Request for an explanation of an automated decision
(2) Rights may be exercised through the settings menu within the Service or by writing to heimlog@heimdex.co, and the Company will act without delay (within ten (10) days from the date of receipt of the request in the case of access, correction and deletion).
(3) Where a data subject requests correction of an error in personal information, the Company will not use or provide that personal information until the correction is complete.
(4) Rights may be exercised through a legal representative or an authorized agent, in which case a power of attorney in the form of Attached Form No. 11 of the Enforcement Rules of PIPA must be submitted.
(5) A third party appearing in video may also exercise rights pursuant to Article 3(4).
(6) Unlinking of external platforms and deletion of data: A Member may unlink their YouTube, TikTok or Instagram account at any time through the settings menu within the Service, and upon unlinking the Company deletes the access tokens and account information for that platform without delay. A Member may also revoke the Company's access by the methods below, and the Company deletes the information in the same manner where it receives an unlinking or data deletion request from the relevant platform. Deletion of linking-related information held by the Company, such as posting records, may be requested by writing to heimlog@heimdex.co.
- - YouTube: remove HeimLog's access on the Google Account security settings page (https://security.google.com/settings/security/permissions)
- - TikTok: remove HeimLog under Settings and privacy > Security > Manage app permissions in the TikTok app
- - Instagram: remove HeimLog under Settings > Website permissions > Apps and websites in the Instagram app
(7) The Google Privacy Policy (https://policies.google.com/privacy) also applies to information processed through the YouTube API Services, and a Member who uses the YouTube posting feature is deemed to have agreed to the YouTube Terms of Service (https://www.youtube.com/t/terms).
Article 14 (Children Under the Age of 14)
(1) The Company does not accept membership registration by children under the age of 14. The Company verifies age by requiring entry of the year of birth at registration and, in the case of social login, also checks the age information provided by the relevant provider. An account subsequently confirmed to belong to a person under the age of 14 is immediately suspended and the related data is destroyed without delay.
(2) Where a child under the age of 14 appears in video uploaded by a Member, the rights relating to that child's personal information may be exercised by their legal representative.
(3) Where a Member seeks to enroll in the Dataset Program content in which a minor appears, the Company will separately verify the consent of the legal representative.
Article 15 (Installation, Operation and Refusal of Automatic Personal Information Collection Devices)
(1) The Company uses cookies and the following analytics tools to maintain login status, analyze usage statistics, improve the Service and measure advertising performance.
| Tool (operator) | Purpose | Items collected | How to refuse |
|---|---|---|---|
| Cookies (the Company) | Maintaining login status, storing usage settings, identifying acquisition channels | Session identifier, usage settings, acquisition information (UTM parameters, landing path of the first visit, referring site domain) | Cookie settings of the web browser |
| Google Analytics 4 (Google LLC) | Web usage statistics analysis; measurement of sign-ups and conversions by acquisition channel | Page view and event records, acquisition channel, device and browser information, approximate location, cookie identifiers, pseudonymized account and project identifiers | Install the Google Analytics opt-out browser add-on (https://tools.google.com/dlpage/gaoptout) or block cookies in the web browser |
| Microsoft Clarity (Microsoft Corporation) | Improvement of usability through analysis of on-screen usage flows (session recordings and heatmaps) | Records of on-screen interactions such as clicks, scrolling and mouse movement, device and browser information, cookie identifiers (values entered in input fields are masked and not collected) | Block cookies in the web browser |
| Meta Pixel (Meta Platforms, Inc.) | Measurement of advertising performance and personalized advertising | As set out in Article 16 | As set out in Article 16 |
(2) A user may refuse the storage of cookies through their web browser settings. However, refusing cookies may cause difficulties in using certain parts of the Service, such as maintaining login status.
- - Chrome: Settings > Privacy and security > Third-party cookies
- - Safari: Preferences > Privacy
- - Edge: Settings > Cookies and site permissions
Article 16 (Collection, Use and Provision of Behavioral Information and Refusal Thereof)
(1) For the purposes of measuring advertising performance and personalized advertising, the Company has installed the Meta Pixel on its website and permits Meta Platforms, Inc. to collect behavioral information as follows:
| Category | Details |
|---|---|
| Behavioral information collected | Website visit records (addresses of pages visited), records of events such as completion of sign-up and payment, cookie identifiers, IP address, browser information |
| Method of collection | Collected automatically through the Meta Pixel script when a user visits the website or an event occurs |
| Purpose of collection | Measurement of advertising performance, optimization of advertising audiences, and provision of personalized advertising based on the user's interests |
| Business permitted to collect and country | Meta Platforms, Inc. (United States) |
| Retention and use period | In accordance with Meta's Privacy Policy (https://www.facebook.com/privacy/policy) |
(2) The Company does not transmit through the Meta Pixel any information that directly identifies users, such as email addresses or telephone numbers.
(3) Users may refuse the collection of behavioral information and personalized advertising by the following methods:
- - Blocking third-party cookies in the cookie settings of the web browser (Article 15(2))
- - Turning off ads based on activity information from partners in the Facebook and Instagram ad preferences (https://www.facebook.com/adpreferences)
(4) The Company does not conduct personalized advertising targeted at children under the age of 14 and does not collect sensitive behavioral information, such as information on users' ideology, beliefs or health.
(5) Inquiries and reports of damage relating to behavioral information may be directed to the Chief Privacy Officer under Article 18.
Article 17 (Measures to Secure the Safety of Personal Information)
Pursuant to Article 29 of PIPA, the Company takes the following measures to secure the safety of personal information:
- - Administrative measures: establishment and implementation of an internal management plan (approved by the CEO), minimization of personnel handling personal information and periodic training, periodic self-inspection
- - Technical measures: management of the grant, modification and revocation of access rights to the personal information processing system; installation of an access control system; encryption of unique identifying information and passwords; encryption of stored data and of the transmission channel (TLS); encrypted storage of external platform access tokens; installation and updating of security software
- - Protection of pseudonymized information: separate storage of and restricted access to the pseudonymization key (HMAC key); preparation and retention of records of the processing of pseudonymized information (Article 6)
- - Protection of the admin console: member information is displayed in masked form in the admin console, and the person accessing, the date and time and the subject are recorded whenever full member information is viewed or an email address is copied
- - Retention of access logs: access logs of the personal information processing system (including records of access to member information in the admin console) are retained and managed for two (2) years or more, with measures applied to prevent forgery, alteration, theft and loss
- - Physical measures: access control for the server room, document storage room and similar areas
Article 18 (Chief Privacy Officer and Department Handling Access Requests)
(1) The Company has designated a Chief Privacy Officer to oversee personal information processing and to handle data subjects' grievances, as follows:
| Category | Details |
|---|---|
| Chief Privacy Officer | Name: Heejo Kang / Title: CSO / Contact: heimlog@heimdex.co |
| Department receiving and handling access requests | Department: Business Strategy Team / Contact: heimlog@heimdex.co |
(2) A data subject may direct all inquiries, grievances and requests for remedy relating to personal information protection to the Chief Privacy Officer or the responsible department, and the Company will respond and act without delay.
(3) The Company's proprietor or representative, as the person ultimately responsible for the safe processing of personal information and the protection of data subjects' rights, effectively carries out overall management measures, including the provision of necessary personnel and budget.
Article 19 (Remedies for Infringement of Rights)
(1) A data subject who needs to report or seek counselling regarding an infringement of personal information may contact the following bodies:
- - Personal Information Dispute Mediation Committee: 1833-6972 / www.kopico.go.kr
- - Personal Information Infringement Report Centre: 118 / privacy.kisa.or.kr
(2) A person whose rights or interests are infringed by a disposition or omission of the head of a public institution in response to a request under Article 35 (Access to Personal Information), Article 36 (Correction or Deletion of Personal Information) or Article 37 (Suspension of Processing of Personal Information, Etc.) of PIPA may file an administrative appeal in accordance with the Administrative Appeals Act.
Article 20 (Changes to this Privacy Policy)
(1) This Privacy Policy applies from its effective date.
(2) Where this Policy is amended, the Company will give notice on the initial screen of the Service and in its notice board from seven (7) days before the amendment takes effect; where the amendment has a material effect on data subjects' rights (such as provision to third parties, transfer abroad or the addition of purposes of use), notice will be given from thirty (30) days before, and separate consent will be obtained where necessary.
(3) Previous versions of this Policy are available within the Service.
Date of publication: October 23, 2026 / Effective date: November 22, 2026