Legal
Privacy policy
Last updated: September 2, 2026
The short version, which will never change: your meal and symptom logs belong to you. We do not sell your health data, we do not use it for advertising, and you can export or delete everything at any time.
1. Who we are
AllerPrism ("AllerPrism", "we", "us") is a wellness application that helps you log meals and symptoms and spot patterns in your own data. This policy explains what we collect, why, who we share it with, and the rights you have over it. It applies to the AllerPrism mobile apps, the web app at app.allerprism.com, and this website.
AllerPrism is not a medical device and does not provide medical advice, diagnosis or treatment. For anything health related, talk to your doctor.
2. Data we collect
We collect only what the product needs to work:
- Account data. Email address, display name, and authentication identifiers. If you sign in with Google (or Apple, where offered), we receive the identifier and email those providers share.
- Health-adjacent log data you create. Meal photos, detected and corrected food entries, portion notes, symptom check-ins (bloating, pain, stool form, mood, sleep, stress), diet phase, reintroduction results, and onboarding answers such as the conditions you say you manage. This is sensitive data and we treat it that way.
- Profile photo (optional). If you add one, we store it in private storage tied to your account. It is used only to show you your own profile. It is never sent to any AI provider, never used for advertising, and replacing it deletes the previous file. You can remove it at any time from Profile.
- Health Connect data (Android, optional). Only if you grant permission, we read sleep, steps and menstruation data from Android Health Connect to enrich your own insights. You can revoke this in Health Connect at any time, and we never write to it or share it.
- Payment data. Subscriptions are processed by Google Play (and the Apple App Store on iOS, where offered) through RevenueCat. We receive subscription status, plan and renewal dates. We never see or store your full card number.
- Usage and device data. App interactions, feature usage, approximate region, device type, app version and crash reports, collected through first-party analytics and PostHog to keep the product working and improve it. This never includes the contents of your meals, symptoms or reports.
- Notification tokens. If you enable reminders, we store a push token so we can deliver them. Turn notifications off to stop this.
3. How we use your data
- To run the core loop: analyse meal photos, compute FODMAP and fiber estimates, and correlate your meals with your symptoms to surface your personal trigger candidates.
- To generate reports you explicitly request, such as the doctor-ready PDF.
- To operate your account, subscription, trial and billing.
- To send service messages and, if you enable them, reminders and notifications. You can turn these off at any time.
- To understand aggregate product usage and improve features.
- To meet legal obligations and enforce our terms.
4. AI processing of meal photos
When you photograph a meal, the photo is sent from our backend to a third-party AI model provider to identify the foods on the plate. The photo is used to produce the food list you see and is not used by us, or by the provider, to train AI models. Nutritional values (FODMAP and fiber) come from our curated dataset, not from the AI model.
Insights are framed as observations from your own data. They are statistical patterns, not clinical conclusions.
5. Legal bases (EEA and UK)
- Contract: providing the service you signed up for.
- Consent: processing your health-adjacent logs, Health Connect data, marketing emails, and optional notifications. You can withdraw consent at any time by revoking a permission, deleting data, or deleting your account.
- Legitimate interests: product analytics, security and fraud prevention, balanced against your rights.
- Legal obligation: tax, accounting and lawful requests.
6. Who we share data with
We never sell your data. We share it only with processors that run the service:
- Supabase: database, authentication and file storage.
- Railway and Vercel: application hosting.
- AI model providers: meal photo recognition, as described above.
- Google Play, Apple, RevenueCat: payments and subscription management.
- PostHog: product analytics.
Sharing you choose: clinician report links. You can generate a link to one of your doctor reports so a clinician can open the PDF without an AllerPrism account. This is the only way your health data reaches someone outside the processors above, and it only ever happens because you created the link. Every link expires on a date you pick, you can withdraw it at any moment from Reports, and we record how many times it was opened so you can see it was used. Anyone holding an unexpired link can read that report, so treat it like the PDF itself and withdraw it when the appointment is over. Deleting the report, or your account, kills its links immediately.
Each processor is bound by a data processing agreement. We may also disclose data if the law requires it, or as part of a merger or acquisition, in which case this policy continues to apply to your data.
7. International transfers
Our processors operate primarily in the United States and the European Union. Where data leaves the EEA or UK, transfers rely on adequacy decisions or standard contractual clauses.
8. Retention
- Your logs and photos are kept while your account is active so your history and insights keep working.
- If you delete individual entries, they are removed from the live product immediately and from backups within 30 days.
- Clinician report links stop working the moment they expire or you withdraw them. We keep the withdrawn record itself so you can still see the link existed and how often it was opened, and it goes with your account when you delete it.
- If you delete your account, all personal data is deleted within 30 days, except records we must keep for tax or legal reasons.
- Inactive accounts may be deleted after 24 months following advance notice by email.
9. Security
Data is encrypted in transit (TLS) and at rest. Database access is protected with row-level security so your records are readable by your account only. Photos and reports live in private storage buckets scoped to your user. Secrets and AI keys stay on our servers, never in the apps. No system is perfectly secure, but if a breach affects your data we will notify you and the relevant authority as the law requires.
10. Your rights
Wherever you live, we honor these for everyone: access, export, correction, deletion, restriction, objection, and portability. In the EEA and UK you can also complain to your data protection authority; in California you have equivalent rights under the CCPA/CPRA, and we do not "sell" or "share" personal information as defined there.
Export and deletion are self-serve inside the app (Profile, then Data). Anything else, email [email protected] and we will respond within 30 days.
11. Children
AllerPrism is not for children. You must be at least 16 years old (or the age of digital consent where you live) to create an account. We do not knowingly collect data from children; if you believe a child has an account, contact us and we will delete it.
12. Cookies and analytics on this website
This marketing site uses PostHog to measure pages visited and general usage. The embedded demo video is served by YouTube in privacy-enhanced mode, which sets no advertising cookies until you play it. The interactive product demo on the homepage runs entirely in your browser and stores nothing.
13. Changes to this policy
We will update this policy as the product evolves. Material changes, meaning anything that reduces your rights or widens how we use your data, are announced in the app or by email at least 14 days before they take effect.
Clarifications take effect when published: describing an existing feature more fully, naming a processor we already used, or documenting an optional feature you have to switch on yourself. Those do not change what we do with your data, so waiting 14 days to say so would leave the policy less accurate, not more. The date below always reflects the current version.
14. Contact
Privacy questions and requests: [email protected]. General support: [email protected].