Subprocessors

Supabase, Inc. · United States

Authentication, PostgreSQL database hosting, file storage. Holds the primary KitBee account, recipe, meal-plan, pantry, and shopping-list data.

Data processed

• Account information (email, hashed password, display name)
• User-generated content (recipes, meal plans, pantry items, shopping lists, eaters)
• Uploaded images (recipe photos, fridge scans)

Vercel Inc. · United States (with global edge CDN)

Application hosting and edge network delivery. Runs the KitBee web application and serverless API functions.

Data processed

• Request metadata (IP address, user-agent, request paths)
• Function logs

Anthropic, PBC · United States

AI-powered recipe parsing, customization, fridge-photo analysis, and meal-plan generation via the Claude API. Recipe text and uploaded images may be transmitted to Anthropic for processing. Anthropic does not use API inputs to train its models.

Data processed

• Recipe content you submit (URLs, pasted text, photos)
• Fridge scan photos
• Meal-plan context and preferences

OpenAI, L.L.C. · United States

AI image generation for recipe hero images via the gpt-image-1 model. Recipe titles and a brief textual description are sent to OpenAI to generate stylized images.

Data processed

• Recipe title and short generation prompt

webknox GmbH · Germany

Recipe-search results when you use search to find recipes. Search queries are transmitted to Spoonacular to retrieve matching recipe metadata.

Data processed

• Search query strings

Unsplash Inc. · Canada

Recipe hero image search. When choosing or generating a recipe image, KitBee sends a short search query (recipe title, cuisine) to Unsplash and displays returned stock photos. No personal data is sent.

Data processed

• Search query strings (recipe titles, cuisine keywords)

Pexels GmbH · Germany

Recipe hero image search. KitBee sends a short search query to Pexels and displays returned stock photos as image options. No personal data is sent.

Data processed

• Search query strings (recipe titles, cuisine keywords)

U.S. Department of Agriculture · United States (public government API)

Nutrition data lookup. When you save a recipe, KitBee queries the USDA public food database with each ingredient name to compute per-serving calories, protein, carbs, and fat. No personal data is sent.

Data processed

• Ingredient name strings

Jina AI GmbH · Germany

Fallback URL content extraction. When importing a recipe by URL fails due to anti-bot protection on the source site, KitBee proxies the URL through Jina Reader to retrieve cleaned page text for parsing. The URL you submit is sent to Jina; your IP address is not.

Data processed

• Recipe source URLs (only on direct-fetch fallback)

Google LLC · United States

Optional Google Calendar integration (OAuth-based) for syncing meal plans to your calendar. Only enabled when you explicitly connect your Google account. Tokens are stored encrypted; we do not access your calendar except to write meal events.

Data processed

• OAuth access and refresh tokens (when connected)
• Meal-plan slot data written as calendar events (when connected)

PostHog Inc. · United States

Product analytics and feature usage tracking to help us understand which parts of KitBee are used and where users encounter friction.

Data processed

• Anonymized event data (page views, feature interactions)
• Account ID linkage for funnel analysis

Resend, Inc. · United States (EU routing for EU recipients)

Transactional email delivery. Sends account verification, password reset, beta invite, and security notification emails on our behalf.

Data processed

• Email address
• Email body and subject (verification codes, security notices)

Cloudflare, Inc. · United States (with global edge presence)

DNS resolution and CDN edge protection for kitbee.ai and related domains.

Data processed

• Request metadata (IP address, request URL) at the network edge