Build the data the field doesn’t have yet.
The peptide field has almost no large-scale outcome data. Most of what passes for “evidence” in the community is forum anecdotes, vendor copy, and small case series. That’s a real gap, and it leaves users guessing.
We’re building something different: an opt-in, anonymized outcomes registry where Juno users can contribute their regimens, their dosing windows, and their self-reported outcomes — and where, in return, the field gets the first look at what actually works at scale. Your participation matters because the population size is the whole point.
This page describes how the research engine will work. The opt-in flow lands in a future release; until then, no research data is being collected from anyone.
Why this matters
Imagine a future user asking Juno: “What dose of CJC-1295 actually moves IGF-1 in someone my age and weight, and how long does it take?” Today, the honest answer is “the published trials used X-Y mcg in this population, and forum reports suggest Z, but we don’t actually know what happens in users like you.” That gap is what the research engine closes.
We’re not running a clinical trial. We’re pooling self-reported data — same shape as Whoop’s community insights or Strava’s segment leaderboards — but for a population that has no other infrastructure for it.
Five commitments
These commitments are what make the research engine ethically defensible. They are non-negotiable; if we change any of them, you’ll be told before the change takes effect and given the chance to opt out first.
- 01
Identity stays separate from research
Your name, email, and device fingerprint never sit in the same table as the regimen and outcome data the research engine reads. The research dataset is keyed by an opaque participant_id that we re-roll if you ever ask us to.
- 02
We never sell your data, full stop
Not to peptide vendors, not to clinics, not to insurers, not to wellness brands, not to data brokers. The research engine is for the field, not for buyers. If we ever change this, we'll tell you in plain text first and let you opt out before the change takes effect.
- 03
k-anonymity ≥ 10 + differential privacy
Every aggregate result a researcher can see is bucketed so at least 10 distinct participants contributed to it. On top of that, calibrated noise is added (differential privacy budget) so that no single person's contribution can be reverse-engineered out. If a query would reveal less than 10 contributors, the engine refuses to answer.
- 04
Opt-in, opt-out, and purge
Research participation is off by default. You can turn it on from your account settings. You can turn it off at any time, and you can request that all of your historical contributions be deleted from the research dataset. Same single click as deleting your Juno account, but scoped only to the research data — your account stays.
- 05
Open methodology
When the research engine starts producing aggregate findings, the methodology, the queries, the noise budget, and the participant-count thresholds will be documented publicly. No black-box claims. If we publish a finding, you'll be able to see exactly how the number was computed.
What gets collected (and what doesn’t)
- · Peptide name + class
- · Dose, frequency, route, cycle length
- · Coarse demographics (age band, sex, weight band)
- · Self-reported outcomes (free text, cardinality bucketed)
- · Optional: lab values you’ve already pasted on Juno
- · Your name or email
- · Your IP address or device fingerprint
- · Your exact date of birth
- · Your address or precise location
- · Anything you didn’t explicitly mark for research use
The columns we encrypt at rest in your account (medications, conditions, allergies) are never sent to the research engine. Those stay in your private profile, encrypted under a key that’s scoped to your user record.
Want to be among the first to opt in?
The opt-in flow lives behind your account settings (it ships in a future release). Until then, you can keep tabs on the rollout via the public roadmap, or email if you have feedback on the methodology — we’re actively designing the schema and the privacy guarantees, and informed pushback is welcome.