Privacy Policy

Article 1 · Personal data we collect

The Service collects and uses the following items.

a. Sign-up and authentication (Google sign-in)

• Google account identifier, email address, name (if set on your Google account), internal member identifier, sign-in session token
• Date of birth: processed once, at sign-up or on your first sign-in after a change to the minimum-age requirement, solely to confirm you are 18 or older. Only users aged 18 or older may register. Your date of birth is never stored or logged; only the over-18 confirmation result is kept on your account.
• Internal plan status and expiry date (retained for a future policy transition while all features are currently free)

b. While using rate comparison

• Search conditions: hotel name, city, country, check-in/check-out dates, guest count, room count
• Hotel autocomplete, web hotel search, and official and supported booking-site link generation are available without signing in. A random search token and the search conditions are retained for up to 7 days solely to generate those links, without being connected to a member identifier, rates, comparison candidates, recent searches, favorites, or claims.
• Compared rates: price, currency, whether taxes are included, room type, meal/cancellation terms, the booking site address (domain only — no paths or query strings), and capture time
• Depending on the site policy, automatic saving may start when the user reaches a supported checkout stage or only when the user opens the Chrome extension popup. On click-triggered sites, Easy BRG does not read or save the page title, page content, or booking details before the popup is opened. Site policy may also suppress page overlays, badges, and comparison links; this does not add any data fields.
• On Manual entry sites, you use the Chrome extension popup to select a recent comparison and site, then enter the total and currency you checked. Manual entry does not read the page title or content.
• On Service restricted sites, before authentication the extension may transiently derive only the hostname locally for a public policy decision and immediately discard it. It does not read or store the page title, content, or booking data. Only search and rate conditions entered on the Easy BRG website are stored: the existing hotel is read-only, while check-in/out, adults, children, rooms, provider, total, currency, optional room, and meal, cancellation, payment, and tax conditions are editable. An optional free-cancellation deadline uses the hotel's local time and cannot be later than check-in. The current page URL and hostname are not included in the web-entry request and are not stored. The server derives and stores the selected provider's canonical domain as source_hostname. The web-entry request also excludes page title, HTML, DOM, cookies, credentials, card data, form entries, screenshots, and browsing history.
• Booking conditions on official hotel sites are processed by the Chrome extension only when that hotel chain’s permission status is active. For chains that are inactive in the latest Chrome extension, the extension does not read the page body or title, and the server also refuses to store booking conditions for that chain.

c. Payment information

• The Service does not currently accept user payments and therefore does not collect new order or payment information.
• If paid features are introduced later, the data collected, purpose, payment processor, and retention period will be added to this policy before payment begins.

d. Automatically generated data

• Service usage records (search, comparison, and claim history), access times
• For abuse prevention on public hotel autocomplete and search, the actual connection IP is used transiently as an in-memory rate-limit key and is not stored in a separate usage-history table.
• Automatic-capture failure diagnostics: supported-site domain, failure reason code, whether key fields were detected, Chrome extension version, occurrence count, and last occurrence time (no page address, hotel name, or page content). Identical site/reason pairs are aggregated, with no more than 20 distinct combinations recorded per account per day.

Article 2 · Why we process personal data

• Identifying and authenticating members and keeping you signed in
• One-time confirmation, at sign-up or on first sign-in after a minimum-age change, that you may use the Service (18 or older), and management of that confirmation result
• Hotel rate comparison (Best Rate Guarantee, BRG) and result guidance
• Authorized operators’ account support and monitoring of automatic-comparison operations
• Service improvement and abuse prevention (such as rate limiting)

Article 3 · Retention periods

In principle, personal data is destroyed without delay once its processing purpose is fulfilled. The Service’s automatic retention and deletion policy is as follows.

• Sign-in session tokens: expire and are deleted after 7 days of inactivity, or 30 days at most
• Date of birth: discarded immediately after the over-18 check; never stored
• Over-18 confirmation result: kept with your account until you delete the account
• The Chrome extension’s Google authentication token for age verification: kept in Chrome session storage for up to 5 minutes while waiting for date-of-birth input, and deleted on completion, failure, sign-out, expiry, or browser close
• Search history: the most recent 100 searches per account (older entries are deleted automatically). Searches and comparisons whose check-in date has passed are deleted automatically at sign-in (linked claim records are kept for statistics and record integrity). Of these, direct web searches with no automatic capture or claim attached keep only the 3 most recent, and search conditions are not stored separately in cookies or browser storage.
• Anonymous search context: only a random token and search conditions, deleted automatically after no more than 7 days and never stored as account search history.
• Comparison (capture) history: up to 20 per search; older entries are deleted automatically. Saving the same site again updates its existing row. Restricted-site web entries follow the same lifecycle.
• Anonymous rate-pool data (Article 4 below): kept only for the day of collection, then destroyed
• On account deletion: related personal data, including the Google account identifier, is destroyed and operator identifiers in audit history are anonymized (transaction records that must be retained by law are kept separately for the required period)

Transaction records that must be retained under the Act on Consumer Protection in Electronic Commerce and related statutes are kept for the periods below.

• Records on contracts and withdrawal of offers: 5 years
• Records on payment and supply of goods or services: 5 years
• Records on consumer complaints and dispute resolution: 3 years
• Completed, failed, or cancelled transactions past the 5-year retention period, and their linked payment events, are destroyed automatically by a scheduled batch job

Article 4 · Anonymous rate statistics

The Service may anonymously aggregate rates confirmed by multiple users and show them as a “suggestion” (for reference) to other users searching the same conditions. This aggregation stores nothing that could identify who collected the rate (no member identifier, no page address), and a rate is included only when the official and candidate rates’ dates, guest count, room count, and room type are all confirmed to match, with no explicit mismatch in meal, cancellation, or tax terms. Only Automatic save rates are eligible; Manual entry and Service restricted-site web entries never contribute. The data is used only on the day of collection and then destroyed.

Article 5 · Third-party provision

The Service does not provide personal data to third parties without your consent, except where required by law or upon a lawful request from an investigative authority. (For processing entrusted to service providers, see Article 6.)

Article 6 · Entrusted processing and cross-border transfers

The Service entrusts the following processing to provide the Service.

Cross-border transfers — personal data leaves Korea only for AI processing (Anthropic, US) and Google sign-in (US). Closed tokens and rule data sent to the AI are not stored separately by the Service and are discarded after processing; page text, titles, URLs, hotel names, free-text room/meal/ cancellation descriptions, claim bodies, screenshots, raw HTML, cookies, passwords, and card details are never sent. If you do not wish to use Google sign-in, member features are unavailable; if you do not wish to use AI assistance, those assist features are unavailable. Rate comparison and history work without the AI assist features.

Article 7 · Your rights and how to exercise them

• You may request access to, correction or deletion of, or suspension of processing of your data at any time.
• Send requests by email to the privacy officer below; the Service will act without delay (within the statutory period).
• Signing out revokes your sign-in session immediately.
• Deleting your account from the account page immediately deletes your account and your search, comparison, and claim history. Transaction records that must be kept by law are retained separately for the required period. If you need help with deletion, contact flowx.system@gmail.com.

Article 8 · How data is destroyed

• Data past its retention period, or whose purpose is fulfilled, is destroyed without delay.
• Electronic files: permanently deleted from the database so they cannot be recovered.
• Automatically deleted data (sessions, searches, comparisons, anonymous statistics) is destroyed by the system under the retention policy above.

Article 9 · Security measures

• Sign-in uses Google authentication only, with no passwords — the Service stores no passwords.
• Session tokens are issued from cryptographic randomness and expire on schedule (7 days unused, 30 days maximum).
• All traffic is protected with HTTPS, and access is restricted to allowed origins (domains).
• Authorized operators see masked emails and minimal aggregate data for account support and automatic-comparison operations, and manage per-chain feature permission status. Booking-condition text, payment approval keys, and card details are not visible in the admin screens.

Article 10 · Cookies and similar technologies

• Easy BRG itself does not set advertising or tracking cookies.
• Easy BRG may receive a commission when you visit or book through a link marked “Affiliate link.”
• When you follow an “Affiliate link” to an external site, that destination site may use affiliate identifiers, cookies, or similar technologies under its own privacy and cookie policies.
• To keep you signed in, the Service uses an authentication cookie (brg_session) and a request-forgery protection cookie (brg_csrf). The authentication cookie is httpOnly, so JavaScript cannot read it, and it expires after 30 days at the latest (sooner if unused for 7 days). You stay signed in after closing the browser, so on a shared computer be sure to sign out when finished.
• The Chrome extension does not read or transmit cookies, passwords, payment details, screenshots, or raw HTML.
• Signing out or clearing your browser cookies removes the sign-in data.

Article 11 · What we do not collect

• Screenshots or raw HTML
• Cookies, other sites’ login sessions, or passwords
• Payment card details (never stored on the Service’s servers)
• Full browsing history
• No server-side automatic price crawling or scraping

Article 12 · Privacy officer

• Operator (trade name): UPCODE
• Business registration number: 502-57-00970
• Privacy officer: Heewook Kang
• Contact (email): flowx.system@gmail.com

Article 13 · Remedies for privacy infringement

For counseling or dispute mediation regarding privacy infringement, you may contact the following Korean authorities.

• Personal Information Dispute Mediation Committee (privacy.go.kr / +82-1833-6972)
• KISA Privacy Infringement Report Center (privacy.kisa.or.kr / 118, within Korea)
• Supreme Prosecutors’ Office Cybercrime Division (spo.go.kr / 1301, within Korea), National Police Agency Cyber Bureau (ecrm.police.go.kr / 182, within Korea)

Article 14 · Changes to this policy

This policy may be revised to reflect changes in law or the Service. Revisions and their effective dates will be announced on this page.

Change notice: 2026-08-11 Added notice about affiliate-link commissions and possible destination-site affiliate tracking.

Change notice: 2026-08-18 Added the transient hostname-only policy decision and Easy BRG website entry flow for Service restricted sites.

Change notice: 2026-09-22 Added the all-features-free operation, fair-use limits, search and comparison retention, and aggregated capture-failure rules.

Change notice: 2026-08-24 Added per-site controls for automatic-save triggers, page feedback, and popup links.