Loopyti · Privacy policy
This policy reflects Loopyti’s actual service structure and approved personal data retention and erasure policies.
Announcement date: 2026-11-06
Effective date: 2026-11-07
Operator: Choi Hwi-yeon · Privacy Officer: Choi Hwi-yeon (operator)
Contact: contact@loopyti.com · 010-5635-3581
This English translation is provided for understanding. If interpretations differ, the Korean original takes precedence.
Article 1 Information processing by feature
- Images selected in Object Split, Coloring Book, PNG Auto Crop and Background Remover, their contents and conversion results, and table or file contents pasted or selected in Order Change Diff and Excel/CSV Value Check, are processed in your browser. These tools do not upload originals or results to Loopyti servers or external conversion or generative AI services. Saving results to your device or sharing them directly with another service involves processing by that destination.
- Problem report text, attached files, and individual questions and answers are stored on the server to provide the service. Choosing a file in an image tool and uploading an attachment to a report are separate features.
- Playground progress, settings, and personal records are stored in that browser. The word similarity game sends guessed words, puzzle dates, and hint or answer-reveal requests to Loopyti’s server for calculation. It does not ask an external generative AI API to calculate results or store those requests as per-member game records in the database.
- Features that process file contents in the browser may still process connection information and usage statistics needed to open webpages. Articles 2 and 8 explain their scope.
Article 2 Personal data items and purposes
Loopyti processes information needed for the features you choose. Information needed for member services and your requested actions is processed under Article 15(1)4 of the Personal Information Protection Act. Consent-based processing such as optional publication and detailed analytics is explained and chosen separately. No registration is needed to view public pages or use basic image tools.
| Category | Information processed | Purpose and basis |
|---|---|---|
| PNG Auto Crop and Background Remover | Selected images and processing results | Processed in your browser; original and result files are not uploaded to Loopyti servers. |
| Order Change Diff and Excel/CSV Value Check | Pasted or selected table and file contents | Processed in your browser; input contents and result files are not uploaded to Loopyti servers. |
| Email registration and sign-in | Email address, password, pending registration information, email verification status, and registration and update times | Account creation, email verification, sign-in, and account protection. Article 15(1)4. Passwords are stored as salted, one-way scrypt hashes. New registrations record confirmation of age 14 or older, Terms of Use and Privacy Policy versions, and server confirmation time; birth dates are not collected. |
| Social registration and sign-in | Unique account identifier from your chosen Google or Kakao account, verified email if supplied, registration method, and connection time | Registration and sign-in with your chosen account and confirming the same user. Article 15(1)4. Age and terms confirmation records for new registrations are the same as email registration. See Article 3 for details. |
| Authentication and session maintenance | Internal member identifier, session, verification and recovery information, and credential creation, expiration, use and revocation times | Maintaining sign-in, access to your materials, sign-out, password reset, and request-forgery prevention. Article 15(1)4. |
| Problem reporting and management | Current work, process, difficulties, desired result, frequency, time spent, material types, visibility choices, selected industry and circumstances, member links, creation and update times, and versions | Understanding problems, review and replies, solution guidance, and viewing, editing and managing your reports. Article 15(1)4. |
| Posts written without logging in | Current work, process, difficulties, desired result, frequency, time spent, material types, selected industry and circumstances, deletion password, the policy version agreed to, and creation time | Publication on the board and confirming the author’s deletion request. Consent given on the writing screen (Article 15(1)1). The deletion password is stored only as a salted PBKDF2 one-way hash. Attachments are not accepted. The human check against automated posting (Cloudflare Turnstile) and per-IP limits on writing and deletion attempts follow the security and operations records. |
| Optional attachments | Contents of originals and public copies you submit, filenames, formats, sizes, report and owner links, and submission and review times | Understanding problems through materials and providing attachments. Article 15(1)4. Publication follows the separate choices in Article 4. Reports do not require attachments. |
| Questions, answers, and participation | Question and answer text, selected applicable circumstances, author and participant links, and creation and review times | Clarifying reports and providing common questions and answers and participation. Article 15(1)4. Individual-conversation publication is chosen separately. |
| Support and resolution outcome responses | Links between members, problems, and solutions; support, cancellation and change history; use, resolution and reuse responses; optional work-related need and willingness to pay | Preventing duplicate participation, maintaining current support, and assessing demand and outcomes. Article 15(1)4. You can support a problem without answering optional questions. |
| Email inquiries, rights requests, and tool requests | Sender email, any name, inquiry text and attachments supplied by the user, inquiry and reply times, and the minimum information needed to verify a request. The site’s tool request form emails the message, optional reply email, page, and language; it does not store the message in the site database. | Replies and follow-up. Article 15(1)4. Statutory rights requests follow Article 15(1)2 and related provisions. |
| Former anonymous feature requests | Request title, contents, and receipt time; separately managed browser-identifier hashes, request dates and counts | New submissions have ended. Existing requests are retained only for the Article 5 period for review. These were optional requests unrelated to contract performance and are no longer collected. |
| Security and operational records | IP address and browser information in connection requests; rate-limit hashes derived from authentication IPs, emails or member identifiers; request time windows and counts; member and operator action identifiers and times | Authentication and access control, service security, abuse prevention, and change tracking. Limited to contract performance or the minimum scope of legitimate interests under Article 15(1)6. Hashing alone does not make information anonymous. |
| Statistics and detailed analytics | Visit identifiers, usage events, device and browser information described in Article 8 | Understanding feature use and improving errors. Analytics with identifying information follow the basis explained in Article 8. |
Do not include others’ contact details, customer data, resident registration numbers, health data, passwords, authentication keys, payment information, or private company materials in input or attachments. Remove or redact information unnecessary to understand the problem. Report descriptions may be published as written as soon as they are submitted, and Loopyti does not automatically detect or remove personal or confidential data. Loopyti does not request sensitive or unique identifying data without the separate legal requirements.
Article 3 Google and Kakao sign-in
Google sign-in requests the openid email permissions for account identification and email verification. It processes Google’s verified unique identifier and supplied verified email. It does not request names, profile photos, Gmail, Google Drive, contacts, or calendar access.
Kakao sign-in processes Kakao’s verified unique account identifier and a valid, verified email if supplied. You can register with the Kakao account identifier even without an email. Kakao’s consent screen shows the information actually provided.
Loopyti does not collect social account passwords. Authentication codes are exchanged and checked on the server. Provider access and refresh tokens are not stored in Loopyti’s member database or sent in member browser responses. Accounts using different sign-in methods are not linked automatically merely because their emails match.
When you choose Google sign-in, temporary identifiers and authentication codes needed for the request and verification are exchanged between Google and Loopyti. Google directly processes connection information such as IP address and browser when you visit its authentication screen. Authentication is separate from GA4 detailed analytics; you can choose Google sign-in while rejecting detailed analytics.
Social account information is used for registration, sign-in and account management. It is not automatically published as a display name or used for ad targeting, personal data sales, or general-purpose AI training. Use of Google API information and transfer to other services comply with the Limited Use requirements of the Google API Services User Data Policy.
Article 4 Choosing publication of reports and materials
Report originals and original attachments are accessible to the author and authorized operator. New member reports are private by default. Report descriptions a member sets to “Public on the board” and posts written without logging in are published as soon as they are submitted, without prior operator review. Attachment copies and individual case conversations are each published within their chosen scope and review result.
| Choice | Scope published | If not chosen or withdrawn |
|---|---|---|
| Report description | The content as written, for reports a member sets to “Public on the board” and posts written without logging in: the work, difficulty, desired result, current method, circumstances, frequency and time entered by the author. The difficulty, desired result and current method are also shown as the board title and summary. The operator may take inappropriate posts down. “Redacted public” can no longer be selected; reports that already chose it show only the operator-approved description. | Private reports are excluded from public lists, search, sitemaps, and public demand counts. Private reporting and operator review remain available. Posts written without logging in cannot be private; to stop publication, delete the post with the password set when writing it. |
| Display name in public cases | Public cases use “Reporter” by default. Member emails, social member IDs, social account names and photos are not shown. | Email and account names are not used as public display names. Descriptions are published as written as soon as they are submitted, so do not include personal details or contact information. The operator may take down posts that contain personal data. |
| Public attachment copies | Copies separately permitted per file, submitted by the author, and approved by the operator | Originals remain private. Withdrawing file-publication permission ends access to its public copy. |
| Individual question-and-answer cases | Reviewed content within the separately permitted scope of that report’s case conversation | Only the author and authorized operator see individual conversations. Withdrawing case-conversation permission does not withdraw public file copies. Change each file’s permission separately. |
| Common questions and answers | Operator-reviewed public versions of content submitted for a common topic | Private circumstances may be sent through your report’s individual conversation. Member emails, account identifiers, and names are not automatically published on common questions and answers. |
Public materials are provided to unspecified visitors to Loopyti’s public pages, to understand shared problems, share cases and questions and answers, and review solutions. Items are the public descriptions, approved versions and public copies in the table. Publication lasts while permission remains or until deletion or publication ends. Publication of materials containing personal data requires separate consent under Articles 15(1)1 and 17(1)1. Refusing publication does not restrict private reports or basic tools.
When a member edits a public description, the edited content is published as soon as it is saved. To stop publication, switch it to private or delete the report. Posts written without logging in cannot be edited and can be deleted with the password set when writing them. Making a description private also disables case-conversation and all file-publication permissions; returning to public does not restore them. Representative problems supported by other public reports or independent operator research may remain, but this does not justify continued publication of withdrawn personal data.
Search engines may collect public pages, and others may save public descriptions and files. Loopyti stops publication on the site but cannot instantly recall all downloaded copies or existing external search caches. Publishing a new policy alone does not expand existing reports’ publication permissions.
Article 5 Processing purposes and retention and destruction periods
The following periods are Loopyti’s approved operating policy, not statutory mandatory retention periods. Personal data no longer needed because its purpose is fulfilled, retention expires, or deletion or account closure is requested is destroyed without delay unless law requires retention. Statutory retention is checked for its basis, items and period and managed separately. If direct payments are introduced, applicable transaction records will be defined separately. Current external-transfer support is not treated as Loopyti e-commerce payment.
| Data type | Processing purpose | Retention and destruction criteria |
|---|---|---|
| Member email and account information | Member identification, account management, sign-in and service provision | Until account closure |
| Original problem reports and revision history | Analyzing difficulties, review, categorization and grouping, finding solutions, and report management | Until the report is deleted or the account is closed |
| Posts written without logging in and deletion password hashes | Publication on the board and confirming deletion by the author | Until the author deletes the post with its password or the operator deletes it outright. The password hash is erased with the post. Posts the operator only takes down are kept privately until deleted. |
| Original attachments and public copies | Understanding circumstances, reviewing solutions, and publishing permitted materials | Until the file or report is deleted or the account is closed |
| Support, questions, answers, and solution ratings | Assessing demand, gathering opinions, and verifying effectiveness and reuse | Until the content is deleted or the account is closed. Canceling support changes its current state and is separate from destroying its history |
| Sign-in sessions | Maintaining sign-in, checking access rights, and preventing abnormal access | Valid for up to 7 days. Invalidated immediately on sign-out |
| Email registration verification information | Verifying email ownership and preventing fraudulent registration | Verification link valid for 24 hours |
| Password reset information | Verifying account ownership and changing passwords | Reset link valid for 30 minutes; cannot be reused after use |
| Temporary social sign-in state | Checking authentication request validity and forgery | Valid for up to 10 minutes; used state removed after authentication |
| Visit identifier hashes and individual visit records | Preventing duplicate visit counts and understanding recent use | Last 90 days. Analytics withdrawal triggers deletion requests for identifiable records of that browser |
| Hashes for authentication and request-abuse prevention | Preventing abnormal sign-in, automation, abuse, and attacks | Deleted in the next daily cleanup after the relevant limiting purpose ends |
| General inquiry email | Receiving and replying, confirming results, and follow-up inquiries | 6 months after the inquiry is resolved |
| Admin security and action audit records | Checking action history, preventing abuse of authority, and verifying changes, publication and deletion | Normally 90 days. Records needed for disputes or rights protection require a separate retention basis; no arbitrary extensions |
| Existing anonymous feature requests | Checking improvement demand, development priority, and duplicate requests | Up to 1 year after receipt. New submissions have ended |
| GA4 user-level and event-level data | Usage analysis, tool-use patterns, and improvement effectiveness | 2 months. Configured not to restart the retention period with new activity |
| Statistical totals that cannot identify individuals | Long-term visit trends, feature usage, and service outcome analysis | No time limit while individuals remain unidentifiable |
| Separately downloaded database backups | Disaster recovery | Up to 7 days from creation. Expired backups are automatically deleted in registered storage locations |
| Minimal deletion and publication-withdrawal records stored separately from backups | Preventing restoration from reactivating deleted or withdrawn information | Records whose purpose has ended are cleaned after a default 14 days, allowing a margin beyond the 7-day restore window. Holds needed for ongoing destruction or restoration are shown to administrators and do not justify arbitrary retention extensions. Simple identifiers and hashes are not treated as anonymous |
Authentication-link and session validity periods differ from actual database destruction times. Expired or revoked credentials are unusable, and unnecessary rows are automatically cleaned once a day. Duplicate-request hashes are cleaned daily after the maximum 24 hours needed for retries; those with identifiable owners are removed on account closure. Some older hashes with unknown owners are not retained long-term or treated as anonymous.
Hashing, removing a member ID, or hiding a name alone does not make data anonymous. Materials that could identify a person when combined with other information remain subject to purpose and destruction criteria. Statistical totals left after personal data removal do not include IPs, member IDs, browser UUIDs, filenames, or report text.
The current Cloudflare D1 Free plan Time Travel restore window was confirmed as 7 days. This is not immediate deletion equivalent to deleting the operational database. Separate backups are managed by creation time and registered location. Restored data is not made available through the service until separate deletion and withdrawal records have been reapplied and checked. Provider-managed backups follow their own rules, distinguished in Article 7.
Article 6 Withdrawal of publication, deletion, account closure, and destruction methods
- Making content private stops external publication but differs from deleting the author’s report original and attachments. Making a description private also revokes related case-conversation and file-copy publication permissions. Returning to public does not restore them automatically.
- Withdrawing case-conversation publication stops only that report’s individual questions and answers. File-publication permission must be withdrawn per file. File withdrawal stops public access to copies; deleting an original requires file or report deletion.
- Report or attachment deletion requests immediately block public screens, APIs, and download access and delete originals, revisions and links without a statutory retention basis. Actual deletion of server-held R2 originals and public copies is attempted immediately. Failed files are retried through a secure queue at the next cleanup. Database deletion and stored-file removal are separate steps.
- Confirming account closure in My problems invalidates all existing sessions and destroys the account, authentication methods, your reports, files, questions, answers, support, ratings and identifiable links. Other people’s valid materials and shared descriptions are not automatically deleted, while the former member’s distinctive content and identifiers are removed as publication grounds. Mixed summaries containing withdrawn materials are hidden and reorganized.
- Failures or partial completion are retried with ordinary access blocked while the operator monitors status. If an older shared solution’s provenance cannot be reliably distinguished, publication and access are blocked while it is checked. Deletion is not described as complete during this review, and other users’ independent materials are not arbitrarily deleted. Failures do not justify indefinite retention. Minimal restore-prevention records are stored separately from backups and follow Article 5’s purposes and limits.
- Electronic files are deleted so they cannot be recovered or reproduced; printouts, if any, are shredded or otherwise rendered unreadable. Provider backups, inquiry inboxes and materials already sent externally follow separate procedures in Article 7.
Canceling support removes current support, not all history. Signing out, deleting a report, or disconnecting Google or Kakao does not replace Loopyti account closure. For access, correction, deletion, or suspension unavailable on screen, use Article 12’s contacts. Do not include passwords or verification or reset links in inquiries.
Article 7 External services and international transfers of personal data
Loopyti uses the following external services by feature. For entrusted processing, legally required matters such as purpose limits, safeguards, subprocessors, destruction and incident response must be contracted and managed. General provider terms are distinguished from actual account applicability and acceptance; unverified contracts are not described as concluded. Providers’ own-purpose processing is explained separately by role and applicable terms.
Provider subprocessor information is available from Cloudflare (https://www.cloudflare.com/gdpr/subprocessors/), Resend (https://resend.com/legal/subprocessors), the Google Analytics-related list (https://business.safety.google/adssubprocessors/), and Zoho (https://www.zoho.com/privacy/sub-processors.html). These lists are published by each provider for product categories; they do not mean Loopyti data is sent to every provider listed.
| Provider and feature | Processing tasks and information |
|---|---|
| Cloudflare, Inc. | Website and API delivery and security; account, report, participation and metadata storage in D1; attachments in R2; administrator authentication; basic visit statistics; forwarding incoming inquiries through Email Routing. Processes connection requests and information needed for these tasks. Storage of inquiry email and replies are distinct roles below. |
| Plus Five Five, Inc. (Resend) | Email registration verification and password reset delivery. Processes recipient and sender addresses, subject, bodies with one-time verification or recovery links, and sending and delivery status. Member passwords and report or attachment originals are not included. Not used for inquiry replies or general notices. |
| Google LLC — Google Analytics 4 | Detailed usage analytics permitted by users. Processes Article 8’s visit, device and event information, separate from account information received through Google sign-in. |
| Google LLC — Gmail | Final receipt and storage of inquiry email. Processes sender email, inquiry text and attachments forwarded by Cloudflare. |
| Zoho Mail — manual inquiry replies and tool request delivery | Manual inquiry replies written and sent by the operator using the contact address in Article 12, and delivery of site tool requests to the fixed contact address. Processes reply recipients’ email addresses, reply and quoted content, sending records, and tool request content, optional reply email, page and language. Tool requests have no file attachments, and their original text is not stored in the site database. |
Google and Kakao authenticate the social account you choose; the providers operate their own account services’ processing. This differs from entrusting Loopyti member data processing to them. Information Loopyti receives is described in Article 3. Loopyti does not send member data or private reports to social providers for advertising.
The following table describes international transfers. Processing entrusted to a provider or storage necessary for entering into or performing a contract uses Article 28-8(1)3 of the Personal Information Protection Act; optional detailed analytics uses an applicable basis such as separate consent under Article 28-8(1)1. Reading this policy or continuing to use the site alone does not constitute consent to international transfers.
| Recipient and contact | Transfer countries | Transferred information and purpose | Transfer timing and method | Retention and basis |
|---|---|---|---|---|
| Cloudflare, Inc. / privacy@cloudflare.com | The United States and other countries in which Cloudflare data centers are located (storage in the Asia-Pacific (APAC) region) | Web connection, account, report and participation information, attachments and metadata needed for service provision. Web delivery, storage and security | Transferred through encrypted communication when connecting, registering, signing in, reporting, attaching files or participating | Article 5 criteria. Provider database recovery copies 7 days and Workers logs 3 days (Cloudflare official documentation). Article 28-8(1)3 |
| Plus Five Five, Inc. (Resend) / privacy@resend.com | United States (storage country in official provider guidance) | Recipient email, verification and recovery email bodies, and sending and delivery information. Providing verification mail requested by users | Transferred through encrypted communication when verification, resending or password reset is requested | Email and logs: 30 days; provider backups: 7 days (official security documentation). Separate guidance states that deletion of remaining data after closure of the provider account can take up to 90 days; this is different from deleting an individual Loopyti member account |
| Google LLC — GA4 / https://support.google.com/policies/troubleshooter/7575787?hl=ko | The United States and other countries in which Google and its subprocessors operate data centers | Online identifiers, device and browser, generalized pages and referral sources, and usage events. Optional usage analytics | Transferred through encrypted communication on relevant pages after consent to analytics and international transfer | User and event data: 2 months; retention reset on new activity disabled. Standard aggregate reports are outside this setting. Separate consent under Article 28-8(1)1 |
| Google — Account authentication | The United States and other countries in which Google data centers are located | Temporary identifiers and authentication codes needed for sign-in verification. Providing sign-in with the chosen Google account | Exchanged through encrypted communication when choosing Google sign-in and authenticating | Loopyti does not store authorization codes or provider tokens, and removes sign-in verification values within 10 minutes. Retention on Google's side follows the Google Privacy Policy |
| Google LLC — Gmail (incoming inquiries) | The United States and other countries in which Google data centers are located | Sender email, inquiry text and attachments. Receiving inquiries | When inquiry email is forwarded and stored | Retained in the Loopyti inbox for 6 months after inquiry completion and deleted manually by the operator. The provider’s official guidance states that deleted mail may remain in Trash for 30 days |
| Zoho Mail (manual inquiry replies and tool request delivery) / privacy@zoho.com. Contracting entity: Zoho Corporation | United States | Recipient email, reply and quoted text, tool request message, optional reply email, page, and language. Inquiry replies and tool request delivery | When the operator replies to an inquiry or a user submits a tool request | Loopyti retains this information for 6 months after inquiry completion; the operator manually deletes sent replies. The provider’s official guidance states that deleted mail may remain in Trash for 30 days and encrypted backups for 3 months |
Refusing Cloudflare connection-data processing needed for webpage delivery and security may limit site use. If you do not want international entrusted processing or storage needed for accounts, reports or mail, stop using those features and request suspension or deletion. Rejecting optional analytics transfers still allows basic tools and member features. Choose another sign-in method if you do not agree to social authentication.
External solution or support links you open are governed by that service’s Privacy Policy. Loopyti’s support screen links to external transfer services and does not collect card numbers or bank-account passwords. Sender labels in transfer records and inquiry materials received by the operator are processed only as needed to confirm support and handle inquiries under Article 5.
Article 8 Cookies, browser storage, and analytics
1. Required authentication and usage settings
| Stored item | Use | Retention criteria |
|---|---|---|
__Host-loopyti_session Cookies | Maintaining sign-in and access to your materials | Up to 7 days from issue. Can be invalidated by signing out. |
__Host-loopyti_oauth Cookies | Checking social sign-in progress and preventing forged requests | Up to 10 minutes. Removed when sign-in finishes. |
| Analytics choice | Remembering permission or rejection of detailed analytics | Until that site’s browser data is deleted or your choice changes |
| Playground progress, settings and personal records | Continuing games in that browser | Until site data is deleted or the records are reset. No automatic sync to other devices. |
| Random identifier for Loopyti’s visitor count | Avoiding duplicate counts by browser and date for permitted analytics visits | Created only when analytics is allowed. Rejection or withdrawal immediately deletes the stored visit-count value. A separate copy for withdrawal retries is explained in the next row. Otherwise it remains until site data is deleted. Session storage or temporary window memory may be used if local storage is unavailable. |
| Minimal value for retrying visit-record withdrawal | Used only to retry deletion requests for that browser’s server records | A copy of the previously allowed value is kept in restricted separate storage for up to 24 hours. Not used for visit records or external analytics. Deleted on completion or purpose ending; expired values are cleaned on the next page opening. |
_ga, _ga_<식별값> and other GA4 cookies | Analyzing usage flows for permitted visits | Up to 2 years (the Google Analytics default, which has not been changed). Separate from server retention of user and event data. |
You can block or delete cookies and stored information in browser privacy and site-data settings. Blocking authentication cookies may limit sign-in; deleting site data may reset analytics choices and playground records.
2. Basic statistics and Loopyti visitor counts
Cloudflare basic visit statistics and tool and platform usage and error counts are used. Counts store dates, permitted screen, feature, action and error categories, and necessary public problem and solution identifiers. Email, member identifiers, report text, images, attachments, filenames and authentication tokens are not included in these counts.
Loopyti’s visitor counter creates random identifiers only for browsers allowing analytics on Object Split, Coloring Book and Playground. The server stores derived values and first and daily visit times for 90 days. No identifier is created or sent before a choice or after rejection. Rejection or withdrawal immediately deletes the browser’s stored identifier. Withdrawal requests deletion of identifiable server records using the existing browser identifier; failures use a deletion-only minimal value for restricted retries up to 24 hours. This value is not reused as a new visit identifier. Server race-prevention hashes are deleted at the next daily cleanup after a limited purpose of up to 120 seconds. If the browser already lost its identifier, records may be unidentifiable, so inquiry handling is distinguished from automatic 90-day cleanup. Identifier-free daily and total visit counts remain. These records are not described as fully anonymous merely because account names are not collected.
This counter measures visits deduplicated by consenting browser and date, rather than total page openings. ‘Unique browsers in the last 90 days’ and ‘Total accumulated visits’ are different metrics and are not labeled as unique browsers over the service’s entire history. A new browser identifier or multiple browsers may count the same person separately.
3. Google Analytics 4
When detailed analytics is allowed, GA4 is used on Object Split, Coloring Book and Playground tool pages. It analyzes pages, referrals, device and browser information, online identifiers, and permitted events such as tool selection, processing success and errors, downloads and game actions. Loopyti’s detailed events do not include image or file contents, filenames, original report, question or answer text, guessed words, or member emails.
Detailed analytics does not apply to sign-in, email verification, password reset, report entry, My problems, administrator screens, platform home or public problem pages. This policy and Terms of Use are also excluded. Page addresses sent to GA4 are generalized and stripped of queries and authentication values.
Code denies advertising storage and personalization for detailed analytics. Actual Google Signals settings are checked separately, and sign-in authentication and analytics are not activated together. Google may process IP addresses during connections but states that GA4 does not log or store individual IP addresses.
4. Advertising provisions (conditional — currently inactive)
Loopyti currently displays no advertisements. This section applies when advertising is activated; until then, no advertising-related personal data processing occurs. Before introducing advertising, Loopyti will finalize actual settings such as pages, providers, countries, retention periods and consent paths, activate these provisions, and update this policy and the relevant tables in Articles 2, 7 and 8 together.
When advertising is activated, advertisements will be displayed through Google AdSense. Advertisements will be distinguished from the service’s ordinary content and features.
Third-party advertising providers, including Google (vendors and advertising networks), may place or recognize cookies in your browser or use web beacons, IP addresses and other online identifiers to collect and process information as a result of serving advertisements. This information is used for ad requests and delivery, impressions and clicks, frequency capping, fraud prevention, advertising measurement and aggregate reporting. Depending on your choices and applicable law, personalized advertisements may use past visits to Loopyti or other websites.
Google’s use of advertising cookies may enable Google and its partners to serve personalized advertisements based on your visits to this site and other sites on the Internet. Information about how Google processes information from users of partner sites and apps is available in Google’s partner-site information guide (https://policies.google.com/technologies/partner-sites?hl=ko).
You can opt out of personalized advertising in Google’s ad settings (https://myadcenter.google.com or https://adssettings.google.com). You can also visit www.aboutads.info/choices (or www.aboutads.info) to opt out of third-party providers’ cookies for personalized advertising. Where third-party advertising providers or networks offer their own opt-out tools, use the paths provided on their websites or privacy policies. You can also block or delete cookies in your browser settings.
Advertising cookies and identifiers are processed separately from GA4 detailed analytics under Article 8, Section 3. Consent to detailed analytics is not expanded to advertising personalization; personalization requires a separate choice. Declining detailed analytics does not also decline advertising cookies.
Loopyti does not provide original or result images processed by image tools, private problem reports and attachments, account emails or authentication information as advertising materials or targeting data. Processing connection and usage information for ad requests is separate from providing the contents of uploaded files. Advertising scripts are excluded by default from screens handling private information, such as sign-in, report submission and My problems.
Before introducing advertising, the following items will be finalized and disclosed using actual operational settings:
- Pages displaying advertising: public and tool pages where advertising scripts actually load
- Advertising providers and networks: Google LLC (or the regional Google contracting entity) and third-party Ad Technology Providers actually enabled, including their names, roles, provider-list links and opt-out links
- Processed information: cookies, web beacons, IP addresses, mobile and online advertising identifiers, browser, device and network information, visited page URLs and referrers, and interactions such as ad requests, impressions and clicks
- Purposes: advertising delivery (including contextual and non-personalized advertising), personalization where selected, frequency capping, advertising measurement, and prevention of fraudulent clicks and abuse
- Cookie and data retention: actual expiration of advertising cookies and identifiers, and server retention by provider
- International transfers (under the applicable subparagraphs of Article 28-8(1) of the Personal Information Protection Act): ① recipient names and privacy contact details; ② destination countries; ③ personal data transferred; ④ timing and methods (such as encrypted network transfers when advertising scripts load or send requests); ⑤ recipient purposes and retention periods; ⑥ how and where to refuse transfers and the effects of refusal (consent controls, ad settings, browser cookie blocking, and service effects such as non-personalized or general advertisements); ⑦ the legal basis for international transfers (reflected identically in the Article 7 transfer table)
- Consent, refusal and withdrawal paths: on-site advertising privacy settings or consent management screen
When serving advertisements to users in the European Economic Area (EEA), United Kingdom or Switzerland, Loopyti will use a Google-certified consent management platform (CMP) integrated with the IAB Transparency and Consent Framework (TCF), in accordance with Google’s EU User Consent Policy. In those regions, using cookies or local storage for frequency capping, aggregate reporting and fraud prevention requires user consent and a certified CMP under applicable local law and Google policies, including for non-personalized advertisements. The current GA4 analytics choice panel is not a Google-certified CMP. Advertising regions, a certified CMP, IAB TCF integration and disclosure of enabled Ad Technology Providers (ATPs) must be checked before advertising is introduced.
5. Changing choices and refusal
Allow or reject analytics through notices on tool pages. Optional analytics consent is not needed for basic tools. Deleting records already sent externally is separate from clearing browser storage and can be requested through Article 12’s contacts.
Change your choice anytime in Analytics settings on tool pages. Rejection stops detailed analytics requests and further loading, clears related cookies and Loopyti’s visitor identifier, and requests deletion of identifiable Loopyti server records. Already loaded analytics scripts disappear completely only after refreshing.
Before introducing a new analytics provider or advertising technology that changes data items, purposes, sharing or international transfers, Loopyti will update this policy and the choice interface and obtain any required consent. Existing analytics and separate advertising are not covered by a single blanket consent. Loopyti currently displays no advertisements. The advertising provisions in Article 8, Section 4 apply when advertising is activated; until then, there are no advertising data items processed.
Article 9 Users under 14 and automated decisions
Registration, reporting and participation are intended for people aged 14 or older. If data from a child under 14 requiring legal-representative consent is found collected without it, processing is restricted and necessary steps such as deletion follow law. Legal representatives may exercise rights through Article 12’s contacts.
This registration and reporting standard is not an age ban on all image tools used without registration. Features needing children’s personal data require legal-representative consent and verification and clear guidance first.
Loopyti does not make decisions with significant effects on user rights or duties solely through fully automated personal data processing. Report descriptions are published as soon as they are submitted, within the scope the author chose; authorized operators decide whether to take inappropriate posts down and review publication of materials such as attachment copies and conversations. Automated tool conversion and game scoring are not such decisions.
Article 10 Rights of users and legal representatives and how to exercise them
You may request personal data access, correction, deletion, suspension, consent withdrawal and account closure. My problems lets you view, edit and delete your reports, change visibility and case-conversation and per-file publication permissions, and delete attachments and public copies. You may also request account closure there. For matters unavailable on screen and individual deletion of common questions, answers or support history, use Article 12’s contacts.
State the sign-in method used, subject of the request and desired action. Do not send passwords, one-time codes, recovery links or complete resident registration numbers. Loopyti checks only the minimum information needed to verify you or an authorized representative. Representatives may submit authorization evidence such as a power of attorney.
Loopyti acts within statutory procedures and periods and explains results. If law restricts a request, the reason and appeal route are explained. Withdrawing optional-processing consent does not restrict unrelated basic features. Features unavailable after account deletion are explained before processing.
Disconnecting Google or Kakao permissions differs from deleting personal data already stored by Loopyti. If needed, manage the provider connection and request Loopyti deletion separately.
Article 11 Safeguarding personal data
Loopyti applies safeguards appropriate to service features and data. Authentication uses HTTPS, passwords are stored as one-way hashes, and authentication tokens are checked for purpose, validity and hash. Authentication cookies have security attributes.
Member and operator permissions are separated. Servers check ownership, publication permission and approval state. Original attachments are in private storage and served only to authorized requests. Operator access to personal data and downloaded copies is limited to work needs.
Private reports and attachments are not arbitrarily supplied to external AI tools, promotional channels or other businesses for purposes unrelated to service operation. New external processing or uses require a lawful basis and necessary notice and consent first.
Article 12 Privacy Officer and remedies
Privacy Officer: Choi Hwi-yeon (operator)
Email: contact@loopyti.com
Phone: 010-5635-3581
Use the contacts above for privacy inquiries and rights requests. For reporting or consulting on privacy violations or dispute mediation independently of the operator’s response, contact these institutions.
- Personal Information Infringement Report Center: 118 (no area code) / https://privacy.kisa.or.kr
- Personal Information Dispute Mediation Committee: 1833-6972 / https://www.privacy.go.kr
Article 13 Policy changes
Changes to processing items, purposes, retention, processors, international transfers or user rights are announced before application, and this policy and announcement and effective dates are updated. Separate consent is obtained where law requires. Users are informed of important changes and can review the preceding policy.
The policy before this change is available as the 2026-11-02 Privacy Policy.
Announcement date: 2026-11-06
Effective date: 2026-11-07
External privacy information for reference
- Google Privacy Policy: https://policies.google.com/privacy?hl=ko
- Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
- How Google uses information from partner sites: https://policies.google.com/technologies/partner-sites?hl=ko
- Google advertising settings (My Ad Center): https://myadcenter.google.com (or https://adssettings.google.com)
- Kakao Privacy Policy: https://www.kakao.com/policy/privacy
- Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/
- Resend Privacy Policy: https://resend.com/legal/privacy-policy
- Zoho Privacy Policy: https://www.zoho.com/privacy.html
- Resend security and retention: https://www.resend.com/security
- D1 Time Travel: https://developers.cloudflare.com/d1/reference/time-travel/
- Google Analytics data retention: https://support.google.com/analytics/answer/7667196?hl=ko