How a session cookie works
When a site sets a cookie it can include an expiry date. If it does not, the browser stores the value only for the current browsing session and throws it away when the browser is closed. That is the entire difference between a session cookie and a persistent cookie: one has a date on it and one does not.
The name is slightly misleading, because a browser session is not the same as an analytics session. Analytics tools define a session by inactivity or by a change of campaign, and they usually end one long before the browser is closed. A session cookie survives for as long as the window stays open, which on a phone can be days, and on a laptop that never fully shuts down can be longer still.
Why session cookies matter
They hold the state that makes a website usable within a single visit. A logged-in session, a shopping basket, a multi-step form or booking flow, a security token that proves a form submission came from your own page — all of these are typically session cookies, and all of them are things the visitor asked for by using the site.
That gives them a useful property: because they are necessary for the service the visitor requested, they generally do not require consent. It is one of the reasons a well-built site can still work properly for someone who refuses every optional cookie, and why refusing a banner should never leave a customer unable to check out.
Where session cookies go wrong
The first problem is treating one as a memory. A visitor who reads about you on a phone in the morning and returns in the evening arrives with an empty session, so nothing carries over: not the basket, not the login, not the answer they typed into your form. If a session cookie is holding something the customer would be annoyed to lose, it is the wrong tool.
The second is misclassifying them in a cookie policy. Some session cookies really are necessary and some are not, and a marketing script can set one just as easily as a checkout can. Judge each by purpose rather than by lifetime.
The third is a session that quietly outlives its usefulness on a shared device — an internet cafe, a hotel desk, a family tablet — where the next person inherits an open window and whatever it remembers.
What to do about it
List the cookies your site sets and note which have no expiry date. For each one, ask what would break if it disappeared mid-visit and what would leak if it did not. Anything holding sensitive state should also have a server-side timeout, so an abandoned window stops being a valid session even if the browser stays open.
Where a session cookie is doing necessary work, say so plainly in the cookie table of your privacy policy rather than lumping everything together as “tracking”. And if a customer’s progress through a long form or a booking is being lost between visits, that is a design decision to revisit — conversion rate work often starts with something as small as remembering what someone already typed.
