Privacy Policy
How we treat your data.
This Privacy Policy explains how ZUMI ("ZUMI", "we", "us", "our") collects, uses, stores, and shares personal data when you interact with our service through messaging platforms (currently WhatsApp and Telegram, with iMessage planned) and through our website and dashboard at meetzumi.com.
ZUMI is currently in private beta. The service, its features, and the way data is handled may change frequently during this phase. We will keep this policy up to date and will notify users of material changes.
1. Who we are (Data Controller)
The data controller of ZUMI is operated from Italy. As ZUMI is in private beta, the controller currently operates as a private individual residing in Italy and not yet as an incorporated entity. The full identity of the controller is provided upon any legitimate request (for example, a GDPR data-subject request, a complaint, or a lawful order from a competent authority) by writing to:
This is the canonical contact for any privacy, security, data-protection or legal matter related to ZUMI. We aim to reply within 30 days, in line with Article 12(3) GDPR.
2. What data we collect
When you interact with ZUMI we collect the following categories of personal data:
- Identity from messaging platforms. Your platform user ID, username/handle, display name, phone number where the platform provides it (for example WhatsApp), and language/timezone hints. Telegram does not normally share your phone number with us.
- Conversation content. The text, images, and voice messages you send to ZUMI. Voice messages are transcribed to text. Images are analyzed to estimate food content. Both the transcripts and the image analyses are stored.
- Food, lifestyle and wellbeing data you choose to share. What you ate, when, dietary preferences, allergies, habits, routines and goals. Text and voice meal logs can be stored as descriptive logs. Meal photos can be analyzed to estimate calories and macronutrients. If you explicitly state calories or macros, we may store those numbers as user-provided values. Some of this is "data concerning health" under Article 9 GDPR and is processed only with your explicit consent (see Section 3).
- Body metrics and goal data (optional). If you choose to set a goal, the profile form may collect your age, gender, biological sex, height, current weight, weight history, activity level, goal type, start weight, target weight, target date and goal pace. We use this to estimate your maintenance energy needs, daily tracking target, daily balance and goal progress. These figures may be shown to you in chat and in the dashboard as approximate tracking signals, not prescriptions. These are "data concerning health" under Article 9 GDPR and are processed only with your explicit consent (see Section 3). Setting a goal is optional.
- Workout and movement data. If you tell ZUMI about workouts or movement, we may store the workout type, title, duration, intensity, date/time, notes and any calories burned that you explicitly provide. We do not infer workout calories unless you provide them or a connected import provides them.
- Memories. Stable facts ZUMI extracts from the conversation to remember you (e.g. "user is vegetarian"), with an internal importance rating. You can ask ZUMI to forget any memory at any time.
- Automation preferences. Reminders, check-ins, follow-ups and engagement check-in settings you set up or enable.
- Delivery metadata. Whether outbound messages were delivered, read, or failed.
- Dashboard and consent records. Dashboard magic-link/session data, account settings, language preference, consent type/version/text shown, timestamp, IP address and user-agent.
- Technical data on the website and dashboard. When you visit meetzumi.com your browser sends us an IP address, user-agent, referrer and basic request metadata. This is used to operate the site, dashboard and security controls.
We do not ask for, store, or process your bank or payment details, government IDs, biometric identifiers, or precise location.
3. Why we process it (Legal basis)
- Performance of the service (Art. 6(1)(b) GDPR). To answer your messages, log meals, run reminders, and provide ZUMI's core companion features.
- Explicit consent for health-related data (Art. 9(2)(a) GDPR). When you share food, allergies, workouts, wellbeing-related information, or the body metrics and goal data described in Section 2, we treat that as data concerning health. You give explicit consent to process this data for the sole purpose of providing the service. You can withdraw consent at any time from the dashboard where available, by asking us to delete your account, or by writing to info@meetzumi.com. Withdrawing this consent may require us to disable goal, meal, workout and dashboard features that depend on that data.
- Legitimate interest (Art. 6(1)(f) GDPR). Operating the service securely, preventing abuse, debugging, ensuring delivery of messages, and improving stability during the beta phase.
- Legal obligation (Art. 6(1)(c) GDPR). When required by applicable law (e.g. responding to lawful requests from authorities).
4. Who has access (Subprocessors)
To run the service we rely on the following providers, each of whom processes your data only on our instructions and under written or platform-equivalent data-processing terms:
- Cloudflare, Inc. (USA, with global edge): hosting, DNS, edge caching, R2 object storage for media you send.
- Supabase, Inc. (database hosted on AWS in eu-west-1, Ireland): the structured database where users, conversations, memories, food events, workouts, goals, consents and automations are stored.
- OpenRouter, Inc. (USA): LLM gateway. We send conversation snippets to OpenRouter to obtain AI-generated replies and analyses. OpenRouter routes the request to the underlying model provider.
- DeepSeek (China) and Google LLC (USA): underlying AI model providers reached via OpenRouter for text generation, vision and audio transcription respectively.
- Meta Platforms Ireland Ltd. / WhatsApp (EU) and Kapso Spa: WhatsApp messaging and WhatsApp API infrastructure used to receive and send WhatsApp messages and media.
- Telegram FZ-LLC (UAE): Telegram messaging platform used when you reach ZUMI through Telegram.
Where transfers to countries outside the European Economic Area are involved, we rely on adequacy decisions of the European Commission, on Standard Contractual Clauses (SCCs), or on equivalent safeguards under Chapter V GDPR. The current list of subprocessors may evolve during the beta. Material changes will be reflected in this page.
5. Where we store data
Structured data lives on Supabase in Ireland (eu-west-1). Files (images, voice notes) live in Cloudflare R2. Some processing is global (Cloudflare edge, LLM providers).
6. How long we keep it
- Conversation messages: kept for as long as your account is active.
- Inbound media (meal photos, voice notes): we delete the stored image/audio files on a rolling basis, typically within 90 days of upload. The structured analysis derived from them (e.g. the meal entry) is kept while your account is active.
- Memories, food events, workouts, body metrics, weight history and goals: kept for as long as your account is active, or until you delete them or ask us to delete them.
- Consent records: kept for as long as necessary to demonstrate the lawfulness of processing.
- Dashboard session cookies: normally expire within 30 days. Language preference cookies may last up to 1 year.
- Delivery metadata, error logs: kept for up to 90 days, then deleted.
- Backups: retained according to our backup policy and overwritten in a rolling window not exceeding 30 days.
- Account deletion: when you delete your account, all data tied to your user is deleted within 30 days, except where we are legally required to retain it.
- Beta caveat: during the private beta, the service architecture may change; we may need to migrate or rebuild data. We will not retain or use data beyond what is necessary to operate ZUMI.
7. Your rights
Under GDPR (and equivalent laws where applicable), you have the right to:
- Access your data and obtain a copy (Art. 15).
- Rectify inaccurate data (Art. 16).
- Erase your data — "right to be forgotten" (Art. 17).
- Restrict processing (Art. 18).
- Data portability — receive your data in a machine-readable format (Art. 20).
- Object to processing (Art. 21).
- Withdraw consent at any time, without affecting the lawfulness of processing prior to the withdrawal.
- Lodge a complaint with a supervisory authority. In Italy: Garante per la protezione dei dati personali.
To exercise any of these rights, write to info@meetzumi.com. We will reply within 30 days. To verify your identity we may ask you to confirm your messaging-platform user ID.
8. Children
ZUMI is not directed to children under 16 years of age. We do not knowingly collect personal data from children. If you are under 16, do not use ZUMI. If you believe a minor has shared data with us, contact us and we will delete it without delay.
9. Security
We use industry-standard measures to protect your data: encryption in transit (TLS), webhook signature verification (HMAC), restricted database access via service role keys, Row-Level Security on the database, principle of least privilege, and isolated edge runtimes. No system is perfectly secure, especially during the beta phase: if you discover a vulnerability, please report it to info@meetzumi.com.
10. Cookies and tracking
The public website meetzumi.com does not use analytics or advertising trackers. The dashboard uses essential first-party cookies: a signed session cookie (zumi_dash) so you can stay logged in after opening your magic link, and a language preference cookie (zumi_lang) when you choose a dashboard language. The site loads web fonts from Fontshare and Google Fonts, which may receive request metadata as part of font delivery, governed by their respective privacy policies. Messaging itself runs on WhatsApp, Telegram or other messaging platforms and is also governed by their respective privacy policies.
11. International transfers
Some of our subprocessors are located outside the European Economic Area or may process data globally (Cloudflare and OpenRouter in the USA; Google in the USA; DeepSeek in China; Telegram in UAE; Cloudflare edge locations globally). Where this is the case, transfers are protected by Standard Contractual Clauses or equivalent safeguards under Chapter V GDPR. By using ZUMI you acknowledge that processing may involve such transfers.
12. Automated processing
ZUMI generates replies, meal-photo analyses, calorie/macronutrient estimates, goal calculations, daily balances and dashboard indicators using AI models and deterministic formulas. Users are informed that they are interacting with an AI system. This is not "solely automated decision-making producing legal effects" under Article 22 GDPR: ZUMI is a conversational wellbeing companion and its outputs are informational. Nonetheless, you should not rely on ZUMI for medical, legal, financial or other consequential decisions. See our Terms of Service.
13. Changes to this policy
We may update this Privacy Policy. The "Last updated" date at the top reflects the most recent revision. Material changes will be communicated through the service or, where applicable, via email.
14. Contact
Questions, requests, complaints: info@meetzumi.com.