Privacy Policy

Last updated: October 17, 2026

1. Introduction

Smart Peptide Tracker ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and website (collectively, the "Service").

Smart Peptide Tracker is operated as a sole proprietorship based in Texas, United States. For data protection purposes, we are the data controller of your personal information.

2. Information We Collect

Account Information

  • Email address
  • Display name (if provided)
  • Authentication provider information (Google, Apple, or email/password)

User-Generated Content

  • Peptide inventory and supply information
  • Research protocols and schedules
  • Dose log entries and tracking data
  • Progress measurements (weight, body measurements, mood, energy, notes)
  • Progress photos, inventory photos, and note images (stored as described under Data Storage and Security)
  • Custom peptide information, overrides, and custom half-life values
  • Research appointments and lab work (dates, locations, and notes)
  • Supplier information (names, websites, ratings, and notes)
  • Lab/biomarker results (marker values, reference ranges, lab names)
  • Cost records, including inventory costs, supplier orders, and optional amounts paid for labs. Lab cost amounts are not included in Amino lab snapshots or Health Reports.
  • Community content: reviews, protocol templates, research programs, peptide requests, mentorship messages, and display names you choose to share publicly
  • Coach Mode content: versioned consent records, relationship status, encrypted assignment revisions, encrypted coach-private notes and templates, sharing permissions, selected encrypted progress photos, optional encrypted shared categories, and non-sensitive activity and export audit records

Health Data (with your permission)

  • When you connect Apple HealthKit (iOS) or Google Health Connect (Android), we may read weight, body fat percentage, blood pressure, blood glucose, sleep duration and stages, resting heart rate, activity/steps/calories, and blood oxygen saturation (SpO2). HRV and body temperature are currently available only through Apple HealthKit and are not requested from Health Connect on Android.
  • Health data is read-only. We do not write data back to HealthKit or Health Connect.
  • Imported health data follows your research-data storage choice: encrypted SPT cloud storage or the encrypted workspace on this device
  • Health data is never sold or used for advertising. Selected biomarker context is sent for AI processing only after a separate, explicit opt-in. Synced health data (for example sleep, heart rate, HRV and steps) is included in an Amino progress summary only after its own separate, explicit opt-in for that conversation, and is then sent to the AI provider for the Amino model you select
  • You can disconnect health data access at any time in your device settings

Payment Information

  • We do not directly collect or store credit card or bank account numbers
  • Payments are processed by Stripe (web), Apple (iOS via StoreKit), or Google (Android via Play Billing)
  • We receive and store transaction identifiers, product IDs, and purchase verification status to manage access and prevent purchase replay
  • For physical-product orders, Stripe provides the shipping name, email, and address needed for fulfillment
  • For referrals, we store your referral code, point balance, point ledger, order qualification status, gift and reward status, and program terms acceptance
  • Referral links may store a code and 30-day expiration in the browser. We use Stripe transaction references and delivery status to award, delay, reverse, and reconcile points. Payment card numbers remain with Stripe
  • To detect duplicate or unusual referral activity, we may compare one-way protected versions of checkout email, shipping address, and payment-card fingerprint. Administrators may review referral account IDs, balances, order status, risk signals, and reward status

Automatically Collected Information

When you open our public install link, we count visits in aggregate by day, source, public campaign label, platform category and recognized referring website hostname. Other referring websites are grouped together. This helps us understand how people find the app. These counts are separate from optional in-app Firebase Analytics. We do not attach account identifiers, device identifiers, cookies, IP addresses or full user agent strings to these counters. Campaign information is also passed to the selected app store under its privacy practices. These counters measure link visits, not completed installations. Our hosting and cloud providers also process technical connection information to deliver and protect the service.

  • Limited reliability records include save and startup outcomes, repeat counts, fixed error codes, timings, platform, app version and build, linked to the account and session already used for error reports. A random 10% sample records the first eligible signed-in launch per app installation or browser profile each UTC day, at most once daily. No new device identifiers or research records are collected. Demo, Only on this device and My cloud backup queue no new records of this kind. Records queued earlier may still arrive. Account device storage sends only filtered technical metadata. These records use the existing technical-record retention and account-deletion process.
    Español · Português · Deutsch · Français

    Los registros limitados de fiabilidad incluyen resultados de guardado e inicio, recuentos de repeticiones, códigos de error fijos, tiempos, plataforma, versión y compilación de la app, vinculados a la cuenta y sesión ya usadas en los informes de errores. Una muestra aleatoria del 10% registra el primer inicio elegible con sesión iniciada por instalación de la app o perfil del navegador cada día UTC, como máximo una vez al día. No se recopilan nuevos identificadores del dispositivo ni registros de investigación. Demo, Solo en este dispositivo y Mi copia en la nube no ponen en cola nuevos registros de este tipo. Los registros ya puestos en cola pueden llegar más tarde. El almacenamiento de cuenta en el dispositivo envía solo metadatos técnicos filtrados. Estos registros usan los procesos existentes de conservación de registros técnicos y eliminación de cuenta.

    Os registros limitados de confiabilidade incluem resultados de salvamento e inicialização, contagens de repetições, códigos de erro fixos, tempos, plataforma, versão e compilação do app, vinculados à conta e sessão já usadas nos relatórios de erro. Uma amostra aleatória de 10% registra a primeira inicialização elegível com sessão iniciada por instalação do app ou perfil do navegador em cada dia UTC, no máximo uma vez por dia. Não são coletados novos identificadores do dispositivo nem registros de pesquisa. Demo, Apenas neste dispositivo e Meu backup na nuvem não colocam novos registros desse tipo na fila. Registros já na fila podem chegar depois. O armazenamento da conta no dispositivo envia apenas metadados técnicos filtrados. Esses registros usam os processos existentes de retenção de registros técnicos e exclusão da conta.

    Begrenzte Zuverlässigkeitsdaten umfassen Speicher- und Startergebnisse, Wiederholungszahlen, feste Fehlercodes, Zeiten, Plattform, App-Version und Build. Sie sind mit dem Konto und der Sitzung verknüpft, die bereits für Fehlerberichte verwendet werden. Eine zufällige Stichprobe von 10% erfasst den ersten zulässigen angemeldeten Start je App-Installation oder Browserprofil und UTC-Tag, höchstens einmal täglich. Es werden keine neuen Gerätekennungen oder Forschungsdaten erfasst. Demo, Nur auf diesem Gerät und Meine Cloud-Sicherung stellen keine neuen Daten dieser Art in die Warteschlange. Bereits eingereihte Daten können später ankommen. Die Kontospeicherung auf dem Gerät sendet nur gefilterte technische Metadaten. Für diese Daten gelten die bestehenden Verfahren zur Aufbewahrung technischer Daten und zur Kontolöschung.

    Les données limitées de fiabilité comprennent les résultats de sauvegarde et de démarrage, les répétitions, des codes d’erreur fixes, les durées, la plateforme, la version et le build de l’app, liés au compte et à la session déjà utilisés pour les rapports d’erreur. Un échantillon aléatoire de 10% enregistre le premier démarrage admissible avec connexion par installation de l’app ou profil de navigateur et par jour UTC, au plus une fois par jour. Aucun nouvel identifiant d’appareil ni donnée de recherche n’est collecté. Demo, Uniquement sur cet appareil et Ma sauvegarde cloud ne mettent en attente aucune nouvelle donnée de ce type. Les données déjà en attente peuvent arriver plus tard. Le stockage du compte sur l’appareil envoie uniquement des métadonnées techniques filtrées. Ces données suivent les procédures existantes de conservation des données techniques et de suppression du compte.

  • Amino service records include request outcomes, whether the app acknowledged receiving a reply, and whether an output limit cut it off. These account-linked records use the existing AI-log retention and account-deletion process. New receipt and failure metadata contains no question or reply text. Receipt does not prove saving or answer quality. Device-storage logs continue to omit text.
    Español · Português · Deutsch · Français

    Los registros del servicio Amino incluyen el resultado de las solicitudes, si la app confirmó la recepción de una respuesta y si un límite de salida la interrumpió. Estos registros vinculados a la cuenta usan los procesos existentes de conservación de registros de IA y eliminación de cuenta. Los nuevos metadatos de recepción y fallos no contienen texto de preguntas ni respuestas. La recepción no demuestra que se haya guardado ni la calidad de la respuesta. Los registros del almacenamiento en el dispositivo siguen omitiendo el texto.

    Os registros do serviço Amino incluem os resultados das solicitações, se o app confirmou o recebimento de uma resposta e se um limite de saída a interrompeu. Esses registros vinculados à conta usam os processos existentes de retenção de registros de IA e exclusão da conta. Os novos metadados de recebimento e falha não contêm texto de perguntas ou respostas. O recebimento não comprova o salvamento nem a qualidade da resposta. Os registros do armazenamento no dispositivo continuam omitindo o texto.

    Amino-Dienstdaten enthalten Anfrageergebnisse, ob die App den Empfang einer Antwort bestätigt hat und ob eine Ausgabelimitierung sie abgebrochen hat. Für diese kontobezogenen Daten gelten die bestehenden Verfahren zur Aufbewahrung von KI-Protokollen und zur Kontolöschung. Neue Empfangs- und Fehlermetadaten enthalten keinen Frage- oder Antworttext. Der Empfang belegt weder eine Speicherung noch die Antwortqualität. Protokolle bei Gerätespeicherung enthalten weiterhin keinen Text.

    Les données du service Amino comprennent les résultats des demandes, la confirmation de réception d’une réponse par l’app et son éventuelle interruption par une limite de sortie. Ces données liées au compte suivent les procédures existantes de conservation des journaux d’IA et de suppression du compte. Les nouvelles métadonnées de réception et d’échec ne contiennent aucun texte de question ou de réponse. La réception ne prouve ni la sauvegarde ni la qualité de la réponse. Les journaux du stockage sur l’appareil continuent d’exclure le texte.

  • Technical error reports and diagnostics may include an error message, stack information, page, app version, user agent, session identifier, and recent troubleshooting breadcrumbs
  • Existing serious save, conflict-choice, startup and crash incidents may also carry a filtered device diagnostic report, at most once per session for each failure kind. This report includes app and device versions, startup timing, save and recovery status, approximate device observations when available, and allowlisted error classifications. It excludes research records, account identifiers, keys, tokens, backups, raw error messages and stack traces. With cloud storage, these plaintext support reports may also include aggregate saved-data counts, coarse payload-size ranges and saved section names, such as logs or protocols. They contain no record contents. Reports stay local in Only on this device and My cloud backup modes. Account device storage uses additional filtering that removes research-derived counts and payload details.
  • Tracker bug reports have an optional Include phone diagnostics checkbox, off by default, with a preview. Diagnostic attachments are private support documents, separate from the community-visible ticket. The account owner and authorized support administrators can access the attachment. A ticket contains only its attachment reference. Deleting a ticket does not immediately remove its private attachment. Uploaded reports expire within 30 days and are removed by asynchronous retention cleanup. Existing backup and recovery retention policies may retain older copies for their limited recovery window. Share Diagnostics still opens your device share sheet and sends nothing unless you choose a destination.
  • Push notification tokens may be stored when notification delivery is enabled
  • To route reminders to the intended profile on each signed-in installation, we store a random app installation identifier, the device name you choose, device type, operating system and version, manufacturer when available, profile assignment, shared-alert choice, and notification behavior settings. The identifier is generated by the app and is not a hardware identifier. Device names and this routing metadata are stored as account metadata and are not part of the encrypted research-data payload, so avoid entering sensitive information in a device name.
  • Firebase Analytics, Performance Monitoring, and Crashlytics are disabled by default in the current app build
  • Controlled cost telemetry is disabled by default and is used only during an explicitly enabled support diagnostic session

3. How We Use Your Information

  • Provide, maintain, and improve the Service
  • Sync research data across devices when SPT cloud storage is selected
  • Send schedule reminders and dose notifications (if enabled)
  • Display health trends and protocol impact analysis on your Progress page
  • Power the AI Research Assistant chatbot (see AI Services below)
  • Facilitate community features (reviews, templates, mentorship)
  • Provide invitation-only Coach Mode organization after both accounts accept the current Coach Mode terms
  • Process purchases and manage access status
  • Detect and prevent technical issues and abuse
  • Diagnose errors, prevent abuse, and improve reliability

4. Data Storage and Security

SPT cloud and account services use Google Firebase services (data centers located in the United States). Device storage and personal backup choices are described below:

  • Firebase Authentication for secure login
  • Cloud Firestore for data storage
  • Firebase Storage for encrypted media
  • Firebase Analytics and Performance Monitoring only after affirmative analytics consent
  • Firebase Cloud Messaging for push notifications

Synced research data is encrypted at rest using AES-256. The encryption key is not stored in plaintext and access requires your PIN or recovery key. Choose a strong PIN, protect your recovery key, and keep your devices secure.

In SPT cloud mode, progress photos, inventory photos, and note images may be stored within encrypted account data or as separate encrypted media in Firebase Storage. On supported mobile builds, inventory note images may move to separate encrypted media when a save is too large. Those images require a connection to load. This does not publish the images or add them to community content.

Account, purchase, notification-routing, and technical diagnostic records are stored separately from the encrypted research-data payload. The research-data encryption statement does not mean that all service metadata is encrypted with your PIN.

Signed-in devices keep encrypted cached research data and pending saves for offline use and recovery. Display preferences and Demo Mode data are also stored on the device. Cloud backups, device backups, and protected recovery copies may retain earlier versions of your records. Backup previews and comparisons decrypt selected records on your device. A restore can keep an encrypted undo snapshot on that same device; it is not a portable backup.

Ordinary JSON backups, CSV exports, recovery downloads, and PDF reports can contain readable personal data. App PIN protection does not automatically protect those files. Device-storage backup packages explicitly identified as encrypted remain encrypted and require the unlock information requested by the restore screen. Keep that information and your backup files secure. Deleting your account cannot remove exported files, personal Google Drive or iCloud Drive backup files, recipients' copies, or data on other offline devices; remove those copies separately.

We implement industry-standard security measures to protect your personal information. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

4A. Your Storage Choice

In SPT cloud mode, research data is encrypted and synced through SPT cloud. On supported iPhone and Android builds, Settings > Data lets you keep that research data in an encrypted workspace on one device while you stay signed in. It is no longer synced to your other devices or the web app. Your account, purchases, access rights, and notification-routing records still use our services.

Moving to device storage can leave a dated copy in SPT cloud. That copy is not kept up to date. You can choose to remove it; the app first prepares and checks an encrypted backup file. Removal covers the cloud research copy and its related backups, history, and media. It does not delete your account or separately held service records, such as purchase records, AI logs, community records, or data already shared through other features. Those records follow the retention and deletion rules in this policy. An unfinished removal is shown in the app. Returning to SPT cloud is a separate confirmed action; the previous device workspace and its local recovery copy can remain on the device.

Device storage blocks automatic research-data sends such as Consistency Ranks updates, Webrequest event deliveries, and Coach Mode background sharing. It still allows actions you request, such as asking Amino or sharing selected records, to send the input needed for that action. Amino usage records in this mode omit question and answer text but retain usage metadata, including question length. Technical error reports are also restricted to diagnostic metadata; purchase failures may include error codes.

For account device storage, backups can stay on this device or be saved as encrypted copies to your own Google Drive or, on supported iPhone builds, iCloud Drive. Google or Apple receives the encrypted files and associated file metadata under its own privacy practices. Google Drive access uses the limited permission for files created or opened with this app. These are backup copies, not live synchronization between devices. iCloud may stage a file locally before the system finishes uploading it. Check the displayed backup and upload status.

Recent saves, daily checkpoints, and copies kept before a restore can retain earlier research records on the device. Restoring a save creates a new revision and can offer guarded Activity History Undo. Changing a backup destination, returning to SPT cloud, or deleting an SPT account does not remove backup files already saved in your personal Google Drive or iCloud Drive. You control and remove those files separately.

5. Data Sharing and Disclosure

The hosted website loads OpenAI's ChatGPT Ads measurement software with measurement consent set to denied. Loading this software contacts OpenAI's content delivery service. Advertising conversion events are disabled in this version. This integration does not pass account identifiers or research records to the software and does not load in the native apps.

We do not sell, trade, or rent your personal information to third parties. We do not use your data for advertising. We may share information only in the following circumstances:

  • Service Providers: Google Firebase (hosting, authentication, storage, callable processing, optional analytics, and notifications), Stripe (web payments and checkout), EasyPost (address verification, shipping labels, and tracking), Anthropic and OpenAI (user-requested AI processing), Apple, and Google (store purchase processing)
  • AI Services: Only when you request an AI feature, Firebase sends the selected input for processing. Amino chat questions, conversation history, and any context you choose to share for that conversation are sent to the provider for the Amino model you select: Anthropic's Claude API for Amino Model 1 (the default) or OpenAI's GPT-6 Luna API for Amino Model 2. Optional context can include active protocol and inventory details, recent doses, separately approved biomarker values, and a separately approved progress summary from your main profile (weekly weight averages, body measurements, blood pressure, glucose readings, mood and energy ratings, body fat estimates and symptom counts, without progress photos or notes), which can separately include synced Apple Health or Health Connect data such as sleep, heart rate, HRV and steps. Lab import, vial-label scan, and Body Fat Estimator remain processed by Anthropic's Claude API; selected files or photos and estimator form values are sent only when you request those features. The app shows feature-specific disclosure and consent before optional sensitive context or an image is sent. In SPT cloud mode, chat questions, response-source metadata, and feedback may be stored for quality and safety review. In device storage, chat usage logs omit question and answer text as described above. For provider data practices, see Anthropic's Privacy Policy and OpenAI's API data controls.
  • Shared Content: When you use the Share feature to share your inventory or protocols via link, a snapshot of that data is stored in a publicly accessible document. Only the data you explicitly choose to share is included.
  • Coach Mode: A client can establish one invitation-only Coach Mode connection and review encrypted setup revisions before applying them. Assigned dose logs are shared for relationship administration. Progress, biomarkers, and selected progress photos are shared only after the client enables the applicable category. The client can revoke optional sharing, pause, report, switch, or end the connection. Smart Peptide Tracker does not verify or endorse coach qualifications.
  • Webrequests: When you configure a Webrequest, Firebase relays selected event data to the HTTPS endpoint you choose. Depending on your subscriptions, a payload may contain account or profile identifiers and selected dose, protocol, inventory, or supply details. We store the configuration, encrypted endpoint headers, event payloads, and delivery diagnostics. Event and delivery records are normally removed after seven days, and the configuration and logs are deleted with your account. The destination operator receives the data under its own privacy practices. You are responsible for choosing and securing that destination.
  • Community Content: Reviews, templates, research programs, and peptide requests you submit are visible to other users. Display names are optional.
  • Consistency Ranks: Ranking publication requires SPT cloud research storage. If you opt in, we store a private 28-day ranking aggregate that can update automatically after your primary-profile records finish syncing, even when you do not open the Ranks page, and show signed-in members a server-created alias or, only if you choose to show it, your short account ID prefix (the same @ID shown in Tracker), plus your comparison group, adherence percentage, confidence-adjusted score, consistency badge, relative rank, kudos count, and optional account badge. If you show your @ID, other Ranks members can send you kudos; we keep a record of who sent kudos for up to two days, only to enforce daily limits, and never show senders. Protocol names, daily records, full account IDs, and partner-profile data are not shown. Taken, scheduled and skipped action counts, scheduled-day count and a bounded compound count are also shown. Compound names and daily traces remain private. Rankings are based on member-entered records and are not independently verified. You can leave at any time, which removes the public row and private ranking aggregate.
  • Health Reports: When you generate a PDF health report, the document is created on your device and is not uploaded to our servers. The PDF contains unencrypted personal data including protocol details, biomarker values, and optionally progress photos. You are responsible for how you share or distribute the exported report.
  • Legal Requirements: When required by law or to protect our rights
  • With Your Consent: When you explicitly authorize sharing

6. Your Rights and Choices

Depending on your jurisdiction, you may have the following rights:

  • Access: Request a copy of your personal data
  • Export: Export your data in JSON format (available in Settings)
  • Coach Mode Choices: Review each setup revision, control optional sharing and locks, revoke selected photo access, pause the relationship, report the relationship, or end it
  • Deletion: Delete your account and deletable account data, subject to the limited retention described below
  • Correction: Update or correct your personal data within the app
  • Data Portability: Receive your data in a structured, machine-readable format
  • Restrict Processing: Request that we limit how we use your data
  • Object: Object to certain types of data processing
  • Withdraw Consent: Withdraw previously given consent at any time
  • Analytics Choice: Analytics collection remains disabled unless you provide affirmative consent
  • Disable Notifications: Turn off push notifications in your device settings

To exercise these rights, use the Settings menu in the app, visit the Account and Data Deletion page, or contact us at the email below.

For California Residents (CCPA)

We do not sell your personal information as defined by the California Consumer Privacy Act. You have the right to know what data we collect, request deletion, and not be discriminated against for exercising your privacy rights.

For European Residents (GDPR)

Our legal basis for processing your data is: (a) performance of our contract with you (providing the Service), (b) your consent (for health data access and optional features), and (c) our legitimate interests (analytics, security, service improvement). Data processed through our account and SPT cloud services is transferred to and stored in the United States. Device workspace data stays on the selected device except for the backups and actions described above. Contact us for information about the safeguards applicable to international transfers of your data. You have the right to lodge a complaint with your local data protection authority.

7. Partner Add-on and Multi-Profile Data

The Partner Add-on allows you to manage inventory and protocols for additional people from your account. You are responsible for obtaining consent from any person whose data you enter into the Service. We process this data under the same security and privacy protections as your primary account data.

8. Data Retention

After server-confirmed account deletion, the app also clears that account's device workspace, local checkpoints, and recovery files on the device running the cleanup, including copies kept after returning to SPT cloud. Interrupted local cleanup is retried when the app can run it. We retain account data while your account is active. When you delete your account, authentication, encrypted sync data, separately stored account media, recovery snapshots, community records linked to your account, messages, AI logs and feedback, error logs, notifications, and other deletable account records are removed. Public share snapshots contain no account identifier and can remain accessible until their automatic expiration, no more than eight days after creation. Your public Consistency Ranks row stops being ranked a few days after your last update and is deleted automatically about 30 days after that. Your private ranking aggregate is retained while you remain enrolled. Leaving Consistency Ranks or deleting your account removes both immediately.

We retain only the records needed for physical-order fulfillment, refunds, tax, fraud prevention, legal duties, and store purchase replay protection. Purchase replay records are de-identified by removing the account user ID. A server-only deletion-safety tombstone containing the former internal account ID and deletion timestamps is retained to prevent cached sessions from recreating deleted data. When a referral account is deleted, one-way protected checkout identity signals and unresolved referral debt or review status may be retained for up to seven years to prevent repeated reward abuse. These protected signals are not displayed to other users. Aggregated information that no longer identifies you may also be retained.

For Coach Mode, terminal invitations are removed after seven days. Revoked encrypted sharing data and selected-photo objects are removed within 24 hours. Superseded encrypted revisions, ended-relationship encrypted content, and deleted coach-note ciphertext are removed after 30 days. Export audit metadata is retained for 12 months. Non-sensitive relationship, assignment, billing, and report audit metadata may be retained for up to 24 months unless a documented legal hold applies. Ending or deleting an account revokes detailed access immediately while scheduled cleanup completes.

9. Children's Privacy

The Service is not intended for users under 18 years of age. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new policy within the app and updating the "Last updated" date. Where a change requires your consent, we will request it before using your information for that new purpose.

11. Contact Us

Email: