Daymarkr
Features Terms Support

Effective date: May 25, 2026

Privacy Policy

This Privacy Policy explains how Daymarkr collects, uses, shares, and protects information when you use the Daymarkr mobile app, website, and related services.

Contact

If you have questions about this Privacy Policy or your data, contact us at support@daymarkr.com.

What Daymarkr Does

Daymarkr is decision-support software for people tracking peptide-related records. Daymarkr is not medical advice, diagnosis, treatment, prescribing, pharmacy, telehealth, or emergency care.

Information We Collect

Account Information

We collect information needed to create, secure, and manage your account, such as email address, authentication identifiers from Apple, Google, or Supabase, account settings, onboarding choices, agreement acceptance, and subscription state.

Health and App Records You Enter

Daymarkr stores records you create or upload so the app can provide private tracking, calculations, timelines, interpretation context, and export features. This may include protocols, stack items, vial records, inventory, dose events, reminders, symptoms, notes, body metrics, medical context, progress metrics, lab uploads, lab result rows, lab interpretation output, vial label photos, lab report files, COAs, vendor verification inputs, community protocol posts, content reports, saved items, and related moderation records.

Apple Health Data

If you choose to connect Apple Health, Daymarkr requests read-only access to selected data types such as weight, body fat, steps, active energy, workouts, sleep, HRV, and resting heart rate. At launch, Daymarkr does not write data back to Apple Health. You can change Apple Health permissions in the Apple Health app or iOS Settings.

Photos and Files

Daymarkr may access photos or files that you choose for vial labels, lab reports, COAs, and progress tracking. Progress photos are designed to stay local on your device and are not uploaded as image bytes for community features. Some other selected files, such as lab reports, vial photos, and COAs, may be uploaded to support app functionality.

Analytics and Diagnostics

We collect limited product analytics and diagnostic information to improve reliability and understand feature usage. This may include screen and feature events, subscription and quota events, crash, error, and performance diagnostics, and device and app metadata needed to debug issues.

Daymarkr is designed not to send peptide names, vendor names, exact dose values, lab marker values, personal notes, photo paths, COA paths, email addresses, or raw route identifiers through product analytics events.

Push Notifications

If you enable push notifications, we store push tokens and delivery records needed to send and audit notification delivery, such as watched-vendor status alerts.

How We Use Information

We use information to provide, maintain, and secure Daymarkr; sync account records across devices; run calculators, timelines, reminders, interpretation, export, and privacy features; process lab uploads and vial recognition; manage subscriptions and entitlement access; send push notifications you enable; send product lifecycle emails; collect product feedback, roadmap votes, and changelog interactions when you open those tools; respond to support requests; detect abuse; protect integrity; support moderation; and improve reliability, safety, and product quality.

AI and External Processing

Some features may send user-selected content, such as lab reports or vial label images, to third-party AI providers to extract structured information. Daymarkr uses this processing to return app functionality, not to sell user data or target advertising. Do not upload content you do not have the right to process.

Third-Party Services

Daymarkr may use these service providers: Supabase for authentication, database, storage, and Edge Functions; Apple Sign In and Google Sign-In for authentication; RevenueCat and Apple App Store for subscriptions, purchases, purchase restoration, and entitlement status; PostHog for product analytics; Sentry for crash and error monitoring; Loops for product lifecycle email contact sync and lifecycle email events; UserJot for in-app feedback, roadmap voting, changelog interactions, and signed feedback identity; OpenRouter and model providers for AI-assisted lab parsing and vial recognition; Expo and Apple Push Notification service for push notifications; and Apple HealthKit for read-only health data access when you authorize it.

These providers process information on our behalf or as needed to provide their services. We do not sell personal data.

When you open UserJot-powered feedback tools, Daymarkr shares your email address and a signed identifier derived from your Daymarkr user ID so feedback can stay connected to your account.

Community and Shared Content

If you publish a community protocol or similar shared content, that content may be visible to other users. Health logs, dose history, lab uploads, body metrics, progress photos, vial photos, COAs, and vendor lab-test uploads are not automatically posted to community surfaces. Content reports are stored privately for moderation review.

COA and Verification Retention

Daymarkr may retain COA records and related verification materials for anti-manipulation, audit, safety, and forensic continuity, even after account deletion. This helps protect public or shared verification surfaces from abuse.

Account Deletion and Data Export

You can export data and request account deletion from within the app. Account deletion is designed to remove your account, authentication record, private account data, private storage objects such as lab uploads and vial photos, and subscription customer data where supported by the provider. Some records may be retained when necessary for legal, security, anti-abuse, moderation, payment, backup, or integrity reasons, including COA and verification records described above.

When supported by the provider, account deletion also attempts to remove third-party lifecycle contact records such as Loops. UserJot feedback records may need separate dashboard or support removal when provider-side deletion is not exposed through Daymarkr's app API.

Your Choices

  • Update Apple Health permissions in iOS Settings.
  • Decline or disable push notifications in iOS Settings.
  • Export your Daymarkr data from the app.
  • Delete your account from the app.
  • Manage or cancel subscriptions through your Apple account.
  • Contact us at support@daymarkr.com for privacy questions.

Data Security

We use technical and organizational measures designed to protect personal information. No system is perfectly secure, and we cannot guarantee absolute security.

Children

Daymarkr is not intended for children. The app is expected to be submitted with a 17+ age rating due to health and medical-adjacent content.

International Users

Your information may be processed in countries other than where you live. By using Daymarkr, you understand that information may be transferred and processed where we and our service providers operate.

Changes

We may update this Privacy Policy. We will update the effective date when changes are made. Material changes may also be communicated in the app or on our website.

Privacy links

Use this page as the App Store Connect Privacy Policy URL.

Privacy choices Terms of Use Contact support
Daymarkr Daymarkr is decision support. It is not medical advice, diagnosis, or treatment. © 2026 Daymarkr. All rights reserved.

Primary

Home Support

Legal

Privacy Policy Terms of Use Contact