finzest← Back to site

Cookie Policy

Last updated: August 21, 2026

This Policy explains how Finzest uses cookies and similar technologies.

1. What cookies are

Cookies are small text files placed on your device when you visit a website. Similar technologies, such as browser local storage and pixels, work in comparable ways. Session cookies last until you close your browser; persistent cookies and local storage remain between visits so returning tasks like staying signed in are easier.

Cookies set by Finzest are “first-party”; cookies set by others are “third-party.” The following describes every type of cookie served through our Services, the purpose it performs, and, where applicable, your ability to opt out.

2. What we actually set

Essential (always on)

These are strictly necessary to deliver the Service. Without them, you cannot sign in.

  • Firebase Authentication (Google), a secure, HTTP-only session cookie that keeps you signed in.
  • Browser local storage, remembering your cookie choice and your on-device learning progress.

How to refuse: because these are strictly necessary to deliver the Service to you, they cannot be refused.

Performance

We set none. Finzest runs no analytics or site-performance tooling of any kind, including no Google Analytics, no Vercel Analytics or Speed Insights, and no third-party product analytics.

How to refuse: there is nothing to refuse, because we serve none. If we add any, we will update this Policy and offer a choice before they run.

Functional

We set no functional cookies. The preference-style data we keep, meaning your cookie choice and your learning progress, lives in browser local storage on your own device and is listed under Essential above.

How to refuse: as with Performance, there is nothing to refuse, because we serve none. If we add any, we will update this Policy and offer a choice before they run.

Targeted advertising

We run the Meta Pixel, supplied by Meta Platforms, so we can measure which of our adverts actually bring people to Finzest. It is on by default and runs unless you turn it off: switch Targeted Advertising off in “Manage Settings” and save, and the pixel stops loading and no further advertising cookie is set. We run no Google Advertising tag and no other advertising pixel.

While it is on, the Meta Pixel sets two cookies in your browser:

  • _fbp, a Meta-generated browser identifier, used to link an advert click to a later visit. Expires after about 3 months.
  • _fbc, which stores the click identifier (fbclid) from the Meta advert you arrived through. Set only if you arrived from such an advert, and expires after about 3 months.

How to refuse: open “Manage Settings” in the cookie banner, either when it first appears or at any time afterwards via “Your Privacy Choices” in the footer, switch Targeted Advertising off, and choose “Save settings.” Because this category is on by default, doing so is what stops it rather than what prevents it starting. Saving with it off also deletes any _fbp and _fbc cookies already set. You can additionally clear these cookies in your browser settings at any time.

3. Related technologies that are not cookies

We also measure the effectiveness of our advertising using Meta’s Conversions API. Our servers send Meta a limited set of event data: a hashed version of your email address, a hashed internal account identifier, and the fact that you registered, started a trial, or paid. Where you have provided them at checkout, this can also include a hashed version of your name, phone number, and billing town, region, postcode and country. We send your IP address and browser user-agent so Meta can match the event, and, unless you have turned Targeted Advertising off, the _fbp and _fbc values described above. This happens server-to-server rather than from your browser, which is why it still works if you block scripts. Hashing means we do not send Meta your email address or other details in readable form. To ask us to stop including you in this measurement entirely, contact hello@alphanoodle.co.

Our emails may include tracking pixels from our email provider (Twilio SendGrid) that tell us whether an email was opened or a link clicked. These operate in email, not on the Service. See our Privacy Policy for details on both.

4. Third-party cookies

Some providers help us run the Service: Google Firebase (authentication), Vercel (hosting), Cloudflare (DNS), Stripe (payments), and Meta Platforms (advertising measurement). Of these, Firebase Authentication sets an essential cookie on Finzest, and Meta sets the advertising cookies described above unless you have turned Targeted Advertising off. Payments happen on Stripe’s own hosted checkout page, where Stripe’s cookies and privacy policy apply.

5. Managing cookies

Use the “Your Privacy Choices” control in our site footer to review your choices at any time. Most browsers also let you block or delete cookies through their settings. Note that blocking essential cookies may prevent parts of the Service from working, including signing in.

6. Changes and contact

We may update this Cookie Policy from time to time. Questions? Contact us at hello@alphanoodle.co.

TermsPrivacyCookiesDisclaimer© 2026 Finzest · A sub-brand of AlphaNoodle