May 1, 2026

Welcome to Allerwise

When we set out to build Allerwise, the brief was small and stubborn: scan a barcode, get a clear answer in seconds, and never make you worry about an account, a subscription pop-up, or a tracker watching what you eat.

What the app does

You set up a profile — a name and the allergens you avoid. You point your phone at a product barcode. Allerwise pulls the ingredient list from Open Food Facts and checks it against your profile. You get one of three answers:

• Safe — none of your allergens were found.
• Caution — the label says “may contain traces of” something you avoid.
• Avoid — the product directly contains an allergen on your list.

That’s it. No score. No long article. No upsell mid-result.

What’s local

By default, your profile, your scan history, and your favorites live in a small SQLite database on your phone. We don’t have a server collecting this data, because we don’t have a server, period — every meaningful operation runs on your device.

What goes to the network

Two things, only when needed:

• Open Food Facts receives a request that contains a barcode and the kind of metadata every HTTPS request carries (your IP, a user-agent). It does not receive your profile.
• RevenueCat and the App Store / Play Store are involved only if you choose to upgrade to Pro. They handle billing and entitlement; we just check whether your subscription is active.

What’s next

We’re working on shareable allergen cards (so a parent can hand a babysitter a clear “what to avoid” sheet), more allergen presets, and a few more languages. We’ll keep posting here as those land.

If you have feedback, write to [email protected]. We read every email.