Privacy policy

Last updated: 9 November 2026

This is a translation for your convenience. Only the German version is legally binding.

This privacy policy explains which personal data we process when you use the Aspira app (iOS and Android) and the website aspira-app.de, why we need it, on which legal basis we process it and which rights you have. Aspira is an app for nutrition, training and progress with a community. This involves health data. We treat it with particular care and only process it with your explicit consent.

1. Controller and contact

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

Kolac Digital
Owner: Yusuf Kolac
Beckhausstraße 108
33611 Bielefeld, Germany
Phone: +49 176 95762018
VAT ID: DE332669210
Email for privacy requests: datenschutz@aspira-app.de

Data protection officer: not appointed. For data protection questions, contact us directly using the details above. You can reach us with any privacy question at datenschutz@aspira-app.de.

2. Principles at a glance

  • EU hosting: database, sign-in, file storage and server functions run on Supabase in the Frankfurt region (AWS eu-central-1).
  • Health data only with consent: we only store weight, body measurements, meals, workouts and progress photos after you have explicitly consented. This is enforced technically in the database.
  • No advertising, no selling of data, no cross-app tracking. We use no advertising IDs and no app tracking within the meaning of Apple’s App Tracking Transparency. We never use data from Apple Health / HealthKit or Health Connect for advertising and never sell it.
  • Analytics only with opt-in: we only collect usage statistics if you agree.
  • Data minimisation: images are re-encoded on your device, which removes metadata such as EXIF and GPS location. We do not store images used for AI analysis.
  • Control: data export and account deletion work directly in the app.

We process personal data on the following bases:

  • Art. 6(1)(b) GDPR (contract): to provide Aspira to you, i.e. account, profile, sync, community features and subscription management.
  • Art. 6(1)(a) GDPR (consent): for product analytics, push notifications and optional features. Where information is stored on or read from your device for this, additionally § 25(1) of the German TDDDG.
  • Art. 9(2)(a) GDPR (explicit consent): for health data as a special category of personal data (see section 5.3).
  • Art. 6(1)(c) GDPR (legal obligation): e.g. retention obligations, proof of consent (Art. 7(1) GDPR) and disclosure obligations towards authorities.
  • Art. 6(1)(f) GDPR (legitimate interest): for security, abuse prevention, community moderation, error analysis and enforcing our rights. Our interest is a safe, stable and fair service. Where your device is accessed for this, we rely on § 25(2) no. 2 TDDDG.

4. This website

The website https://aspira-app.de shows legal texts, help and public share pages (see 5.9). It sets no cookies and uses no tracking. We serve fonts ourselves, so your browser does not connect to Google Fonts.

When you visit it, our web server processes technically necessary data: IP address, date and time, requested address, referrer, browser identifier (user agent) and status code. This is necessary to deliver the site and fend off attacks (Art. 6(1)(f) GDPR). We delete server logs after 14 days. The website is hosted by Vercel Inc. (San Francisco, USA) with servers in Frankfurt.

5. Data processing in the app

5.1 Account and sign-in

You sign in with Sign in with Apple, Google Sign-In or a one-time code by email. We process your email address (with Apple possibly an anonymous relay address), an identifier of the sign-in service and, if provided, your name. Apple’s and Google’s privacy policies apply in addition. For the email code we send an email via Resend (Plus Five Five, Inc., USA; sent from the EU, Ireland). Your sign-in token is stored on the device in the keychain (iOS Keychain or Android Keystore).

When you register, you accept the terms of service and acknowledge this privacy policy. We log this with version and timestamp. Legal basis: Art. 6(1)(b) and (c) GDPR.

5.2 Profile and settings

Public profile: username, display name, profile picture, bio, whether your account is private, follower and post counts and the stage of your profile frame. Other signed-in users can see this unless you have blocked each other.

Private profile (only for you): year of birth, sex, height, activity level, goal (lose, maintain, gain), units, time zone, country and app settings such as “hide scale weight”, streak and push settings. We use this to calculate e.g. your calorie needs. Because these details may allow conclusions about your health, we treat them like health data.

Profile card, gym and home town (optional): your profile can show a profile card: your training plan, your activity over the last 4 weeks (workouts, kilometres run) and your best results. It shows your weekly calorie average only if you switch it on yourself. You can hide each part under Settings → Privacy. The card is visible to everyone allowed to see your profile, or only to your followers if your account is private. If you add a gym or your home town, the gym and the name of your town are public (e.g. on your profile and in suggestions such as “Near you · Paderborn”). We also store a point rounded to about 1 km so we can suggest people near you and from your gym. Nobody sees this point or a distance. You can remove gym and home town at any time.

Place search: when you search for a gym or a place, our server sends only the search text and, if available, a reference point rounded to about 100 m to the Photon search service of komoot GmbH (OpenStreetMap data). komoot does not learn your IP address or your account.

Legal basis: Art. 6(1)(b) GDPR, for health-related details Art. 9(2)(a) GDPR.

5.3 Health data

Health data is specially protected under Art. 9 GDPR. In Aspira this includes in particular:

  • weight, body fat percentage, lean mass, waist circumference, goals and milestones
  • meals, calories and nutrients, nutrition targets
  • workouts, sets, training plans, activities and calories burned
  • progress photos
  • data you import from Apple Health / HealthKit or Health Connect

We process this data only with your explicit consent under Art. 9(2)(a) GDPR, which you give during onboarding. We store your consent with version and timestamp. Without consent our database refuses to store such data, and the health features are not available. You can withdraw your consent at any time under Settings → Privacy. Withdrawal applies to the future; it does not affect the lawfulness of processing before the withdrawal. If you also want to remove data already stored, you can delete it item by item or together with your account.

So that tracking works offline, the app first stores your entries locally on the device and then syncs them with your account. The local database is encrypted with SQLCipher; the key is kept in your device’s keychain.

5.4 Apple Health and Health Connect

If you allow it, Aspira reads from Apple Health (HealthKit) or Health Connect: weight, body fat, lean mass, BMI, waist circumference, workouts, steps and active calories, also in the background and retroactively. This way, for example, readings from your smart scale arrive in Aspira automatically. Optionally, Aspira writes weights you enter and the workouts you record in Aspira (type, time, duration, calories) back. You decide in the system settings which data types Aspira may read or write and can change this at any time.

We use data from HealthKit and Health Connect exclusively for Aspira’s features. We never use it for advertising or marketing, never pass it on to data brokers and never sell it. Legal basis: Art. 9(2)(a) GDPR.

5.5 Progress photos

By default, progress photos are stored only on your device (in the app’s protected area, not in your photo library). If you turn on the optional cloud backup, the app encrypts each photo on your device with AES-256-GCM before uploading it. Our servers only hold the encrypted content in a private storage area that only your account can access. So that you can restore your photos on a new device, your photo key is itself stored with us in encrypted form. This key is managed exclusively by an automated service. Our team does not see your photos and does not open them. Photos never appear in the feed automatically; sharing happens only one by one and actively. Legal basis: Art. 9(2)(a) GDPR.

5.6 AI features (photo scan and AI coach)

For the meal photo scan and the AI coach we use the Claude API by Anthropic, PBC (USA). Requests go through our server function, never directly from the app. We transmit:

  • for the photo scan, the photo of your meal and, if applicable, your answers to follow-up questions,
  • for the coach, your message and the details needed for a useful answer, e.g. your goal, your training plan and your recent workouts.

We do not transmit your name or email address. We do not store photos used for the scan; they are processed for the analysis only. According to Anthropic, data from the API is by default not used to train its models and is only kept for a limited period for abuse detection (currently at most 30 days). We base the transfer to the US on the EU-US Data Privacy Framework, where the provider is certified, and/or on Standard Contractual Clauses (Art. 46(2)(c) GDPR).

For fair use and cost control we count every AI request: type of request, model used, number of tokens processed, status and timestamp. We do not store the content or the image. Legal basis: Art. 6(1)(b) GDPR, for health-related content Art. 9(2)(a) GDPR, for the counting Art. 6(1)(f) GDPR.

AI results are suggestions. They can be wrong and do not replace medical or dietary advice. You can check and change every result.

5.7 Barcode scan and Open Food Facts

When you scan a barcode, the app requests product data directly from your device from Open Food Facts, a non-profit database run by the Open Food Facts association (France). Only the barcode and technical connection data such as your IP address are transmitted, no account data. Open Food Facts is independently responsible for this. Corrections to product data made in Aspira are published by us as open data under the Open Database License (ODbL). This dataset at /data/off-overrides.csv contains only barcode, correction and timestamp, no personal data. Questions: data@aspira-app.de.

5.8 Community

When you use the community, we process your posts, photos, recipes, comments, hearts, follows and follow requests as well as notifications about them. For every post and recipe you choose the visibility: private, followers or public (public means: visible to all signed-in users). With a private account you decide who may follow you. You can block others; you then no longer see each other’s content and notifications between you are deleted. Photos in posts and recipes are kept in a private storage area and are only delivered to people allowed to see the post.

If you share health data in a post (e.g. a workout or a weight change), that is your decision. For weight milestones we only show the change, not the absolute weight, unless you choose to. With “hide scale weight” no absolute kilos appear anywhere.

Share automatically: when it is on, scanned meals and finished workouts appear in your feed without another step, as do new runs, rides and swims from Apple Health or Health Connect (with distance, pace and time). They are visible like your other posts, or only to your followers if your account is private. You can switch this off separately for meals and workouts under Settings → Privacy and delete any post at any time.

Moderation: we automatically check public texts (username, display name, bio, posts, comments) against a list of prohibited terms. You can report content and profiles. For this we store the reason, optional text, the reported content and the status. Content with several open reports is hidden automatically until reviewed; our team reviews reports within 24 hours. The reporting person remains anonymous to the reported person. Details are in the community guidelines. Legal basis: Art. 6(1)(b) GDPR, for moderation and abuse prevention Art. 6(1)(f) GDPR.

5.9 Share links and Instagram story

You can create a link to a recipe, workout, meal, milestone, post or your profile. For this we store a snapshot of the content you share, together with your username, display name and frame stage. Anyone who has the link can open the page without an account. Share pages are blocked for search engines (noindex). We count how often a link was opened. The link contains your referral code (see 5.12). You can revoke any link in the app at any time; the page is then no longer reachable. For a weight change the link only shows the change unless you choose otherwise.

To prevent mass retrieval, we limit requests to share pages per IP address. For this we store the IP address with a counter for the respective time window and delete these records after 2 days at the latest. Legal basis: Art. 6(1)(b) GDPR (sharing), Art. 6(1)(f) GDPR (abuse prevention, view counter).

For an Instagram story, the app creates the image or video on your device and hands it to the Instagram app at your request. We do not send any data to Meta ourselves. Meta Platforms Ireland Ltd. is responsible for processing within Instagram.

5.10 Subscription and purchases

You buy the Aspira subscription through the Apple App Store or Google Play. Apple or Google handle the payment as separate controllers. We receive no payment or card data. To manage your subscription we use RevenueCat (RevenueCat, Inc., USA). RevenueCat receives purchase receipts and subscription events (product, term, trial period, renewal, cancellation, billing issues, refunds) from the stores and links them to your account via an app user ID. From this we store your subscription status, your loyalty level and your frame stage. When you delete your account, we also delete your customer record at RevenueCat. Transfer to the US: Data Privacy Framework and/or Standard Contractual Clauses. Legal basis: Art. 6(1)(b) GDPR.

5.11 7-day free trial and abuse prevention

New members can try the annual plan free for 7 days once. The trial runs through the App Store or Google Play like a purchase (see 5.10): you keep your payment method with the store, we receive no payment data, only the subscription status including the trial period via RevenueCat. We check whether your account already had a subscription or trial. To prevent the trial and the referral programme (5.12) from being used repeatedly via new accounts, we also mark the device: on iOS via Apple’s DeviceCheck service (Apple stores only two bits per device, without any link to your identity), on Android via a non-reversible hash of a device check (Google Play Integrity) and an installation identifier. This hash remains stored after account deletion without any link to your account so that abuse prevention keeps working. Legal basis: Art. 6(1)(f) GDPR; our interest is a fair trial and a fair referral programme that are not exploited.

5.12 Referral programme

Every account has a referral code. If someone installs Aspira via your link or enters your code, we store the link between referrer and referee, the status (installed, activated, rewarded, rejected) and the type of reward. On Android, Google Play can pass the code to the app at installation. The referrer does not learn which data the referee stores in Aspira. Legal basis: Art. 6(1)(b) GDPR, for abuse checks Art. 6(1)(f) GDPR.

5.13 Push notifications

If you allow push notifications, we store a push token and your device’s platform. We send notifications via Expo’s push service (650 Industries, Inc., USA), which forwards them to the Apple Push Notification service or Firebase Cloud Messaging (Google). Notifications contain e.g. hints about new hearts, comments, followers or streaks, but no health values. You can turn off push notifications in the app and in the system settings at any time. Legal basis: Art. 6(1)(a) GDPR.

5.14 Product analytics (only with consent)

Only if you agree do we use PostHog Cloud EU (PostHog, Inc., servers in Frankfurt) to understand which features are used and where things get stuck, and to test new variants. We record usage events (e.g. “paywall viewed”, “post published”) with a random installation identifier instead of your account ID. Health values and free text are not recorded, location lookup via IP address is switched off and no person profiles are created. You can withdraw your consent at any time under Settings → Privacy. Legal basis: Art. 6(1)(a) GDPR, § 25(1) TDDDG.

5.15 Crash and error reports

To fix crashes and errors we use Sentry (Functional Software, Inc., USA) with data storage in the EU (Frankfurt, de.sentry.io). A report contains technical details such as error message, stack trace, app version, device model and operating system. We have configured Sentry so that no health values, no content and no IP addresses or other personal identifiers are sent by default. Legal basis: Art. 6(1)(f) GDPR; our interest is a stable app. You can object to this at any time.

5.16 Contact by email

If you write to us, we process your email address and the content of your message to handle your request (Art. 6(1)(b) or (f) GDPR). We delete the correspondence once it is settled and no retention obligations apply.

5.17 Security and abuse prevention in the backend

To prevent abuse, spam and mass scraping of profiles, we limit the number of certain actions per account and time period. We delete these counters after 2 days at the latest. Legal basis: Art. 6(1)(f) GDPR.

6. Recipients and processors

We only pass on data where necessary for the purposes described. Service providers working on our behalf are bound by a data processing agreement under Art. 28 GDPR (DPA).

RecipientPurposePlace of processingTransfer basis
Supabase, Inc. (processor)Database, sign-in, file storage, server functionsEU, Frankfurt (AWS eu-central-1)DPA; Standard Contractual Clauses for any access from the US
komoot GmbH (own responsibility)Place search for gym and home town (Photon, OpenStreetMap), only search text and a rounded pointGermanyArt. 6(1)(b) GDPR
Anthropic, PBC (processor)AI photo scan, AI coachUSADPA; Data Privacy Framework and/or Standard Contractual Clauses
RevenueCat, Inc. (processor)Subscription status, purchase receiptsUSADPA; Data Privacy Framework and/or Standard Contractual Clauses
PostHog, Inc. (processor, only with consent)Product analytics, A/B testsEU, FrankfurtDPA; Standard Contractual Clauses for any access from the US
Functional Software, Inc. – Sentry (processor)Crash and error reportsEU, FrankfurtDPA; Data Privacy Framework and/or Standard Contractual Clauses for any access from the US
650 Industries, Inc. – Expo (processor)Sending push notificationsUSADPA; Standard Contractual Clauses
Apple (APNs, DeviceCheck, Sign in with Apple, App Store)Push delivery, device check, sign-in, purchaseEU / USAApple’s own responsibility or DPA; Data Privacy Framework
Google (FCM, Play Integrity, Google Sign-In, Google Play)Push delivery, device check, sign-in, purchaseEU / USAGoogle’s own responsibility or DPA; Data Privacy Framework
Open Food Facts (own responsibility)Product data for the barcode, directly from the deviceFrance (EU)no third-country transfer
Resend / Plus Five Five, Inc. (processor)Sending sign-in codesEU, Ireland (AWS eu-west-1)DPA; for any access from the US Data Privacy Framework and/or Standard Contractual Clauses
Vercel Inc. (processor)Hosting this websiteEU, FrankfurtDPA; for any access from the US Data Privacy Framework and/or Standard Contractual Clauses

Content you make visible in the community or via share links can be seen by the people you share it with. Beyond that we only pass on data where we are legally obliged to (e.g. to law enforcement authorities) or where it is necessary to enforce our rights.

7. Transfers to third countries

Some service providers are based in the US. Transfers there only take place if an adequate level of data protection is ensured: on the basis of the adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR), where the recipient is certified, and/or on the basis of the European Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR) with supplementary measures. You can request a copy of the safeguards at datenschutz@aspira-app.de.

8. Retention

DataPeriod
Account, profile, entries, posts, recipesuntil you delete them or your account
Consent logas proof for the lifetime of the account and afterwards until possible claims expire (3 years)
Share linksuntil you revoke the link or delete your account
Photos for the AI scannot stored by us
Counting of AI requests13 months, at the latest until account deletion
Counters for request and action limits (incl. IP address for share pages)2 days at most
Website server logs14 days
Reports and moderation decisions12 months after closure, earlier on account deletion unless evidence must be preserved
Device marker against abuse of the trial and the referral programmewithout link to the account, as long as the trial or the referral programme is offered
Backupsoverwritten on a rolling basis; deleted data disappears after 30 days at the latest
Invoices and payment recordskept by Apple or Google according to their tax obligations

Deleting your account: under Settings → Privacy → Delete account you delete your account directly in the app. We then immediately delete all files in your storage areas (profile picture, photos, encrypted progress photos), your customer record at RevenueCat and all data of your account in the database. It disappears from backups after 30 days at the latest. Please note: you cancel a running subscription separately in the App Store or on Google Play; otherwise it continues there.

9. Data security

  • All connections are encrypted with TLS; stored data is encrypted on the server side.
  • The local database in the app is encrypted with SQLCipher; the key is kept in the device keychain.
  • Progress photos are encrypted on the device with AES-256-GCM before upload.
  • All storage areas are private; access is restricted per account at database level (row level security).
  • Images are re-encoded before upload, removing metadata such as EXIF and GPS location.
  • Keys for services such as the AI live only on the server, never in the app.

10. Your rights

You have the right at any time to:

  • access your stored data (Art. 15 GDPR),
  • rectification of inaccurate data (Art. 16 GDPR),
  • erasure (Art. 17 GDPR), directly in the app or by email,
  • restriction of processing (Art. 18 GDPR),
  • data portability (Art. 20 GDPR): under Settings → Privacy you export your data as a JSON file,
  • withdraw consent with effect for the future (Art. 7(3) GDPR).

Right to object (Art. 21 GDPR): where we process data on the basis of a legitimate interest (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. We will then stop processing the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims.

Just write to us at datenschutz@aspira-app.de. You can also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), for example in your country of residence or with the authority responsible for us: the State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia (Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, www.ldi.nrw.de.

11. Other

Obligation to provide data

For an account we need a sign-in (Apple, Google or email). Health data, analytics and push notifications are voluntary. Without them, individual features are not available.

No automated decision-making

We do not make decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). Calorie targets, forecasts and AI suggestions are non-binding recommendations. The automatic hiding of reported content is provisional; a human decides on the outcome.

Minimum age

Aspira is intended for people aged 16 and over. Children may not use Aspira. If we learn that an account belongs to a younger person, we delete it.

Changes

We update this privacy policy when Aspira or the law changes. We inform you about material changes in the app. If a new processing requires your consent, we ask you beforehand.

More information: Terms of service · Community guidelines · Help · Imprint