vialfile

Injection log

Log each injection — peptide, dose, route, site, notes. Your log stays in this browser. No account, no server, no ads.

Site rotation

No entries yet.

Why log injections

  1. Rotate sites. Repeat injection into the same site causes local irritation, fibrosis, and slower absorption. Seven-site rotation is the baseline standard.
  2. Catch dose drift. Multi-peptide stacks are easy to mis-time. A written record surfaces accidental double-doses or long gaps before they affect your bloodwork.
  3. Correlate side effects. Mark notes on water retention, sleep change, injection soreness, mood — the pattern only shows up in weeks of data, not a single entry.

This v1 is intentionally narrow: one peptide + one dose + one site per entry. Side-effect severity tracking and bloodwork reminders ship in later releases.

Log FAQ

Where is my data stored?

In your browser's localStorage under key vialfile-log-v1. Nothing is sent to a server in this v1. When we add sync (opt-in), your existing entries will migrate over cleanly.

Can I export or back up my log?

Export + import are coming in the next release. For now you can inspect the raw JSON in browser devtools (localStorage.getItem('vialfile-log-v1')) and copy it elsewhere as a backup.

Why only 7 sites?

Because that's the rotation peptide users actually follow — both delts, abdomen, both glutes, both thighs. Granular sub-quadrants (upper-left abdomen vs lower-right abdomen) added visual complexity without behavioral value in v1.

What happens if I switch browsers?

Your log stays on the original browser until you export and re-import, or until we ship cloud sync. Private-mode windows have their own storage scope that clears on close.