Loading…
LoadingVeripsa is PII-minimal by design — we’d rather you follow us on a channel you already control than hand us your inbox. Here are the no-signup ways to keep up with releases, posts, and incident notes.
Public repos, changelogs, issues, and discussions live under GetVeripsa. Open the org to browse the repos and choose any GitHub-side follow settings you want — GitHub handles those settings, so we never see your email.
We publish design notes, incident write-ups, and deeper product articles on Zenn. Zenn handles the follow relationship, so again — no email lands with us.
Veripsa Core is content-free — it uses only the minimum operational metadata needed for the advisory. Source file bodies are not stored, displayed, or used for code review. That boundary only means something if we hold the same line on the marketing surface. Asking for an email here would create a list whose only purpose is to market back at you, and a database we’d then have to secure, audit, and honour deletion requests against.
So we don’t. You can install the GitHub App without giving us your email, you can read the docs without giving us your email, and you can follow updates without giving us your email. The trade-off: our reach is whatever GitHub and Zenn give us. We think that’s the right trade-off for the kind of product Veripsa is trying to be.
If you want to talk to a human — about free access, coverage, an evaluation, or a question we haven’t answered — the contact page has three direct email addresses. You write to us; we don’t write to you first.
