Version transition notice: since 2026-10-26 the server runs in private-record-only mode. The click-to-read and private-record descriptions apply to Chrome extension 0.5.11 or later and the web record features. Automatic reading, automatic saving and failure-diagnostic uploads from versions before 0.5.11 are no longer accepted and receive an update notice, and anonymous reference-rate aggregation and rate recommendations have stopped. Previously aggregated anonymous data no longer exists because it was deleted on the day of collection. Web entries, device imports and reviewed personal saves are never used for anonymous aggregation or AI processing.
Page reading requires both an explicitly listed hotel or booking domain in the Chrome extension and permission under the current site policy. Reading capability includes Expedia, Hotels.com, Hotwire, Orbitz, Travelocity, CheapTickets and Vrbo domains; bundled permission or capability alone does not activate reading. You click on the final rate page to fill a draft, review it and save. Only country and city are normalized from displayed hotel addresses; full addresses are not saved. Site form values, including guest addresses, and payment-card details are not read.
The Chrome extension stores the acknowledged notice version on your device, without sending it to the server. It is removed when the extension is uninstalled. To select campaigns, only the language and searched hotel’s chain and country are sent to the Easy BRG API, without your account, hotel name or stay dates. Campaign images are served by Easy BRG without external advertising tracking pixels. Clicking a campaign link may subject you to the partner’s tracking and cookie policies.
When you type two or more characters into the hotel name field in the Chrome extension, the text you are typing is sent to the Easy BRG API to show official hotel suggestions. Selecting a suggestion fills the hotel and location; it does not save a rate. On save, a hotel name that exactly matches an official hotel alias is stored under the official name, country and city; ambiguous names are kept as entered. A separate entry window receives only the allowed draft fields through a single-use memory handoff valid for up to 30 seconds. Drafts are not written to browser storage or disk. After transfer they remain only in the entry window until saved or closed. Signing out clears the draft.
Guest rate records stay in website IndexedDB or Chrome extension device storage: hotel, location, stay dates, guests, rooms, provider, total, currency, optional terms, a random record ID and creation time. Up to 100 rates are retained for 30 days; expired records are removed on the next storage access. Signing in does not upload them. Choose “Save device records to account” or “Later.” Starting an import binds the record to that account, so another account cannot view or import it. Successful import removes the device rate payload and keeps minimal record/account/server IDs until the original expiry. Moving extension records to the website also requires your action; the original payload is removed only after transfer acknowledgement. Signing out leaves unimported device records on the device. Individual and bulk deletion are available. Delete records after using a shared device. Clearing browser data or uninstalling the extension may remove records.
The server retains record IDs and account bindings to prevent duplicate imports. Account deletion removes the linked account, search, capture, result and payload hash. Only the random record ID remains permanently reserved against reuse by another account, with no personal identifiers or rate content attached.
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
- In version 0.5.11 or later, no page title or content is read before the click. Page reading starts only after a user clicks the Chrome extension on an allowed final rate page. The normalized draft remains local until the user reviews it and presses Save. Guest saves stay on the device; signed-in saves go to the account. Navigation does not save rates. There are no automatic comparison overlays or badges.
- On Manual entry sites, users can enter a new rate in the Chrome extension popup; signed-in users can also select their recent comparisons. For a new comparison, you enter the hotel name, country, city, check-in/out dates, adults, children, and rooms, together with the site, total, and currency. No prior website search is required, and either an official or booking-site rate can be saved first. Manually entered data saved to an account follows the existing search and comparison retention and deletion rules and is excluded from AI and the anonymous price pool. 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. - Click-triggered page reading on official hotel sites runs only when permitted by the chain policy. When page reading is disabled, the extension does not read the page body or title and the server rejects page-derived records. Manual entry mode permits saving conditions entered by the user; Service restricted mode provides no saving within the Chrome extension.
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, sign-in attempts, Chrome extension pairing and AI features, the actual connection IP is used transiently as an in-memory rate-limit key (AI features have a daily per-IP limit) and is not stored in a separate usage-history table.
- AI abuse-prevention counter: a keyed hash of the Google account identifier (not reversible), the date and the call count. It is used only so that deleting the account and signing up again with the same Google account does not reset that day’s AI limit; it contains no email, name or account ID.
- Server access logs: the web and API servers record the connection IP, request time, request path and response code, and browser type. They are used only for security incident and outage response and contain no sign-in email, rates or page content.
- 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. Identical stay, site and rate records reuse the existing record. Restricted-site web entries follow the same lifecycle.
- Anonymous rate-pool data (Article 4 below): kept only for the day of collection, then destroyed
- AI abuse-prevention counter (hash, date, count): deleted automatically 7 days after that date, and kept for that period even after account deletion
- Server access logs: deleted automatically after 90 days. Access records for administrator functions are kept for at least one year under Korea’s Standards for Ensuring the Safety of Personal Information
- 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). The AI abuse-prevention counter remains without any identifier and is deleted automatically after 7 days
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 · Private rate records
Device records remain in the current browser; account rates are provided only to the account owner. New records saved through web entry, device import, or review and save in version 0.5.11 or later do not contribute to an anonymous price pool or shared rate recommendations. Private records retain their existing retention and deletion lifecycle.
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.
| Processor | Entrusted work | Data involved | Location | When and how | Retention basis |
|---|
| Amazon Web Services (AWS) | Web/API server and database hosting | Member, search/comparison, claim, and transaction records the Service collects and stores | South Korea (Seoul region) | Processed over HTTPS during Service use | Retention periods in this policy |
| Anthropic, PBC | AI-assisted rate extraction, comparison explanations, and claim checklist tips | Pattern-extracted amount/date/guest tokens; numeric, date, enum, and closed condition tokens; chain rules and checklist states (no page text, titles, URLs, hotel names, free-text room/meal/ cancellation descriptions, claim bodies, member identifiers, or emails) | United States (cross-border) | Sent over HTTPS when you run an AI-assist feature | Anthropic’s policy and contractual retention terms |
| Google LLC | Google account sign-in (authentication) | Authentication token, email and profile | United States (cross-border) | Sent over HTTPS when you sign in with Google | Google’s policy and contractual retention terms |
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
- Google AdSense is not currently active, and Easy BRG itself does not set advertising or tracking cookies. Before introducing ads, we will disclose the affected pages, providers, data processing and consent choices. Information obtained through the Chrome extension and private comparison records is not used for advertising targeting.
- When you click an ordinary booking link, the supported hotel name or code, dates, guests and room count may be sent to the destination site. The supported scope varies by site and is displayed on screen. This connection does not imply partner endorsement or permission for the Chrome extension to read pages.
- Easy BRG uses ordinary hotel and booking-site links without affiliate revenue tracking identifiers and does not earn commissions from visits or bookings through these links.
- The destination site’s privacy policy governs its use of cookies.
- 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-10-27 The hotel name field in the Chrome extension now autocompletes; the text being typed is sent to the API, and exact official aliases are stored under the official name.
Change notice: 2026-10-26 Ended the legacy compatibility period and switched to private-record-only mode: legacy automatic saves, failure-diagnostic uploads, anonymous reference-rate aggregation and rate recommendations stopped.
Change notice: 2026-10-26 Stated what server access logs record and how long they are kept (90 days; administrator-function access records for at least one year). No new data is collected.
Change notice: 2026-10-24 Added a daily per-IP limit and a keyed-hash counter of the Google account identifier (kept 7 days after deletion) to prevent abuse of AI features. No other processing changed.
Change notice: 2026-10-23 Click-to-read and private-record descriptions now state that they apply to Chrome extension 0.5.11 or later. The data processed and retention periods are unchanged.
Change notice: 2026-10-20 Affiliate revenue links and partner campaigns were discontinued in favour of ordinary links.
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-10-14 Added direct creation of a comparison from manually entered hotel and stay details in the Chrome extension, without a prior website search.
Change notice: 2026-08-24 Added per-site controls for automatic-save triggers, page feedback, and popup links.