Merchant Lens Privacy Policy

Effective date: October 26, 2026
Applies to Merchant Lens version 0.3.3.

Merchant Lens displays bank-reported merchant category codes (MCCs) and category descriptions beside transactions on supported Capital One and Rogers Bank websites. It is an independent project and is not affiliated with those banks.

Information processed by the extension

Merchant Lens runs page scripts only on myaccounts.capitalone.com and selfserve.rogersbank.com. It checks the current page address and existing transaction-response URLs to identify supported pages and responses. It reads copies of transaction responses already requested by the bank website and the transaction text displayed on the page.

These response bodies may contain additional personal or financial fields. The extension extracts the following subset into temporary matching caches: bank identifier, merchant name, amount, transaction and posting dates, transaction status, MCC, merchant type, category description, card last-four digits, and, for Rogers Bank, cardholder name when supplied. It does not retain full card numbers or account numbers as fields in these transaction caches.

The extension handles pointer position, hover/focus events, scrolling and shortcut key events to display, position, dismiss or toggle tooltips. It does not keep an interaction log, record typed text, or maintain a browsing-history log. It does not read authentication cookies or passwords.

Purpose and local processing

The information is used only to match bank-provided category information to visible transaction rows and provide Merchant Lens's controls and tooltips. The extension makes no additional banking requests and uploads no transaction information to the publisher or another server.

There are no analytics, advertisements, separate Merchant Lens accounts, third-party libraries or remotely hosted application code in this version. The user's bank and browser continue their own normal operations, including banking requests and extension-store updates, under their own policies.

Storage and retention

Transaction-matching metadata is held only in bounded caches in the current tab's memory, up to 5,000 records in each cache. Records have a 30-minute expiry policy, measured from capture or recapture. Cleanup runs periodically while the page executes and during relevant interactions. Browser suspension can delay memory cleanup; this is not a promise of forensic memory erasure at an exact time.

The caches clear on page unload or when the extension detects leaving the supported transaction route. Closing the tab ends the page context. Merchant Lens does not write transaction data to extension storage or Chrome's storage.session. Only the enabled/disabled preference is saved in chrome.storage.local so it persists between browser sessions.

Turning tooltips off

The toolbar toggle and keyboard shortcut hide tooltips but leave the temporary transaction observer and MCC cache active. This lets users enable tooltips without refreshing the bank page. To stop the extension from executing, use the browser's extension controls and reload or close already-open bank tabs.

Sharing and limited use

The extension does not sell transaction information or transfer it to third parties. It does not use data for advertising, profiling, determining creditworthiness or lending. Merchant Lens's use of data is limited to the disclosed transaction-category display and associated controls and complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

The capture script runs in the bank page's JavaScript environment and passes matching metadata to the tooltip script within that page. This is not an independently secured banking-data vault or independent verification of a bank's classifications.

Support and your choices

You can disable or remove Merchant Lens through your browser. Removing it removes its saved preference through the browser's normal extension-data handling. You can clear current page caches by closing the bank tab. Browser controls also let you restrict website access.

If you email support, the publisher receives the information you choose to include and uses it to respond. Email is processed through the email provider; support correspondence is separate from the extension's in-memory cache and does not automatically expire after 30 minutes. Please do not email passwords, authentication codes, cookies, full card/account numbers or unredacted transaction logs.

Privacy policy website hosting

This policy website is hosted on Cloudflare Pages. When you visit it, Cloudflare processes ordinary web-request information, such as IP address, browser information, requested URL and request time, to deliver and protect the website. Cloudflare may retain request or security information under its own policies. See Cloudflare's Privacy Policy for more information. This page includes no analytics scripts, advertising, forms or third-party fonts.

Visiting this policy page does not send your banking transactions to the publisher. Merchant Lens does not automatically contact this policy website to transmit transaction data.

Changes and contact

This policy will be updated when Merchant Lens's data practices change. Contact the Merchant Lens publisher at djino.redflagdeals@gmail.com with questions about this policy.