Privacy Policy
Effective October 3, 2026
The short version.
Bolo collects what it needs to track your food: your sign-in email or phone number, what you tell it about yourself and your goals, and the meals, photos and messages you send. We use that to run Bolo for you. We don’t sell it, we don’t use it for ads, and we don’t use your meal photos, messages or food logs to train AI. We route AI requests to providers with no-training policies. You can export it or delete it at any time.
Who we are
Bolo (“Bolo”, “we”, “us”) makes the Bolo app and this website, textbolo.com. Questions about this policy or your data: hello@textbolo.com.
What we collect
- Account details: the email address or phone number you sign in with. If you use Sign in with Apple or Google, we receive the email address they share with us (Apple lets you hide your real one).
- What you tell Bolo about yourself: your first name, your goal, your daily calorie and macro goals, units, and, only if you choose to give them, your age, sex, height, weight and activity level.
- Your food log: photos you choose to send, descriptions and messages you type, barcodes you scan, and the estimates, corrections and edits that result, with their dates and times.
- Onboarding answers: your answers to the first-run questions (for example what matters to you, whether you’ve tracked food before, how you heard about Bolo), which version of those questions you saw, and whether you allowed camera access.
- Technical information: your device’s time zone (so your days start at midnight), the app version, and standard server logs such as IP address and request times that our hosting providers keep for security and debugging.
- Notifications: if you allow them, a push token for your device, so Bolo can send mealtime nudges and the occasional check-in. They’re timed from when you usually log, and never say what you ate. Turn them off in Settings → Notifications or in your phone’s settings.
- Usage and crash data: which screens and features you use (for example “logged a meal by photo”, “opened the weekly recap”), how long Bolo took to answer, which version of an experiment you saw, and error and crash reports with your device model and OS version. It’s tied to a random account id, never to your name, email or phone number, and it never includes your photos, what you ate or what you typed. You can turn it off in Settings → Share usage data.
- Support reports: descriptions you voluntarily send, an optional reply email, app and device details if you include them, and a link to the food entry if you report from it. Photos and chat are not automatically attached. Reports are stored with your account and deleted when you delete it.
- Previous early-access sign-ups: if you previously joined the waitlist, we may still hold the email address you supplied. The launch website no longer collects waitlist sign-ups.
We don’t collect your location, contacts, or anything from your photo library other than the photos you pick. The app has no advertising and no advertising or cross-app tracking SDKs; the only analytics tool is PostHog, described above and below. This website sets no cookies.
How we use it
- To run Bolo: estimate your meals, keep your daily totals, goals, history and streaks, and answer your messages.
- To sign you in and keep your account secure, including sending one-time sign-in codes.
- To improve Bolo in aggregate, for example comparing how two versions of a screen perform, seeing where people get stuck, and finding and fixing crashes. We look at patterns, not at your individual meals.
- To contact you about your account or respond to your requests. If you previously requested launch updates, we may send the update you asked for. No marketing email unless you ask for it.
- To investigate problems and respond to support reports you send us.
- To prevent abuse and meet legal obligations.
Photos, AI and training
Bolo does not use your meal photos, messages or food logs to train AI models. To estimate meals, make corrections, interpret goals and prepare summaries, we send the relevant content through OpenRouter to a model provider. We configure requests to exclude providers that allow training on submitted content. The app explains this and asks for your agreement before sending your content to AI services.
No-training policies do not necessarily mean zero retention. AI providers may retain content for security or compliance under their policies. Retention depends on the selected endpoint and account settings. Bolo stores your food log to provide the app’s features; you can export your food log or delete your account in Settings.
OpenRouter has separate controls for prompt logging and use of inputs and outputs. Our policy is to keep optional input/output logging and content-use opt-ins disabled. OpenRouter may retain request metadata, such as token counts and response times. Nutrition values are estimates and may be inaccurate; see the Terms.
Who processes your data for us
We use a small number of service providers who process data to provide their services, under the policies and settings described here:
| Provider | What for |
|---|---|
| Supabase | Database, private photo storage, and sign-in (including sending email codes) |
| Railway | Hosting the Bolo server |
| Expo (and Apple / Google push services) | Delivering notifications to your device (a device token and the nudge text, never your food) |
| OpenRouter and the model providers it routes to | Processing meal estimates, corrections, goals and summaries under no-training policies; retention is described above |
| Twilio | Sending sign-in codes by text message |
| PostHog | Usage statistics, error and crash reports, and experiments (no photos, meals or messages; you can opt out in Settings) |
| Apple, Google | Only if you choose Sign in with Apple or Google |
| Vercel | Hosting this website |
If we add a paid plan, purchases are handled by Apple through the App Store; we never see your card details.
What we don’t do
We don’t sell your personal information, share it for cross-context behavioral advertising, or give it to data brokers. We’d only disclose it if the law requires it, to protect someone’s safety, or as part of a merger or acquisition, in which case this policy would continue to apply and we’d tell you first.
How we protect it
Data is encrypted in transit (HTTPS) and at rest. Photos live in private storage and are only ever shown through short-lived links to your own account. Access to production systems is limited to the people who run Bolo.
How long we keep it
We keep your data while your account exists. Deleting a meal deletes its photo. Deleting your account (Settings → Delete account) removes your profile, meals, photos, messages, support reports and sign-in identity from our active systems. Backup copies may remain until they expire under our providers’ retention schedules. Previously collected waitlist emails are kept until you ask us to remove them or we no longer need them. We no longer collect new waitlist sign-ups on the website.
Your choices and rights
- Access and export: Settings → Export my data gives you every entry as a CSV file.
- Correct: edit any meal, your name, your goals and your answers in the app.
- Delete: delete a meal, or your whole account, in the app, or email us.
- Permissions: camera access is optional and can be turned off in your phone’s settings; you can still log by describing meals or choosing a photo. Bolo doesn’t ask for access to your photo library: your phone’s picker hands over only the photo you choose.
- Usage data: Settings → Share usage data turns usage statistics and crash reports off.
Depending on where you live (for example California, the EU or the UK), you may have further rights, such as to object to or restrict processing or to complain to a regulator. Email hello@textbolo.com and we’ll respond within 30 days. We won’t treat you differently for exercising them. Where the law asks for a legal basis, we rely on performing our contract with you (running Bolo), your consent (optional details and permissions, which you can withdraw), and our legitimate interest in keeping Bolo secure and improving it.
Health information
What you eat and details like your weight are personal. We treat them as sensitive: they’re used only to run Bolo for you, never for advertising. Bolo is not a medical service or a healthcare provider.
Children
Bolo isn’t meant for children under 13, and we don’t knowingly collect their data. If you believe a child has given us information, email us and we’ll delete it.
Where data is processed
Bolo’s providers process data in the United States and the European Union. If you use Bolo from elsewhere, your data will be transferred there, with the protections described in this policy.
Changes
If we change this policy in a way that matters, we’ll tell you in the app before it takes effect. The date at the top shows the latest version.