Privacy Policy

Effective 2026-11-01 · Revised 2026-10-25

This Policy consists of Part 1 (personal information) and Part 2 (personal location information); Part 2 is the personal location information processing policy under Article 21-2 of the Act on the Protection and Use of Location Information. This is a translation of the Korean original. If the two differ, the Korean text prevails.
View Part 2: Personal Location Information Policy → · View the Location-Based Service Terms →

Gorocket Company Co., Ltd. (the "Company") processes the personal information of users of Every Ticket (the "Service") in accordance with the Personal Information Protection Act, the Act on the Protection and Use of Location Information (the "Location Information Act"), and other applicable laws. This Policy explains what information we process, on what basis, and for how long, and what rights users have and how to exercise them.

At a glance

• The Company processes information users enter, capture, or register; the route of travel of trips on which recording has been started; photos and videos stored in the cloud and their capture information; and information needed to run the Service. The device's real-time location is collected only while a trip is being recorded, and the capture location contained in photos and videos may be processed when they are stored in the cloud, independently of whether recording is in progress. The capture location of photos and videos is processed only if the user has consented to its collection and use. Even without consent, files with the location tags removed can be stored in the cloud.
• Routes of travel and photos and videos stored in the cloud are, in principle, used in the user's own account. Cuts, photos, and videos the user chooses to share are provided to the members of that trip. GPS data is removed from files for sharing, and capture coordinates and trip place identifiers are not included in sharing records or the API. Personal location information is not used for advertising purposes.
• Settlement bank details are optional. Only members of the same trip can copy them, and they are deleted 30 days after the trip ends.
• Trip photo and video files are stored in R2 of Cloudflare, an overseas processor, and the related management information is processed in the Google Cloud Seoul region. The information is destroyed upon a deletion request, deletion of the trip or account, or the end of the retention period. Content is not deleted when a subscription ends, and deletion of original files when Max ends and clean-up when storage stays over the limit for a long period follow Part 1, Article 7.
• AI features (ticket information extraction, trip drafts) use Google's Gemini model. Photos and surveys you submit are not used for training, and Google keeps them for abuse monitoring for at most 55 days before deleting them.
• The processors, destination countries, items, retention periods, and how to refuse for processing abroad are set out in Part 1, Article 6.
• On the Free tier, ads from Google AdMob are shown. Behavioral information such as advertising identifiers is collected by Google to serve ads, and the Company does not use personal location information for advertising. You can refuse personalized ads in your device settings.
• The quality and face detection analysis for photo organisation is performed on the device. When the user turns on automatic cloud saving, and after photo and video access permission and the necessary steps are completed, the photos and videos eligible for saving from registered trips are uploaded over Wi-Fi. The whole photo library is not uploaded, and automatic saving can be turned off in the app's storage settings.

Part 1 Privacy Policy

Article 1 (Items, Purposes, Basis, and Retention Period of Personal Information Processed)

The Company processes the items below for the purposes and on the legal bases stated. For items processed on the basis of consent, the Company informs the user of the necessary matters and obtains consent before that processing. The procedures under the Location Information Act apply to personal location information.

② On iOS we ask for App Tracking Transparency permission once, after you start using the app, and collect the advertising identifier (IDFA) only if you allow it. Declining does not limit the service. On Android we collect the advertising ID to measure ad performance and to serve ads on the Free tier. Advertising identifiers are used only to see which ad led to an install, to measure ad performance, and for Google AdMob to serve ads on the Free tier (Article 9-2). If you do not allow tracking or you delete the advertising ID, non-personalized ads are shown; your routes, photos, videos and plan contents are never provided for advertising.

You can stop this at any time: (1) ask us at the contact in Article 13, which also stops transmission for ad measurement; (2) iOS: Settings > Privacy & Security > Tracking, and turn off Every Ticket; (3) Android: reset or delete the advertising ID in your device settings.

③ The Company does not collect sensitive information (thoughts and beliefs, health, etc.) or unique identifying information (resident registration number, etc.).

④ At sign-up the Company confirms that the user is 14 or older, and does not collect the personal information of children under 14. If use by a person under 14 is found, the account and related information are destroyed without delay.

⑤ The photo gathering and organisation features analyse, on the device, the photos the user has allowed access to. Quality scores, photo feature values, and face detection and quality assessment results are not sent to the cloud. The organisation is processed under "Photo organisation records" in the table above, and cloud storage of photos, videos, Cut files, and thumbnails follows the "Cloud storage" item. The Company does not use face recognition that identifies people for photo organisation.

Article 2 (How Personal Information Is Collected)

1. The user enters, captures, or selects it directly in the app or on the website
2. On social sign-in, Google, Apple, Kakao, or Naver passes it to the Company with the user's consent (for Kakao and Naver, the Company's server verifies the token issued by the provider and receives the member identifier, nickname, profile photo, and email (where consented))
3. Automatic collection through the device's location feature, only for a trip being recorded
4. Automatic generation and collection by software development kits (SDKs) included in the app (Article 9)
5. The store passes the payment result to the Company
6. Within the scope of the photo and video access permission granted, photos and videos eligible for saving that fall within the period of a registered trip are uploaded automatically when connected to Wi-Fi, or uploaded by the user's choice. Automatic uploading takes place when the user turns on automatic saving, and it can be turned off in the app's storage settings. If the user has not consented to the collection and use of photo capture locations, capture coordinates are not sent and a copy with the location tags removed is uploaded. The whole photo library is not uploaded, and turning off automatic saving does not delete files already saved. Files already saved can be deleted separately.

Article 3 (Processing Beyond the Purpose of Use)

The Company uses personal information only within the scope of the purposes in Article 1, and if the purpose changes, processes it only with separate consent under Article 18 of the Personal Information Protection Act or within the scope permitted by law. If a feature is introduced that shows users' ratings and one-line reviews to other users, they are provided only in an anonymised, aggregated form from which individuals cannot be identified, and this Policy is revised to announce it.

Article 4 (Provision of Personal Information to Third Parties)

① In principle the Company does not provide users' personal information to third parties, and provides it only in the following cases.

Google's processing is described at https://policies.google.com/technologies/ads.

Copies of Cuts, photos, and videos for sharing do not include GPS, and sharing records and the API do not include capture coordinates or trip place identifiers. The user's route of travel is not shared either. A public itinerary link includes the place coordinates the user made public, and anyone who accesses the link can view the public content without signing in. The Company cannot itself delete copies that recipients have saved outside the Service. Place search terms and the map view area are passed to Google Maps Platform through the Company's server, but account information, IP address, and device information are not sent with them, so this is not provision of personal information to a third party; for transparency it is listed in the table in Article 6.

② Where there is a special provision in law, or an investigative agency requests it in accordance with the procedures and methods prescribed by law, the Company may provide information within that scope; the Company verifies the legality of the request, provides the minimum necessary, and records the details.

Article 5 (Outsourcing of Personal Information Processing)

① To provide the Service, the Company outsources personal information processing as follows.

② In its outsourcing contracts the Company stipulates, under Article 26 of the Personal Information Protection Act, the prohibition of processing beyond the outsourced purpose, technical and managerial protective measures, restrictions on sub-outsourcing, management and supervision of the processor, and compensation for damages, and supervises whether the processor handles personal information safely.

③ Where a processor sub-outsources the Company's work, it obtains the Company's consent, and the sub-processor and its work are disclosed in this Policy. The current processors carry out their work using their own cloud infrastructure (Google Cloud, Amazon Web Services).

④ If the content of outsourced work or a processor changes, this Policy is revised without delay to announce it.

⑤ The Apple App Store and Google Play are not processors of the Company but independent businesses that enter into payment contracts directly with users; payment method details are held only by the store and are not passed to the Company. The sign-in services of Kakao, Naver, Google, and Apple are also governed by each company's privacy policy.

Article 6 (Cross-Border Transfer of Personal Information)

① Under Article 28-8 (1) 3 (a) of the Personal Information Protection Act (outsourcing of processing or storage for the formation and performance of a contract with the data subject, where the following matters are disclosed in the privacy policy), the Company outsources processing and storage of personal information abroad as follows. PostHog, Airbridge and Meta Platforms are outsourced processing needed for operating and improving the Service, for the invitation link feature and for ad performance measurement, and fall under the same subparagraph, but users may refuse at any time.

② How to refuse cross-border transfer, and the effect

• Firebase (authentication, storage, notifications, diagnostics), Gemini, Google Maps Platform (places, routes, maps), RevenueCat, OpenWeather: these are processing needed for the basic structure of the Service, so to refuse them you must not use the feature concerned (AI features, place search, paid purchases, weather) or withdraw from the Service. Tickets can be entered manually without using AI features, and places can be added by tapping the map directly instead of searching.
• PostHog, Airbridge, Meta Platforms: a request to the contact in Article 13 stops transmission from the app, with no disadvantage in using the Service. The advertising identifier sent to Meta Platforms can also be stopped under iOS Settings > Privacy & Security > Tracking, or by resetting or deleting the advertising ID in Android's device settings. PostHog usage statistics on the website stop when you turn off the "Send usage statistics" switch on the website's account page or delete or block the browser's cookies and storage.
• Cloudflare: you can stop sending new files by turning off automatic saving in the app and not uploading or sharing manually. Files already saved can be deleted in the app. If you refuse the transfer, use of the cloud storage, restoration, and sharing features concerned is restricted.
• Google AdMob: you can refuse personalized ads by not allowing Every Ticket to track under iOS Settings > Privacy & Security > Tracking, or by deleting or resetting the advertising ID under Android Settings → Google → Ads. Refusing does not limit your use of the Service; non-personalized ads are shown instead. No ads are shown while you subscribe to Pro or Max.
• Requests to refuse or withdraw may also be made through the contact in Article 13.

③ For cross-border transfers the Company takes the protective measures under Article 28-8 (4) of the Personal Information Protection Act and its Enforcement Decree (concluding outsourcing contracts, encrypted transmission, supervising processors).

Article 7 (Procedure and Method of Destroying Personal Information)

① The Company destroys personal information without delay when the retention period has passed or the purpose of processing has been achieved.

② When the user deletes content or the account, the server operational data within that scope is deleted without delay, and on account deletion the social sign-in links are disconnected and deletion of identifiers held by processors is requested. Existing server backups in Google Cloud are destroyed within 7 days at most. Cloud photo and video files, thumbnails, and per-file management information are also included in that deletion scope. Files saved separately in the device's photo library are distinct from cloud deletion; where the user also chooses deletion from the photo library, they are handled according to that choice and the device permissions.

③ Method: electronic files are deleted in a way that cannot be recovered, and any printouts are shredded.

④ Information kept under law (the payment and enquiry records in Article 1) is stored separately from other personal information, is not used beyond the purpose of retention, and is destroyed when the period has passed.

⑤ Personal information is not destroyed in bulk merely because the Service has not been used for a long period. However, information for which another ground for deletion, such as deletion of originals when Max ends or clean-up of long-term excess storage, has arisen is destroyed according to its retention period.

⑥ Retention and deletion of subscription-related content are as follows.

When photo and video sharing ends, copies for sharing are kept for 1 day after it ends and sharing records for 7 days after it ends, then destroyed. This is distinct from the retention and deletion of the user's own original files. A public itinerary link stops being viewable 30 days after it is created, and the public link document is also deleted automatically. The original itinerary remains in the sending user's trip and follows that trip's retention and deletion standard.

A public itinerary link does not carry the sender's name. This is distinct from showing member nicknames in photo and video sharing.

Settlement bank details are destroyed automatically every day once their retention period ends. They remain in server backups, in encrypted form, for up to 7 days before being deleted.

Paragraph ④ applies to information to be retained under law. The provisions of Part 2 also apply to deletion of personal location information and withdrawal of consent, and this table does not delay any statutory obligation to destroy.

Article 8 (Rights of Data Subjects and Legal Representatives and How to Exercise Them)

① Users may exercise the following rights against the Company at any time.

1. Request access to personal information
2. Request correction or deletion where there is an error
3. Request suspension of processing
4. Withdraw consent (advertising notifications, marketing use of content, consent to cross-border transfer, etc.)
5. Refuse, or request an explanation of, a fully automated decision (Article 37-2 of the Personal Information Protection Act). The Service currently has no automated decisions that materially affect users' rights or obligations.

② How to exercise: App → My Page → Account (delete account) / App → My Page → Notifications (trip reminders, marketing messages) / for personal location information, My Page → Location settings (Part 2) / other requests by email to the contact in Article 13. The cloud automatic saving setting, and checking, downloading, and deleting saved files, are available on the app's storage and storage space management screens. Turning off automatic saving is distinct from deleting files already saved. Refusing personalized ads and resetting the advertising identifier can be done in the device settings (iOS Tracking, Android Ads). Settlement bank details can be edited or deleted in App → Expenses tab → Settle up → My bank account. The Company handles requests within the time limits and by the procedures set by the applicable laws for each type of request, and informs the user of the result.

③ A user's legal representative or an authorised person may exercise the rights on the user's behalf by submitting a power of attorney.

④ Where a request for access, correction, deletion, or suspension of processing is restricted by law (for example, where another law imposes a retention obligation), the Company informs the user of the reason.

⑤ No disadvantage results from exercising rights. However, requesting deletion or suspension of processing of information needed to provide the Service may make the feature concerned unavailable.

Article 9 (Installation and Operation of Automatic Collection Devices and How to Refuse)

① The Company's app includes the following SDKs; the information each collects automatically and how to refuse are as follows.

② Session replay (screen recording) is not used. The IP address sent to PostHog is set to be discarded immediately on collection. When app collection is stopped at a request to the contact in Article 13, the setting is saved to the account, so it stays off after reinstalling the app with the same account.

③ The website (everyticket.kr) and the web planning tool use the browser storage needed to provide the Service, such as keeping you signed in. The website (including the blog and the web planning tool) uses PostHog for usage statistics. It collects page views, link and button clicks (including affiliate links, app guidance and the calendar) and feature use (sign-in and sign-up, creating and editing plans, creating, opening and joining through invite links) together with a randomly generated identifier, which is stored in browser storage and a cookie. For signed-in users, the same member identifier as in the app is sent as well, so that app and website use can be analysed together. Email addresses and names are not sent, and the part of a page address after the question mark (?), such as the confirmation value in an invite link, is removed before sending. The IP address is discarded immediately on collection, and no screen recording is made. Turning off the "Send usage statistics" switch on the website's account page stops the collection in that browser immediately, and deleting or blocking this site's cookies and storage in your browser also stops it. In either case there is no disadvantage in using the Service. No cookies are used for advertising; if you refuse the sign-in cookie, you may not stay signed in.

Article 9-2 (Collection, Use, and Refusal of Behavioral Information)

① To show ads to Free tier users, the Company uses Google LLC's advertising service (AdMob), and in the process Google collects and uses behavioral information as follows.

② The Company does not collect or provide personal location information, trip records, photos and videos, or itinerary contents for advertising. Location information is not passed to the ad SDK.

③ The Company does not accept sign-ups from children under 14 and does not provide personalized ads to children.

④ You can refuse personalized ads or reset the advertising identifier as follows. Even if you refuse, ads may still be shown (non-personalized ads), and your use of the Service is not limited.

• iOS: Settings → Privacy & Security → Tracking → turn off Every Ticket
• Android: Settings → Google → All services → Ads → delete the advertising ID or turn off personalized ads

⑤ No ads are shown while you subscribe to Pro or Max, and the ad SDK does not collect behavioral information.

⑥ Inquiries and requests for remedies concerning behavioral information may be made through the contact in Article 13.

Article 10 (Measures to Ensure the Safety of Personal Information)

The Company takes the following measures in accordance with Article 29 of the Personal Information Protection Act and the Standards for Measures to Ensure the Safety of Personal Information, and Article 16 of the Location Information Act and the Standards for Managerial and Technical Protective Measures for Location Information.

1. Managerial measures: designating a privacy officer and a location information manager, establishing and operating guidelines for handling personal and location information, training staff who handle it, supervising processors
2. Access control: minimising persons with access to the management console (currently 1) and applying two-factor authentication, not issuing service account keys, keeping records of granting, changing, and revoking access rights for 5 years, allowing access only within the scope permitted to the user and to users with whom content has been lawfully shared, through authentication and access-right checks
3. Access logs: keeping access logs for the database, storage, and management console for 1 year or more and inspecting them regularly
4. Encryption: encryption in transit and of data stored in the cloud, protection of device storage. The account number in settlement bank details is stored encrypted, is not shown on screen, and is provided only after the server verifies a request to copy it made by a member of the same trip within the retention period
5. Backup and recovery: daily database backup (Seoul region, kept for 7 days)
6. Incident response: if a breach of personal information occurs, the Company takes the necessary measures, such as notifying data subjects and reporting to the relevant authorities, in accordance with the requirements, time limits, and methods set by the applicable laws (Article 15)

Article 11 (Other People's Information in Photos, Videos, and Audio)

① Photos, videos, and Cuts a user registers or stores in the cloud may contain other people's information such as faces, voices, and names. The Company processes such content to the extent necessary to provide the Service, such as storing, displaying, and restoring it, or carrying out sharing the user has chosen. Users can delete such content in storage space management and elsewhere, and requests to exercise rights over content containing one's own information may be made through the contact in Article 13.

② "Fill in with AI" is designed to extract only nine fields: whether it is a ticket, type, title, place, date, end date, origin, destination, and seat. It is instructed not to extract booking numbers, barcodes, or personal identification numbers, and the server filters them out once more.

③ Users are advised to mask other people's information before registering a photo, and must obtain that person's consent when sharing another person's information externally.

④ A person who believes their information is contained in another user's content may request deletion through the contact in Article 13, and may request notice of the source of collection and the purpose of processing under Article 20 of the Personal Information Protection Act.

⑤ To suggest the best of similar photos, the photo organisation feature uses functions provided by the device's operating system to determine, on the device, whether a photo contains a face and its quality. This is face detection, not face recognition that identifies who a person is. The Company does not create or store facial landmarks, contours, or feature values (biometric information), does not group photos by person, and the results remain on the device only as a few numbers per photo and are not sent to the Company.

Article 12 (Use of Generative AI)

The Service's "Plan trips with AI" and "Fill in with AI" (ticket information extraction) features use a generative artificial intelligence model (Gemini) of Google LLC. The information processed, the transmission path, retention, and the user's choices are set out in detail in Appendix 1. The Company announces this once more on an app screen when an AI feature is first run, and labels outputs made by AI as "AI generated".

Article 13 (Privacy Officer and Contact for Access Requests)

As a small business, the Company's Chief Executive Officer also serves as privacy officer. Users may direct enquiries, complaints, and requests for remedy concerning personal information arising from use of the Service to the contact above, and the Company responds and handles them without delay.

Article 14 (Remedies for Infringement of Rights)

Users may contact the following bodies for remedy or advice concerning personal information infringement.

• Personal Information Dispute Mediation Committee: 1833-6972, kopico.go.kr
• Personal Information Infringement Report Center (Korea Internet & Security Agency): 118 without area code, privacy.kisa.or.kr
• Supreme Prosecutors' Office Cyber Investigation Division: 1301 without area code, spo.go.kr
• Korean National Police Agency Cyber Bureau: 182 without area code, ecrm.police.go.kr
• Location information disputes: application for adjudication by the Korea Media and Communications Commission (02-2110-1300, kcc.go.kr)

A person who objects to the Company's disposition of a request for access, correction, deletion, or suspension of processing under Articles 35, 36, and 37 of the Personal Information Protection Act may file an administrative appeal under the Administrative Appeals Act (Central Administrative Appeals Commission 110, simpan.go.kr).

Article 15 (Notification of Personal Information Breaches)

If a breach of personal information occurs, the Company takes the necessary measures, such as notifying data subjects and reporting to the relevant authorities, in accordance with the requirements, time limits, and methods set by the applicable laws.

Article 16 (Changes to and Notice of the Policy)

① When the Company changes this Policy, it discloses the changes and their effective date so that they can be checked on the website or in the app. Changes that materially affect data subjects' rights are separately notified before or immediately upon the revision. Where prior notice or consent is required by law, that procedure is carried out first.

② Where this Policy and the Terms of Service differ, whichever is more favourable to the user applies.

③ Previous editions can be viewed in the revision history on the website.

Part 2 Personal Location Information Processing Policy

This Part is the personal location information processing policy under Article 21-2 of the Location Information Act and Article 25-2 of its Enforcement Decree. The Company is a location-based service provider reported to the Korea Media and Communications Commission (No. 12279, 8 September 2026), and the conditions for collecting and using personal location information follow the "Every Ticket Location-Based Service Terms".

Article 1 (Purpose of Processing and Retention Period of Personal Location Information)

① Purposes of processing

② The Company retains the personal location information needed to record trips and to organise, store, and restore photos and videos by location. Upon deletion of the trip or content, deletion of the account, withdrawal of the relevant consent, or the end of the retention period, the personal location information within that scope is destroyed. The retention period for cloud content following deletion of originals when Max ends and clean-up of long-term excess storage follows Part 1, Article 7.

③ Real-time location collection through the device's location feature takes place from when the user starts recording a trip until recording ends. The capture location and time contained in photos and videos stored in the cloud follow a path separate from real-time location collection and may be processed even for trips on which recording was not started. Personal location information is not used for advertising, marketing, or sales purposes.

④ Location coordinates in routes of travel and in cloud storage management information are kept in the Google Cloud Seoul region, and the capture location contained in photo and video files is kept with the files in Cloudflare R2. Matters relating to processing abroad follow Part 1, Article 6. Keeping the capture location in the user's own files is distinct from removing the location from copies for sharing, and the scope of shared information follows Part 1, Article 4.

Article 2 (Basis and Period of Retention of Records Confirming Collection, Use, and Provision of Location Information)

① In accordance with Article 16 (2) of the Location Information Act, the Company automatically records and keeps in its location information system materials that confirm the collection, use, and provision of personal location information (confirmation records). Confirmation records do not include coordinates.

② Items: start and end time of collection for each trip, method of collection (device location feature), consent version and consent time, date and time, purpose, and trip concerned for each use, any provision to third parties (where applicable), the user's exercise of rights, the date, time, and purpose of collection and use of photo and video capture locations, the collection path, and the related consent history.

③ Basis for retention: Article 16 (2) of the Location Information Act. Retention period: 6 months from the date of the record. Records are destroyed automatically when the period has passed, and if the user withdraws consent or withdraws from the Service, that user's confirmation records are destroyed without delay regardless of the period.

Article 3 (Procedure and Method of Destroying Personal Location Information)

① When destroyed: when the user deletes the trip or route; when the user withdraws (including withdrawal of consent, with confirmation records destroyed together); when the user withdraws consent (including confirmation records and the capture locations in cloud photo and video files); when use by a person under 14 is found. When cloud files are destroyed through deletion or the end of the retention period under Part 1, Article 7, the capture location in the files and the location coordinates in the related management information are destroyed with them.

② Method: operational data in cloud storage is deleted without delay, and existing server backups in Google Cloud (created once a day) are destroyed automatically within 7 days at most. Files the user has saved separately in the photo library or outside the Service are not deleted by deletion on the server, and the user can delete them directly. When consent to the collection and use of photo and video capture locations is withdrawn, the capture coordinates stored in the management information within that scope are deleted, and location tags remaining in cloud files are also removed without delay. Even after withdrawing consent, the user can use trips, tickets, and cloud storage features that do not use location information.

③ Confirmation records are destroyed automatically when the retention period in Article 2 has passed.

Article 4 (Provision of Personal Location Information to Third Parties)

① When Cuts, photos, and videos are shared, capture coordinates are not included in sharing records or API responses, and GPS metadata is removed from files for sharing. Trip place identifiers are also not included in sharing records or the API.

② The capture location contained in the user's own cloud files is processed for storage and restoration, and is distinct from the removal of location from copies for sharing. Storage, outsourced processing, and storage abroad follow Part 1, Articles 5 and 6.

③ A public itinerary link includes the coordinates of planned places the user made public. The scope of shared content and itineraries follows Part 1, Article 4.

Article 5 (Deleted)

Article 6 (Rights and Obligations of Guardians of Children Aged 8 or Under, etc., and How to Exercise Them)

① Where the guardian of a child aged 8 or under, a person under adult guardianship, or a person with a severe mental disability under the Act on Welfare of Persons with Disabilities (limited to registered persons with disabilities) consents to the collection, use, or provision of that person's personal location information to protect that person's life or body, the person is deemed to have consented.

② The guardian submits to the contact in Article 8 a signed written consent form stating the name, address, and date of birth of the child aged 8 or under, etc., the name, address, and contact details of the guardian, and that the purpose is limited to protecting life or body, together with a document proving guardianship.

③ The guardian may exercise the rights in Article 7 regarding the personal location information of the child aged 8 or under, etc., and must use that personal location information only to protect the life or body of the child, etc., giving priority to the child's interests.

④ The Company does not collect the personal location information of children under 14, and should it intend to do so in future, obtains and confirms the consent of the legal representative under Article 25 of the Location Information Act.

Article 7 (Rights of Subjects of Personal Location Information and How to Exercise Them)

Turning off the location permission in the device operating system technically prevents location collection but is separate from the withdrawal of consent above; to have already-collected personal location information destroyed, please use withdrawal of consent or deletion.

New automatic uploads can be turned off in the app's storage settings, and files already saved can be deleted in the app. Turning off the device location permission alone does not stop the upload of capture locations contained in files.

Article 8 (Location Information Manager)

Article 9 (Protective Measures for Location Information)

In accordance with Article 16 (1) of the Location Information Act and the Standards for Managerial and Technical Protective Measures for Location Information, the Company establishes guidelines for handling and managing location information, minimises persons with access and applies two-factor authentication, keeps access-right records for 5 years, encrypts data in transit and at rest, allows access only within the scope permitted to the user and to users with whom content has been lawfully shared, keeps access logs for the location information system for 1 year, and automatically records and retains confirmation records (see Part 1, Article 10).

Appendix 1. Details of Generative AI Processing

Appendix 2. Revision History