Privacy Policy

Ale Pro has no sign-in, so the app never asks for your name, email address or any account details. It does collect a small set of device identifiers and usage events, all of them through Google services:

• Advertising ID: your device advertising identifier, sent with every ad request through Google AdMob and used by Google and its ad partners to select and measure ads.
• Firebase installation ID and Firebase Cloud Messaging token: used to group analytics events coming from the same installation and to deliver push notifications.
• App interaction events: the screens you open and a few named actions inside the app, listed in section 3.
• Crash logs and diagnostics: crash reports and device state at the moment of a crash, sent to Firebase Crashlytics.

The app does not collect location data. Neither the Android nor the iOS version requests a location permission, and neither contains code that reads your position.

Your shopping lists and favorite stores stay on your device. They are kept in the app's local database and are never uploaded to us. Push notifications are delivered through topic subscriptions, so we do not hold a token tied to you.

• User Content: shopping lists and favorite stores are stored on your device only. The app does not upload them.
• Usage Data: screen views and named in-app events, plus app performance and crash information.
• Identifiers: the advertising ID, the Firebase installation ID and the Firebase Cloud Messaging token.
• Location Data: the app does not access or use your device's location.
• Contact Information: the app does not collect your email address, phone number or any other contact detail.
• Health Data: the app does not access or collect health-related data.

Google Analytics for Firebase

Ale Pro uses Google Analytics for Firebase. When you open the app, the Firebase SDK stores an installation ID on the device and sends event records to Google's servers. Each record carries that installation ID together with the app version, the device model and its operating system version. The request also reaches Google with your device's IP address, which Google uses to work out an approximate region.

The events the app records itself are brochure_open, brochure_page_view, store_favorite and list_item_add, plus a screen view each time you move to a different screen. Firebase adds a few of its own, including session_start, notification_open and ad_impression.

Google processes these events on our behalf and gives us aggregate reports on which features people use. Google describes its own handling of this data in the Firebase privacy and security notice and in How Google uses information from sites or apps that use our services.

Google AdMob

Ads in Ale Pro are served by Google AdMob. When the app requests an ad, the AdMob SDK sends your advertising ID with the request, and Google and the ad vendors it works with use it to choose an ad and to count impressions and clicks. You can reset or delete this identifier in your device settings: on Android under Settings, Privacy, Ads; on iOS by turning off "Allow Apps to Request to Track".

Crash reports go to Firebase Crashlytics, which is also a Google service.

In the EEA and the UK, a consent form appears the first time you open the app, before any ad is requested. It is Google's certified consent management platform and follows version 2.3 of the IAB Transparency and Consent Framework. It asks about advertising and about analytics separately.

You can change your answer whenever you want. Open the app's settings screen and choose "Ad privacy settings" to bring the same form back.

On iOS, Apple's App Tracking Transparency prompt appears after the consent form. It controls whether the app may use the advertising identifier for tracking.

Turning consent down does not take any feature away. You still get ads, but they are non-personalized.