BiteBoogie · Karkossa Apps

Privacy Policy

Last updated: 4 November 2026

How BiteBoogie handles your account, planning and optional health information.

Movement and relaxation

Movement routines, animations, time windows and the easier variation run in the browser or app view. The daily suggestion uses the local time; it does not analyse health details or laboratory reports. Exercise progress and time remain only in the memory of the open session and reset when you reload or sign out. They are not saved to your account or sent to fitness services. This area does not request sensor, location or Health Connect permissions.

The short exercise videos with sound are loaded on demand from our own application server. This involves the web requests described under technical data, including the IP address and requested file path. Playback events and exercise completions are not sent to your account as workout history or to an external video service. You control sound and playback.

1. Who is responsible?

BiteBoogie is published under the Karkossa Apps / Karkossa brand and operated by MÉLUNÉE Paris Korlátolt Felelősségű Társaság (MÉLUNÉE Paris Kft.), Izabella utca 68/B A. lház. Fsz. 5. ajtó, 1064 Budapest, Hungary. For privacy requests, contact p.karkossa@melunee.com. This policy covers the BiteBoogie Android app (com.biteboogie.app), biteboogie.melunee.com and its application service at api.melunee.com.

2. Data you provide

3. Purposes and legal bases

We process account and planning data to provide your requested service and synchronise it across devices (GDPR Article 6(1)(b)). Security, abuse prevention and essential diagnostics rely on our legitimate interest in a secure, reliable service (Article 6(1)(f)). Applicable accounting or legal duties rely on Article 6(1)(c). Optional health data is processed on your explicit consent (Articles 6(1)(a) and 9(2)(a)). Support requests are handled to provide the service or respond to your request.

4. Health information and laboratory PDFs

Health features and document uploads are optional. You can use general planning without uploading a report. The app requests consent when saving health-related profile choices; the laboratory upload disclosure explains your consent to private document storage. PDFs are stored for your own access, history and medical appointments. They are not automatically medically interpreted or sent to a generative-AI service for analysis. Recipe matching uses your selected profile and ingredient choices, not an automated interpretation of PDF contents. Upload only documents you are entitled to provide. Withdraw consent by removing optional profile information, requesting document deletion by email, or deleting your account. Withdrawal does not affect earlier lawful processing. BiteBoogie does not provide a diagnosis or replace medical care.

5. Google sign-in and Google Play purchases

If you choose Google sign-in, Google supplies a unique account identifier and your verified email address. We use them to sign you in or link your account. We do not receive your Google password or contact list. Google also processes information under its Privacy Policy. When Google Play purchases are enabled and used, Google handles payment details. We process the product/base plan, purchase token, subscription state, expiry and a pseudonymous account association to verify access and handle subscription changes. We do not receive your full card details. Google may retain its own payment records. Deleting BiteBoogie does not cancel a Google Play subscription.

6. Technical data, cookies and local storage

Requests transmit IP address, request time, requested URL, browser/app information and technical error data. Server-side IP-to-country lookup may suggest a language; it does not use GPS or send your IP to an external geolocation lookup service. Essential session cookies keep you signed in, normally for up to 30 days. Short-lived security cookies and app-local proof values protect Google sign-in. The web version may store your language preference locally and use a service worker for installation/offline assets. Browser or Android controls let you clear local data. Login and synchronisation then require signing in again. BiteBoogie does not include advertising SDKs or behavioural advertising trackers, and we do not sell personal or health data.

Optional usage reports and profile sharing

Your profile provides two independent sharing choices, both off by default. Your choice does not affect access to the app. If you allow usage reporting, authorised BiteBoogie staff can see, under your name or email, when and how often you use the app, areas and recipes opened, and recipe, cooking, favourite and shopping-list actions requested. This includes PDF, print and share requests, sessions, timestamps and estimated foreground time. This supports personal assistance and app improvement. A requested action does not confirm a completed file download or a meal actually cooked. Usage events do not include messages, document contents or device identifiers.

A separate explicit profile-sharing choice allows your selected diet, exclusions and health restrictions you entered to appear in the protected Producter for support and statistics. Health details are also shown only if you consented to saving them in your dietary profile. We do not infer diagnoses from this information or your behaviour. This choice does not release laboratory PDFs for usage reporting.

You can change or withdraw either choice at any time under “Profile & subscription” → “Your data choices”. Withdrawing usage consent deletes active usage events and related sessions for your account. Withdrawing profile sharing stops its display in these reports; your dietary profile for your own planning remains. Reports cover at most the last 90 days. Older usage events are removed at the next cleanup, triggered by reporting or usage ingestion at most once daily. The storage rules below apply to backups.

For gifted access we process the number of free months, reason, grant and expiry times, and your acknowledgement so that the gift notification is shown correctly. This service notification also appears without usage-reporting consent.

Data reporting terms supplement

7. Recipients, hosting and international processing

Our authorised personnel and technical service providers can process data only as needed to operate, secure and support the service. Supabase provides the application database and private document storage in the configured EU Frankfurt region; this does not mean every provider operation occurs exclusively in the EU. Google provides optional sign-in and Play distribution/payment services. Providers may use subprocessors or process operational information outside the EEA. Applicable provider arrangements include data-processing terms and international-transfer safeguards such as Standard Contractual Clauses where required; see Supabase’s DPA. Contact us for information about safeguards. We may disclose information where required by law or to establish or defend legal claims. We do not share laboratory PDFs with Google for login or billing.

8. Retention and security

Account information and saved planning data are kept while your account remains active, unless you request earlier removal where available. Documents are kept until account deletion or a document-deletion request. Account deletion removes active account data and sessions; file cleanup starts promptly and is retried if needed. Deleted data may temporarily remain in restricted provider backups until overwritten under the applicable backup cycle; it is not used for ordinary service access. Routine web-server access logs are rotated daily with 14 archives (approximately 15 days including the current log); incident evidence may be retained longer where necessary. Support correspondence is kept while needed to resolve the request and related claims. Legally required transaction/accounting records may be retained for the applicable statutory period. We use HTTPS, hashed passwords, private document storage and server-side account access checks. No system can promise absolute security.

9. Delete your account or documents

In BiteBoogie, open Profile & subscription → Delete account at the bottom, then confirm. For security, a recent sign-in may be required. Alternatively, email p.karkossa@melunee.com with the subject “BiteBoogie account deletion”, preferably from your registered email. You may also request deletion of individual PDFs by identifying the relevant report dates; do not attach medical documents to the email unnecessarily. We may verify your identity before acting. Account deletion removes your profile, planning and shopping state, Google linkage, sessions and app-associated purchase records, and triggers deletion of uploaded PDFs. Necessary legal records and temporary restricted backups are subject to the retention rules above. Cancel an active subscription separately in Google Play to prevent future charges.

10. Your rights and complaints

Subject to the GDPR’s conditions, you can request access, correction, erasure, restriction and portability, withdraw consent, and object to processing based on legitimate interests. Contact the address above. We normally respond within one month; lawful extensions may apply and will be explained. You can complain to your local supervisory authority or Hungary’s National Authority for Data Protection and Freedom of Information (NAIH). Recipe filtering is automated matching, not a decision producing legal or similarly significant effects.

11. Minors and changes to this policy

Some dietary profiles require adult-status confirmation. Minors should use health-related features only with appropriate parental or professional guidance; where legally required, parental authorisation is necessary. If a child has supplied data without required authorisation, contact us to arrange removal. We will update this page when processing changes and provide additional notice or obtain new consent when required. Providing account data is necessary to operate an account; health choices and PDFs are optional. Without those optional inputs, the related personalised features are limited, but general planning remains available.

Personal details and recorded account access

In “Profile & subscription” you may optionally save your name, date of birth, country of residence and gender. Authorised BiteBoogie administrators can see these details for personal customer support and account administration. Processing is based on your consent under Article 6(1)(a) GDPR when you select the explicitly labelled “Save optional details” button. You can use the app without these details. Select “Remove details” to delete them and withdraw consent at any time; withdrawal does not affect the lawfulness of previous processing. Missing details are not guessed or copied from accounts in other services.

From 4 November 2026, successful registrations, sign-ins and confirmed account access record the first and latest observed IP addresses, a registration IP only for an actually observed registration, the latest sign-in IP, associated times, a broad platform category and the BiteBoogie application service used. Country is resolved from a local IP database without sending your IP to an external geolocation service. It is approximate, may differ because of mobile networks or VPNs, and does not establish residence. Earlier registration IPs are not reconstructed without a reliable source.

These limited technical account details support account security, abuse prevention and assistance with sign-in issues, based on our legitimate interest in a secure service under Article 6(1)(f) GDPR. They are not used for advertising, diagnosis or optional content-usage analytics. Only authorised administrators may view them in the protected Producter; opening the detail view is audited without the displayed data values. Individual IP addresses stop being displayed after 90 days and are removed by a daily cleanup task. Approximate countries, platform and times remain as a limited account history until account deletion. The deletion, backup and objection rights in this policy also apply. Separate optional usage and health-data permissions remain in place.