Cookie Policy
Last updated
LA Dodger Talk uses a handful of small first-party cookies, and only to make features work, like editing your own comments. We don’t use advertising or analytics cookies, and we don’t track you across other sites.
What cookies are
Cookies are small text files a website asks your browser to keep. Local storage is a similar browser feature that keeps data on your device. It is never sent to the website automatically.
Cookies we set
All of these are “first-party”: they belong to ladodgertalk.com and are only sent back to it. Each one is needed for the feature it supports.
__Host-ladt_co
A random ownership token. Lets the browser you commented or liked from edit your own comments and keep your likes. It contains no personal information and can't be read by scripts on the page.
- Lasts
- 3 years
- When it’s set
- Set the first time you post a comment or like one
ladt_v
A single "0" or "1" telling the page whether there is any comment, like or sign-in state to look up for you. It lets most visitors skip that lookup entirely. No identifier.
- Lasts
- 7 days (0) or 1 year (1)
- When it’s set
- Set on your first visit, and updated when you post, like or sign in
__Secure-authjs.session-token and related authjs.* cookies
Keeps writers and editors signed in to the admin area, and protects the sign-in form from forgery.
- Lasts
- Session token: up to 14 days. Others: end of sign-in or session
- When it’s set
- Writers and editors only, when they sign in
Information kept in your browser’s local storage
ladt.commenter
Your name and email for the comment form, if you tick "Remember me". Only sent to us inside a comment you post.
- Lasts
- 12 months
- When it’s set
- Only if you tick "Remember me"
ladt.comment-draft:…
An unfinished comment, so you don't lose it if you leave the page. Never sent to us until you post it.
- Lasts
- Until you post or clear it
- When it’s set
- While you type a comment
Cookies we don’t use
No advertising, retargeting, social-tracking or analytics cookies. Sponsor placements on the site are plain links and images, not ad-network code.
Third-party content
Some articles and comments embed content from other services. When your browser loads it, that service may set its own cookies, which are controlled by its own policies:
- YouTube: we use YouTube’s privacy-enhanced (youtube-nocookie.com) player, which avoids most cookies until you press play.
- Vimeo: embedded Vimeo players.
- X (Twitter): embedded posts load X’s widget script.
- Images in comments: commenters can link images hosted on other sites, and those sites receive a normal request from your browser.
- Google: writers and editors sign in with Google, which sets its own cookies during sign-in.
Managing cookies
You can block or delete cookies and local storage in your browser’s settings. The site still works for reading if you do. You’ll lose the ability to edit comments you posted from that browser, your likes will no longer show as yours, and writers will need to sign in again. Because we only use cookies that the features you use need, we don’t show a cookie banner.
For more about the information we handle, see the Privacy Policy.