Salsa: AI Recipe Guide

Privacy Policy

Last updated 3 November 2026

Salsa: AI Recipe Guide is operated by Ashton McHardy. For privacy questions, access or correction requests, or help deleting data, contact ashton.mchardy@gmail.com.

Information we use

OpenAI processing

Salsa explains what is shared with OpenAI before you enable AI processing, including when entering through the free app. With that permission, Salsa sends selected recipe text and recipe photos through its server to OpenAI to organise and check imports, and sends recipe context and your cooking questions to answer them. Recipe text may also be used to create a labelled fallback cover illustration. AI can make mistakes; verification is not a guarantee of recipe accuracy or food safety.

In versions offering social-post imports, sharing a post usually supplies its link and selected text, rather than the video recording. Salsa uses accessible post descriptions and text you share. If you separately allow social media processing in Settings → Privacy, Salsa may temporarily retrieve accessible recipe recordings or slideshow images and send narration audio, slideshow images and sampled original video frames to OpenAI for transcription and recipe extraction. Samples can miss brief on-screen details; comments are not read. Salsa does not receive your social-account password, sign into a social platform on your behalf or bypass a platform's access restrictions. Media that is blocked, incomplete or unsupported may require you to supply the creator's complete recipe text or screenshots instead. Only supply content you have permission to use.

Source recordings and extracted audio or frames are processing inputs, not saved recipe videos. Server working files are removed after processing; staged import sources follow the cleanup schedule below. Saved recipes retain the original post link and an explanation of the evidence used. A generated cover is an AI illustration and does not establish what the creator's finished dish looked like. Turning off social media processing stops future authorised media requests once the server receives the change; an already-running request may finish.

Your passwords, sign-in tokens, private recipe notes and privately saved cover photos are not deliberately included in these AI requests. A photo you explicitly select for a recipe import is different: it is sent for reading and verification. Original import photos and private notes are not placed in a shared image catalogue. New versions of Salsa offer optional cooking illustrations. With your separate permission in Settings, Salsa uses the current and previous cooking instructions and ingredient names on its server to identify a generic cooking action, ingredient and preparation state. Only that generic description is sent to OpenAI to generate and check a missing illustration. Approved generic illustrations and their review metadata are saved in Salsa’s shared image bank and may be reused across recipes and accounts. Original recipe text, uploaded photos and private notes are not added to that bank. An illustration is an example, not evidence of quantities or safe doneness. Unknown actions, processing failures or usage limits may show the recipe cover instead. Turning off cooking illustrations stops new requests from your app; a request already running may finish and previously saved illustrations may still display. Shared generic illustrations may remain after account deletion because they contain no account identity or private source material. Spoken narration of Salsa’s cooking steps remains disabled.

Salsa requests that AI responses not be stored as retrievable response history where the API supports this. This is not a promise of zero retention. OpenAI's API data is not used for model training by default; abuse monitoring may retain content for up to 30 days, with legal and safety exceptions. See OpenAI's API data controls.

Service providers and sharing

We use Google Firebase/Google Cloud for authentication, hosting, private recipe storage, processing and optional crash reporting; OpenAI for the AI functions described above; and Apple for purchases and platform services. Google or Apple also processes sign-in if you choose that provider. These services may process data outside your country, including in the United States. We use service-provider terms and access controls to protect information and limit its use to providing the service, security and legal obligations. See Firebase privacy and security and Apple's privacy information.

Google sign-in may use your IP address to estimate a general location for fraud prevention. Its included SDK also declares account/contact information (including phone-number information), user and device identifiers, usage information and other technical data for sign-in functionality and service analytics. Salsa does not ask for your phone number or precise location, read your contacts, or request access to Google mail or files. These provider disclosures are included in our App Store privacy information; they are separate from Salsa's optional crash-reporting switch. See Google sign-in's data disclosure guidance.

RevenueCat provides the optional subscription and Apple Ads measurement described above. We send this information through Salsa's server; the app does not include a RevenueCat purchase-observer SDK. RevenueCat may process data in the United States and other locations under its service-provider terms. See RevenueCat's privacy information. Salsa does not sell personal information, request your advertising identifier (IDFA), or use this measurement to track your activity across other companies' apps and websites. Optional crash reporting is separate from ad measurement. We may disclose information when legally required or to address fraud, abuse or a security incident.

If you create a recipe invitation, anyone with its link can see the sender name you enter and the recipe preview. A registered subscriber can save a separate copy. The invitation excludes private notes, star ratings and privately uploaded cover photos. Disabling a link or deleting your account does not remove copies another person already saved.

Retention and deletion

Your choices and rights

In Settings you can export recipes, control Recipe sync and Help improve Salsa, manage AI permission, and delete your account under Account & more. Turning off AI processing stops future authorised requests and cancels queued processing when the server receives the change; an already-running request may finish. Saved recipes and cooking steps remain available. iOS controls camera, selected-photo, notification, alarm and Live Activity permissions separately.

Where offered, Apple Ads & subscription measurement is optional and can be changed under Settings → Privacy. Declining does not restrict paid features. Turning it off stops new reporting once Salsa reconnects and the server receives your choice; an already-running request may finish. It does not automatically erase previously reported data. Delete your Salsa account or contact us for a data-deletion request. Older app versions without this measurement choice do not enable it.

You may contact us to request access, correction or deletion, or exercise other privacy rights available where you live. We may need to verify that the account is yours. You can also raise a concern with your local privacy regulator. Parents or guardians should contact us if a child has supplied personal information without appropriate permission.

Deleting Salsa or your Salsa account does not cancel an Apple subscription. Use Manage subscription in Salsa or your Apple account's subscription settings.

Changes

We will update this page when practices change. Material changes affecting permission will be explained before the new processing begins.