Cookie Policy

Scope: this website only

Cookies are small files a site asks your browser to store and send back on later visits. They are a website mechanism, and this policy is about the website you are reading: chasenowsavings.com, including the documentation and changelog.

The Chase Now extension sets no cookies. It does not read or write cookies on merchant sites, it does not carry an identifier across sites, and it does not fingerprint your browser. What it remembers, it remembers through chrome.storage in your own browser profile: five keys in chrome.storage.local that survive a restart — cn.wallet, cn.offers, cn.codes, cn.settings and cn.runs — and four in chrome.storage.session that the browser discards when your browser session ends: cn.run.active, cn.frames, cn.autorun and cn.catalog:<url>, the last being a six-hour cache of the optional catalog URL. The Privacy Policy describes each of them in detail. Declining cookies here has no effect on the extension, and clearing cookies does not erase your wallet.

Where this policy says “cookies” it also covers equivalent browser-storage techniques used for the same purposes, such as localStorage or sessionStorage entries. This site currently uses none of those either: the one cookie in the table below is the whole of it.

The one category we use

Cookie policies usually divide cookies into essential, analytics, preference and advertising buckets. On chasenowsavings.com only the first bucket has anything in it, and it has exactly one cookie in it.

Essential — needed for the site to respect a choice you made: remembering that you answered the cookie notice, so it is not shown again on every page. That is the only cookie this site sets.
Analytics — none. We load no analytics or measurement library, so no analytics cookie exists to accept or decline.
Preference — none. The site has one presentation and no display switches, so there is no display choice to remember.
Advertising, retargeting and social media — none. No ad pixel, no retargeting tag, no social widget, and no data broker receives anything from this site.

This is the complete list as of the date at the top of the page. If we add one, this table changes before it ships.

Name	Purpose	Type	Provider	Retention
`cn_consent`	Records that you answered the cookie notice, and which answer you gave, so it is not shown again on every page. Set only when you click one of its buttons; first-party, path `/`, `SameSite=Lax`, and not sent to anyone.	Essential	chasenowsavings.com (first party)	365 days

Measurement: what we do not run

There is no analytics or measurement product on this site. No Google Analytics property, no tag manager, no product-analytics SDK, no heatmap recorder, no A/B testing script and no advertising pixel. Nothing counts your page views on our behalf, so there is no aggregate measurement data for us to hold, export or be asked to disclose.

The only record that a page was requested at all is the standard server log described in the Privacy Policy — IP address, user agent, URL, timestamp and response status, kept for 30 days for security and debugging, and not tied to any cookie.

If we ever add measurement, it will appear in the table above and be gated behind the notice before it is switched on, and this section will say what it is instead of saying that it does not exist.

The first time you arrive, a notice tells you that the site sets one essential cookie and offers you a choice about it. Nothing is stored before you answer, and your answer is a single click — there is no pre-ticked box and no hidden tab of real toggles, because there is only one cookie to decide about.

To revisit it later, use the Cookie settings link in the footer of every page, which reopens the same notice.

Your answer is recorded in cn_consent for 365 days, after which the notice asks again. Clearing your cookies also clears that record, so the notice will reappear — that is the mechanism working, not a reset of your preference against your wishes. Your answer never restricts access to any part of this site, and no content is gated behind it.

Browser-level controls

Independently of anything we offer, your browser can block or delete cookies for this site and every other one. The controls live under Settings in each browser: Privacy and security → Third-party cookies / Site data in Chrome and Edge, Privacy & Security → Cookies and Site Data in Firefox, and Privacy → Manage Website Data in Safari. Most browsers also offer a private or incognito window that discards cookies when you close it.

You can block everything from chasenowsavings.com and the site will still work. Nothing is gated behind a cookie: if cn_consent cannot be stored, the only consequence is that the cookie notice appears again on your next visit.

Browser-level blocking is broader than our notice and takes precedence over it. We make no attempt to work around a browser or privacy extension that blocks cookies or requests.

Do Not Track and Global Privacy Control

Neither signal changes what this site does, because there is nothing for them to switch off. We load no tracker and set no advertising, analytics or preference cookie in any configuration, so a browser sending Sec-GPC: 1 or DNT: 1 already gets the outcome those signals ask for.

Under the CPRA, Global Privacy Control is a valid opt-out of the sale or sharing of personal information. We neither sell nor share personal information, on this site or in the extension, so the signal reinforces a position we already hold rather than changing one.

Neither signal reaches the extension, because the extension has nothing to opt out of: it sends no telemetry and contacts no analytics service in any configuration.

No third-party embeds

A great deal of everyday cookie exposure comes from embedded third-party content rather than from the site you chose to visit. chasenowsavings.com avoids it: fonts and images are served from our own domain, there is no hosted video player, no social share widget, no comment platform, no chat bubble, no tag manager and no content-delivery script from someone else’s origin.

The practical consequence is that no other company can set a cookie or observe a request while you read this page: every request the page makes goes to our own domain.

Links out to the Chrome Web Store are ordinary links: nothing is exchanged until you click one, and from that point Google’s own cookie and privacy terms apply to the page you land on.

Changes to this policy, and contact

We review this inventory whenever we change the site, and at least once a year. If a cookie is added, removed or given a different retention period, the table above and the date at the top are updated at the same time as the change goes live — and if a non-essential cookie is ever introduced, the notice will ask you before it is set.

Questions about cookies, or a discrepancy between this table and what you observe in your browser’s inspector, are genuinely useful to us:

Email: [email protected]
Post: Chase Now Labs, Inc., 2261 Market St #4718, San Francisco, CA 94114, United States

For the wider picture of what we do and do not collect, read the Privacy Policy.

Questions about this document? Write to Chase Now Labs, Inc., 2261 Market St #4718, San Francisco, CA 94114 or email [email protected].