// privacy
// effective :: 2026-06-04
// last updated :: 2026-06-04
short version: this site remembers your browser only if you talk to the terminal, it never saves what you type to it, and it never logs your IP. the long version is below, in plain language.
// what we collect
aggregate analytics
Vercel Analytics records aggregate, privacy-respecting page metrics: which pages get visited, roughly how often, what kind of device. it is counts, not people. no cross-site tracking, no advertising profile.
browser recognition (only if you engage the terminal)
if you click a chip or send a message to the terminal, the site writes one record to your browser's local storage, under the key vbkd-visitor. it holds a generated id, the first and last time you engaged, a visit count, and a reserved slot for a future guided tour. that's it. it is a number that lets the terminal know if you have been here before. it never leaves your browser, and it is never written if you only scroll past and leave.
voluntary email
if you fill out the form at /work-with-us, the details you type, including your email, are sent so the operator can reply. you give that on purpose, and only then.
// what we don't collect
- :: no IP addresses persisted. Vercel sees your IP in the request headers because HTTP requires it, but no code here reads it or writes it to disk.
- :: no browser fingerprints. no canvas hashing, no device profiling, no cross-site identifiers.
- :: no chat content saved. what you type to the terminal lives in memory for the length of the session and is gone when the tab closes. aggregate session events may be counted anonymously for funnel metrics, but the words of the conversation are never written down.
- :: no advertising trackers. nothing here feeds an ad network.
// how to opt out or clear
- ::don't want the browser record? close the tab without engaging the terminal. nothing gets written.
- ::already engaged and want it gone? right-click the page, open the application tab in your browser's dev tools, find local storage, delete the
vbkd-visitorrow. gone. - :: or browse in a private / incognito window. storage clears when you close it, and analytics stays aggregate either way.
// contact
questions about any of this? email vibekoded@gmail.com. a dedicated privacy address is coming; for now this reaches the operator directly.