CHROME EXTENSION PRIVACY POLICY

1. What the Extension Is

The Extension is a companion to the MoneyRoom application for MoneyRoom members. It helps you decide which of your own credit cards to use: the best-earning card in your wallet on a store's product, cart or checkout page, and the value your cards offer on a Google Flights or Google Hotels search. The Extension requires a MoneyRoom account and is paired to your account from MoneyRoom Settings. Its recommendations are included in MoneyRoom Pro; on a plan without them, the Extension sends no store or travel details.

2. Your Agreement Comes First

When you install the Extension, it opens a page that explains what it reads and sends and asks you to agree before you can pair it with your account. The same explanation is available in the Extension's toolbar popup. Until you agree, the Extension sends nothing to MoneyRoom — not a store, not a trip, and not even a check of your connection. If that explanation changes, the Extension reads nothing on any page and sends nothing to MoneyRoom until you agree to the new version; meanwhile its toolbar icon shows "!" ("MoneyRoom needs your OK to keep working"), and its toolbar popup shows the new explanation and asks you to agree. Choosing "Disconnect & clear data" in the Extension withdraws your agreement, and nothing is sent again until you agree again.

3. What the Extension Reads on Your Device

Before reading any page. Before the Extension's shopping and travel scripts read anything on a page, they ask the Extension's own background process whether you have agreed to the Extension's current explanation (Section 2), whether MoneyRoom is paused and whether that site is snoozed. This question stays inside your browser. If you have not agreed yet, MoneyRoom is paused, the site is snoozed, or no answer comes back, they read nothing from the page and send nothing. A page restored with the browser's back or forward button asks again before anything is read.

Store pages. The Extension's shopping script loads on secure (https) web pages so it can recognize store pages. It checks each page on your device only, using the page's web address, its product and checkout markup, its buttons and form labels, and — to recognize bill-payment pages — some of its headings and visible wording. The shopping script does not read what you type into a website's forms. It does not run on moneyroom.net or on Google Flights and Google Hotels pages at www.google.com/travel.

Pages the Extension skips. The Extension skips a list of major bank, card-issuer, brokerage, payment and health-insurance websites, and every website whose address ends in .gov or .mil. It also skips pages it recognizes as bill-payment pages — for example, a hospital's or health system's, a utility's, a bank's or credit union's, or a loan or mortgage servicer's payment page. On a page it skips, the Extension shows nothing and sends nothing; it reads the page only as far as needed to recognize that it should skip it.

Google Flights and Google Hotels. On Google Flights and Google Hotels pages at www.google.com/travel, a separate travel script reads the search and the results Google shows so it can match them with your cards. While the page stays open, the travel script also remembers, in that page's own memory, the searches it has accepted there with the results they were read over — for flights, up to eight such searches, each with its trip, dates, cabin, number of travellers and bags selection and the labels of its first eight results; for hotels, the latest such search, with its destination, dates and search text and the names and prices of its first eight listings — so that it never pairs a changed search with results Google is still showing from the previous search. This memory is never sent and never written to storage, and it is gone when the page is closed or reloaded, or when your browser discards the page after you leave it.

On the Google Flights home page and on Explore, before you choose a flight, the travel script reads only where Google's search form or destination list is on the page, to place MoneyRoom's card there; it reads nothing else on those pages and sends nothing from them.

moneyroom.net. The Extension also runs on moneyroom.net solely so the MoneyRoom website can show whether the Extension is installed. On moneyroom.net it only writes a version marker for the site to read; it reads nothing from the page and sends nothing, whether or not MoneyRoom is paused.

What stays in your browser. The Extension's background process learns each page's site domain from Chrome, which reports the origin of every page that asks it a question; it uses that domain to answer whether the page is paused or snoozed and to accept messages only from the page they claim to come from. Apart from the store domains you choose to snooze, it keeps page information only for each open tab: the records below, in your browser's session storage, and a copy of the tab's latest Google Flights or Google Hotels result, in its own memory (described after them):

• the store domain of the last page in that tab it recognized as a store page, or of a page on a store you snoozed (so the popup can offer to snooze that store or turn the snooze off);
• for a page that shows or has shown MoneyRoom's panel or card, on the page or, when the page blocks it, in the toolbar popup: that page's domain and any result MoneyRoom returned; and
• for a Google Flights or Google Hotels page for which MoneyRoom returned a result: the search and result details sent from the page (Section 4(b)), the result MoneyRoom returned, and details read from the page that are never sent: the departure date of a flight search, the destination and check-in and check-out dates of a hotel search, the airline names Google shows for up to eight results, which result is Google's first row, and the number of travellers Google's prices are for.

The panel, card and Google Flights and Google Hotels records are removed when the tab moves to another page or closes. The store record is replaced when the tab shows another such page, and removed when the tab closes or when the popup finds that the tab no longer shows that store. All of these records are removed when you pause MoneyRoom or choose "Disconnect & clear data", and your browser discards its session storage when it closes. These records never leave your browser.

The background process also keeps, in its own memory and never in storage, the latest Google Flights or Google Hotels result it delivered to each tab together with the request it answered — the search and result details read from the page, including the departure date of a flight search and the destination and dates of a hotel search, which are never sent — so that it can answer an identical request from the same page within 12 seconds without asking MoneyRoom for that result again. A result that involves a credit on one of your cards is never kept this way. The copy is used only within 12 seconds of the answer, but it can stay in that memory, unused, until the tab's next result replaces it, the tab closes, you pause MoneyRoom, the pairing changes (including "Disconnect" and "Disconnect & clear data") or Chrome stops the Extension's background process, whichever comes first. It never leaves your browser.

The background process also keeps, in its own memory and never in storage, MoneyRoom's latest answer about your best card for flights (Section 4(b)), so that the Google Flights home page and Explore do not ask again on every visit. It is used only until the answer's own expiry, at most 15 minutes, and only while the same pairing stands; it is removed when you pause MoneyRoom or the pairing changes (including "Disconnect" and "Disconnect & clear data"), and otherwise stays, unused, until the next such answer replaces it or Chrome stops the Extension's background process. It never leaves your browser.

4. What the Extension Sends to MoneyRoom

The Extension sends information only to MoneyRoom, over an encrypted (HTTPS) connection, only after you have agreed (Section 2), and — apart from the requests you start in its popup — only while MoneyRoom is not paused (Section 10). Store and travel details are sent only when the Extension is paired with an account whose plan includes the Extension's recommendations, such as MoneyRoom Pro. The store and travel requests also carry version numbers for the Extension's request format and page-reading logic, and a Google Hotels request can also name the optional result details the Extension can show, such as your hotel status (Section 7).

(a) On store pages

When the Extension recognizes a page as a store's product, cart or checkout page, it sends:

• The store's domain (for example, target.com) — never the page's full web address, its path or its search terms;
• When the store's address puts one of the words shop, store, merch, gear, gift, gifts or shopping in front of its domain (as in shop.hulu.com), that one word, so MoneyRoom can tell a merchandise store from the streaming or subscription service it belongs to;
• The page type (product, cart or checkout); and
• A spending category, if you pick one in the Extension's panel.

On cart and checkout pages, the Extension's panel opens by itself and sends these details as the page loads; if the store's own page then removes the panel, the Extension puts it back, up to three times for the same page address, and each time sends these details again unless you closed the panel on that page. On product pages, it sends them only when you open the panel. It sends them for any page it recognizes as a store page, including stores MoneyRoom has no specific information about. A purchase amount you type into the Extension's panel stays in the Extension and is never sent.

(b) On Google Flights and Google Hotels

When search results load, the Extension sends:

• For flights: the origin and destination as Google shows them (for example, city names), the airport codes when Google shows them, and the return date of a round trip — never the departure date.
• For hotels: no search details — not the destination and not the check-in or check-out dates.
• For up to eight of the results shown: for flights, the fare and its currency, the airline code, the cabin and any layover airport codes; for hotels, the property name, the hotel brand when the Extension recognizes it, the total price and its currency, the number of nights when shown, and whether the listing is a vacation rental. Each of these results carries a label the Extension numbers itself (such as "offer-1").
• For all results shown (up to 64 distinct combinations): for flights, only the airline code and any layover airport codes; for hotels, only the hotel brand and whether the listing is a vacation rental.

The Extension sends these details again, for the results then on screen, when a request for them fails without being refused (up to three more times for the same page address, 5, 15 and 45 seconds after each failure, never sooner than MoneyRoom asks it to wait; results that load during such a wait are sent when it ends), when a display-settings answer lets its card return to the page after a failed check (Section 4(c)), and when, with the page open, you agree, pair this browser or turn pause off, or the page is restored with the back or forward button.

The Extension does not send the web address of the Google page.

On the Google Flights home page and on Explore, before you choose a flight, the Extension asks MoneyRoom for your best card for flights booked directly with an airline. That request sends the Extension's pairing token and that it is asking about flights — no page details, no search and no results. MoneyRoom answers with that card's nickname, its last four digits when MoneyRoom has them, and its earn rate on airfare, which the Extension shows in its card within the Google page.

(c) Connection and display-settings checks

On every plan, once you have agreed and paired, and while MoneyRoom is not paused, the Extension checks your MoneyRoom connection and plan when you open its toolbar popup, when it recognizes a store page (and again when it puts back a panel the store removed, after a store request fails and after this browser is paired), each time it asks about Google Flights or Google Hotels results, and each time it asks for your best card for flights on the Google Flights home page or Explore (Section 4(b)). On Google Flights and Google Hotels it also asks MoneyRoom how to display its results, including before it asks for your best card for flights, and repeats that request about every 30 seconds while its card is shown within the Google page. If that request fails or gets no answer, the card moves to the toolbar popup, and while it waits there the Extension asks again after 5 seconds, then after 10 and 20 more seconds, and then about every 30 seconds, only while the tab is visible; it stops when MoneyRoom answers (when the answer lets the card return to the page, the Extension asks again about the results on screen, Section 4(b)), when MoneyRoom refuses the request, when the results change or the card expires, when you pause MoneyRoom or withdraw your agreement, when this browser is paired again, or when you leave or close the page. These checks send the Extension's pairing token but no page details.

When you open the popup, or finish pairing, the popup's connection check also asks MoneyRoom for the email address of the account this browser is connected to; only the popup's check asks for it. MoneyRoom reads that email from its sign-in service for that request only and returns it when it can, and the Extension shows it in the popup without storing it.

(d) Pairing and your device record

To pair, you create a single-use pairing code in MoneyRoom Settings, which expires after five minutes, and enter it in the Extension. The Extension sends the code and a fixed label ("Chrome extension") to MoneyRoom, which returns a device pairing token. The token links the Extension to your MoneyRoom account and is the only credential the Extension holds — the Extension never sees your MoneyRoom password or your signed-in website session. The Extension keeps the token in its own storage in your browser, which websites and the scripts the Extension runs on web pages cannot read, and sends it only to MoneyRoom, with the requests described in this section and with the requests that end a pairing (Section 10). The pairing lasts through browser restarts and Extension updates until you remove it (Section 10) or it expires 180 days after you paired.

MoneyRoom keeps a record for each paired browser: its label, when it was paired, when it was last used (updated at most every five minutes), when it expires and, if you remove it, when. MoneyRoom stores pairing codes and pairing tokens only as one-way hashes, never the code or token itself.

5. What the Extension Does Not Collect

The Extension does not collect:

• Full web addresses (URLs), page paths or search queries, other than the Google Flights and Google Hotels search details listed in Section 4(b)
• Page content, other than the specific details listed in Section 4
• The address of any page that is not a store page (Section 4(a)) or a Google Flights or Google Hotels results page — nothing is sent from those pages, not even the domain
• Card numbers, security codes, expiration dates, or anything else you type into a store's checkout or payment forms
• A purchase amount you type into the Extension's panel
• Bank or financial-institution login credentials
• Bank-connection (Plaid) tokens
• Transaction history
• Screenshots

6. What MoneyRoom Keeps

MoneyRoom uses the store and travel details it receives only to calculate the result it sends back to the Extension. It does not save them to your account or to any other MoneyRoom database, and it does not write them to its logs; our error reports never include the content of a request. MoneyRoom therefore does not keep a record of the stores or trips you look at.

MoneyRoom does keep:

• Your paired-browser records (Section 4(d)), for as long as your account exists. A removed or expired pairing stays listed as such in Settings. These records are deleted when you delete your account.
• A record of each pairing code you create: the code's one-way hash, when it was created, when it expires, when it was used and which paired browser used it. Each record is deleted when you create a new code after it has expired, or when you delete your account.
• Short-lived abuse-prevention records. For requests it answers, MoneyRoom records the account (once the browser is paired), your IP address, the kind of request (for example, a store recommendation) and its time — never the store or the trip. These records are deleted once they are about a minute old, the next time MoneyRoom checks a request against its limits.
• Ordinary hosting and security logs and error reports, as described in our general Privacy Policy. The Extension sends store and travel details in the body of its requests, never in the web address it calls.

7. How We Use Extension Information

We use the details the Extension sends only to calculate the card recommendation or travel value the Extension shows you, using the cards you have added to your MoneyRoom account. For a store page, MoneyRoom may also use the store's domain to check whether a statement credit on one of your cards may apply at that store. When one may, the Extension names the card and the credit, says the credit may apply, and names what it does not cover at that store; this never changes which card MoneyRoom recommends. Your MoneyRoom account is the system of record for your cards. We use pairing and device records, connection checks and abuse-prevention records to authenticate requests, manage access and protect the service. For a Google Hotels listing whose hotel chain matches a hotel elite status you entered in MoneyRoom Settings, the results the Extension receives can also include that status, labelled as what you told MoneyRoom (MoneyRoom does not verify it), and, where the program's published terms give your tier them, its bonus on base points and the other benefits those terms guarantee your tier, each with its published condition, for stays booked directly with the chain; the Extension shows the status only inside its own card, never beside Google's listing, and never receives an airline status. The Extension receives card and benefit facts, and any such status, to display its results and keeps them in your browser's session storage for that tab until the tab moves to another page or closes, and keeps a copy of the tab's latest Google Flights or Google Hotels result that involves no credit on your cards in its own memory, as described in Section 3. Each result carries a 15-minute freshness period: when it ends, the Extension stops showing the result and withdraws it from the panel or card that showed it. That period is not an account-data deletion deadline.

8. How We Share Extension Information

We do not sell your personal information, and we do not share it with third parties for advertising. Information the Extension sends goes only to MoneyRoom's service, which our hosting and database providers operate for us as described in our general Privacy Policy. Calculating a result does not involve any other outside service. We may disclose information only where required by law, or to protect against fraud, abuse, or security threats to MoneyRoom or its users, consistent with our general Privacy Policy.

9. What We Never Do

Information collected by the Extension is never:

• Used or transferred for personalized advertising;
• Sold to data brokers; or
• Used to determine creditworthiness or for lending purposes.

10. Your Choices

• Do not agree. If you do not agree in the Extension, it sends nothing to MoneyRoom.
• Pause MoneyRoom everywhere. The switch is in the Extension's popup, in the popup's view for a browser paired with your MoneyRoom account, on every plan (when the popup opens on a recommendation for the current page, its "Account & settings" button leads to that view); while MoneyRoom is paused, the popup shows the switch to turn pause off. While MoneyRoom is paused, the Extension reads nothing from store pages or from Google Flights and Google Hotels pages, and sends nothing from them (Section 3). Opening the Extension's popup while MoneyRoom is paused sends nothing. While MoneyRoom is paused, the Extension refuses every request to MoneyRoom except the ones you start in its popup: pairing it with your account, and disconnecting it ("Disconnect" or "Disconnect & clear data").
• Snooze a store. When the current tab shows a page the Extension recognized as a store page, or a page on a store you snoozed, the same popup view offers a switch to snooze that store's domain or turn the snooze off. Snoozing covers every page on the domain the switch names, so on a shared shop-hosting domain it covers every shop there; the switch says so for the shared hosting domains the Extension recognizes. google.com is never offered. While a store is snoozed, the Extension reads nothing from that store's pages and sends nothing from them. The Extension keeps up to 500 snoozed store domains in its own storage in your browser, until you turn the snooze off, choose "Disconnect & clear data", or uninstall the Extension.
• Disconnect in the Extension. "Disconnect" in the Extension's popup asks MoneyRoom to end this browser's pairing and deletes the Extension's copy of the pairing token. "Disconnect & clear data" also withdraws your agreement, turns pause off, clears your snoozed stores and clears the Extension's other settings. Before it carries out a "Disconnect" or "Disconnect & clear data", the Extension records which one it is starting, with a one-way hash of the pairing token it is removing (never the token itself), in its own storage in your browser, where it survives a browser restart, in its session storage and in its background process's memory, and it removes that record when the disconnect finishes. If a disconnect does not finish, the record stays. While that record stands, the popup shows "Disconnect didn't finish" (or, when the pairing is gone but the data was not cleared, "Disconnected, but data wasn't cleared") with "Try again", MoneyRoom shows no card picks on any page, and the Extension sends no request with that token except a request to end its pairing. The record is removed when a retry finishes, when a new pairing replaces the one it concerns, or, for "Disconnect", once that pairing is gone.
• Remove a browser in MoneyRoom Settings. You can remove a paired browser at any time under Settings → Browser Extension → Paired browsers. The removal takes effect on that browser's next request to MoneyRoom: MoneyRoom refuses the request, and the Extension deletes its stored token, withdraws MoneyRoom's panels and cards and deletes its Google Flights and Google Hotels records. Removal does not remotely erase anything: until that next request, the browser can still show what it already has.
• Signing out or changing your password does not disconnect the Extension. Signing out of moneyroom.net, or changing or resetting your MoneyRoom password, leaves a paired browser connected. To disconnect it, remove it in Settings or disconnect it in the Extension.
• Pairings expire. A pairing ends 180 days after you created it; pair again to keep using the Extension.
• Uninstall anytime. Uninstalling the Extension removes the data it stores in your browser, including its copy of the pairing token. It does not end the pairing on MoneyRoom's side: the browser stays listed in Settings, as active until you remove it or its pairing expires, and after that as disconnected or expired.
• Delete your account. Deleting your MoneyRoom account deletes your paired-browser records, so a paired Extension can no longer reach your account.

11. Chrome Web Store Limited Use

MoneyRoom's use and transfer to any other app of information received from Google APIs and the Extension adheres to the Chrome Web Store User Data Policy, available at https://developer.chrome.com/docs/webstore/program-policies/user-data-faq, including its Limited Use requirements.

12. Relationship to Our Other Policies

This Chrome Extension Privacy Policy governs the Extension specifically. Information in your MoneyRoom account — including the cards you add and any financial accounts you link — is governed by our general Privacy Policy at https://moneyroom.net/privacy?version=2026-10-07 and our Financial Privacy Notice at https://moneyroom.net/financial-privacy-notice?version=2026-10-07. Your use of the MoneyRoom service, including the Extension, is subject to our Terms and Conditions at https://moneyroom.net/terms?version=2026-10-07.

13. Changes to This Policy

We may update this Chrome Extension Privacy Policy from time to time. When the explanation shown in the Extension changes, the Extension asks you to agree again before it reads a page or sends anything. If we make material changes, we will update the "Last Updated" date above and provide notice consistent with our general Privacy Policy.

14. Contact Us

MoneyRoom LLC
PO Box 1393, Prescott, AZ 86302, USA
Email: moneyroomtracking@gmail.com

Publication and Change Log

Version displayed: 2026-10-07. Extension policy — takes effect when the Extension is available in the Chrome Web Store.

When this policy applies. This policy takes effect when the Extension becomes available in the Chrome Web Store. The Extension is not available there yet. Nothing described here is collected unless you install the Extension and agree in it. Its effect follows the Extension's availability in the Chrome Web Store, not the effective date of our Terms or Privacy Policy.

What changed in this document: Rewritten on September 23, 2026, before the Extension became available, to describe what it actually does: its shopping script checks secure web pages on your device; it sends a recognized store's domain and page type (cart and checkout pages automatically, product pages when you open the panel) and Google Flights and Google Hotels search details and results; a purchase amount you type is never sent; nothing is sent before you agree in the Extension; bill-payment and sensitive sites are skipped; connection checks send no page details; pairing lasts until you remove it or 180 days pass, and a password change does not disconnect it; and MoneyRoom keeps no record of the stores or trips you look at. The policy's effect now follows the Extension's availability in the Chrome Web Store instead of a date, and the July 20, 2026 draft is withdrawn. Revised on September 24, 2026, also before the Extension became available, to describe pausing MoneyRoom and snoozing a store on every plan, what the Extension's background process learns and keeps in your browser, the account email the popup shows, the pairing-code records MoneyRoom keeps, and the possible check of a store's domain for a card credit and what the Extension shows when one may apply, and to state more precisely where the shopping script does not run, which requests carry version numbers, what "Disconnect & clear data" clears and how an uninstalled browser stays listed. Revised on September 25, 2026, also before the Extension became available, to name the one storefront word (such as shop in shop.hulu.com) the Extension may send with a store's domain, and to say that it no longer sends a flight search's departure date or a hotel search's destination and dates. Revised on September 29, 2026, also before the Extension became available, to state that the Extension reads nothing on a page until you have agreed and shows "!" on its toolbar icon when its explanation changes; to state precisely in Section 5 that it collects nothing from pages that are not store pages or Google Flights or Google Hotels results, since the domain of a recognized store page is sent; and to describe when store and travel details are sent again, the repeated display-settings checks while its card waits in the toolbar, the copy of a travel result kept in its memory, what the travel script remembers while a page is open, and the record kept when a disconnect does not finish. Revised again on September 29, 2026, also before the Extension became available, to say that for a Google Hotels listing whose hotel chain matches a hotel elite status you entered in MoneyRoom Settings the Extension can receive that status, labelled as what you told MoneyRoom, and shows it only inside its own card, and that a Google Hotels request can name the optional result details the Extension can show. Revised on October 6, 2026, also before the Extension became available, to say that the hotel status the Extension can receive may also list, each with its published condition, the other benefits the program's terms guarantee that tier, not only its bonus on base points. Revised on October 10, 2026, also before the Extension became available, to describe its best card for flights on the Google Flights home page and Explore: that there the travel script reads only where Google's search form or destination list is; that the request sends the pairing token and that it is asking about flights, and nothing about the page or your trip; what MoneyRoom answers and how long the Extension keeps that answer in memory; and that the connection and display-settings checks also run before it.

Earlier draft. A draft of this policy dated July 20, 2026 (version 2026-07-20) never took effect, because the Extension was not available while it was published. It was withdrawn because it did not accurately describe the Extension, and it is not the policy for the Extension. It remains readable, labelled as withdrawn. The text first published under version 2026-10-07 (revised September 6, 2026) never took effect either; this rewrite replaced it before the Extension became available.

Revision dates, effective dates, and consent versions have separate meanings. Updating a revision date alone does not request new consent.