YOUR RECIPE, YOUR CHOICE

Privacy

Last updated: 4 October 2026. This policy covers the BakeIQ Chrome extension and bakeiq.app.

BakeIQ sends the recipe name, ingredient lines, and recipe language to its Rust service when you press Convert. Structured recipe ingredients and pasted ingredient lists are parsed without AI.

Text extraction with Groq

When you choose Recipe text and press Convert, or click Convert on a page without recipe schema, BakeIQ sends the supplied text through its service to Groq to identify ingredients. The extension prefers the visible recipe or article region and sends at most 16,000 characters. This can include surrounding article text; avoid using extraction on private pages. It does not read form values, cookies, passwords, or browsing history. Review extracted ingredients against the original. Groq processes this text under its own privacy policy. Under Groq's data controls, inference content is not retained by default, but troubleshooting and abuse-prevention exceptions may retain it for up to 30 days or longer where legally required. BakeIQ stores the extracted ingredient lines, not the full source text.

Saved recipes and links

Converted recipes are available for 24 hours so you can open them on another device. Anyone with the unguessable recipe link can read that recipe. Do not include private information in recipe names or ingredients. Expired recipes cannot be retrieved; expired records are removed from the active database on service startup or the next conversion. Encrypted recovery snapshots of the service's disk are retained for seven days and may contain expired records.

Extension settings

Preferences are stored using Chrome sync storage and may sync through your Google account. The most recent conversion for each tab is stored in Chrome session storage until that tab closes, navigates, or the browser session ends. Automatic conversion is off by default and applies only to pages with recipe schema. Text extraction with Groq always requires a click.

Page access and permissions

The extension reads recipe schema on HTTP and HTTPS pages to detect recipes and show its conversion panel. Page text is sent for extraction only after you click Convert. The source page URL is not included in conversion requests or saved recipe records. The storage permission saves preferences and the current tab's conversion. You can restrict site access or remove the extension through Chrome's extension settings.

Hosting and data use

Netlify hosts bakeiq.app and forwards conversion requests to the Rust service on Fly.io. Fly.io stores shared recipes; Groq is called only for text extraction. Requests use HTTPS. These providers may process ordinary request metadata, such as IP addresses, for delivery, reliability, and abuse prevention, under their respective Netlify, Fly.io, and Groq policies. BakeIQ does not include advertising or analytics scripts, sell user data, or use recipe content to train AI models. API keys stay on the server.

Limited use

BakeIQ's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Recipe content is used only to provide the requested extraction, conversion, and sharing features.

Contact

For questions, privacy requests, or help, email support@bakeiq.app. Support messages are forwarded through ImprovMX to our support inbox hosted by Google. Include only the information needed to handle your request; do not send passwords or private recipe links.