The few cookies we set, and why

1.1We set a session cookie to keep you signed in, and a security cookie to protect forms from cross-site requests. These are required for the service to work.

Needed to sign in and stay secure.

2.1If you choose settings such as your default account type, we store them in a cookie so they persist between visits.

Remembers your choices.

2.2This cookie, cp_prefs, lasts twelve months and holds only your settings: default account, language, and notices you have dismissed.

One cookie, your settings only, 12 months.

3.1We measure page visits with privacy-preserving, cookieless analytics. No cross-site tracking takes place.

We count visits without tracking you.

3.2We count the page visited, the referring site’s domain, country and device type. IP addresses are not stored and no identifier links one visit to another.

Counts, not people.

4.1The attribution block on publisher pages sets no cookies and collects no data about readers.

Readers of publisher pages are not tracked.

4.2The block loads from citepep.com, so our server receives the request as it would for any image. We do not log readers’ IP addresses; publishers see only a total view count per page.

Publishers get a view count, nothing about who.

5.1Our payment provider sets its own cookies on checkout pages only, to prevent fraud. If you sign in with Google or Facebook, that provider may set cookies during sign-in.

Only on payment and social sign-in, only if you use them.

6.1You can clear or block cookies in your browser. Blocking essential cookies will prevent sign-in.

You’re in control; sign-in needs the essentials.