Foodprint — Privacy Policy

Last updated: 5 September 2026

Foodprint is a personal food diary. You log meals — a name, notes, place, price, a star rating, tags, and optionally one photo — and can share your diary with friends you have explicitly added. This policy explains what data the app collects, why, where it is stored, and the choices you have.

Foodprint is operated by Aleksander Zmarzły ("we", "us"). Contact: foodprintappcontact@gmail.com.

1. Data we collect

Account information

• Email address — used to create and identify your account. You sign in with an email/password or with Google Sign-In.
• Display name — shown to you and to friends you connect with.
• Friend code — a short code generated for your account so others can send you a friend request.
• Preferences — your chosen currency and your notification on/off settings.

Content you create

• Diary entries — the meal name, description, place name, a free-text location, price, star rating, tags, and the date.
• Photos — if you attach one, a single image per entry. It is cropped to a square on your device and stored as image data on your entry. We do not use a separate photo/media hosting service; the image is saved inside your diary database record.

Social data

• Friend connections — the accounts you have accepted as friends, and pending friend requests you have sent or received (which include the sender's display name).

Technical data

• Push notification token — if you allow notifications, a device token issued by Apple Push Notification service or Firebase Cloud Messaging is stored on your account so we can deliver friend-request and friend-activity alerts. It is removed when you sign out or when the messaging service reports it as stale.
• Authentication metadata — handled by Google Firebase Authentication (for example, account creation time and the sign-in method).

Advertising data

• Advertising identifiers — Foodprint shows ads served by Google AdMob. AdMob and its ad-serving partners may collect your device's advertising ID (Android) or IDFA (iOS, only if you allow tracking), IP address, general device information, and app usage/interaction data related to the ads shown, in order to serve and measure ads and, where you consent, personalize them. This processing happens on-device and via Google's ad-serving infrastructure — we do not receive or store this data ourselves.
• Consent — where required (for example in the EEA/UK), you are shown a consent form (Google's User Messaging Platform) before any ad request, letting you choose whether ads are personalized. On iOS, you are also asked for App Tracking Transparency permission. You can decline either; ads may still be shown, but without personalization.

We do not run any analytics SDKs beyond what AdMob itself requires to serve ads. We do not collect your precise device location, contacts, or browsing activity. The "location" field on an entry is text you type yourself, not GPS.

2. How we use your data

• To provide the core app: storing and showing your diary on your devices.
• To let friends you have added see the entries in your shared diary, and to show you theirs.
• To deliver the push notifications you have opted into (a friend request, or a batched "friend added new entries" alert).
• To authenticate you and keep your account secure.

We do not sell your data. Aside from the AdMob advertising data described above (which is processed by Google and its ad partners, not by us), we do not share your data with third parties for marketing, and we do not build advertising profiles ourselves.

3. Where your data is stored

Foodprint uses Google Firebase (Firestore database, Firebase Authentication, and Firebase Cloud Messaging / Cloud Functions) as its backend. Your data is stored on Google Cloud infrastructure. Database access is restricted by security rules so that:

• only you can read or write your own account details, entries, photos, and notification token;
• friends you have accepted can read the diary entries you share with them;
• nobody else can read your data.

Firebase's own handling of data is covered by Firebase's privacy documentation and the Google Cloud Data Processing terms.

4. Sharing and disclosure

• With friends: when you accept a friend, the diary entries you choose to keep in your feed become visible to that friend, along with your display name.
• With service providers: Google Firebase, as described above, acts as our data processor.
• With advertising partners: Google AdMob and the ad networks it mediates receive advertising identifiers and ad-interaction data as described in "Advertising" below, in order to serve and measure ads.
• For legal reasons: we may disclose data if required by law, or to protect the rights, safety, or property of users or the public.

5. Advertising

Foodprint shows ads (native ads in your diary feed, and a banner above the navigation bar) served through Google AdMob. AdMob may work with third-party ad networks to fill these ad slots. To do this, AdMob and its partners may access:

• your device's advertising identifier (the Android Advertising ID, or on iOS the IDFA — only if you grant App Tracking Transparency permission);
• your approximate IP-based location and general device information (device model, OS version);
• ad interaction data (impressions, clicks) for the ads shown to you.

Where required by law (for example the EEA, UK, and Switzerland), a consent form is shown before any ad is requested, using Google's User Messaging Platform (UMP), so you can choose whether ads are personalized. On iOS you are separately asked for App Tracking Transparency permission. Declining either does not stop ads from being shown — it only means the ads you see are not personalized to you.

This processing is carried out by Google and its ad-serving partners under their own privacy policies, not by us directly: Google's Privacy Policy and how Google uses information from sites or apps that use AdMob. You can review or adjust Google's ad personalization settings at adssettings.google.com, and on iOS you can change App Tracking Transparency permission at any time in Settings → Privacy & Security → Tracking.

6. Data retention

Your data is kept for as long as your account exists. When you use Delete Account in the app, we make a best-effort deletion of your entries, photos, friend links, friend requests, your friend-code entry, and your user record, and we delete your authentication account. Copies may persist for a short time in backups or logs before being overwritten. Some friend-side references (for example, a friend's record that they were connected to you) may require server-side cleanup and are not guaranteed to be removed immediately.

To request deletion without using the in-app option, email foodprintappcontact@gmail.com.

7. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. You can edit your profile and entries directly in the app, export your diary (JSON, CSV, or PDF) from the app, and delete your account from the app. For any other request, contact us at the email above.

8. Children

Foodprint is not directed at children under 13 (or the minimum age of digital consent in your country), and we do not knowingly collect their data. Ads shown in Foodprint are not configured for child-directed treatment, and the app is not intended for use by children. If you believe a child has provided us data, contact us and we will delete it.

9. Security

Data in transit is encrypted with TLS. Access to your data is enforced by Firebase security rules. No method of storage or transmission is completely secure, but we take reasonable measures to protect your information.

10. Changes to this policy

We may update this policy. Material changes will be reflected by an updated "Last updated" date at the top of this page. Continued use of the app after a change means you accept the revised policy.

11. Contact

Questions or requests: foodprintappcontact@gmail.com.

This document is provided as-is and is not legal advice. If Foodprint gains a significant user base, gathers additional data, or enters regulated markets, a lawyer should review it.