Privacy Policy
Last updated: September 26, 2026
HitThree ("HitThree", "we", "us") is a phone-first progressive web app at www.hitthree.com that helps adults log calories, protein, activity burn, and related targets. This Privacy Policy explains what we collect, why we collect it, how we use it, and the choices you have. By using HitThree you agree to this policy. Our Terms of Use cover additional rules for using the service.
Nutrition and body metrics can be sensitive. We treat your logging and profile data carefully and do not sell it.
Who operates HitThree
HitThree is operated by Jason Peters. For privacy questions, access requests, correction requests, or deletion requests, email jkbsllco@gmail.com.
What we collect
- Account & authentication. Email address and auth credentials handled by Supabase Auth. You can sign in with a magic link or a password. We receive session tokens and related auth metadata needed to keep you signed in securely.
- Profile. Details you choose to provide, such as display name, date of birth / age, sex, height, weight, goal weight, body-fat percentage (BF%), activity level, timezone, and preference settings.
- Food & burn logs. Daily food-ledger entries (calories, protein, meal items/notes), burn / activity logs, weigh-ins, and related targets or rolling deficit metrics computed from that data.
- Saved meals. Named meal templates and items you save for reuse.
- Communications. Transactional email (for example magic links and account messages) sent through Resend on our behalf. Message content and delivery metadata may be processed by that provider.
- Technical data. Basic server and security logs (approximate timing, request paths, error diagnostics). Optional error monitoring (for example Sentry) may be enabled to keep the service reliable. We do not use advertising cookies or sell analytics to third parties.
- Optional integrations (if enabled later). If you connect a wearable or other integration (for example Garmin), we may store encrypted tokens and sync burn or related metrics you authorize. Those features will only run with your consent when available.
How we use data
- Provide core logging, targets, rolling 7-day deficit views, and saved meals.
- Authenticate you and secure your account.
- Send transactional email needed for sign-in and account operations.
- Apply safety guardrails (for example 18+ eligibility and soft intake-floor messaging). These are product features, not medical care.
- Debug outages, prevent abuse, and improve reliability.
- Respond to your privacy or support requests.
We do not sell your personal information, and we do not share it with advertisers. We do not use your health or logging data for third-party marketing.
Legal bases & regional notes
HitThree is primarily offered to users in the United States during private beta. Depending on where you live and how the product evolves, consumer privacy laws and health-data rules (for example certain U.S. state consumer-health-data laws, the FTC Health Breach Notification Rule, or GDPR/UK GDPR for EU/UK residents) may give you additional rights. Contact us at the email above to exercise access, correction, deletion, or other applicable rights. We will respond within a reasonable time and as required by law.
Where data lives & who helps us
- Supabase — Postgres database and authentication, with row-level security so your rows are scoped to your user id.
- Cloudflare Workers — hosts the HitThree application edge. Product health data is stored in Supabase, not in Cloudflare KV, D1, R2, or Durable Objects.
- Resend — transactional email delivery (magic links and account mail).
- Optional monitoring — error/performance tooling such as Sentry may receive limited technical diagnostics when enabled.
These providers process data only to run HitThree for us. Secrets and service credentials stay in environment configuration / a secrets manager — never bundled into the public client beyond public keys.
Retention
We keep your account, profile, and logs while your account is active so the app can show history and trends. If you ask us to delete your account, we will remove or irreversibly de-identify your personal account data within 30 days of a verified request, except where we must retain limited records (for example abuse prevention, security logs, or legal obligations) for a longer period. Backups may take a short additional time to expire.
Your choices
- Update profile and settings in the app.
- Request a copy / export of your data by emailing jkbsllco@gmail.com (CSV or equivalent export as available).
- Request account deletion at the same address; we aim to complete hard delete within 30 days of verification.
- Turn off reminders or notifications when those features are enabled.
- Disconnect optional integrations when offered.
Security
We use industry-standard measures appropriate for a small consumer app: encrypted transport (HTTPS), authenticated sessions, database row-level security, and restricted operator access. No method of transmission or storage is 100% secure. Please use a strong unique password if you choose password sign-in, and protect access to your email inbox used for magic links.
Children
HitThree is for adults 18 years of age or older only. We do not knowingly collect personal information from anyone under 18. If you believe a minor has created an account, contact us and we will delete it.
Not medical advice
HitThree is a logging and planning tool. It does not provide medical advice, diagnosis, or treatment. See our Terms of Use for related disclaimers.
Changes
We may update this Privacy Policy from time to time. The "Last updated" date at the top will change when we do. For material changes during private beta we will also try to notify active users in-app or by email when practical. Continued use after an update means you accept the revised policy.
Contact
Privacy requests and questions: jkbsllco@gmail.com. Operator: Jason Peters. Service: HitThree / www.hitthree.com.
Policies may be updated as the product evolves. Independent counsel review is recommended before a broad public launch. This page is not legal advice.