Privacy policy

Last updated: 29 October 2026

Who operates Almeya

Almeya is operated by Mykola Kulakov Puls IT. Contact: contact@pulsit.dev.

Your data on this device

Your diary, recipes, saved foods, weight, water and settings are stored on your device. Dietary preferences and ingredient reports remain local. Local ingredient photo reading uses Apple Vision. Local meal recognition uses a bundled pretrained model on supported devices. These local analyses do not upload photographs to an AI provider.

Optional account and synchronization

Signing in with Apple enables synchronization through Supabase of diary entries, recipes, custom foods, favorites, app-entered weights, water and shared nutrition settings. Device permissions, dietary preferences and ingredient reports are not synchronized. The Staging and Production account services currently configured for Almeya are hosted in the EU. This policy will be updated before a deployment changes where your account data is processed.

External food databases

Barcode and online food searches send the barcode or search query to Open Food Facts, or to the USDA proxy when configured. Saved food records may include source attribution and ingredients. Photos are not automatically published to Open Food Facts.

Apple Health

Health access is optional. With your permission, Almeya reads selected activity, height and weight summaries and writes nutrition, water or app-entered weights. Raw Health history is not uploaded. If you choose to apply Health summaries to your goal profile, the selected profile values become part of your app settings and may be synchronized with your account. Read and write permissions are managed separately in Apple Health. Turning off integration does not erase existing Apple Health samples.

Voice input

Voice entry uses Apple Speech with your microphone and speech permissions. On-device recognition is requested when Apple advertises support for your selected language. Otherwise Apple Speech may process audio through Apple services under the system permission you grant. You can always type and edit the transcript or use manual entry.

Purchases

Apple processes payments. Almeya verifies transaction signatures, product, app, environment and account binding on its server. A device-only Keychain cache permits access until the last confirmed entitlement expiry while offline. Local Premium does not allocate cloud-scan credits.

Cloud AI

Cloud AI is currently disabled. It will not be used automatically after a local recognition error. Any future cloud photo analysis requires an enabled service, a separate explicit user action, permission to send the photo and server access checks. Relevant policy changes will be published before such processing is offered.

Optional analytics and diagnostics

Where configured and enabled with your consent, limited usage events help us understand application reliability and feature use. They exclude food names, nutrition, photographs, dietary restrictions, weight and Health values. Local diagnostics use fixed operational codes. Analytics can be disabled in Profile.

Retention, export and deletion

Local records remain until you remove them or erase local app data. Profile → Your data offers JSON export and local erasure. Cloud account deletion removes the authenticated account and associated private server records. Local erasure and cloud deletion are separate actions; neither cancels an Apple subscription. Existing Apple Health samples remain unless removed through the connected integration or Apple Health. Provider backup copies, if any, follow the provider's configured retention and are not used to recreate a deleted account.

Your choices and requests

You can use basic logging without an account, manage permissions, revoke optional analytics, export or delete records, and contact us for privacy questions or access/correction/deletion requests. Applicable data-protection rights and complaint mechanisms remain available.