We’re a small team. The fastest way to get help is to email us, since we read every message.
Typical response time: within 2 business days.
A few common questions answered upfront so you can move quickly:
Most often this is a wrong-account issue. Abello stores everything scoped to the email you signed up with. Sign out and sign back in with the correct email, and your data will reappear.
If you’re certain the email is right and the data is still missing, email us with:
We don’t process billing directly. Apple App Store and Google Play do. Cancel from your device:
Cancelling stops future charges. You keep your current tier’s access through the end of your current paid period.
Refund requests go through the platform you bought on:
We can’t process refunds on Apple’s or Google’s behalf. If a charge looks like fraud, contact us at contact@abello.app and we’ll help where we can.
In the app: Profile → Delete account. This permanently removes your account and all associated data (pets, vehicles, homes, meal plans, records). The action is irreversible.
If you also have an Abello+ subscription, you’ll need to cancel that separately through Apple or Google (see above). Deleting your Abello account does not stop App Store / Google Play billing.
Profile → Export my data writes a JSON file with everything we hold about your account: profile, grocery preferences, meal plans, pets and their records, vehicles and their service history, home and maintenance tasks. The share sheet lets you send it to Notes, Mail, Files, Drive, or anywhere else.
Each plan has a different monthly cap on grocery AI generations:
The counter resets on the first of each month. Once you hit the limit you can:
AI outputs in Abello (meal plans, recipes, macro estimates, vet prep, vehicle assistant, home assistant) are informational only and can be inaccurate. They are not a substitute for a licensed professional. Confirm dosing and diagnoses with a vet, safety-critical car issues with a mechanic, and electrical / gas / structural work with a licensed pro. See our Terms for the full AI disclaimer.
If a specific output was alarmingly wrong (not just imperfect), please email us. That kind of feedback helps us improve the prompts.
Reminders are local to your device. We don’t send remote push. Check:
If the toggle is on and notifications are allowed but reminders still don’t fire, email us with the type of record (pet vaccine, service, maintenance task) and the due date you expected to be reminded about.
Please email contact@abello.app with:
A screenshot helps a lot.
Right of access, deletion, correction, portability: all go to contact@abello.app. Reference our Privacy Policy for the rights available to you depending on where you live (GDPR, CCPA, etc.). We respond within 30 days.
We try to make AI behavior predictable instead of black-box. Here’s exactly how your preferences translate into what the AI plans for you.
When you tap a chip like Low-carb or Keto in Preferences, the AI receives concrete macro ranges, not just the label, and not a single threshold either. Every macro is a min/max range so the AI has room to find the cheapest combination inside your nutritional tolerance. The mapping lives in the public source code at constants/dietPresets.ts:
| Diet | Net carbs (g/day) | Protein (g/day) | Fat (g/day) |
|---|---|---|---|
| Keto | 0–30 | 80–200 | 50–250 |
| Low-carb | 0–100 | 100–200 | 30–150 |
| Paleo | 0–400 (wide) | 50–250 (wide) | 20–200 (wide) |
| Vegetarian / Vegan / Gluten-free / Dairy-free / Nut-free | 0–400 (wide) | 50–250 (wide) | 20–200 (wide) |
“Net carbs” means total carbs minus fiber, matching the convention on nutrition labels and what most low-carb / keto communities use. The “wide” ranges on food-rule-only diets are effectively unconstrained; they exist so the AI always sees real numbers, not a missing field.
Each diet also has explicit food rules sent verbatim to the AI. For example, Keto sends: “No grains, no sugar, no starchy vegetables (potato, corn, peas), no most fruits (small portions of berries OK). Heavy on meat, fish, eggs, leafy greens, low-sugar vegetables, full-fat dairy, nuts, and healthy fats.”
If you fill in a number under Macro ranges (optional), that number wins over the preset’s default, even if your override is less restrictive. min and max are independent: you can override just the max and keep the preset’s min, or vice versa.
The food rules from the preset stay in force; only the numbers change.
Ticking both Low-carb and Vegan gives the AI: vegan food rules (no animal products) + low-carb’s macro ranges (0–100g net carbs, 100–200g protein, 30–150g fat). For numeric conflicts between presets, the more restrictive bound wins on each side independently (highest min, lowest max).
The Preferences screen shows a min and a max. The AI plans meals to land between those bounds. Filling in just one collapses to an exact target.
Priority order the AI follows:
Because macros are RANGES, the AI is told to land at the cheaper end of each range when budget is tight. For protein that usually means at the lower bound (less meat = less cost); for carbs and fat it picks whatever combination fits cheap commodity ingredients (ground turkey 93%, eggs, lentils, cabbage, frozen veg).
If the AI genuinely can’t fit your budget even at the cheap end of every range, it generates the closest possible plan AND adds a note to the prep tip at the bottom of the plan. For example: “Est. $193 is $43 over your $150 budget; adjust quantities or upgrade your plan to fit.” Honest disclosure, not a silent failure.
When estimating grocery costs, the AI defaults to discount-supermarket prices (Walmart, Aldi, Kroger store-brand), not Whole Foods, not organic. Anchor prices include:
Setting a Preferred store in Preferences shifts these anchors: Whole Foods / Erewhon marks them up; Aldi / Trader Joe’s brings them down 10-20%.
Only your country, state/region, and approximate age (computed from birth year) are sent to the AI alongside the specific module data for your request. Your name, email, and phone are never sent. See our Privacy Policy §3 for the full AI privacy contract.
The source code is the canonical reference:
constants/dietPresets.tssupabase/functions/generate-meal-plan/index.ts (see GROCERY_STAGE_1_SYSTEM and GROCERY_STAGE_2_SYSTEM)lib/claude.ts (buildUserContext)If anything here doesn’t match what you see in the app, that’s a bug. Email contact@abello.app.
We’d love to hear what works, what doesn’t, and what you’d like to see next. Feedback is read and noted.