NoosletterNoosletter

Start here

  • About Noosletter
  • Contact

Guides

  • How points and levels work
  • How newsletter points and rankings work
  • Sending reputation
  • Plans and pricing
  • Account limits
  • How we check email addresses
  • Checks before you send
  • Sending domains
  • Inviting and importing subscribers
  • Trash, archive and deleting
  • Team roles

Developers

  • API and webhooks

Legal

  • Terms of service
  • Privacy policy
  • Cookie policy
Cookie policy

Start here

  • About Noosletter
  • Contact

Guides

  • How points and levels work
  • How newsletter points and rankings work
  • Sending reputation
  • Plans and pricing
  • Account limits
  • How we check email addresses
  • Checks before you send
  • Sending domains
  • Inviting and importing subscribers
  • Trash, archive and deleting
  • Team roles

Developers

  • API and webhooks

Legal

  • Terms of service
  • Privacy policy
  • Cookie policy

Cookie policy

Last updated: 9 November 2026

Noosletter uses a small number of cookies, only to keep you signed in and to make features you ask for work. We don't use advertising cookies. On publishers' profile and email pages we ask before we record which pages you visit; that is the banner you see there, and it is separate from cookies.

The cookies we use

CookieWhat it's forHow long it lasts
App sign-in (set by our sign-in system, names begin authjs)Keeps publishers and their teams signed in to app.noosletter.com, and protects sign-in formsUntil you sign out, or it expires
noos_readerKeeps readers signed in on noosletter.com. It is also set when you open a "read on the web" link from an email, which unlocks that newsletter's gated pages without a separate sign-in.Up to 90 days
noos_refSet only when you arrive at sign-up through a referral link or a "Powered by Noosletter" badge, so the account that sent you is credited30 days
sidebar_stateRemembers whether the app sidebar is open or closed7 days

Sign-in cookies for the app and for readers are kept separate: one never works on the other's site.

What we store in your browser

On a publisher's profile and email pages we show a banner with Accept and Reject. Only if you accept do we use your browser's local storage (not cookies) for:

ItemWhat it's forHow long it lasts
noos_consentYour choice, accepted or rejected, so we don't ask every visitUntil you clear it, or change your choice from "Tracking" in the page footer
noos_sid, noos_seenA random visit code, so the pages you view in one visit are recorded together (and linked to a subscriber if you arrived from their email or later sign up)A visit ends after 30 minutes of inactivity; the code is replaced on your next visit

If you reject, neither the visit code nor any identified recording is used. Your choice on the banner is what counts; browser signals such as Global Privacy Control are not read as a choice either way. Only anonymous, cookie-free totals are counted, made from a one-way code that changes every day and can't be linked to a person. See our privacy policy.

What we don't use

  • No advertising cookies.
  • No analytics cookies. Recording of visits uses local storage, and only after you accept.
  • Opens and clicks in emails are recorded against the subscriber they were sent to. Emails can't ask for consent the way a web page can; the privacy policy explains what is recorded.

Your light or dark theme choice is saved in your browser's local storage, not in a cookie.

Managing cookies

You can clear or block cookies in your browser settings. If you block the sign-in cookies, you won't be able to sign in.

Contact

Questions about cookies: hello@noosletter.com.

Start your Noosletter