Privacy policy
At a glance
- Pavelo is built local-first. Your stack, logs, notes, and reminders live on your phone.
- No account needed. If you turn on sync, you sign in with Google and we keep an encrypted copy we cannot read.
- Coach and the label scan are optional and ask first. Nothing is sent until you agree, and the consent screen says what goes out.
- AI requests go through our server, which doesn't pass your IP address to Anthropic. What you send can still contain personal information.
- Usage statistics are off unless you turn them on. They are plain counts, with no supplement names, times or notes.
- We don't sell your data, and we don't use third-party tracking or ad SDKs.
- Uninstalling wipes the app's data from your phone, but not backup files you saved elsewhere or a synced copy on our server. If sync was on, delete that copy in the app first.
What lives on your device
Everything that defines your day lives in the app's local database:
- Everything you track, with its doses, schedules, and reminder times
- Daily check-offs
- How-you-felt check-ins and journal notes
- Your profile name and photo, settings and preferences
- Backups you keep on the phone (the app keeps the five most recent in each backup folder)
- A random app identifier, used for AI request and report limits and subscription status. It is never sent with optional usage counts.
Nothing in this list ever leaves your phone unless you use one of the features below.
Sync and your account
Pavelo works fully without an account. Sync is optional: it keeps an encrypted copy of your data on our server so your other devices can pick it up.
- Off until you set it up. You sign in with Google and choose to turn it on. An app update never switches it on or off.
- What we can't read. Your records are encrypted on your phone before they leave, with a key only your devices hold.
- What we can see. Your Google account identifier, and housekeeping details of each record: type, size, when it changed, whether it was deleted. Signing in sends us the token Google gives your phone. It includes your email address, your name and a link to your profile photo. Our server checks the token and keeps only your account identifier. Cloudflare, which hosts the service, sees your IP address, as with any internet request.
- Signing in. Google confirms it is you, under its own privacy policy. Your phone keeps a sign-in credential for up to 180 days, renewed while you use sync.
- Your recovery key. The app shows it the first time you turn sync on. Keep it safe, because we cannot recover it or read your copy. Supported Android phones also keep recovery material in the app's backup and in Google's Block Store, but that depends on your device and backup settings, so don't count on it. A phone that already syncs can show the key again.
- Deleting it. The copy stays until you delete it. Signing out or uninstalling does not remove it. Settings → Sync → Delete synced copy removes the encrypted records and keys, or you can ask by email (see Delete your account). Your phone keeps its own data. Our cloud provider's recovery copies can outlast the deletion for as long as its retention rules allow.
- Kept apart. Sync sends nothing to Coach or Anthropic. Pavelo Dev, the test build, uses its own separate sync and statistics storage.
What we send to a server, and why
Coach and the label scan run on Claude, made by Anthropic. The first time you use one, the app asks your permission and lists what will be sent. If you decline, nothing goes out.
- Coach chat. Your message with the rest of the last 10 messages in the chat; your stack (names, doses, routines, supply left, how you rated each); your routine and reminder times; today's date; short summaries of your consistency and check-ins; and the Coach profile fields you filled in (age range, sex, body details, diet and sleep, conditions, notes, goals). Never your journal notes. The medicines you list in your Coach profile are never sent, and their names are taken out of your conditions and notes. Coach is told only that you take medicines it can't see. Pavelo is for supplements, and your stack is sent as you entered it, so a medicine you added to it is sent too.
- Routine check. Your stack (names, doses, forms, routines, food timing, how often) and the profile fields you filled in except body details and the medicines you list, so Coach can propose a tidier daily arrangement. As-needed supplements stay on the phone.
- Coach's read. A read each Monday, monthly on a month's first Monday and weekly otherwise. It starts as numbers worked out on your phone: consistency, streak, days logged, check-in counts, the feelings you tagged most, how you rated each supplement and the one whose consistency changed most. When you open the read, these go to Claude to write it. Never your notes.
- Label scan. First, the front and back photos of the label go to Claude to read the brand, product name, dose and ingredients. Then our server looks the product up in two public databases, listed below, by the barcode your phone reads with Google ML Kit or by its brand and name. Last, the product details, your stack, your age range and your goals go to Claude for the result you see.
The Stack Map, Stack check and doctor report are made on your phone. Nothing is sent to make them. One exception: app version 0.7.4.1 and earlier still ask Claude to write a short summary for the doctor report. They send summary numbers from your log and the names of your most and least consistent supplements, never your name.
AI requests travel through our server. We do not forward your device's IP address, AI metering identifier or purchase token to Anthropic. The content itself can contain personal information, including anything you type into Coach or include in a photo. These requests are not guaranteed to be anonymous.
Our server reads the country and region of each AI request from its IP address. It uses them to check that Coach and the label scan are offered there, and to choose which crisis lines Coach shows. If the request comes from the Philippines, Coach chat can also be told so, to point you to local care. Our server doesn't store the country or region.
Our server counts requests by IP address and by app identifier to apply its limits. It keeps the whole IPv4 address, or the first half of an IPv6 address, for up to 48 hours after the last request from that address. Counts tied to the app identifier expire 2 hours to a year after their last use, depending on the count. A free label-scan count made by an older app version never expires. Database recovery backups can hold an address or app identifier up to 30 days more.
Saying no to AI stops those requests and nothing else. Crash reports, feedback, sync and usage statistics are separate, and each has its own section on this page. Checks for app updates and downloads of supplement facts carry none of your records.
Optional usage statistics
Usage statistics are off until you turn them on, in every country. The tracker works exactly the same either way.
- Only a yes counts. You say yes from an invitation in the app or in Settings. Signing in, turning on Sync, finishing setup or closing a message never counts. An update keeps your choice.
- What is counted. App opens, progress views, scans started, scan results shown, failed scans, scan results saved, plan views and share files prepared. A phone adds at most one app open and three of each of the others per UTC day.
- The reminder check. Once it is switched on for your release, a phone also sends one reminder check a day. It says whether this week's reminders arrived (missed or late, in ranges: none, one, two or three, four or more), the phone's brand family and Android version range, and its reminder settings: whether reminders are working, exact alarms, battery optimization, app standby, the full-screen permission and whether a routine is set to ring. It has no times and no routine or supplement names.
- What is never sent. Supplement names, doses, schedules, check-offs, notes, photos, barcodes, Coach messages, account or payment details. Nothing from before you said yes.
- No identity. No installation ID, no session ID, nothing that follows a phone from day to day. A count carries its name, the day, a random one-time receipt, the policy version and an opt-in marker (the reminder check also carries the ranges and settings above), then joins a weekly total. We can't tell from it how many people use Pavelo.
- How it travels. Counts go to our own service on Cloudflare, which sees an IP address as with any internet request, so we don't call this anonymous. This service stores no IP addresses, user agents, location or region, and its request logging is off. A short-lived daily hash of the address limits abuse. Counts are never used for advertising.
- How long we keep it. Weekly totals stay up to 12 months, delivery receipts up to three days. Database recovery backups can hold older contents up to 30 days more. Counts waiting on your phone expire within two UTC days.
- Turning it off. Collection stops and anything not yet sent is cleared. A count already in a weekly total can't be taken back out, because nothing ties it to your phone.
- If you ran an earlier preview. One preview build kept usage history linked to an installation. The update first asks our server to delete it, and Settings shows a retry if that fails. Anything left, the deletion receipt included, is gone within 120 days.
Who processes data for us
These are the services that handle data for us, each only for the purpose listed. An AI request can contain details of your stack. A usage count never does.
- Anthropic (Claude), in the United States. Processes the content sent for the AI feature you choose. Its standard API policy retains inputs and outputs for up to 30 days. Different contractual terms, certain services or models, safety enforcement and legal requirements can change or extend retention. We do not promise zero retention. Current policy: privacy.claude.com.
- Cloudflare. Runs our server. It stores request counts, optional usage statistics, AI-text reports when Sentry isn't active, and, if you turn on sync, your encrypted copy, which neither Cloudflare nor we can read.
- US National Institutes of Health (Dietary Supplement Label Database). Our server sends it the barcode, or the brand and product name, during a label scan.
- Open Food Facts. Our server sends it the barcode number during a label scan, nothing else.
- Sentry (EU region). Receives crash reports, feedback and AI-text reports you send.
- Google sign-in and Android backup services. Handle optional account sign-in and recovery material on supported Android devices.
- Google Play Billing. Handles your subscription if you upgrade to Pro. We never see your payment details.
Subscriptions
If you upgrade to Pavelo Pro, the purchase runs through Google Play Billing. Google notifies us whether your subscription is active. Subscription verification is separate from optional usage statistics.
Sharing from the app
When you share a Stack Map image or send a backup copy somewhere, Pavelo prepares the file on your phone and hands it to Android's share sheet. Where it goes from there is your choice, and we don't see it.
Crashes and feedback
Crash reports and feedback go to Sentry. We don't use Crashlytics.
- Crash reports. When the app crashes or recovers from an error, the report carries the error and where it happened, a short trail of recent screens and app events, the app version, the Android version and the phone's make and model. Page addresses lose their names (a "Magnesium" page becomes
/supplement/<redacted>). No console logs, session tracking or screen recording. - Crashes in Android code. Sentry's Android library reports these and can add its own random ID for the phone and more device details.
- Feedback. Settings → Send feedback sends your message and the app version, only when you tap Send.
- AI-text reports. The Report button under AI-written text sends that text, where it appeared and the app version. If Sentry isn't active in your build, our server keeps the report for 90 days instead. That request also carries the app identifier, used only for a daily report limit and never stored with the report.
What we never do
- No third-party tracking or advertising SDKs. No Google Analytics, Facebook SDK, ad networks, or data brokers.
- We never sell your data or share it for advertising. The service providers listed here process data for the purposes described in this policy.
- No location tracking. Our server reads the country and region of AI requests, as described above, and doesn't store them.
- No access to your contacts or calendar. Pavelo sees only the photos you take or pick for a label scan or your profile.
- No device fingerprinting.
Permissions Pavelo asks for
Each one is asked for when a feature needs it:
- Notifications. For the reminders you set. Your phone asks when you finish setup with reminders on, or later when you turn them on.
- Camera. None. A scan opens your phone's camera app, and only the photos you take come back.
- Alarms & reminders. So reminders and the alarm go off on time. Without it, reminders can come late and an alarm rings as a normal reminder.
- Full-screen alarm. So a reminder you switch to Alarm can ring over the lock screen. Never used for regular reminders.
- Foreground service while ringing. Keeps the alarm sound playing while it rings, for about 5 minutes at most. It stops when you answer or when the ring ends.
- Battery optimization exemption. So reminders fire reliably on aggressive battery savers. Optional but recommended.
Your data, your control
- Back up. Settings › Backup. Keep a backup on your phone, save or send a copy, and restore it in the app. Your statistics choice, counts waiting to send and the old deletion credential are left out of backups.
- Delete. Settings › Danger zone › Clear all data removes your supplements, history, reminders, milestones and settings from your phone. A switch there also deletes the backup files and report PDFs Pavelo saved; it is off unless you turn it on. If sync is on, Settings → Sync → Delete synced copy removes the encrypted server copy. Do this before you uninstall, because an uninstalled app can't send it. Usage statistics have their own controls, above.
- Decline AI. Tap "Not now" and that AI request is not sent. The app asks again the next time you open that feature. Settings › Coach and label scan turns each one off at any time. This choice has nothing to do with usage statistics, crash reporting or the other network services above.
Children
Pavelo is built for adults. The app is designed and listed for people 18 and over, and we don't knowingly collect data from anyone younger.
Changes to this policy
If we change the policy, the date at the top updates. The current version always lives at pavelo.app/privacy, and the app links to it from Settings.
Contact
Questions, concerns, or requests: support@pavelo.app.
Operator: Rudolf Arthur H., based in the Philippines.
See also: Terms of service.