1. Controller
The controller responsible for processing personal data in connection with MacroSensei is:
Sriraam Sinnarajah
Bahnhofstraße 44
23843 Bad Oldesloe
Germany
Email for privacy enquiries:
Support:
Please direct privacy enquiries to the privacy contact listed above.
2. Scope
This Privacy Policy applies to the MacroSensei app on iOS and Android, its associated website and related online services.
MacroSensei is an app for managing and analysing nutrition, calories, macronutrients, fitness, training, activity, sleep and other information entered or authorised by the user. It also includes social features such as friends, chats, shared content and a rewards system.
MacroSensei is intended for people aged 16 and over. Protected account features provide for explicit date-of-birth confirmation and the setup steps required for the respective feature. The date is protected for the account; later edits to sign-in metadata do not replace that confirmation. A birthday declared at registration or existing metadata is not automatically treated as an age confirmation. This is self-reporting, not independent identity or age verification.
Individual features depend on the platform, installed app version, account status and server-side release. A published version does not mean that every feature is available or enabled on every device.
The separate consent features may require an up-to-date app version. Previous use, existing data, configured synchronisation or agreement to Terms are not reinterpreted as new consent. Already installed older apps or apps running offline cannot be updated on every device through a server change alone. Check available updates; a staged transition does not establish consent or remove age, Health, deletion or privacy safeguards. With your first choice confirmed by the account backend for the purposes described in section 3, including a refusal, the new safeguards apply account-wide to affected server-backed features. Older app versions then need an update for those features; a later withdrawal does not remove these safeguards. Merely opening the choices does not trigger this transition or grant permission.
3. Principles of data processing
We process personal data to operate MacroSensei, provide the features selected by the user, protect the service and fulfil legal obligations, and for processing to which the user has consented.
You decide separately about personal tracking on your devices, private cloud storage and synchronisation, tracking progress for server-side rewards, and sharing selected tracking content. No option is preselected. Each decision is protected for the account with its purpose, applicable information version and time; granting one purpose does not grant another.
The underlying personal-tracking decision applies account-wide. Each device also checks its local startup state and any denials not yet transmitted before processing. A restart or an older cached status must not turn a pending denial into permission. Section 24 explains the conditions for permitted offline continuation.
Without the required choice, the affected area stays off; missing permission is not presented as an empty diary with fabricated zero values. Account, legal documents, support and lawful access, export and deletion requests remain separately available. Sections 5, 11, 17, 21 and 24 explain the purposes and consequences.
Apple Health and Health Connect, Google UMP advertising privacy and transmission of each AI photo have additional separate permissions. They neither replace the choices above nor are granted by them. Section 6 explains imported Health permissions and data flows; section 24 describes the legal bases.
Health data are not used for advertising profiles or personalised advertising.
4. Registration and user account
Depending on the chosen sign-in method, the following data in particular may be processed:
Email address, telephone number, username, display name, authentication and session information, and technical account IDs.
MacroSensei supports or is preparing the following sign-in methods:
Email address and password, telephone number/SMS verification, Sign in with Apple and Google Login.
When signing in with Apple or Google, the respective provider may transmit identification data and, depending on the permissions granted by the user, their name or email address to MacroSensei.
MacroSensei does not store passwords in plain text.
For users aged 16 or 17 residing in Germany, a user declaration that their legal representative has permitted the usage agreement is stored in a protected account record: account ID, declaration and terms versions, and the server confirmation time. It is not a verified parental identity or guardianship and does not grant consent to tracking, Health, AI, advertising or sharing. It creates no parent account, parent email or parental access to records. The declaration is account data and is removed on account deletion; a new registration does not inherit it.
Other users generally do not see your email address or telephone number. In social features, your chosen username or display name is used in particular.
5. Profile, body and nutrition data
MacroSensei may process the following information in particular:
Body weight, height, date of birth, gender or the sex value used for calculations, activity settings, stride length, goals, desired weight change, calorie and macronutrient targets, food diary, meals, foods, quantities, portions, calories, protein, carbohydrates, fat, water, weight history, dietary preferences, exclusions and allergens.
These data serve in particular to provide the tracking, statistics, goals and calculation features requested by the user.
Combined manually entered body, nutrition, activity, training, sleep and wellness data can be health information. Their storage and processing for your personal diary, targets and statistics require separate explicit consent to personal tracking. This applies without an Apple Health or Health Connect connection and before loading existing personal records, making calculations or starting a new data import.
This choice alone does not allow tracking data to be sent to private cloud storage, for server-side reward progress or to other users. Local-only tracking is possible without private cloud synchronisation. Sections 21, 17 and 11 separately explain cloud, tracking rewards and sharing; additional permissions needed for an optional action are not silently enabled.
Other ordinary users have no general access to your private body, nutrition or health records. Shared content and the social rewards information described in section 11 are separate from these private records.
6. HealthKit and Health Connect
Imported HealthKit or Health Connect data, including derived values, require their own explicit account-bound Health consent in addition to the operating system read permission. Depending on the use, personal tracking, private cloud synchronisation, tracking rewards or selected sharing must also be permitted. None of these decisions replaces another. You can decline the Health connection and use manual features with the relevant tracking choice. Older installations may need an update; previous access does not create new consent.
Current functionality includes steps and sleep data. Heart rate, heart rate variability, respiratory rate and oxygen saturation may also be processed for certain sleep analyses where available and authorised. MacroSensei currently does not write data back to Apple Health or Health Connect.
Authorised imported step entries are stored locally. Only with the required tracking, Health and cloud permissions may they be transmitted to the backend together with activity, profile and other private settings. Raw sleep stages and vital signs are analysed on the device and are currently not stored by MacroSensei as a complete permanent raw dataset. Derived sleep duration, day assignment and evidence identifiers may be stored locally with tracking and Health permission and transmitted only with additional private cloud synchronisation permission.
For tracking rewards, signed-in accounts may transmit daily progress, step and sleep task values, evidence identifiers, and observation day and time to the backend. This flow requires personal tracking and the separate tracking-rewards choice, but not private cloud synchronisation. Health-derived values additionally require Health consent. Raw sleep stages and vital signs are not transmitted in this flow. Sharing resulting achievements with other users additionally requires the separate sharing choice and specific permission described in section 11.
You can withdraw account-bound Health consent in the app and operating system permission separately. On withdrawal, the updated app immediately stops new Health work and transmits the account decision to the backend when connectivity is available. Withdrawal on an offline device reaches the server and other devices only after transmission. Once the withdrawal is stored, the server blocks new Health uploads and Health rewards processing, and automated retrieval of mixed Health synchronisation data through the new protected endpoints. A later grant requires another explicit decision.
Withdrawal is not the same as immediate deletion of the entire account. It also does not allow indefinite further processing or restricted storage of previously stored Health data. Where affected data have no other valid legal ground and, where required, an exception for health data, they must be appropriately erased. Necessary legal exceptions need specific justification; access, export and deletion requests remain available. Sections 27 to 29 and privacy@macrosensei.com apply to retention, account deletion and rights. Health and fitness data are not used for personalised advertising.
7. Training and fitness
When using the training features, training plans, exercises, sets, weight, repetitions, duration, rest periods, RPE, notes, training history, manually entered energy values and media added by the user may be stored in particular.
These data serve training planning, documentation, statistics and the provision of recommendations requested by the user. Required permissions for personal tracking and, where applicable, cloud or selected sharing apply; a training feature does not grant them automatically.
During shared training, only the information necessary for the shared feature is disclosed to the participating users.
8. Own foods, recipes and images
Users can create their own foods, meals and recipes.
Personal notes and private images are generally intended only for the respective user unless deliberately shared with others.
User-created product information may be added to the shared MacroSensei food database. Successful account deletion removes the creator association from these shared product records in the updated database; shared product information may remain. Copies already imported by other users or saved outside MacroSensei may remain.
The public product view does not show other ordinary users the original creator's name or email address.
9. Open Food Facts and external food sources
MacroSensei uses external food data sources, including Open Food Facts.
During online searches, search terms, barcodes, language and the selected food market in particular may be transmitted to MacroSensei servers or directly to the respective data provider. For direct requests, the external service may also technically receive your IP address.
MacroSensei does not transmit HealthKit or Health Connect data to Open Food Facts in this process.
10. Camera, photos and videos
Following an explicit user action, MacroSensei may access the camera or selected media, for example for:
Barcode scans, profile pictures, food images, recipe images, chat photos, chat videos, training media, support screenshots, importing food information from screenshots or the AI photo scanner described in section 19.
Access occurs only when the user uses the respective feature and grants the operating system permission.
Barcode camera images are not transmitted to Open Food Facts as complete camera images. The recognised barcode is used for the product search.
According to the current technical implementation, screenshot text recognition takes place locally on the device or locally in the browser, rather than through a generative AI service.
11. Friends, profiles and social features
MacroSensei provides features for finding, adding and managing friends.
Depending on the feature and friendship status, other users may see in particular your username or display name, profile picture, streak or reward information and selected badges.
Step and sleep badges may show, for example, that at least 5,000 steps or at least six hours of sleep were achieved on a certain number of days. These derived achievements can also be health information. Disclosing them and sharing selected tracking content require the separate explicit sharing choice and the specific action with its displayed content, recipients and visibility settings. The sharing choice publishes nothing automatically and does not generally open your diary. This does not publish raw health values, sleep stages or vital signs.
Required personal tracking and Health permission for Health content additionally apply. Permission to share your own health data is not required merely because you receive a message. Later withdrawal blocks new related sharing; data already transmitted to recipients or copies lawfully stored by them cannot always be recalled. See sections 27 to 29 for deletion requests and rights.
Your real first and last name do not have to be displayed publicly; your chosen username or display name is used for social features.
12. Chat and shared content
MacroSensei provides direct and group communication. Depending on the feature, text messages, photos, videos, foods, meals, recipes or training content may be sent. Transmitting sensitive tracking content additionally requires the permissions and specific selection described in section 11; general sharing consent is not an instruction to send. Messages and media are stored on the server and are not end-to-end encrypted.
Deleting content "for me" hides it from the user who deletes it. Deleting content "for everyone" makes it inaccessible to participants. Updated media paths release original files no longer needed for removal through the storage service; other valid message references or pending evidence copies prevent premature removal.
Account deletion removes authentication, personal synchronisation data and account associations. Where the updated deleted-contact context feature is enabled, text visible to remaining participants in the current communication period may remain as context with a neutral sender label. Structured identifiers of the deleted sender and private media are removed from that context; another account's deletion does not grant participants editing rights. Independent moderation cases and explicitly protected cases are handled as described in sections 13 and 14.
Content already imported, downloaded or copied outside MacroSensei by recipients cannot technically be recalled.
13. Reports and moderation
Users can report inappropriate profiles, messages or shared product information.
Reported content, the reporting user, the reported user, time, report reason, screenshots and internal moderation notes may be stored. Reported media may be secured as a private evidence copy.
These data serve to handle reports, protect users, prevent abuse and, where applicable, assert or defend legal claims. In the updated database, product, profile and message reports remain independently of the reporting account. On its deletion, the account association and technical case information are anonymised; messages retain their role as requester or administration. Evidence content may still contain information about the reported person or the incident. Deleting the reported account does not automatically erase these independent cases either.
Closed moderation cases are intended for deletion review after 24 months. Explicit protection holds, media preservation not yet verified and active restrictions prevent release for removal. Original media remain protected until the private evidence copy is verified. The new retention function initially provides only a deletion preview; automatic retention deletion is not enabled. See sections 27 to 29 for retention and deletion requests.
14. Support
If you contact us by email or through a support feature, we process contact information, enquiry content and any attachments or technical information you provide.
In-app support cases and related messages are stored in the backend and linked to the account. Closed Support cases are intended for deletion review after 12 months. Successful account deletion removes the user's own unprotected Support cases. Explicitly protected cases remain independently with an anonymised account association; necessary attachments use the same verified evidence copy before account-owned original files are removed. Evidence content may still contain information needed for the protected incident. The new retention function initially provides only a deletion preview; protection holds are not released merely because a review date has passed.
Support emails are outside this app deletion process; deletion can be requested through privacy@macrosensei.com. See section 27 for retention criteria. We use Microsoft Outlook and Microsoft 365/Exchange Online for email.
Where a public contact channel without login is actually enabled, it is offered with its own privacy notice directly before the form. This channel processes email address, subject, message, language, a random request reference, timestamps and handling and delivery status. Transmission goes through Cloudflare and the protected MacroSensei backend at Supabase to the fixed Microsoft Exchange support mailbox. Account or tracking data are not attached automatically; the entered reply address receives no automatic message. In-app support, direct emails and this contact channel are separate data flows.
Abuse prevention for this contact channel uses daily-changing keyed identifiers derived from IP and email address. They are pseudonymous, not anonymous. Retention of contact content, technical rate counters, received and sent mailbox copies and provider logs must be assessed separately; a short technical counter period is not a message-deletion period. Do not submit health data, private media, chat histories, passwords or access tokens through such a form. Free text can still contain sensitive information; a contact enquiry does not provide general consent to health processing.
15. Push notifications
If you enable push notifications, MacroSensei processes technical push tokens or installation identifiers.
Push notifications may be used, for example, for chats, friend requests, support, reminders, streaks, training, nutrition or water.
Depending on the platform, Apple Push Notification Service, Expo or Google services, among others, may be used for technical delivery.
Push notifications can be disabled at any time in the device settings.
16. Advertising with Google AdMob
The native MacroSensei app includes the Google AdMob SDK for banners, where applicable ads after completed meal actions, and voluntary rewarded ads. Availability depends on account tier, platform, consent status and separate server-side approval for the respective advertising purpose. The WebApp currently does not request AdMob ads.
Depending on consent, region, platform and AdMob configuration, Google may process in particular technical information such as IP address, device and advertising identifiers, advertising interactions, and diagnostic and performance data.
The native app requests current privacy status through Google UMP. Depending on region, status and Google configuration, a consent message may appear where you can consent, decline consent or manage individual options. You can reopen privacy options through “Advertising privacy options” in the app settings where Google makes them available. If the request fails, the app offers the option to continue without advertising. Declining or an error does not automatically authorise ads; normal manual app features remain separate.
The Google SDKs may store or access consent information and technical identifiers on the device. More information about Google's use of data is available at https://policies.google.com/technologies/partner-sites and https://policies.google.com/privacy.
The app does not request advertising when the relevant consent status does not permit it. Where the status and configuration permit it, non-personalised or restricted advertising formats may be used.
MacroSensei does not transmit HealthKit, Health Connect, weight, sleep, vital-sign, training, nutrition or chat content to AdMob as targeting content.
Voluntary scanner ads to earn a scanner key and voluntary Ramen ads are separate purposes with their own release controls and reward rules. For server-verified rewards, Google receives a random session identifier and a separate random pseudonymous identifier instead of the Auth account ID. Google's signed verification callback transmits in particular these identifiers, ad unit, transaction identifier, reward type and amount, and event time to the MacroSensei backend. There they are associated with the authorised account to credit only the verified reward and prevent duplicate credits. These identifiers are pseudonymous, not anonymous. Health, nutrition, chat or private media content is not sent to Google for this purpose. Working scanner verification does not automatically enable Ramen ads or other advertising formats.
Where the scanner ad delivers an SDK revenue event, MacroSensei may store currency, estimated revenue amount and precision level with the associated session in the backend. This estimate replaces neither signed verification nor account authorisation. Testing uses only official Google test ads or properly registered test devices. Tests do not prove general production ad delivery.
17. Ramen Energy and rewards system
MacroSensei distinguishes tracking rewards based on nutrition and fitness progress from ordinary account balances, inventory, scanner keys, subscription entitlements and separately verified rewards for voluntary ads.
Deriving, storing and transmitting sensitive tracking progress for server-side rewards require personal tracking and the separate explicit tracking-rewards choice. Private cloud synchronisation is not required for this. Information may include manual task values, step counts or derived sleep duration with additional Health permission, evidence identifiers, tracking days and observation times. Required age, account, Health and security conditions continue to apply.
Without this choice, the affected tracking-reward progress is not newly evaluated or transmitted to the backend. Existing ordinary balances, scanner keys, inventory and subscription entitlements are not automatically removed as a result; their own rules, privacy and verification requirements remain. In particular, an ad verification does not grant tracking consent or transmit health content as advertising targeting data.
Authorised progress information serves the chosen rewards and prevention of duplicate or abusive credits. Making selected achievements visible to other users additionally requires the specific sharing permission described in section 11.
18. Statistics and improvement of MacroSensei
MacroSensei may use fully anonymised statistics to improve the service.
Identifiable or pseudonymised health and fitness data are used for cross-user model improvement or comparable research or optimisation purposes only where the user has given separate explicit consent.
Names, email addresses, private chat messages and private images are not used as training data for such models.
Such optional consent must not be a prerequisite for normal use of MacroSensei.
Participation in commercial industry reports is an additional choice that is off by default. It is offered only where a separate approval exists for the confirmed country of residence and its reviewed minimum age. Approval for normal app use does not enable industry reports. The four other processing purposes, accepting the Terms, and verifying an email address do not count as consent to this purpose.
If you explicitly participate, the function considers only base calorie targets you newly enter by hand afterwards. It does not import earlier values, calculated targets, meals, macros, body weight, steps, photos or imported Health data. On the device, the entered value is assigned to one of four bands: 1,000–1,799, 1,800–2,199, 2,200–2,599 or 2,600–10,000 kcal per day. Only the band is sent to the backend; the exact calorie value is not transmitted or stored for this purpose.
At most the latest band is held for each participant, together with an account link, entry time, technical event identifier and the associated consent version. No target history is created. The account link is personal data; assignment to a band alone is not described here as anonymisation. This processing relies on your separate explicit consent, where applicable under Articles 6(1)(a) and 9(2)(a) GDPR.
Authorised administrators can access a fixed monthly snapshot without individual accounts, arbitrary filters or export. Displayed participant counts are rounded down to multiples of five. Groups with fewer than 20 people and inferable complementary groups are suppressed together. The snapshot does not change with every request. These rules alone do not establish a general assurance that data are anonymous in all circumstances. Currently no industry reports or individual contributions are sent to companies or other external report recipients.
You can withdraw at any time under Settings → Legal → Industry reports without losing other app features. New contributions on this device stop immediately. Confirming the server change requires a connection; a pending withdrawal is continued when checked again and is not displayed as already completed. Withdrawal removes the account-linked band contribution; account deletion, withdrawal of manual tracking, and retirement of the relevant country approval also remove it. If you consent again, earlier targets are not imported retrospectively. Previously created monthly snapshots contain no account or event identifiers and cannot be broken down by individual account.
19. Artificial intelligence
The optional “AI Photo” feature analyses a food photo you select. Selecting a photo and viewing its local preview do not start an upload. The photo is sent to an external AI service only after you explicitly agree to the transfer for that photo and start the analysis.
The photo is compressed and transmitted through the MacroSensei backend at Supabase to OpenAI for image analysis. OpenAI estimates a dish name and calories, protein, carbohydrates and fat. The results are approximations and you can edit them before adding them to your diary.
OpenAI receives the selected, compressed image, the requested response language and the analysis instructions needed for this assessment. EXIF, location and other embedded image metadata are removed before transmission. Profile, body, Health and chat records are not automatically attached to this request. Information visible in the photo is transmitted, however; please show only food and no people or private information.
The transmitted photo is not stored as a permanent file in the MacroSensei backend by the current scanner flow. Analysis results and technical request data, such as account association, request identifier, photo checksum, timestamps, status and usage data, are stored to provide results, handle retries safely, manage allowances and control costs. An entry you accept becomes part of your food diary. Sections 27 and 28 also apply to retention and account deletion.
MacroSensei does not request OpenAI to store the API response for later reuse. This does not mean that all provider data are immediately deleted: under its current API data rules, OpenAI may retain abuse monitoring logs, including request content, for up to 30 days by default. Temporary technical caches and longer retention for legal or security reasons remain possible. Images suspected of containing child sexual abuse material may be retained for manual review.
The AI processing is not guaranteed to take place exclusively in Europe or under a special agreement that prevents all provider retention. OpenAI information about API data processing is available at https://developers.openai.com/api/docs/guides/your-data. Section 26 and the contact privacy@macrosensei.com also apply to international transfers and requests for further information.
You can decline photo analysis and use food search, the barcode scanner or manual entry instead. Before starting, you can withdraw your agreement or change the photo; that photo will then not be uploaded for analysis. Doing so cannot reverse a transfer that has already occurred. You can send questions or deletion requests to privacy@macrosensei.com.
20. Account tiers and any payments
A paid Pro offering through the Apple App Store and Google Play is planned. The plan is a subscription with a twelve-month term, paid in advance, automatically renewing annually at EUR 23.88 per year, mathematically equivalent to EUR 1.99 per month. The annual plan's equivalent monthly amount is not a monthly charge. A separate monthly subscription is not planned. The planned paid offerings are not currently available; this planned price is not an offer that can be ordered or a worldwide price guarantee.
MacroSensei distinguishes Free, Plus and Pro account tiers. These names and an assigned tier do not by themselves mean a purchase or an ongoing payment. Current entitlements and any expiry are processed in the account backend.
Where advertising is enabled and permitted under applicable privacy requirements, Free provides for banners and meal interstitials; Plus provides for banners but no meal interstitials; Pro provides for no normal banners or meal interstitials. Voluntary Ramen ads are separate. For the AI photo scanner, Free and Plus use verified scanner keys. Collected keys can be used later without starting a new ad for every analysis. Pro has a limit of 20 AI analyses per personal day using the app's day assignment. This daily allowance is not credited as scanner keys; unused analyses do not accumulate or carry forward to later days. Availability and allowances are displayed in the respective feature; a tier does not bypass consent, device, budget or security requirements.
RevenueCat is planned as an additional service for purchase and entitlement administration in the native store flow. This processing is not active yet. If actually introduced, the product, purchase, transaction, technical device/SDK and status information necessary for purchase and entitlement administration and the Supabase account ID will be transmitted to RevenueCat to associate purchases and entitlements with the account. The MacroSensei backend may retrieve confirmed subscription status from RevenueCat and receive authenticated status notifications. Account association, store, product, validity, activity, renewal status and technical event identifiers may be stored for this purpose. The account ID is not anonymous. Health records, chats and private photos are not intended purchase-administration content or targeting data.
Before an actual order, the applicable store prices, durations, renewal, cancellation and, where relevant, withdrawal information are displayed separately. Automatic renewal can be stopped through the respective store's subscription management; the remaining period already paid for is unaffected. The Terms and this Policy do not themselves trigger a purchase. A payment method actually used processes only the information required to administer the contract and entitlements.
The app paths currently reviewed contain no entry of complete credit card or bank details to MacroSensei. Account deletion does not automatically cancel a store subscription that may have been purchased separately.
21. Private synchronisation and Supabase
MacroSensei uses Supabase for authentication, database functions, storage, synchronisation, social features and server-side functions, among other purposes.
Private cloud storage and cross-device synchronisation are a separate optional choice. Sensitive tracking data additionally require personal-tracking permission and, where applicable, the Health or tracking-rewards permissions required for their data type. These data include food diaries, recipes, training data, dietary preferences, targets, activity, body and weight data, steps, derived sleep information, private media references and historical changes. Cloud permission alone does not allow sensitive collections to be read or transmitted; sharing remains a separate action under section 11.
Selected nonsensitive app settings, such as language and contact preferences, can be synchronised separately with the cloud choice without enabling personal health tracking. Authentication and necessary account and security information are distinct from this. The private cloud choice does not give other users general access to your private records.
Restoring existing body and target settings on a new device requires the relevant tracking and cloud permissions in addition to account safeguards. Without them, these data are not read merely for setup. You can continue with local-only tracking without cloud synchronisation. Backups, imports and stored changes retain the safeguards of their original data type; a backup is not a way around missing consent.
Suspended synchronisation does not overwrite existing originals with empty defaults and is not acknowledged as a successful import. A later explicit grant may resume permitted pending data changes; it is not retroactive consent. Temporary deferral is neither confirmation of erasure nor a ground for indefinite retention; see section 24 and sections 27 to 29.
The production Supabase project's primary region is eu-west-1 (Ireland). This identifies the primary project location and does not exclude processing by providers, subprocessors, support or other infrastructure outside that location. Supabase publishes information about subprocessors at https://supabase.com/legal/customer-resources/subprocessor-list.
Private synchronisation settings do not control all online features: authentication, social features, support and rewards have separate backend data flows.
For local use and offline opening, MacroSensei stores app data on the device or in local browser storage. These data are separate from server-side account storage. Authentication information uses protected device storage in the native app and respective browser storage in the web version.
22. Website and WebApp
The public information website at macrosensei.com, including these legal documents, is provided through Cloudflare. When these pages are accessed, Cloudflare may process in particular IP address, URL, browser and network information, and technical error reports. According to the current implementation, these static pages contain no own analytics or advertising tracking scripts and set no own cookies or local tracking storage. Cloudflare information is available at https://www.cloudflare.com/policies/privacy/.
A public contact channel, where actually offered, is distinct from purely static information pages. Its own notice before the form explains necessary inputs, technical protection identifiers, recipients and rights; section 14 provides further information. Merely preparing a contact channel does not mean a working form is already offered.
The Expo-hosted WebApp at macrosensei.expo.app is separate. It additionally uses the account and app data flows described in this Policy. The browser may store session information, local app data, settings and content required for offline features; technical connection data is also processed for delivery. Signing in, synchronising or using an online feature may connect to Supabase and the respective providers described here. The statement about static information pages does not mean that the WebApp operates without browser storage or online data processing.
23. Marketing
Service emails relating to accounts, login, security, support and essential contractual or feature information may be necessary and do not require marketing consent.
Newsletters, email advertising or other marketing communication take place only with separate consent where legally required.
Marketing consent, once given, can be withdrawn at any time with effect for the future.
24. Legal bases
Depending on the processing, we rely in particular on:
Article 6(1)(b) GDPR for performance of the user relationship, necessary account features and requested contractual services,
Article 6(1)(a) GDPR for the separately chosen consent-based purposes, particularly personal tracking, private cloud, tracking rewards and selected sharing,
Article 9(2)(a) GDPR for processing special categories of personal data based on explicit consent, in particular the relevant health data,
Article 6(1)(f) GDPR for security, abuse prevention, error analysis, protection of our services, and assertion and defence of legal claims,
Article 6(1)(c) GDPR for legal obligations.
Consent must be informed, voluntary and explicit for its particular purpose. Special categories such as health data additionally require an applicable exception under Article 9 GDPR. Mere necessity for an app feature, a general security interest or an existing account does not replace this requirement.
You can change or decline choices under “Manage data processing” and withdraw consent with effect for the future. The affected local processing and new related transmissions stop. Lawfulness of processing before a valid withdrawal is unaffected. Previously stored data are handled according to their actual remaining legal ground, not automatically retained indefinitely in restricted storage; see sections 27 to 29.
A first grant becomes active only after protected confirmation by the account backend. If that confirmation is unavailable, no new purpose is provisionally enabled. A previously genuinely confirmed tracking permission matching the account and current information version may continue automatically for local offline use on the same installation. This requires a safely saved local resumption state, its durable safety check, and no pending denials or known newer blocks. This also applies to temporary network failures during already safely authorised local use. Following an uncertain interruption, uncertain denial, an unknown browser tab, a permission that no longer matches, or storage failure, automatic continuation is not allowed; a renewed check and explicit confirmation of permitted resumption are required. An older stored status alone is insufficient. Offline continuation does not grant new server-confirmed consent or permit cloud, tracking-reward or social transmissions. The Health connection is not continued in this offline mode; new Health work remains blocked.
A denial or withdrawal takes effect locally on the affected device immediately. Whether the decision has been durably saved there and whether the server has confirmed it are shown separately. While offline or following a transmission failure, the decision reaches the server and other devices only later; transmissions already made cannot be undone by this. Reconnection transmits the pending decision, not an automatic renewed grant. Account or device changes and restarts must not bypass this pending denial.
Acknowledging this Privacy Policy, accepting Terms, existing Health permissions, advertising choices or agreement to an AI photo do not grant any of the other consents. Purpose and information version belong to the decision. Changed information or adopted existing data are not silently treated as new agreement.
25. Recipients and service providers
Depending on the feature used, personal data may be processed in particular by the following categories of recipients:
Supabase for authentication, database, storage and backend functions; Google for Google Login, AdMob/UMP and, where applicable, Google Play; Apple for Sign in with Apple, HealthKit and, where applicable, App Store and push services; Expo for WebApp hosting, app updates and certain push features; Microsoft for email services; Cloudflare for website delivery and network services; Open Food Facts and other food sources for product searches; OpenAI for the expressly requested AI photo scanner described in section 19.
Data may also be deliberately disclosed to other MacroSensei users when the user uses a sharing, chat, friends or shared training feature.
26. International data transfers
MacroSensei is offered worldwide and uses providers whose processing may partly take place outside Germany or the European Economic Area. The primary Supabase project location in Ireland does not exclude such additional processing locations.
Providers publish their own information about international transfers and intended safeguards, such as adequacy decisions and standard contractual clauses. Supabase information is available at https://supabase.com/legal/customer-resources/data-processing-addendum and https://supabase.com/legal/customer-resources/subprocessor-list. That provider information does not describe all individual MacroSensei settings and agreements.
You can request information about a specific processing operation or transfer through privacy@macrosensei.com.
27. Storage period
Storage periods depend on processing purpose, account existence, open enquiries or reports and, where applicable, legal retention obligations or necessary legal defence. For email enquiries, relevant factors include whether the enquiry is still being handled, questions or a dispute remain open, or the content is still needed as necessary evidence of a specific obligation or legal claim. A review period provided within the app is not an automatic email deletion period.
Scanner jobs, results, key wallets and associated verification data may also be stored for feature continuation, account administration, abuse prevention and traceable rewards. A session can expire without automatically deleting all related records. The scanner path keeps no permanent copy of the uploaded photo at MacroSensei; the limitations in section 19 apply to provider retention. This Policy does not promise a separate fixed automatic deletion period for all scanner and verification data.
Account data and private synchronised data are retained only as long as needed for their respective lawful purpose. Following refusal, withdrawal or loss of a consent ground, the affected data still needed on another valid ground must be specifically assessed. Without such a ground, data must be appropriately erased; merely restricted storage, suspended synchronisation or continued account existence is no substitute. Health data must also have any required Article 9 GDPR exception. Statutory retention or legal defence allows only the data, purposes and period actually necessary for it, not all tracking data indiscriminately.
Existing data and interrupted imports are not silently replaced with defaults or treated as retrospectively authorised. Temporary technical preservation for integrity and handling a rights request is not an unlimited new purpose. You can ask about the affected data and the specific retention justification and request access, export or erasure.
Retention review considers closed in-app Support cases after 12 months, all moderation kinds after 24 months, and administration audit data after 24 months from recording. These dates are review points, not a blanket minimum retention period or a guaranteed automatic deletion. Case time starts on closure; reopening resets it. For cases closed before rollout, time conservatively starts at rollout because a reliable earlier closure time was not stored.
Explicitly protected cases and audit data remain protected until release. An overdue review date does not automatically release a hold. Pending evidence copies, protected original files, active restrictions and incomplete account deletions are not treated as eligible for removal.
The technical account deletion receipt contains the account ID, hash of the random deletion receipt, and creation and completion times; the file list is cleared on completion. Completed receipts enter deletion review after 30 days; incomplete operations do not.
The retention function initially provides only a deletion preview. It removes no cases, audits, receipts or their media and starts no automatic deletion schedule. Actual retention cleanup requires separate approval after reviewing specific data types, protection reasons and the preview. Account deletion requested by a user remains separate; see sections 13, 14 and 28.
Account deletion does not immediately remove data from all provider logs, backups, email inboxes, other devices or copies saved outside MacroSensei. For technical logs, relevant criteria are how long specific errors, security incidents or abuse cases need investigation and necessary evidence needs preservation. For backups, relevant criteria are the recovery purpose, the respective system's backup and overwrite cycle and any statutory retention obligations. This Policy does not promise a specific backup or log deletion period or an automatic deletion process. Copies already transmitted to or stored by other users may remain. You can send deletion requests and questions about specific retention to privacy@macrosensei.com.
28. Deletion of the user account
Users can initiate deletion of their MacroSensei account through the designated app feature or contact privacy@macrosensei.com.
The technical process removes account-owned original files from the active backend, deletes the authentication account and dependent personal account records, and clears account-linked local app data on the device on which the process completes. An interrupted deletion can be retried with the secret receipt created beforehand. Pending operations block new account writes and reward actions.
Before removing needed original media, the process secures private evidence copies for independent moderation cases and explicitly protected Support cases. The copy must be present in private storage with the matching media type and size; until then, the original remains protected. The user's own unprotected Support cases are removed. Independent moderation and protected cases remain with an anonymised account association, as may necessary security, audit and deletion receipt data; see sections 13, 14 and 27.
Shared product information may remain after removing its creator association. Where the updated context feature is enabled, visible chat text may remain for other participants without the deleted sender's structured identifier or private media; see section 12. Copies already imported, downloaded or saved outside MacroSensei by other users may remain.
Account deletion does not erase source data in Apple Health or Health Connect or automatically erase support emails, provider logs, backups or copies on further devices.
29. Users' rights
Where the statutory requirements are met, you have in particular the rights of access, rectification, erasure, restriction of processing, data portability, objection and withdrawal of consent you have given.
Requests can be sent to privacy@macrosensei.com. You can exercise these rights without active personal tracking, without cloud synchronisation or after declining optional processing. Account, support and protected routes for requesting access, export or deletion remain separate; a request need not be initiated by loading your diary. Appropriate proof of your entitlement may be required before disclosure or deletion. A request is not treated as new consent for normal tracking processing.
Users in the European Economic Area also have the right to lodge a complaint with a competent data protection supervisory authority.
Depending on your place of residence, additional regional privacy rights may apply. MacroSensei will also respect such statutory rights for users outside the EEA where the respective laws apply.
30. Sale and disclosure for advertising purposes
MacroSensei does not sell personal data for money.
Depending on the applicable law, personalised advertising may, however, be classified as "sharing", "targeted advertising" or a comparable disclosure.
Where such rights exist, users can withdraw their consent or object to such use through the privacy and advertising settings.
31. Security
MacroSensei implements technical and organisational measures to protect personal data.
These include authentication, access controls, Row Level Security, private storage areas, encrypted network connections and protected local storage for authentication information, among other measures.
Chats and app content synchronised on the server are currently not end-to-end encrypted.
No technical measure can guarantee complete protection against all risks.
32. Changes to this Privacy Policy
This Privacy Policy will be updated when features, providers used or legal requirements change.
In particular, it will be updated before future features such as address book access, voice messages or microphone use, further external AI purposes or additional health data imports are activated.
Users will be informed in an appropriate manner of material changes.