Additional terminal advertising privacy notice

1. Information and purposes

Account information includes social-login identifiers, email and display name, or email-registration information, a password hash, verification status and verification/reset-token checks. We use it to create, secure and recover accounts; we do not store the password in plain text.

Advertising data includes impressions, clicks, visible time, ad/campaign/client IDs, time, version, display context, authentication/deduplication data, and selected region/language. It supports billing, rewards, fraud prevention and the interface. Hosting infrastructure may process IP addresses and request logs for security and reliability.

Redemption data includes name, email, phone number where needed, country, residence/tax eligibility information, verification result/reference, reward ledger, order details and supplier status. The standard gift-card profile does not request or collect a new passport number, including for non-residents. If applicable law requires additional tax information, we separately identify the necessary items, legal basis and retention and obtain any required consent before fulfillment. New SodaGift LINK requests send the recipient's name, product, amount and order reference. We do not register an overseas bank account for a U.S. cash-out feature.

We process support messages and email recipients, subject lines, message contents and necessary verification/reset/delivery links. Optional launch alerts use email, language and consent/confirmation records.

To complete new account setup, you must answer one occupation from a fixed list and select at least one interest or explicitly choose ‘no specific interest.’ Setup participation is optional for existing accounts in the legacy state before manual country confirmation; participants answer the same questions. After country approval, missing required answers must be completed before new earning or redemption activity. These setup answers are required regardless of personalization availability, while personalized-ad consent is a separate optional choice. Submitted answers are validated; without consent, their values are not stored in the server’s ad profile. Consent, decline or withdrawal, the applicable version and processing time are recorded separately. The setup-answer requirement is separate from later voluntary Ad preferences, where you may leave occupation blank or select no interests. Once the required setup is complete, declining or withdrawing personalization has no adverse effect on service access or earnings. Only with consent do we retain your selected interests and occupation in the active ad profile for relevant-ad priority. We do not use occupation to confirm or infer employment, tax treatment or residency, and do not provide individual member profiles to advertisers. Clearing consent and saving in Ad preferences immediately clears the active interest and occupation values and stops their use for personalization. Unsubmitted answers are held temporarily in this tab’s browser session storage and may be restored after a reload. This temporary draft never stores or restores the consent choice and is removed after a successful submission.

Individual advertisers for the Korean service: We use the advertiser name displayed in ads, its link to the signed-in member account, individual/Korean-service registration category, registration/purchase agreement version, document reference, displayed language and acceptance-processing records, and account-based promotion duplicate-award records for account linkage, advertiser-name display, creative review and delivery, transaction support, and promotion capacity and duplicate-award controls. Individual registration does not collect business numbers, opening dates, representative names or government business-verification data. It does not establish Korean nationality, tax residency, employment status or one first promotion award per natural person. Receipt issuance identifiers are entered directly in Toss checkout, not in individual registration.

We confirm a new account’s service country from the country code supplied through a trusted web connection. A verified country from the start of web social login applies to a new account; an account created without that signal waits for its first setup request made by the signed-in account owner. The initial email signup request does not fix the country. We store the country code, confirmation state, source and time. This country-confirmation path does not read, forward or store a raw IP address in the account database. Later login locations, language or travel do not automatically change it. Connection country does not establish nationality, tax residency or eligibility for cash payment.

For existing accounts created before this feature, we do not reconstruct the signup country or record the current connection as the location at signup. Existing members may request manual country confirmation if they wish. A confirmation or change request records the requested country (KR, JP or US), a reason from a fixed list (moved, detected wrong or other), request and review status and times, and the deciding operator’s identifier. There is no free-text field. A request alone does not change the country; approval records the review source and approval time. Once the country is confirmed, any missing required setup answers must be completed before new earning or redemption activity. Existing balances, transaction history and rights to view or resolve them are preserved. Past orders, settlements and ledger entries are not rewritten.

2. Local processing and contents we do not receive

Supported-site detection, generation status, panel visibility and device activity are processed locally to derive ad events. Your conversations, source-code contents and prompt text are not sent to our servers. This does not mean that only an ad identifier and timestamp are processed.

3. Service providers and international processing

The business in the footer is the controller/operator in South Korea. Our main account, advertising and transaction database uses Supabase in Seoul; API servers use Google Cloud Platform in Seoul. The table describes external hosting, email and security services and their locations and retention criteria.

Vercel Customer Data hosting and SSR/BFF processing, and Cloudflare site-protection verification, use the contract-necessity route in Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act for necessary entrusted processing and storage, with disclosure of the statutory particulars. This entrusted-processing basis does not include a provider's independent improvement purposes. Resend rely on the contract-necessity route in Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act. This basis does not cover optional launch alerts, marketing messages or a provider's independent service-improvement processing.

When you request a web page or server operation, Vercel processes your IP address, request information and necessary access logs, as well as login session information and account, advertising and transaction requests and responses that actually pass through the web server, over encrypted connections. When an authentication or reset email is requested, or a necessary service message arises, sender and recipient addresses, subject, content and required links are sent to Resend in the United States over encrypted SMTP.

You may ask the privacy contact in the footer to stop processing or close your account. Stopping hosting processing prevents use of the website; stopping authentication or reset emails prevents those email functions. Optional alerts can be withdrawn separately through their withdrawal link or our contact.

Where enabled, Cloudflare Turnstile processes browser/network signals and verification tokens for bot prevention. Identity verification uses the provider identified on the verification screen through the PortOne integration. SodaGift processes gift-card order information. If you follow a supplier's recipient link, that supplier's notice applies to information it collects directly on its site.

We do not send individual member lists, conversation contents or source-code contents to advertisers. We use information needed for each provider's function and may disclose it when required by law. New gift-card or payment features include the relevant recipient, countries, data, timing and method, purpose, retention, basis and refusal choices, with separate consent where required. Accepting general terms alone does not replace legally required transfer consent.

Browser and connection signals are processed when the Cloudflare Turnstile widget runs, which may happen before submission of a form. On submission, the verification token is checked through Siteverify. Turnstile does not collect form inputs or communications. The token validity of 300 seconds is not a retention period for personal information.

For rights requests concerning Cloudflare processing as a processor to protect our site, contact our privacy contact in the footer. For its own bot-detection improvement as an independent controller, you may contact Cloudflare at dpo@cloudflare.com.

Cloudflare determines retention using the processing purpose, nature of the information, processing risks, available alternatives and legal or contractual obligations. When retention is no longer needed, it deletes or destroys the information; if deletion is technically unavailable, it takes measures to prevent further use.

Vercel's public DPA distinguishes its processor role for Pro and Enterprise customer data handled under customer instructions from its independent controller role for its own service-generated usage records and support contact information. Its own privacy notice governs the purposes and rights for that independent processing.

Vercel's current public subprocessor table lists the United States, Spain and United Kingdom as locations. This describes providers for particular functions; it does not mean all information from our site is sent to every provider or that the table completely lists CDN and support processing countries. We currently use the Pro plan and Fluid Compute. The Functions settings screen has Washington, D.C., U.S. (iad1) as its default region, with a confirmed source override selecting Seoul (icn1). These settings do not guarantee the actual execution location of every function or restrict all CDN and support processing to Korea. No Drains for external log forwarding are associated with this project.

The documented runtime-log retention is 1 day on standard Pro, or 30 days if Observability Plus applies to this project. Plus applicability has not been confirmed. This period does not apply to all information. Separately from its customer-data deletion rules, Vercel retains its own usage and contact information while needed for service operation, support and legal or contractual obligations, and anonymizes or deletes it when no longer needed. Preventing caching of authenticated responses does not mean no access logs are collected.

When the widget runs, signals pass directly from your browser to Cloudflare. On form submission, our server checks the verification token through Siteverify; our current signup and notification checks do not separately attach your IP address. This is not a transfer of member information from the company database to Cloudflare.

Cloudflare's Korean addendum lists Article 15(1)(4) (performance of contract) as its stated basis for End Users information and describes operation, improvement and security purposes. This is the provider's explanation; it does not mean that we include its independent processing in our entrusted-transfer basis or have obtained your separate consent to it. Contact our privacy contact for site-protection processing under our instructions, and dpo@cloudflare.com for Cloudflare's own bot-detection improvement.

Security signals are processed when the widget runs on the signup and notification paths. If you do not want this direct processing, you can avoid those paths and request rights through our contact or Cloudflare as described above. We do not promise an improvement-only opt-out or an alternative signup path that we do not provide. This role notice is not a consent checkbox and is separate from optional notification-email consent.

4. Retention and deletion

We keep account data while providing the service and delete eligible data after closure. Required transaction and tax records are separated and retained for the applicable legal purposes. Pending redemption or a legal obligation may require limited continued retention; we explain the relevant limits when handling a request.

Unconfirmed launch-alert requests are removed after 7 days. Confirmed requests are removed after processing the alert, except an uncertain delivery result may be checked for up to 7 days before removing the address and tokens.

Backups, security logs and provider copies follow their actual retention and deletion procedures; deletion from the active service is not a claim that every copy disappears simultaneously. The published detailed retention and transfer disclosures must match the operational settings.

Identity information collected through earlier workflows, if retained, is reviewed separately for its legal basis, continuing need and deletion. Ending new collection does not itself establish that all historical records have been deleted.

Your selected interests and occupation remain in your active profile while you maintain optional consent. Clearing consent and saving immediately deletes your active interests and occupation and stops their use for personalization. Transaction and tax retention periods do not apply to this optional profile. Existing backup and provider-copy deletion descriptions remain applicable.

When deletion of an individual advertiser account is confirmed, we delete its registration link, agreement-processing records and account-based duplicate-check key if there is no confirmed payment, provider transaction or first deposit-confirmation record, issued virtual-account receipt or payment-confirmation attempt, or promotion award. A plain pending intent with no issuance or confirmation attempt does not itself retain the registration link. If an actual transaction, issuance/confirmation attempt or promotion history exists, we separately retain only the minimum link and transaction records needed to reconcile the original payment, preserve original-order refund authority and check account-based duplicate awards. After a refund or award revocation, items needed to reconcile those original records are used only for those purposes and managed under the existing transaction-record retention/deletion policy.

The server records the setup completion time and the required-answer validation time (reward_profile_answered_at) once each. These completion markers contain no occupation or interest answer values. When account deletion is actually finalized, we clear the active ad profile, account country, that account’s country-review requests and both setup completion timestamps. If a deleted operator decided another member’s request, we remove the operator’s identifier from that decision. Past transaction, tax and ledger records, backups and provider copies follow the existing retention and deletion disclosures. There is no blanket automatic 30-day deletion period for country, profile or review records.

5. Cookies and security

We use an encrypted session cookie that browser JavaScript cannot read, and may store language or service settings locally. Blocking cookies can prevent login. Security tools may separately process the signals explained above.

We protect sensitive payout information with encryption and restrict access to authorized personnel. Staff may access necessary information to fulfill a verified payment or support request. No transmission or storage system is an absolute security guarantee.

6. Your requests and U.S. rights

Use My personal data or the privacy contact in the footer to request access, correction, deletion, restriction or withdrawal of consent. We verify the requester using information reasonably needed to prevent unauthorized disclosure. You can ask why a request was limited and request review of that decision.

Depending on your state and whether the law applies to this business, additional rights may include obtaining a copy, opting out of sale, sharing or targeted advertising, and appealing a decision. We assess and honor rights that apply; this notice does not claim that a business-size threshold or other statutory test has already been satisfied. Exercising a right does not itself justify unlawful discrimination.

We do not provide individual member profiles to advertisers. Personalized ads use only the interests and occupation that you directly select and separately consent to retain. Required answers during new account setup, including missing answers after an existing member’s manual country approval, are separate from optional personalization consent and from later voluntary Ad preferences, where occupation may be left blank. Once required setup is complete, you may decline or withdraw personalization without adversely affecting service access or earnings; withdrawal clears the active selected profile. Existing balances, transaction history and rights to view or resolve them are preserved.

7. Contact and changes

The operator's registered details and privacy officer's contact are in the footer. Contact them about handling, complaints or a privacy request. We announce notice changes and their effective date at least 7 days in advance, obtaining separate consent when required. The revision date above is not a claim that every new data transfer has begun.

8. Terminal ad connection and minimum data

This supplement applies to Greedy Krab terminal ad connection and measurement alongside the existing privacy notice. It applies from the effective time shown below. This notice and any required consent are completed before terminal rewards are activated.

A terminal connection starts when you run greedykrab login and approve it on the signed-in website. We process member and device identifiers, the device name you choose, OS type, CLI version, the accepted terms and terminal disclosure versions, creation, approval, last-use and revocation times, and the revocation reason for device authentication, connection management, account protection and advertising eligibility. Do not put conversation content or personal information in the device name.

Pairing uses approval-code verification data, hashes of delivery and replay-prevention secrets, request status, and creation, expiry, approval, denial and delivery times. The device stores its authentication key; the server retains an authentication hash. An encrypted copy used to deliver the key once after approval is removed after delivery. Copies past the delivery window are removed by request handling and cleanup jobs.

Terminal ad measurement uses member, device, ad, campaign and exposure identifiers, creative and plugin versions, service country and language, measurement and approval versions, signals that an ad line is shown while work is active, server start, update and end times, accrued time and block counts, sequence, duplicate-prevention and verification data, charges, rewards and policy versions. Purposes are calculation, limits, duplicate and abuse prevention, and transaction evidence. Each task gets a fresh random reference; the server keeps its verification value.

Opening an ad link processes a click ticket and Cloudflare Turnstile verification token on a Greedy Krab security page. Paid clicks retain member, device, ad, campaign, exposure and ticket identifiers, click time, charge, reward and policy version for verification, duplicate prevention, navigation and transaction evidence. The advertiser’s privacy notice applies after you reach its site.

9. Work content we do not send and your choices

This integration does not send Claude prompts, answers or conversations, source code or file contents, terminal screen contents, project paths, or Claude’s actual conversation or session identifiers to Greedy Krab servers. Claude’s own provider notice applies to content you send to its service. We do not provide conversation or code contents to advertisers.

Approving a connection does not turn on ad measurement. Display time is counted only while the account-wide measurement setting, including Chrome and VS Code, is on. You can revoke each device through connection management or CLI logout. Sign-out everywhere, password reset and account deletion also invalidate the relevant keys. Declining this ad connection does not restrict use of Claude itself.

My personal data shows connected devices and daily terminal measurement and reward totals. Confirmed account deletion revokes devices, replaces device names with an erasure label and deletes the member’s pairing requests. Disconnecting does not immediately erase transaction evidence that must be retained.

The provider roles, processing locations and rights described above apply to the server, database, web hosting and Turnstile. Hosting security may process your connection IP address. Pairing and click rate limits use verification values derived from an address or network range, request counts and expiry times; they do not store the original IP address in terminal device or exposure tables. Infrastructure security logs are processed separately under the provider’s actual retention settings.

10. Terminal retention and deletion

We separate connection authentication, operational monitoring and monetary evidence. Cleanup removes records after their retention period. Backups and provider copies follow actual retention settings and deletion reapplied after restoration; not every copy disappears at the same instant.

Operational monitoring aggregates member identifier, five-minute bucket, fixed outcome kind and count. A review flag records a fixed rule, member identifier where applicable, severity, count, state, first and last detection, review time and reviewing administrator identifier. These records exclude prompts, conversations, code, files, original IP addresses, tickets, tokens, ad URLs and raw error text.

Review flags are retained for 30 days from first detection regardless of resolution. An unresolved state does not extend that period. Necessary ongoing monetary-case evidence is managed through existing transaction, adjustment and refund processes; flags are not all retained for five years.

The five-calendar-year period for paid terminal details starts at the latest confirmed related processing time: exposure closure or expiry, ad charge or reward posting, a payment tied to that earning, an ad-funding refund or adjustment, or a recorded reward-hold or correction resolution. We do not purge while a hold, review, payment, refund or adjustment remains unresolved, or linkage and consistency with original records cannot be confirmed. A resolution recorded as a source-linked posting, payment, refund, adjustment or hold release restarts the five years from that latest time. Dismissing an operational alert alone is not a new monetary action and does not extend the period. This does not determine that all terminal data is legally required for five years.