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

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

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:

ProviderWhat for
SupabaseDatabase, private photo storage, and sign-in (including sending email codes)
RailwayHosting 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 toProcessing meal estimates, corrections, goals and summaries under no-training policies; retention is described above
TwilioSending sign-in codes by text message
PostHogUsage statistics, error and crash reports, and experiments (no photos, meals or messages; you can opt out in Settings)
Apple, GoogleOnly if you choose Sign in with Apple or Google
VercelHosting 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

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.

Contact

hello@textbolo.com