◇ Contact · three lanes
We answer email.
We do not run a support queue.
Three lanes below. Pick the one that matches what you're bringing. We respond on the order of days, not minutes — the work is the priority.
§ 01 · Direct lanes
01 · General
hello@qubblelabs.comBriefings, partnerships, general questions about the work. Tell us who you are and what you build — that's enough.
02 · Security
security@qubblelabs.comVulnerability reports, audit-firm coordination, cryptographic critique. PGP key fingerprint posted below; encrypted reports preferred but not required.
03 · Press
press@qubblelabs.comReporters, researchers writing publicly. We will respond on the record, in writing, with sufficient lead time. We don't do background calls without a name attached.
§ 02 · Security — disclosure terms
Coordinated disclosure, on a 90-day clock, no NDA required.
We treat security reports as gifts. We will not surprise-drop a report on you, and we ask that you not surprise-drop one on us. Anything in the primitive stack, the ratchet, the delivery integrity layer, or the authentication flow is in scope.
§ 03 · Briefing line
Technical updates, in writing, when there is something to send.
The briefing line is an email list. We send technical updates when there is technical work to communicate — releases, security posture changes, new surfaces going live, audit results. The frequency is whatever the work produces, not a marketing cadence.
Mail is read. Real correspondence is welcome. If you're reaching out about the underlying work, please mention what you've already read — it saves us from re-explaining things you already understand.