Privacy Policy

When you sign up, we collect your email address, a password, and, optionally, your first name. Your password is securely hashed by Supabase, our authentication provider — we never see or store it in plain text. Your email is used to confirm your account and to send password-reset links when you request them.

As you use REMI., we store the recipes you add (title, ingredients, steps, images, source URLs, serving size, cook time, category, and dietary tags), your grocery list items, the lists you organise recipes into, your personal notes, and which recipes you have marked as favourites.

We also generate a short taste-profile summary based on your saved recipes to personalise your dashboard. This summary is stored in your account and updated as your collection grows.

If you take the cooking-card quiz, we store your result (your cooking archetype) along with the favourite meal and least favourite food you choose to enter, so your card is there when you come back.

Your data is used exclusively to provide the REMI. service: storing your recipes, powering the cooking mode, and personalising your experience.

When you use AI features — such as extracting a recipe from a URL or photo, generating a recipe from a description, or looking up an ingredient substitute — the relevant content (recipe text, image, or prompt) is sent to Anthropic's Claude API for processing. Your email address and full recipe library are never sent to Anthropic.

When you use the store-finder feature, your ingredient query is sent to the Serper API to surface nearby stores. No personal information is included in that request.

If you share a recipe or a list, REMI. creates a public link. Anyone who has that link can view the shared recipe or list without an account, so only share what you are happy for others to see.

REMI. relies on the following third-party services to operate:

• Supabase — database and authentication (supabase.com)

• Anthropic — Claude AI for recipe extraction, generation, transformations, and ingredient substitutions (anthropic.com)

• Groq — fast AI processing for some recipe-extraction steps (groq.com)

• Apify — fetching post captions when you share a recipe from Instagram or TikTok (apify.com)

• Serper — local store search powered by Google Maps data (serper.dev)

• Google Fonts — typography (fonts.googleapis.com)

Each of these services has its own privacy policy. We encourage you to review them.

REMI. uses session cookies managed by Supabase to keep you signed in. These are essential cookies — the app cannot function without them. We do not use any advertising or tracking cookies, and we do not run any third-party analytics.

All data is stored in Supabase's encrypted PostgreSQL database. Passwords are hashed using industry-standard methods and are never stored in plain text. All API keys are stored server-side and never exposed to the browser.

Every API endpoint verifies your identity before reading or writing any data, so your recipes are only ever accessible to you.

You can delete any recipe at any time from within the app, and you can update your name, email, and password from your Profile page. If you would like to request a full copy of your data or have your account permanently deleted, please contact us at the email below.

We do not sell your data to anyone, ever.

We may update this Privacy Policy from time to time. When we do, we will revise the "last updated" date at the top of this page. Continued use of REMI. after changes are posted constitutes your acceptance of the updated policy.

If you have any questions about this Privacy Policy or how your data is handled, please reach out to the developer directly through the app.