How we handle your data

What we collect

Basic visit data. Like any website, our hosting infrastructure logs standard request data (IP address, browser/user-agent, requested page) to serve pages and keep the site secure and running.

Analytics. We use Cloudflare Web Analytics to see aggregate traffic patterns: which posts get read, and roughly how much traffic. It’s cookieless: Cloudflare Web Analytics sets no cookies of its own, uses no client-side state to track you, and doesn’t build cross-site profiles. Cloudflare’s count of page loads stays, and the site will also keep its own daily totals, described in the next paragraph. Apart from the Google Analytics cookies described under Google Analytics, the one cookie this site sets is the language preference described under Cookies below. It has nothing to do with analytics and is not part of those totals.

Daily totals kept by the site. In addition to Cloudflare’s page loads, the site will keep daily totals of three things: which page path was opened, which outside host a link went to, and a few actions the page marks. Each total is only a number per path, host or action per day. No network address, cookie or identifier is stored with it. So that one reader cannot inflate a count, a hash of your network address (your IP address) is kept for the clock hour of your visit and then deleted. Daily totals are deleted after 90 days. The lang cookie is unchanged and is not part of these totals.

Comments, only if you choose to comment. Signing in to leave a comment stores your name, email address, and the comment text, plus standard session data (IP address, user agent) tied to that sign-in. Sign in with Google, or email + password if you’d rather — sign-in and verification email is sent through Resend. We never post, comment, or sign in on your behalf anywhere else.

Fix feedback and fix requests, only if you send them. Under each fix you can answer whether it worked, and add an optional one-line note when it did not. You can also send us an error we have no fix for yet, with the tool you use. We store exactly that (your answer and note, or the error text and tool), which page it came from, and when. We do not ask for your name or email, it is not linked to a comment account, and your IP address is not stored with it: our host uses it only for a moment, to limit how often one connection can send. Anything that looks like a key, token, password or email address is replaced with [redacted] before it is stored, but please leave those out yourself. Only our editors read notes and requests; a fix page shows only how many readers said it worked, and only once five or more have answered. We delete these records after 180 days, and we never reply to them.

If you email us. Writing to hello@vibecoderdaily.com means we receive whatever you send — your address and your message.

Cookies

One cookie of our own, and it only remembers a language. Vibe Coder Daily is published in English, Hebrew, and Arabic. If you read it in Hebrew or Arabic — or switch back to English — we store that choice so the next page you open comes up in the same language instead of guessing again from your browser settings.

What’s in it. The cookie is named lang and holds a language code — en, he, or ar. Nothing else. It isn’t an identifier, it isn’t tied to an account or to anything you’ve commented, it holds no personal information, and it can’t be used to recognise you.

How long it lasts, and how it’s set. One year, unless you clear it sooner. It’s set SameSite=Lax and Secure, so it’s sent only to this site, only over an encrypted connection, and never to anyone else’s.

Who doesn’t get it. Search-engine crawlers, which are served every language directly and are never given a cookie at all.

It’s a preference, not tracking. No profile, no cross-site history, no advertising use, and it’s never shared with anyone. Clearing your cookies removes it and the site works exactly the same afterwards — it simply falls back to your browser’s language setting, or, if your browser asks for a language we don’t publish, to the country our host sees your connection coming from. Other than lang and the Google Analytics cookies described under Google Analytics, this site sets no cookies; if you sign in to comment, the sign-in session is held by our comments service on its own comments. subdomain.

Saved on this device

Four features keep things in your browser, not with us. Vibe Coder Daily writes them to your browser’s own storage (localStorage). What is kept there stays on this device: it is never sent to our servers, it is not synced to your other browsers or devices, and unlike a cookie it does not travel with any request you make. Clearing this site’s data in your browser settings removes all of it, and the site works the same afterwards.

New since your last visit. To mark the fixes that were published or re-checked since you were last here, the site keeps the time of your last two visits in this browser under vcd:v1:visits. That is all it holds, and it is used for nothing else. Clear history, beside the count of new fixes, deletes it.

My fixes. When you save a fix, its address and the time you saved it are kept in this browser under vcd:v1:saved, so it can appear under My fixes on the home page. To delete one, use the remove button beside it under My fixes, or tap Saved on the fix’s own page.

One note on your device, only if you answer. When you answer “Did this fix work?”, your browser keeps a small record under vcd:v1:outcome: followed by that page’s name. It holds only your answer, so the question is not asked again on that page. It is browser storage rather than a cookie, it is never sent to us or to anyone else, and clearing this site’s data removes it.

Launch check ticks. When you tick a check on the launch check page, the ids of the checks you ticked are kept in this browser under vcd:v1:launch: followed by the tool you picked, so you can come back mid-way. Nothing else is kept, and nothing is sent to us. Clear these ticks, under the list, deletes them for that tool.

What we don’t do

No ad trackers, no third-party marketing pixels, no ad networks, and we don’t sell or rent your data to anyone. There’s no newsletter list — the RSS feed is the closest thing to a “subscribe,” and it collects nothing.

Third parties involved

• Cloudflare — hosting, and the cookieless analytics described above. Our hosting layer is also what stores your language choice in the lang cookie; that choice stays on this site and isn’t sent anywhere else.
• Google — only if you choose to sign in with Google to comment.
• Resend — sends the comment sign-in/verification email.
• npm and PyPI: only if you use the package check. The package names you check are sent from your browser straight to the public npm registry (registry.npmjs.org, api.npmjs.org) or to PyPI (pypi.org), without cookies and without the address of the page you are on. Nothing else from the page is sent, and the results are not stored, by us or in your browser.

Each handles data under its own privacy policy; we only share what a feature needs to work — e.g. your email address reaches Resend solely to deliver a sign-in email.

Your comment data

You can delete your own comment at any time. To delete your account and everything tied to it, email hello@vibecoderdaily.com and we’ll handle it.

Children

Vibe Coder Daily isn’t directed at children, and we don’t knowingly collect data from anyone under 13.

Changes

If this policy changes in a way that matters, we’ll update this page and the effective date above.