Data Use

Data Usage Summary

Last updated: June 15, 2026

This page is a plain-language summary of how Roots & Rhythm uses data. It is meant to be easy to read. For full details, see the Privacy Policy.

In plain language

Roots & Rhythm uses data mainly to:

• show you seasonal ingredients based on where you are
• generate recipes that match your preferences
• let you save recipes if you sign in
• support optional cycle-aware recipe personalization
• improve recipe quality and keep the service working
• understand app usage, app stability, and whether key features are working for users

We do not currently use third-party advertising SDKs or cross-app tracking.

What we collect

Depending on how you use the app, we may collect:

• your city or region
• your approximate or precise location if you choose to share it
• your dietary preferences and ingredient exclusions
• your cycle-sync settings and, if enabled, cycle inputs such as last period start date and cycle length
• recipe-generation requests and recipe feedback
• compact recent recipe history used to avoid repeating the same recipe ideas too soon
• account details such as your email address if you sign in
• saved recipes if you store them in your account
• local app state saved on your device
• app analytics events and crash diagnostics, such as recipe generation, recipe saves, recipe skips, paywall views, app version, and device/operating-system metadata

What stays on your device

A lot of app state is stored locally on your device or browser, including things like:

• your profile settings
• onboarding progress
• active recipe view
• local recipe history
• recent recipe freshness history for about 60 days
• cached saved recipes
• auth session state

If you clear app storage, clear browser storage, or uninstall the app, local-only data may be removed from your device.

What is sent to our backend

When you generate a recipe, we send the information needed to create that recipe, such as:

• location context
• meal type
• selected ingredient
• dietary preferences
• ingredient exclusions
• cycle-related inputs if cycle syncing is enabled
• relevant recent recipe history, such as title, selected ingredient, recipe style, technique, and ingredient names, so we can avoid showing repeated recipe ideas within the freshness window

When you save, skip, or delete recipes, we may also log recipe feedback and related recipe/context information to improve the service.

What is shared with third parties

We currently rely on a few third-party services:

• Supabase for sign-in and account-linked saved recipes
• geocoding/location services such as GeoNames, Open-Meteo, and OpenStreetMap Nominatim to support city lookup and location-based features
• Google if you choose Google sign-in
• Firebase / Google Analytics and Crashlytics for Android app analytics, crash diagnostics, stability monitoring, and product improvement
• Google Fonts and jsDelivr for some web-delivered assets

These providers may receive the data needed to perform their part of the service.

Your choices

You can choose whether to:

• sign in
• share your location
• enable cycle syncing
• save recipes to an account

We only ask for device location if you choose a location-detection feature. You can also use manual city search instead.

You can also change your city, preferences, and exclusions in the app.

Questions or deletion requests

If you want to ask about your data, request deletion, or update your privacy choices outside the app, contact hello@rootsandrhythm.app or use the account deletion page.