Cookie Policy

A cookie is a small file a site asks your browser to keep. Every one this site sets is needed for something you asked it to do: sign you in, take a payment, or remember the answer you gave here. There is nothing on this page to refuse.

This page lists every cookie this site sets, and it is a complete list rather than a representative one. If we add a cookie, this table changes before it does. Read an article while signed out and having answered nothing, and your browser keeps nothing at all. The cookies below appear when you do something that needs one: open the sign-in form, start a checkout, or answer the question about cookies.

Last updated: 17 September 2026

What we do not do

We run no advertising cookies. None.
We run no third-party trackers. No Google Analytics, no Meta pixel, no ad network, no social widgets that phone home.
Our analytics, Koko Analytics, is cookieless and self-hosted. It sets nothing on your device and it sends nothing off our server. There is no analytics cookie to accept or reject, because there is no analytics cookie. We would rather say that plainly than offer you a switch that does nothing.
We do no cross-site tracking of any kind.

So there is no non-essential storage on this site at all. The cookies in the table below are the ones that sign you in, take a payment and remember the answer you gave here. There is nothing else to switch off.

The cookies

Strictly necessary, and the only kind here

Name	Set by	Purpose	Lifetime
`wordpress_test_cookie`	WordPress	Checks that your browser will accept a cookie before the sign-in form is shown.	Session
`wordpress_[hash]`	WordPress	Authenticates you on sign-in. Only sent to the admin and portal areas.	Session
`wordpress_logged_in_[hash]`	WordPress	Tells the site which account is signed in, so your own pages are shown to you.	Session, or 14 days if you tick “remember me”
`wordpress_sec_[hash]`	WordPress	The same, for secure areas, sent over HTTPS only.	Session, or 14 days with “remember me”
`PHPSESSID`	Our server	Holds the state of a multi-step form, chiefly membership checkout, while you complete it.	Session
`pmpro_visit`	Paid Memberships Pro	Marks the current visit so a checkout is not counted twice.	Session
`pmpro_levels`	Paid Memberships Pro	Remembers which membership level you selected while you finish paying.	Session
`_lscache_vary`	LiteSpeed Cache	Tells the cache to serve you the signed-in version of a page instead of the cached public copy. Only set once you are signed in.	Session
`idz_consent`	This site	Records the cookie choice you made here, so we do not ask you again every visit. Stores your answer and its date, nothing else.	12 months
`wfwaf-authcookie-[hash]`	Wordfence, the security plugin	Lets the firewall tell a signed-in account from a visitor, so it does not challenge you on your own pages. Only set once you are signed in.	As long as your sign-in
`idz_book_buying`	This site	Set while you buy a book, so the page you come back to from the payment provider can find your order. Holds an order number and a check value, never your address. Removed when the purchase completes.	1 hour
`idz_session_ended`	This site	Set when a newer sign-in on another device has ended this one, so the page can tell you why you were signed out.	10 minutes
`idz_maint_pass`	This site	Only while the site is closed for maintenance: remembers that you were given the key to look at it. Never set for readers of the open site.	30 days

Razorpay sets its own cookies on its checkout, for payment security and fraud prevention, when you are handed over to pay. Those are Razorpay’s, set on Razorpay’s domain, and are governed by Razorpay’s own policy. We cannot read them.

Our CDN and page cache (Hostinger CDN, LiteSpeed Cache) cache public pages only. Signed-in pages and the entire client portal are never cached and never served from the edge. Caching sets no identifier on you.

Analytics

Nothing. Deliberately. See above.

The client portal

The portal sets no cookies beyond the sign-in cookies listed as strictly necessary. Nothing you write is stored in your browser: drafts are saved to the site’s own database, so that closing a tab does not lose your work and so that a shared or borrowed device does not keep it. Analytics does not run on portal pages at all.

Choosing, and changing your mind

You will have seen a box about cookies the first time you came here, and it is worth being straight about what it does. Because everything this site stores is necessary for something you have asked for, the same cookies are set whichever button you pressed, and none are held back. Your answer is kept in idz_consent so that you are not asked again, and that is the whole of it.

We say so because the alternative is a control that looks like a choice and is not one, and this publication would rather lose the gesture than keep it. If we ever add storage that is genuinely optional, that box will begin to do something, and this page will say what it is before it does.

To be asked again, delete the idz_consent cookie for this site and the question comes back on your next visit. To clear everything at once, use the browser controls below.

Browser controls

Every major browser lets you see, block and delete cookies for a single site, usually under Settings → Privacy. Browsers also offer “Do Not Track” and Global Privacy Control signals. Since we run no tracking and no advertising, there is nothing for those signals to switch off here; we honour them by not having built the thing they turn off.

Questions about this page go to iam@idinsayit.com. A formal complaint goes to the Grievance Officer at the same address, in whatever words you have; how that is handled, and how to take it further if our answer does not satisfy you, is on the Data Protection and Grievance Redressal page.