Team G Makers (hereinafter "the Company") explains how it processes users' personal information through this Privacy Policy. This Policy applies to the Company's mobile applications and website, and is established and disclosed in accordance with Article 30 of the Personal Information Protection Act ("PIPA").
The Company processes only the minimum information necessary to provide its services. The Company does not require login or sign-up, and does not collect directly identifying information such as email address, real name, or phone number.
The Company operates multiple mobile applications, and this policy applies commonly to all of them. The permissions used differ by app; information for permissions an app does not use is not processed. The permissions each app actually uses can be checked at the permission prompts shown on installation and in the "App Privacy" information on the App Store.
| Item | Purpose | Storage Location | Legal Basis | Required / Optional |
|---|---|---|---|---|
| Camera video / photos | Performing the app's core function (e.g., capturing objects/surroundings, displaying name tags/records) | User's device (and the user's own iCloud when iCloud sync is enabled) | User consent | Optional |
| Microphone input (audio) | Recording sound together with video (only for apps that provide video features) | User's device (and the user's own iCloud when iCloud sync is enabled) | User consent | Optional |
| Photo library | Saving captured results, or importing saved photos | User's device (and the user's own iCloud when iCloud sync is enabled) | User consent | Optional |
| Location information (GPS) | Providing location-based features (only for apps that provide location features) | User's device (and the user's own iCloud when iCloud sync is enabled) | User consent | Optional |
| Device / iCloud internal identifier | Identification of user data for synchronization between the device and iCloud (only for apps that provide iCloud sync) | User's device (and the user's own iCloud when iCloud sync is enabled) | Performance of contract | Optional |
The "Device / iCloud internal identifier" refers to an internal identifier created and managed by Apple for synchronization purposes; the Company cannot use it to identify individual users. Even if the user does not consent to optional items, the service can still be used, with only the relevant features being limited.
The Company does not install or operate any device that automatically collects personal information, such as cookies, on its website.
In apps that offer an improvement participation setting, feature-use and error counts are sent only after you turn on that setting or agree to share. We use counts of app launches, opening a composer, attaching photos, tapping location markers or background buttons, saving, canceling and reviewing saved records to improve usability and reliability. Sent information is limited to fixed categories, such as app and version, action and entry method, photo-count range and error type.
Photos, entered content, location coordinates, user/device/session/record identifiers, individual event timestamps and original error messages are not sent as usage information. The Company's aggregation server in South Korea stores daily totals by feature and category instead of individual event histories. We do not use these counts for targeted advertising or to trace an individual's usage path. Information that distinguishes first and repeat use or checks whether a saved record was revisited remains on your device; only the category is sent.
Participation is off by default. Declining does not change the app's features. Turning off improvement participation in app settings stops future transmission. Totals already aggregated contain no information that identifies an individual, so we cannot locate and delete a particular person's past counts. Daily totals and backups currently have no automatic deletion period.
Transmission involves connection information such as IP addresses and request times. The Company's aggregation server uses IP addresses in memory to limit excessive requests, without storing IP addresses, connection details or request bodies in its event database or request logs. In-memory IP information is removed when entries are pruned or the server restarts.
App records, such as photos, entered content and locations, are stored on the user's device, and when iCloud synchronization is used, it is also stored in the user's own iCloud. Data is retained until the earliest of the following:
Optional usage information is stored on the Company's server in South Korea as totals by date, feature and fixed category, as described in Section 2. Individual raw actions are not retained. Totals and backups currently have no automatic expiration period. IP addresses are used only in memory for request limits and are removed when entries are pruned or the server restarts. External relay processing is described in Sections 6 and 7.
Personal information whose retention period has expired is destroyed without delay.
The Company does not sell personal information or provide it for advertising or individual marketing. Connection information processed by external relay and website providers is described in Sections 6 and 7.
We use Cloudflare, Inc. to relay transmissions to our aggregation server in South Korea and provide security. Cloudflare processes connection information such as IP addresses and request details. We do not use Cloudflare as storage for usage totals.
Our website is served by GitHub Pages, which may process visitor IP addresses for security operations. See the Cloudflare Privacy Policy and the GitHub Privacy Statement for the providers’ practices.
Separate from usage totals stored in South Korea, Cloudflare processes connection information such as IP addresses through its international relay and security services. See the Cloudflare Privacy Policy for its practices and rights procedures. You can turn off optional usage transmissions in app settings.
Cloudflare, Inc. (United States, privacyquestions@cloudflare.com) may process connection information in the United States and the service regions handling a request. IP addresses, connection times and technical request information are processed through HTTPS connections for relay, service operation and security. Regions vary with network routing; Cloudflare publishes its network locations and sub-processor locations. The Company does not separately export IP logs or use them to identify individual app users. Cloudflare retains connection information as needed for service operation, security and legal obligations; the Company does not set one fixed retention period or directly delete that provider data. Retention criteria and rights procedures are described in Sections 8 and 11 of the Cloudflare Privacy Policy.
Optional usage sharing uses this connection relay. Declining or turning sharing off in app settings stops future usage transmission while parking features remain available. Questions about overseas processing and rights can be sent to the Company's privacy team (Section 10). Cloudflare's customer contract includes its Data Processing Addendum.
Separately, when the user uses iCloud synchronization, data is stored in iCloud operated by Apple Inc. (United States) through the user's own Apple account, and such storage is governed by Apple's privacy policy (apple.com/legal/privacy).
iCloud synchronization can be disabled at any time via Settings → Apple ID → iCloud → the relevant app on the device. Synchronization features and status are explained in app settings or guidance.
Users may at any time request to access, correct, delete, or suspend the processing of their personal information, or withdraw consent (including consent to iCloud synchronization).
Such rights may be exercised through the in-app settings menu or by emailing the Privacy Officer (Section 10). The Company will take action without delay upon receiving such a request.
If the user has suffered harm in connection with personal information, the user may seek consultation with the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr) or the Privacy Infringement Report Center (118, privacy.kisa.or.kr).
This service is intended for adults. Children under the age of 14 must use the service with the consent of their legal guardian.
The Company takes the following measures pursuant to Article 29 of PIPA:
The Company has no access to directly identifying information such as the user's Apple ID email or real name.
The Company has overall responsibility for the processing of personal information and has designated the Team G Makers Privacy Team () as its Privacy Officer to handle complaints and remedy grievances of data subjects. Business information required under Article 30-3 of PIPA is also disclosed together.
Requests to exercise data subject rights, such as requests for access, correction, deletion, or suspension of processing, may be submitted to the above Privacy Officer in writing or by email.
The Company does not currently carry out any automated decision-making (including profiling) that has a significant effect on the rights or obligations of data subjects. If introduced in the future, the criteria, procedures, and methods will be disclosed in advance in accordance with Article 37-2 of PIPA.
Usage totals contain no identifiers that distinguish an individual, so the Company cannot locate and transfer a particular user’s counts. Device records can be viewed and shared using the app’s features. Transfer or download of data stored in iCloud may be requested through Apple account settings or Apple Support (support.apple.com).
If the Company becomes aware of any loss, theft, or leak of personal information, it will notify users without delay of the items and time of the breach, the Company's response measures, the measures the user can take, and contact information for reporting and consultation. As the Company does not separately retain user contact information, in accordance with the proviso of Article 40, Paragraph 1 of the Enforcement Decree of PIPA, such notification will be substituted by posting on the Notice page and within the app for at least 30 days.
If this Policy is amended, the Company will provide notice through the Notice page and in-app notice at least 7 days before the effective date (at least 30 days in advance for material changes).
Revision history (the full text of earlier versions is available from the "Effective Date" menu below).
This revision was announced on October 11, 2026 and takes effect November 11, 2026. Until then, the June 12, 2026 version applies. Optional usage collection begins only after the effective date and the user opts in within the app. Declining or turning sharing off does not limit app features.