Privacy Policy

Information we collect

• Account and authentication information: the account identifier created through Supabase, email address, and chosen sign-in method. Guest use relies on an anonymous account identifier created by Supabase.
• Profile and preferences: language, household size, dietary preferences, allergy or dietary restrictions, disliked ingredients, equipment and goals.
• Kitchen information: inventory, confirmed scan results, saved recipes, recipe/history records, shopping lists and sessions, menus and cooking activity.
• Usage and quota information needed to apply feature usage and plan limits.
• Subscription status: plan, entitlement, product/platform and status information. Maye does not store payment card details.

Photos and AI

Maye processes a fridge photo you select or capture to identify ingredients and may transmit it to OpenAI for that requested analysis. Maye does not intentionally retain raw fridge photographs in its own persistent application storage. After processing, Maye stores the scan record, identified ingredients and results you confirm—not the raw photograph.

Maye may also use OpenAI services for recipe, menu and related AI-assisted suggestions. AI output can be incorrect or incomplete. You must independently verify results, particularly for allergies, intolerances and food safety.

Why we process information

• to provide your account and personalised Maye experience
• to operate scan, recipe, menu, shopping and cooking features
• to manage quotas and subscription entitlements
• to maintain security, diagnose errors and improve service quality
• to meet legal obligations and respond to requests

Service providers

• Supabase — authentication and account sessions.
• Railway — Maye backend and application database hosting.
• OpenAI — requested photo/ingredient analysis and AI-assisted recipe processing.
• Cloudflare — object storage and delivery for canonical AI-generated recipe images. It is not used to store user fridge photographs.
• PostHog — product-use, performance and error telemetry, with GeoIP and session replay disabled in Maye's configuration.
• RevenueCat — subscription entitlement and purchase-status handling when enabled.
• Apple and Google — sign-in and/or store purchase processes when enabled.

Analytics and error telemetry

When PostHog is enabled, Maye may process limited product-use, performance and error events against a pseudonymous Supabase account identifier. The allowlist for normal product events excludes ingredient, prompt, photo, allergy, email and note content. GeoIP, session replay and console capture are disabled. Technical error telemetry may include technical error information needed to diagnose a fault.

Retention, deletion and security

We retain information for as long as needed to operate your account and the service. When you request deletion in the app, user-associated application data is placed into a durable deletion workflow. Shared canonical recipes and recipe images may remain because they are not personal account data. Some records may be retained where necessary for legal obligations, security or dispute resolution.

We use reasonable technical and organisational safeguards, but no system can be guaranteed completely secure.

International processing

Our providers and infrastructure may be located outside Türkiye. Information may therefore be processed internationally to provide the service.

Your rights and contact

For access, correction, deletion or privacy questions, contact caglar.sert1@gmail.com. We assess requests under applicable law.

Age

Maye is intended for users aged 16 and over. We do not create child-directed accounts.

Changes

We may update this policy when the service or legal requirements change. The current date appears on this page.