Privacy Notice

Accounts and sign-in

We use the account identifier from Kakao or Naver, or the identifier in a Google or Apple ID token, to distinguish accounts and check access rights. Sign-in uses these identifiers. We do not use provider profile details, names or email addresses to sign you in. For phone verification, we send the number to the text-message provider and store an HMAC hash of it. We also hash verification codes and IP addresses for verification and rate limits.

We save your nickname, registration time, the time and version of the notice you accepted, and any interests you choose to help sort listings. You can change your nickname, interests and display language, and remove saved cities or stores.

Reservations and visits

We keep details of the store and offer, reservation time and status, and the visit code and its expiry. Each store can see its own reservations and confirm visits using the QR code or visit code you show. An offline ticket can keep the code on your device until it expires. For simulated deposits, we record the test amount and status and when you accepted the applicable no-show terms.

If you rate a visit, we keep the rating and time. The store sees its average and response count once there are at least five responses. Individual ratings stay private.

If you opt in, the arrival reminder includes the store name and minutes remaining. We record when the reminder was sent, when you requested the five-minute extension and when the store was notified. We use no-show records from the past 30 days and account or browser identifiers to apply booking restrictions. Three eligible no-shows within 30 days restrict new bookings for 24 hours from the latest missed arrival deadline.

Messages and automatic translation

We retain the account, store, offer or reservation associated with a conversation, plus message text, translations, language, provider, send times and read status. We delete message bodies from the service database 90 days after sending. We retain report reasons and log staff access to reported conversations.

If translation is enabled, we mask phone and email patterns and send the text to be translated to DeepL SE in Germany or Anthropic, PBC in the United States, depending on the service configuration. This can include messages, store replies, and public store names or offer text. The provider receives the text at the time of translation for that purpose.

DeepL API Pro deletes submitted text and translations after translation and delivery. Under its free-service policy, DeepL API Free may use text to improve its services. The standard Anthropic API usually deletes inputs and outputs within 30 days, subject to arrangements for specific products or contracts, policy enforcement and legal requirements.

DeepL Privacy Policy Anthropic retention policy

The transfer basis, how to refuse a transfer, recipient contacts and the applicable service plan and retention terms are pending legal and contract review.

Location, maps and age checks

If you allow location access, your browser calculates distances. For a Deal Ping, the server uses the coordinates to find stores within 500 metres and discards the coordinates after the search. A store sees party size, expected arrival time and approximate distance. We retain the request, offers and match, and retain location-processing records for at least six months. You can change location permission in your browser or device settings.

Maps send your IP address and tile requests to OpenStreetMap. When English address lookup is enabled, we send the public store address to the Korean Ministry of the Interior and Safety’s address service and save the result. For age-restricted offers, the verification service checks whether you are at least 19. We retain the verification identifier, result and time. We use the date of birth to check age without storing it.

OpenStreetMap Privacy Policy

New-area suggestions use coordinates of public basic store listings to identify clusters for operator review. Approved clusters can appear in the public area directory. Only public store coordinates are used for this step.

Optional alerts, waitlists and referrals

If you choose alerts for an area or store, we retain the selection, browser push subscription and your consent and preferences. Area alerts can include a weekly summary. You can turn alerts off in settings. A request for offers at a particular store is tied to your account so you can undo it and receive the first-offer alert. The store sees eligible totals. Participant identities stay private.

When you follow or share a referral, we use referral codes and qualifying signup, approval, publication or visit records to attribute the referral and check rewards. Abuse controls use account or browser signals to limit repeat participation.

At participating stores, an eligible verified visit links the account, store, reservation and date to the loyalty stamp and progress. A reward is visible only to the customer who earned it and is available for 30 days. No-shows, the master account and example stores do not earn stamps.

Store applications and staff access

We use your login identifier and store contact details, address and any provided store coordinates to review your application and manage access. Public listings may show approved store locations. For ownership claims, we process your business registration number, registered name, address and certificate. When National Tax Service verification is enabled, the owner’s name and opening date are used for that check. We retain the outcome and the reasons for any match or mismatch.

Registration documents are kept privately. Files are deleted after manual approval or rejection. After automatic approval, they are deleted when reviewed or seven days after approval, whichever is earlier. Backup copies may remain until the applicable backup expires.

Before sign-in, the offer preview draft is stored in your own browser for up to seven days. The preview stays on that browser until you submit information through an application or publishing step. Staff invite records include the link verification value, expiry, relevant accounts and times of issue, acceptance and revocation. Publication records identify who published and when. If enabled, repeat reminders use the existing offer, scheduled day and time, and your notification choice. The store confirms publication. A request to prepare an offer includes the request text, the draft and the approval history.

When the optional certificate route and National Tax Service verification are enabled, an eligible ownership claim may be approved without a certificate attachment. A draft you explicitly save during review is stored privately with the application. After publication, the draft text is cleared. The published offer and publication record remain.

Cookies, abuse controls and measurement

Cookies support sign-in and reservations. We retain records of signed-in offer views to report store performance. Other offer and funnel counts are aggregated by time, source or first display language without storing individual identifiers in those totals. The first source and campaign values are remembered in a browser cookie for 30 days and linked to applicable signups or store applications. The first-display language cookie can last up to a year, and the separate language cookie for operational metrics can last up to 30 days.

To understand how people use the service, we count visits anonymously by day without analytics cookies, keep each day's visit records separate, and omit raw IP addresses and full User-Agent strings from stored data.

We use account and derived browser identifiers to limit duplicate reservations, repeated verification attempts and abuse of waitlists or invitations, and to prevent bookings at a store from its registered browser. The browser identifier in a reservation is cleared after the seven-day check. Participation-limit identifiers last 24 hours and visit verification limits are applied in hourly windows. Operational and publication reports may show grouped counts, including estimated audiences, only when the applicable thresholds are met.

If Meta Pixel is configured, Meta receives supported consumer and merchant-landing events for page views, completed consumer registrations and completed store applications or claims. The requests omit account data, contact details, store names and visited URLs. Meta can receive the connection IP and browser information. Choose the advertising measurement control in settings or the footer to stop future Pixel requests from this browser.

The master account uses a password hash and a session with a selected view. Rate limits use hashed IP addresses and failed-attempt timestamps. Its example store and account practice activity are excluded from actual operating metrics.

The public store check uses store names and addresses to find public listings. To enforce the search rate limit, it records an HMAC of the connecting IP and a search timestamp in a rolling 60-second window. Old entries are cleared during subsequent searches. Area opening progress and weekly success cards use only eligible aggregate counts, such as publishing stores and visits. Thresholds apply, and the master account and example stores are excluded.

Test payments

Test payments are off by default. When enabled, PortOne’s checkout opens only after the service verifies the test channel. PortOne receives the test payment ID, product name, amount and currency, store and channel identifiers, and the return URL for checkout, verification or cancellation as applicable. Card information is entered in the PortOne window.

We record the purchasing account and store, order and product, amount, versions of the purchase and refund terms accepted, payment status and time, and any receipt link. We also retain refund requests, reasons, actors, status and timestamps, and records of credits or subscription periods.

Retention and features in development

We keep account, reservation, service activity and store review records for pilot operation. The operator still needs to confirm item-by-item retention and deletion periods.

Multi-store access is planned.

Planned offer photos would be re-encoded without EXIF such as GPS coordinates. Reports, hiding, restoration or deletion would produce moderation records. An optional public review would require a verified visit and would show a generic “Visiting customer” label and date. Reviews would earn no reward. Planned error and performance monitoring would sample and clean browser data, remove URL queries and mask contact or booking-code patterns. Server-side route and performance summaries would be kept for up to 14 days.

Automated service checks can use the master account and example store when configured. If a check fails, incident reports and screenshots are prepared with sensitive information removed. Example activity stays outside actual metrics.

Your rights and how to make a request

In Settings, open Personal data to download your account, reservation, favorite, stamp, review, and inquiry data as JSON once per Korea Standard Time day. You can also turn off notifications on all devices or confirm account closure in two steps.

Finish or cancel active reservations before closing the account. If you run a store, review which ownership links will be released and resolve that store’s active reservations. Closing the account removes the connected personal data, withdraws location consent, and invalidates earlier sign-ins. A security digest is kept for up to 30 days to prevent replay of those sessions.

When law requires a record to be kept, we keep only the necessary data in separate storage and delete it after the applicable period. For access, correction, deletion, processing restrictions or help with consent, contact official support for a secure way to verify your identity. Keep passwords, ID images, registration documents and visit codes out of direct messages.

Official Instagram support

AI assistant connection (pending legal review)

The integration processes only the location coordinates needed for nearby searches and the response language as user data. We discard both after processing each request and keep neither in databases, logs or caches. See the AI assistant provider’s privacy notice for its data practices.