Legal reference
Withdrawn draft — never took effectCHROME EXTENSION PRIVACY POLICY
On this page
This policy takes effect when the MoneyRoom browser extension becomes available and applies from the moment you install it. The Extension is not yet available, and nothing described here is collected until you install and use it.
Withdrawn draft — correction: This July 20, 2026 draft never took effect: the Extension was not available while it was published. It has been withdrawn because it does not accurately describe the Extension. In particular, the Extension's shopping script loads on secure (https) web pages, not only on Amazon; it sends a store's domain and page type from any page it recognizes as a store's product, cart or checkout page; on Google Flights and Google Hotels it sends your search's origin and destination (or hotel destination), airport codes and dates; and it never sends a purchase amount you type. The current Chrome Extension Privacy Policy is the only policy for the Extension.
Last Updated: July 20, 2026
MoneyRoom LLC ("MoneyRoom," "we," "us," or "our") respects your privacy. This Chrome Extension Privacy Policy explains what information the MoneyRoom browser extension (the "Extension") collects, how we use it, and the choices you have. It supplements, and does not replace, our general Privacy Policy, available at https://moneyroom.net/privacy?version=2026-08-12, and our Financial Privacy Notice, available at https://moneyroom.net/financial-privacy-notice?version=2026-08-11. The three documents are intended to work together and describe the same practices.
By installing or using the Extension, you agree to this Chrome Extension Privacy Policy.
1. What the Extension Is
The Extension is a companion to the MoneyRoom application for signed-in MoneyRoom members. It helps you decide which of your own credit cards to use: the best-earning card in your wallet at checkout on supported stores, or the best 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.
2. Information the Extension Collects
The Extension collects only what it needs to produce a recommendation:
(a) Sanitized on-page context, on supported pages only
The Extension activates only on supported pages — Amazon product, cart, and checkout pages, and Google Flights and Google Hotels search pages. On those pages it reads a sanitized summary of what is on screen:
- At checkout: the store and the page type (for example, "checkout"), and, if you choose to enter one, an optional purchase amount you type into the Extension's own panel.
- On travel searches: the flight or hotel options currently displayed (such as carriers, fares, dates, cabin, and property names), used to compute the value your cards offer.
This context is sent to your MoneyRoom account solely to compute the recommendation shown in the Extension.
(b) A device pairing token
When you pair the Extension, MoneyRoom creates a device pairing token that links the Extension to your MoneyRoom account. The token is stored locally by the Extension in your browser, is revocable, and expires on its own. It is the only credential the Extension holds — the Extension never sees your MoneyRoom password or your signed-in website session.
The Extension also runs on moneyroom.net solely so the MoneyRoom website can show whether the Extension is installed. On moneyroom.net it writes a version marker for the site to read; it does not read or collect anything from the page.
3. What the Extension Does Not Collect
The Extension does not collect:
- Credit-card numbers, security codes, or expiration dates
- Bank or financial-institution login credentials
- Bank-connection (Plaid) tokens
- Transaction history
- Full page content
- The addresses (URLs) or search terms of pages you visit
- Browsing history
- Screenshots
The Extension does not activate on pages other than the supported pages described above.
4. How We Use Extension Information
We use the information described in Section 2 solely to generate and display the card recommendation and travel value inside the Extension. Your card details live in your MoneyRoom account — not in the Extension — and the recommendation is computed against the cards you have already added there. Extension information is not used for any other purpose.
6. 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.
7. Your Choices
- Unpair anytime. You can revoke the Extension's device pairing token at any time in MoneyRoom Settings (Settings → Browser extension). Revocation takes effect immediately.
- Uninstall anytime. Uninstalling the Extension removes the data it stores locally in your browser.
8. 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.
9. 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-08-12 and our Financial Privacy Notice at https://moneyroom.net/financial-privacy-notice?version=2026-08-11. Your use of the MoneyRoom service, including the Extension, is subject to our Terms and Conditions at https://moneyroom.net/terms?version=2026-08-11.
10. Changes to This Policy
We may update this Chrome Extension Privacy Policy from time to time. If we make material changes, we will update the "Last Updated" date above and provide notice consistent with our general Privacy Policy.
11. Contact Us
MoneyRoom LLC
PO Box 1393, Prescott, AZ 86302, USA
Email: moneyroomtracking@gmail.com
Publication and Change Log
Version displayed: 2026-07-20. Withdrawn draft — never took effect.
Withdrawn draft. This draft never took effect: the Extension was not available while it was published. It does not accurately describe the Extension and is not the policy for the Extension; the correction after its first paragraph names what it got wrong.
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.