Privacy policy

This policy applies to the Eatsboard iOS app, the website at https://www.eatsboard.com, the associated backend services, AI features, support communications and App Store and in-app purchase processes.

Eatsboard is a meal planning application with an optional food diary. The app may process accounts, profiles, groups, weekly plans, recipes, shopping lists, preferences, body data, weight history, logged meals with progress displays and AI-assisted suggestions in order to provide its features.

When you visit the website, technical access data is automatically processed on our server at Hetzner in Falkenstein (Germany). This may include your IP address, the date and time of the request, the file requested, referrer, browser type and operating system. This data is needed to deliver the website, analyse errors and secure the systems.

If you contact us by email, we process your email address, your message, any attachments and information you provide voluntarily to handle your request. Support requests sent to [email protected] are handled personally by the operator named in section 1. We use Microsoft 365 for our mailboxes; providers and processing locations are explained in section 9.

The legal bases are Article 6(1)(b) GDPR where the request concerns pre-contractual or contractual purposes, and Article 6(1)(f) GDPR for technical security, error analysis and general communication.

Use of the app may involve processing account data such as your email address, display name, avatar, login provider, authentication data, language, theme and notification settings. You can sign in using email and password, Sign in with Apple or Google sign-in; the relevant provider supplies the data required for sign-in, such as your email address and name.

Depending on how you use it, Eatsboard also processes profile and feature data, such as your nutrition profile, onboarding answers, allergies, intolerances, dislikes, nutrition goals, body profile including height, birth year and sex, weight history, food diary with meals consumed and calorie and nutrient totals, group memberships, invitations, weekly plans, meal slots, dishes, recipes, ingredients, shopping lists, cooking and rating history, chat messages, usage status, credits and internal events for security and error analysis.

Processing to provide the app's features is based on Article 6(1)(b) GDPR. We process security, abuse prevention and stability data on the basis of Article 6(1)(f) GDPR.

You can voluntarily provide information in Eatsboard that may be health-related, such as allergies, intolerances, dietary styles, nutrition goals, preferred or disliked ingredients and personal notes. This information helps the app create suitable suggestions, warnings and shopping lists.

If you use the food diary, you can also record your body weight throughout the day, your height, birth year and sex, and log meals you have eaten. This information is used to calculate your basal metabolic rate and your calorie and nutrient needs, and to display progress towards your nutrition goal. We deliberately collect only your birth year, not your full date of birth, because your age in years is sufficient for the calculation.

To the extent that this information constitutes special categories of personal data, we process it exclusively on the basis of your explicit consent under Article 9(2)(a) GDPR and only for the features you request. You give this consent explicitly before the relevant processing, separately from consent to external AI. You can withdraw it at any time with effect for the future in the app under Profile → Consents & data export.

Eatsboard does not replace medical advice. The app provides meal suggestions and organisational assistance, but does not make medical diagnoses or give binding health instructions.

Eatsboard uses AI features to evaluate profiles, suggest weekly plans, explain dishes, structure recipe or shopping list information and provide similar assistance.

For these purposes, the necessary inputs and contextual data may be transmitted to technical AI providers. OpenAI is used for text and image features, and xAI for image generation. Additional AI recipients will only be enabled after appropriate information and consent. This data may include profile notes, allergies, intolerances, dietary preferences, shared kitchen equipment, selected dishes, chat content, or image and recipe information. Saved allergies and intolerances may also be processed for basic features and transmitted to AI providers as necessary context when tracking is disabled. The tracking switch does not withdraw these consents. Food diary entries may be transmitted only when nutrition tracking and the separate use of tracking for the Guide are enabled and the respective consents are current: this includes dishes and ingredients consumed, calorie and nutrient totals for the relevant day and the associated targets.

Nutrition tracking and “Tracking for the Guide” have separate switches and separate, versioned consents. Turning a switch off stops the corresponding further use, but does not withdraw consent or delete data. Turning off nutrition tracking also turns off its use for the Guide; enabling it again does not automatically re-enable Guide access. Conversation contexts and memories automatically derived from tracking must not be sent to AI again when access is disabled. Unresolved older contexts are excluded from automatic reuse; visible history is retained.

The structured fields of your body profile (body weight, height, birth year and sex) are not transmitted to AI providers through the diary tool. If you include this information yourself in chat messages, profile notes, recipe texts or images, it may reach the named AI providers as part of that content.

Eatsboard may also derive information for your profile from chat content and repeated plan feedback. Depending on the processing involved, external AI features are used for this. Allergies are not adopted as confirmed restrictions solely on the basis of such information.

Transmission to AI providers is based on your consent (Article 6(1)(a) GDPR), which you give separately and explicitly before the relevant processing, and which you can withdraw at any time with effect for the future in the app under Profile → Consents & data export.

The catalog, manual planning and shopping list can be used without health or AI consent. Personal profiles, allergy checks and health-related preferences require health consent. AI features, including scans and image generation, still require both consents. Declining or withdrawing consent blocks the relevant processing while neutral manual features remain available. Saved dish variants and ingredient substitutions remain visible as chosen meals and are included in the shopping list. Without health consent, no new personal preferences are applied and no current personal allergy checks take place. Manual planning does not promise an allergen-free meal. Missing permission must not be replaced with an empty allergy profile to continue personalised AI planning. Withdrawal immediately stops the affected processing and starts deletion of the related data. Withdrawing health processing removes health details, tracking data and dependent Guide content. Withdrawing nutrition tracking removes the diary, body and weight data, tracking goals and Guide content derived from them. Withdrawing AI permission removes Guide conversations and dependent learned analyses; withdrawing “Tracking for the Guide” removes the corresponding tracking-derived content. These last two withdrawals retain your diary while health and tracking consents remain valid. Mixed content that cannot reliably be separated is removed in full. Chosen meals, accepted alternatives and shopping quantities are kept; personal explanations are removed. Cleanup covers database copies, affected profile snapshots and technical AI run files. Failed file and storage deletions are retried automatically. The app displays pending deletion; new consent is blocked until it completes. Legally required purchase and consent records are retained. Shared group profiles contain only the active member count and selected kitchen equipment. Personal health details are not stored as shared group rules or memories. The automatic export excludes mixed AI content about other people and content whose subjects are unclear; you can request supplementary access through our privacy contact. Consents, data export, account deletion and management of existing App Store subscriptions remain accessible through the privacy view. You can also exercise your rights using the contact details below.

Current permission is checked again before further AI calls. Calls in progress are cancelled where possible; data already transmitted cannot technically be retrieved. Work interrupted due to withdrawal does not restart automatically after you consent again.

We limit the data transmitted to what is required for the feature. Do not use AI features for information you do not want to include in the respective processing.

We verify Apple transaction signatures and store a technical purchase association including the store environment, transaction identifier and original Eatsboard account. After complete account deletion, we remove the account association and retain a blocked technical purchase identifier so that the same purchase cannot be credited again or assigned to another account. Deleting your account does not cancel Apple subscriptions.

If you use Premium features, subscriptions or credits, purchase-related data is processed. This may include product identifiers, transaction identifiers, purchase status, restorations, timestamps, usage tiers, allowances and technical synchronisation data.

Payments are handled through Apple and, where used, RevenueCat. Eatsboard processes the information required to verify purchases, unlock features, manage allowances and provide support for purchase issues.

The legal bases are Article 6(1)(b) GDPR for purchase and usage contracts and Article 6(1)(c) GDPR for statutory retention and documentation obligations.

The app stores certain data locally on your device so that sign-in, display and ongoing processes work reliably. On iOS, session tokens and the technical state of secure sign-in are stored in the device Keychain. These entries are tied to the device and are available only while it is unlocked. Local data may also include theme and accent colour settings, OAuth return information, temporary purchase synchronisation data and technical idempotency keys.

This local storage is necessary for the app's functionality. You can remove local app data using your operating system's features; doing so may reset sign-in or ongoing processes.

We use technical service providers to deliver Eatsboard. These include providers for authentication, databases, storage, hosting, AI features, App Store purchases, purchase synchronisation, email communication and error analysis.

Hosting and self-hosted services: We operate the website and backend ourselves on a server at Hetzner Online GmbH in Falkenstein (Germany). We also self-host Supabase there for authentication, database and storage features. This infrastructure processes the account, profile and feature data required for the app, as well as technical access data. Supabase here refers to the software we operate ourselves; we do not use Supabase Cloud for these services.

Sending app emails: We use Amazon Simple Email Service (AWS SES) from Amazon Web Services in the Frankfurt region (Germany) for app emails, such as registration and password reset emails. This involves processing the sender and recipient addresses, message content and technical sending and delivery data required for delivery. The purpose is to provide and secure your account on the basis of Article 6(1)(b) GDPR and, where necessary to prevent abuse, Article 6(1)(f) GDPR.

Mailboxes and support: We use Microsoft Online / Microsoft 365 with mailbox storage in Europe to receive, store and reply to emails. Microsoft processes email addresses, message content, attachments and technical communication data. The purposes and legal bases for handling support requests are described in section 3. This does not constitute a commitment to processing exclusively within Germany.

Database backups: To recover from data loss, we store database backups on our own infrastructure and in Cloudflare R2. These backups may contain the personal data stored in the database, including account, profile and health data. The Falkenstein server location does not describe the storage location of these external backups.

Apple processes App Store payments and, if Apple sign-in is selected, sign-in; Google is involved if Google sign-in is selected. RevenueCat receives account and purchase identifiers and purchase and subscription states to verify and unlock features. RevenueCat also processes purchase history for subscription and revenue reports (dashboard analytics). Our legitimate interest is the traceable management and economic analysis of our subscriptions (Article 6(1)(f) GDPR). Health data is not sent to RevenueCat. Additional advertising or attribution integrations are not enabled. Recipients of AI inputs are described in section 6.

Service providers receive personal data only to the extent necessary for the respective purpose. Even when European storage locations are selected, international providers may process or access data outside the EU or EEA, for example for technical support. Transfers to such third countries require compliance with Articles 44 et seq. GDPR, in particular an applicable adequacy decision or appropriate safeguards such as standard contractual clauses and, where necessary, supplementary protective measures. You can request information about the applicable safeguards and a copy via the email address in section 1.

We retain personal data only for as long as necessary for the stated purposes or as required by statutory retention periods. Account data, app content, profiles, groups, plans and purchase data are generally stored for the duration of the account or contractual relationship.

We retain support and contact requests for as long as required for handling them, maintaining traceability and fulfilling legal obligations. Technical logs omit raw error objects, messages containing user input and profile content, and are deleted once no longer needed for security and error analysis.

Technical AI run artefacts are retained for error analysis for a maximum of 30 days, and detailed development traces for a maximum of 14 days; tracing is disabled in production. Regular automatic deletion runs enforce these periods.

You can initiate account deletion directly in the app under Profile → Delete account. Before deletion, Eatsboard shows a preview of the main consequences. If your account is linked to Sign in with Apple, the app requests renewed Apple confirmation before deletion so that the Apple token can be revoked.

When your account is deleted, we remove in particular your profile, onboarding and preference data, nutrition goals, ingredient preferences, body profile, weight history, food diary including individual entries, chat content, suggestions, AI memory snapshots, personal events and your own dishes and recipes. Your own dishes also disappear from shared plans. Shared group meal plans may remain for other active members; where possible, group ownership is transferred to another active member.

The local technical user record may be retained as a pseudonymised reference so that remaining group, plan, purchase or security data retains its integrity. Your email address, display name, avatar and personal settings are removed or replaced with deletion markers. Purchase, ledger, RevenueCat and transaction data may be anonymised or retained in accordance with retention requirements where necessary for billing, documentation, abuse prevention or legal obligations.

You can also request deletion of individual items of personal data via [email protected] . Statutory retention obligations, payment records or legitimate security interests may mean that some data cannot be fully deleted immediately.

Subject to the applicable legal conditions, you have rights of access, rectification, erasure, restriction of processing, data portability and objection to certain processing.

Where processing is based on consent, you can withdraw that consent with effect for the future. You also have the right to lodge a complaint with a competent data protection supervisory authority.

For requests, you can contact us at [email protected].