Privacy Policy

HealthCompare

Purpose: read-only comparison of health and fitness metrics from multiple sources via Android Health Connect.

3.1 Data sources

• Android Health Connect — steps, heart rate, HRV, sleep, blood oxygen (SpO₂), body temperature, calories, distance, activities and similar metrics that other companion apps share into Health Connect.
• HealthCompare reads only the record types you have explicitly approved in Health Connect.

3.2 Storage and processing

• Read-only — HealthCompare never modifies or writes to your Health Connect records.
• Aggregated values used to render the comparison are kept locally on your device.
• Analysis is generated on-device by default.

3.3 Optional custom AI endpoint

HealthCompare contains an optional feature that lets you point the app at an OpenAI-compatible HTTPS endpoint for richer analysis. This feature is off by default. If you enable it and supply your own endpoint URL, model name and (optional) API key, the relevant comparison data is sent directly from your device to that endpoint of your choosing only when you tap "Run AI analysis". The data is not routed through ALKENS DEVELOPMENT servers — we operate no such servers. The third party's own privacy policy then applies.

3.4 Network

HealthCompare uses network access for Google AdMob banner advertising, Google's User Messaging Platform consent flow, Google Play age-signal compliance checks where available, and optional user-initiated AI endpoint requests if you enable them. Health Connect health metrics remain on your device unless you explicitly start the optional custom AI analysis described above.

3.5 Medical disclaimer

HealthCompare is not a medical device and is not intended for diagnosis or treatment.

Einkaufsmanager

Purpose: receipt capture, grocery-item review, household inventory management and shopping-list planning.

3.6 Data sources

• Camera / document scanner — receipt photos captured by you through the Android document-scanning flow.
• PDF import — receipt PDF files selected by you through the Android file picker.
• Manual input — item descriptions, quantities, categories, storage locations, optional expiry dates and shopping-list entries you create or edit.

3.7 Local processing and storage

• Receipt text recognition and item extraction are processed on your device for the current release.
• Recognised item names, quantities, prices, categories, inventory entries, storage locations, optional expiry dates and shopping-list entries are stored locally on your device.
• Receipt, inventory and shopping-list data is not uploaded to ALKENS DEVELOPMENT in the current release.

3.8 Advertising and consent

Einkaufsmanager uses Google AdMob. The app uses the Google Mobile Ads SDK and Google's User Messaging Platform SDK to request and manage privacy and consent choices where required.

Google and its partners may process advertising-related information such as the Advertising ID, device or other identifiers, approximate device or network information, app interactions, ad interactions, diagnostics and fraud-prevention signals. This processing is used for advertising, measurement, consent management, fraud prevention, security and compliance and is governed by Google's privacy terms and the choices shown in the app where applicable.

3.9 Optional online receipt analysis

The app code supports an optional HTTPS receipt-analysis endpoint for future richer receipt interpretation. The current Google Play release prepared by ALKENS DEVELOPMENT does not configure such an endpoint. If this feature is enabled in a future release, this policy and the Google Play Data Safety information will be updated before submission.

3.10 Network

The app uses network access for Google AdMob, Google Mobile Ads SDK and Google User Messaging Platform SDK. Receipt and inventory data is not uploaded to ALKENS DEVELOPMENT by default in the current release.

THE MI-RATIO

Purpose: free, ad-supported entertainment app with 100% on-device face analysis. Capture a single selfie, receive a beauty score (1-10) based on facial symmetry analysis.

3.10 Camera access

The app asks for permission to access your device's front camera to capture a single photo for analysis.

• The captured image is processed entirely on your device using Google ML Kit (the bundled, on-device face-detection model).
• The photo is never stored on disk. It is held in volatile memory only for the duration of the analysis (typically under one second) and is then explicitly recycled.
• The photo is never transmitted. The face-analysis pipeline makes no network requests. Network access is used only for Google Mobile Ads, consent handling, Google Play age signals and app-store services.

3.11 Face geometry / biometric data note (GDPR Art. 9, BIPA, CUBI)

The on-device ML Kit model computes geometric landmarks (eye positions, contour points, nose-base coordinates, etc.) and a small set of categorical "bands" (eye distance, lip fullness, jawline shape, and similar) from the captured photo.

These values are biometric-adjacent data and we treat them with the same care as biometric data. Specifically:

• They never leave your device.
• They are never used to uniquely identify you (no template matching, no face-recognition database, no comparison to any other face).
• They are not stored on disk. They exist only in volatile memory during the analysis pass and are released when the analysis completes.
• They are not sold, leased, traded, or otherwise monetised.
• We do not run an ID-verification, age-estimation, or surveillance feature against them.

In jurisdictions where face-geometry data is treated as a regulated biometric identifier — notably Illinois BIPA (740 ILCS 14), Texas CUBI (Bus. & Com. § 503.001), and Washington (HB 1493) — our retention period for any such data is the duration of the in-memory analysis pass, typically under one second. We will permanently destroy any biometric-adjacent data when the app is closed, the analysis completes, or the user re-runs a scan, whichever first occurs.

By tapping Accept on the consent screen on first launch, you provide informed written consent (under 740 ILCS 14/15(b) and analogous statutes) to the on-device processing described above.

3.12 Beauty score and character reading

The numerical score (1–10) and the eight-section character reading shown on the result screen are derived on-device from the geometric landmarks and the categorical bands. No image, no landmarks, no score, no text is ever transmitted.

The character reading describes statistical impressions reported in published face-perception research (Todorov, Penton-Voak, Zebrowitz, Rhodes, Kramer & Ward, and others), not factual personality traits. Different observers form different impressions of the same face, and those impressions are shaped by culture and bias more than by anatomy. THE MI-RATIO is intended for entertainment.

3.13 Score widget

If you add the home-screen widget, the app stores your most recent score (1–10) and verdict text in local SharedPreferences. This data never leaves your device and is overwritten on every new scan.

3.14 Shared images

When you tap a share button, a score-card image (containing only your score, verdict and a short text excerpt — not the original photo) is saved locally and handed to the Android share intent for the app you choose. THE MI-RATIO does not upload this image. Once shared, the receiving app's privacy policy applies.

3.15 Consent record

We store a boolean flag and a timestamp in local SharedPreferences to remember that you accepted this policy. It is excluded from Auto Backup and from device-to-device transfer.

3.16 Advertising, consent, and age signals

THE MI-RATIO uses Google Mobile Ads (AdMob) to display ads in the free version. It uses Google User Messaging Platform (UMP) to collect and store ad-consent choices where required. Depending on your region, device settings and consent choices, Google may process the Android Advertising ID, device information, interaction data, diagnostics, fraud-prevention signals and consent state for ad delivery, measurement, fraud prevention, security and compliance.

THE MI-RATIO also integrates the Google Play Age Signals API. For eligible users, Google Play may provide the app with age-related compliance signals such as verification status, age range and an install identifier. These signals are used only to support legal compliance, are stored locally on the device where needed, and are not sent to ALKENS DEVELOPMENT servers.

Our authorized sellers declaration is available at https://alkensdevelopment.ch/app-ads.txt.

New York - Food Guide - ALK

Purpose: browsing curated New York food places, cuisines, areas and saved ideas in a free Android app supported by Google AdMob ads.

3.16 Information collected

The app includes curated food-place data bundled inside the app at build time. It does not require an account and does not collect payment data, photos, files or precise location data. The free Android release uses Google AdMob and Google UMP; depending on your consent choice and Google settings, Google may process advertising identifiers, approximate device/app information, consent status and ad interaction data for advertising, measurement, fraud prevention, security and compliance.

3.17 Permissions and maps

The app requests no Android permissions. When you tap "Open in Google Maps", Android opens the map app installed on your device through a standard geo-intent. New York - Food Guide - ALK does not receive data back from that external app; the receiving app's privacy policy applies.

3.18 Local storage

Food Guide content and saved ideas remain on your device and are not uploaded to ALKENS DEVELOPMENT. Ads, consent handling, Google Play age-signal compliance checks where available, and external map directions require network access and are handled by Google services under their own terms.

Future ALKENS DEVELOPMENT apps

Apps released by ALKENS DEVELOPMENT in the Entertainment, Health, or Productivity categories will follow the same principles documented here. If a future app introduces a materially different data practice (for example optional cloud sync), an updated app-specific section will be added to this page before that app is published, and the in-app onboarding will explain the change.