AKTUA Privacy Policy

Eat better. Train stronger. Go further.

Effective date: September 16, 2026

AKTUA is a fitness, nutrition, hydration, and training application. This Privacy Policy explains what information AKTUA handles, how it is used, the service providers involved, and the choices available to you.

AKTUA is operated by the developer identified on the applicable app-store listing. Privacy questions and requests can be submitted through Settings > Help & Feedback in the app.

Information AKTUA handles

Account and identity information

AKTUA can be used with an automatically created anonymous guest account or a permanent account. Depending on how you use the app, AKTUA may store:

• a Supabase user UUID used as the permanent AKTUA account identifier;
• an anonymous guest identifier;
• name and email address if you provide them;
• linked sign-in methods such as email/password and, when enabled, Apple, Google, or Facebook;
• authentication metadata needed to keep you signed in and secure the account.

Provider IDs and provider email addresses are sign-in methods. AKTUA uses the Supabase UUID, rather than a provider ID, as the ownership key for account data.

Fitness, body, and profile information

Information you choose to enter can include age, sex, height, weight, target weight, weight history, body measurements, activity level, training experience, training schedule, workout duration, training location, equipment, gym or machine setup, goals, target muscles, restrictions, calorie and macro targets, and optional health-related context such as medication context or training restrictions.

Some of this information can be sensitive health- or fitness-related data. AKTUA uses it to provide the fitness and nutrition features you request. It is not used for third-party advertising.

Android Health Connect

On Android, you can optionally connect Health Connect. AKTUA currently requests read access only to body weight, steps, and exercise sessions. After you grant access, AKTUA can refresh this information while you are actively using the app. AKTUA may store imported values, timestamps, record identifiers, and source-app/package provenance in your account so that the data can be used as fitness context across devices.

AKTUA does not currently request Health Connect write access, background health-data access, exercise routes, active-calorie data, or total-calorie-burn data. Health Connect calorie estimates do not change AKTUA nutrition targets. If a Health Connect weight and a manually entered AKTUA weight exist for the same day, the manually entered value takes precedence. Health Connect imports are deleted with the AKTUA account and are also cleared by Reset Guest Data for guest profiles. You can revoke Health Connect permissions in Android settings at any time.

Training information

AKTUA may store workout plans and programs, workout history, exercises, sets, repetitions, load, duration, distance, effort values, notes, personal records, progression state, substitutions, and custom exercises.

Nutrition and hydration information

AKTUA may store food diary entries, food names and brands, barcodes, servings, quantities, grams or milliliters, calories and macronutrients, custom foods, recipes, saved meals, favorites, nutrition targets, water logs, and hydration targets. For FatSecret recipe discovery, AKTUA stores the FatSecret recipe IDs you favorite and the IDs selected for curated collections. FatSecret recipe, food-search, category, autocomplete, and barcode-match content is requested from FatSecret and cached only within the period allowed by the active FatSecret API edition, never longer than 24 hours. If you add a FatSecret food or barcode match to your diary, AKTUA stores the provider food ID and an immutable snapshot of the food, selected serving, and nutrition you logged as your user-owned history.

Feedback and support information

If you submit Help & Feedback, AKTUA may store the message, feedback type, optional contact email, app version, platform, operating-system version, device model, and a limited diagnostic context used for troubleshooting.

Analytics and error diagnostics

AKTUA uses PostHog for privacy-minimized product analytics and JavaScript error monitoring. The current mobile configuration may record application lifecycle events, selected product events, uncaught JavaScript exceptions, and unhandled promise rejections using a pseudonymous analytics identifier.

AKTUA does not currently enable PostHog session replay, touch capture, automatic screen capture, console capture, advertising, or cross-app/site tracking. Common email, credential, token, JWT, and secret values are filtered from event properties before transmission. AKTUA does not currently identify PostHog analytics profiles with your Supabase account UUID or email.

Optional AKTUA Momentum messaging

If you explicitly enable AKTUA Momentum, AKTUA uses OneSignal to provide optional remote push messaging and engagement automation. AKTUA associates the OneSignal user with the AKTUA/Supabase user UUID and may send OneSignal device/app information, push-subscription status, and coarse engagement signals such as whether onboarding is complete, a bucketed count of active days in the last week, and whether at least one training, nutrition, hydration, or progress entry exists in the recent activity window.

AKTUA does not send OneSignal exact body weight, target weight, calories, macros, meal names, food details, exercise names, workout loads, medical information, or the detailed contents of fitness and nutrition logs. AKTUA Momentum can be turned off in Settings. When it is disabled, AKTUA opts the OneSignal push subscription out and revokes the app's OneSignal messaging consent on that device.

Subscriptions and purchases

AKTUA may offer optional AKTUA Pro subscriptions. When real subscriptions are enabled, purchase processing is handled by Google Play or Apple and subscription entitlement information is handled through RevenueCat. AKTUA does not receive your full payment-card details. RevenueCat and the applicable app store may process purchase status, product identifiers, transaction identifiers, subscription status, platform account information, and related technical data needed to provide and restore purchases. The initial Google Play closed-testing build may have purchasing disabled.

AI interactions

The current release does not expose the Coach/AI conversation feature. Before any AI feature that sends user content to an external model provider is enabled publicly, this policy and the applicable store disclosures will be updated to describe that processing.

How AKTUA uses information

AKTUA uses information to:

• provide account access and synchronize your data;
• calculate and display fitness, nutrition, hydration, and training features;
• preserve workout and nutrition history;
• personalize training and nutrition settings you request;
• operate guest accounts and account linking;
• provide local reminders and optional AKTUA Momentum messages you explicitly enable;
• troubleshoot errors, protect reliability, and understand product usage;
• respond to feedback and support requests;
• prevent abuse and secure the service;
• manage subscriptions and restore purchases when AKTUA Pro billing is enabled.

AKTUA does not sell personal data and does not use personal or health-related information for third-party advertising.

Service providers and external services

AKTUA currently relies on or may use:

• Supabase for authentication, database storage, server functions, and synchronization;
• PostHog for privacy-minimized analytics and error diagnostics;
• OneSignal for optional, consented remote push messaging, coarse engagement segmentation, and campaign/Journey automation;
• USDA and Open Food Facts or similar catalog sources for food information and barcode/search results;
• FatSecret Platform API for provider-backed recipes, food search and suggestions, food categories, nutrition information, and backup barcode matches;
• Apple, Google, or Meta/Facebook when you choose an enabled provider to authenticate;
• Google Play and Apple App Store for app distribution and, when enabled, purchases;
• RevenueCat for AKTUA Pro entitlement and subscription-status handling when real billing is enabled.

These providers may process network and technical information necessary to operate their services, such as IP address, request metadata, or device/app information, according to their own privacy practices.

Camera and notifications

AKTUA requests camera access only when you use features such as the food-barcode scanner. Notifications are optional. Local food/water reminder schedules are stored on the device. If you enable AKTUA Momentum, OneSignal handles the remote push subscription and delivery. You can turn reminder features off inside AKTUA and can also revoke notification permission in device settings.

Data retention and account deletion

AKTUA currently uses immediate account deletion rather than a recovery window.

From Settings, permanent users can choose Delete Account and guest users can choose Delete Guest Profile. After explicit confirmation, AKTUA requests deletion of the authenticated RevenueCat customer record and Supabase user. User-owned database records are configured to cascade-delete with that user, including profile, goals, workouts, sets, nutrition, water, weight, measurements, gyms/machines, preferences, progression data, feedback, custom content, and other user-owned records. Local reminders and cached/offline account state are also cleared.

Deleting an AKTUA account does not cancel an App Store or Google Play subscription. You must cancel the subscription through the store's subscription-management flow to prevent future charges. Store or payment-provider transaction records that must be retained for accounting, fraud prevention, or legal obligations remain governed by that provider's policies.

A separate Reset Guest Data action clears a guest's activity data while retaining the anonymous guest identity. It is not a substitute for deleting the guest profile.

Some records may need to be retained if required by applicable law, fraud prevention, accounting, payment processing, or legal obligations. Where a service provider such as an app store or RevenueCat maintains transaction records under its own legal obligations, those records are governed by that provider's policies.

Your choices

You can:

• use AKTUA as an anonymous guest where available;
• add or link supported sign-in methods;
• delete your account or guest profile from Settings;
• reset guest activity data without deleting the guest identity;
• disable local reminders, disable AKTUA Momentum, and revoke notification permission;
• deny camera access and use manual food entry/search instead;
• deny or revoke Health Connect permissions;
• submit feedback without providing an optional contact email.

Security

AKTUA uses authenticated Supabase sessions, row-level security, HTTPS production endpoints, server-side privileged operations, and separation of protected credentials from the mobile client. No system can guarantee absolute security, but AKTUA is designed so provider secrets, Supabase service-role keys, database passwords, and similar protected credentials are not shipped in the mobile application.

Children

AKTUA is not designed as a service specifically for children. If supported age ranges or launch requirements change, AKTUA's onboarding, store age rating, and privacy disclosures will be reviewed accordingly.

Changes to this Privacy Policy

This Privacy Policy may be updated when AKTUA adds material features, service providers, AI functionality, subscriptions, new data categories, or new legal requirements. The effective date above will be updated when the policy changes materially.

Privacy contact

For privacy questions, data requests, or account-deletion assistance, use Settings > Help & Feedback inside AKTUA. This provides a direct mechanism to contact the developer responsible for the app-store listing.