Skip to main content

Documentation Index

Fetch the complete documentation index at: https://bardo-3d6a1fd2.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

PEPEtide is built around a single principle: your personal health data belongs to you. The app uses two completely separate data layers — one that never leaves your device, and one that only ever knows an anonymous username. No registration, no email address, and no tracking of any kind is required to use any feature.

​
Two data layers

Personal data

Stored in your browser’s IndexedDB. Never sent to any server. Fully offline-capable.

Community data

Stored in a shared cloud database. Only your chosen username is ever associated with a submission.

​
Personal data — stays on your device

Everything you create in the personal tracking features is stored exclusively in your browser’s IndexedDB storage. This includes:
  • Peptide entries (names, dosage ranges, contraindications, warnings)
  • Vial records (batch numbers, reconstitution dates, expiration dates)
  • Dosing protocols and schedules
  • Dose logs and completion history
None of this data is transmitted to PEPEtide’s servers or any third party. There is no background sync, no cloud backup, and no telemetry attached to personal records.
Because personal data lives in your browser, clearing your browser’s site data or cache will permanently erase it. Export/import functionality is coming in a future update — until then, treat your browser data as the only copy.

​
Community data — anonymous by design

When you submit a peptide or vote in the community database, only the following information is recorded:
  • Username: a free-text alias you choose at submission time — no registration required
  • Submission content: the peptide name, dosage range, benefits, and any notes you provide
Your IP address is never stored in plaintext. For voting, PEPEtide applies a SHA-256 hash to your IP address on the server side before storing it. This hashed value is used solely to enforce the one-vote-per-peptide limit and to provide a pseudonymous author identifier. The original IP address is discarded.
When you submit a peptide to the community database, the record contains: your chosen username, the peptide data you entered, and a SHA-256 hash of your IP address. No email, no real name, and no persistent account identifier is ever collected.
To prevent duplicate votes, the app hashes your IP address with SHA-256 and stores only that hash. One vote per peptide is permitted per hashed IP. You can change an existing vote (for example, from upvote to downvote), but you cannot cast a second independent vote on the same peptide.
Not directly. The only connection between a submission and a person is the username you choose, which can be any alias. The hashed IP is a one-way transformation — PEPEtide cannot reverse it to recover your IP address.

​
No accounts, no email, no registration

PEPEtide requires no sign-up to use any feature — personal tracking or community participation. There is no login screen, no password, and no email address is ever collected. Community contributions use a username/alias you enter at the time of submission. You can use a different alias on every submission if you choose.

​
No analytics or telemetry

PEPEtide collects zero usage data. There are no analytics scripts, no error reporting services, no session recording tools, and no advertising pixels embedded in the app.
You can verify this by inspecting the app’s network requests in your browser’s developer tools. No outbound requests are made during normal personal tracking use.

​
Data persistence and browser storage

Personal data lives in your browser’s IndexedDB. A few things to be aware of:
  • Clearing browser data — using “Clear site data”, “Clear history”, or equivalent browser settings will erase all your personal peptide records permanently.
  • Private/incognito mode — data written during a private browsing session is discarded when the window closes.
  • Multiple devices — because there is no cloud sync, data does not transfer between devices automatically. Export/import support is planned for a future release.
  • PWA install — installing PEPEtide as a Progressive Web App gives the app its own dedicated storage context, which is less likely to be swept by routine browser cleanup.

​
Browser compatibility

PEPEtide’s IndexedDB storage works in all modern browsers:
BrowserMinimum version
Chrome / Edge90+
Firefox88+
Safari14+
iOS Safari14+
Chrome for Android90+