Recipe API privacy & data

Email address (required)

Company name (optional)

Payment processing is handled by Stripe. We do not store your credit card details.

User agent strings (for debugging and analytics)

API request logs (endpoints accessed, timestamps, and for recipe search the filters and search text sent, with how many recipes matched)

Namespace-separated HMAC hashes derived from IP signals for rate limiting, security, and evaluation-abuse review. Raw IP addresses are not retained.

Provide and maintain the API service

Authenticate your API requests

Enforce rate limits and prevent abuse

Process payments and manage subscriptions

Decide which recipes to add to the catalogue, from searches that matched none

Send marketing communications (only with your consent, with easy unsubscribe)

Account data: Until you request account deletion

API usage logs: 90 days

Payment records: As required by law (typically 7 years for tax purposes)

Generated recipes and cooking briefs: Stored with the catalogue record while that record is retained.

Supabase Database hosting (data stored in the EU/US).

Fly.io API hosting (primary region: London, UK).

Your data may be processed in countries outside your residence, including the United States and European Union.

You can permanently delete your account from the developer dashboard.

Access: Request a copy of the personal data we hold about you

Correction: Request correction of inaccurate personal data

Deletion: Request deletion of your account and personal data

Export: Request your data in a portable format

Withdraw consent: Unsubscribe from marketing communications at any time