Sazón Vital Privacy Policy
In short
- Sazón Vital keeps your information on your device and, for the features described under “What leaves your device”, on our server and with the services listed there.
- No tracking and no ads. Sazón Vital doesn’t track you across other companies’ apps or websites and doesn’t show ads.
- No analytics or crash-reporting services are built in.
- Signing in is optional (Sign in with Apple and Google).
- Purchases are handled by Apple. We never see your payment details.
Who we are
Sazón Vital is published by Marketgence Technologies LLC (“we”, “us”). This policy explains what happens to your information when you use Sazón Vital on your iPhone or iPad. Questions: support@marketgence.com.
What stays on your device
Sazón Vital keeps these on your device, in the app’s own storage that other apps can’t read:
- Your first name, servings, pantry, shopping list, weekly plan, favorites and saved recipes.
- The health conditions you mark in Mi salud and the ingredients you exclude.
- Your recipe feedback (for example too spicy or make again).
- A copy of your Sous Chef conversation (the latest 60 messages).
- A random ID created for this installation.
- Sign-in tokens, in the iOS Keychain, if you sign in.
- Voice clips only in a temporary file until they are sent, then deleted.
Like other app data, it may be included in your device backups (iCloud Backup or a computer backup) if you use them.
What leaves your device
| What | Why | Sent to | When | Linked to you |
|---|---|---|---|---|
| Messages you type or dictate to the Sous Chef, and its replies | To answer you and to keep your chat history | Our backend, then AI providers through Rork Toolkit | When you use the Sous Chef chat | Yes |
| Health conditions you mark in Mi salud (for example diabetes or high blood pressure) | To adapt recipes and Sous Chef advice to them | Our backend and the AI providers | With Sous Chef messages and recipe requests while you have conditions marked; also in your backup if you save one | Yes |
| Kitchen details sent with requests: pantry items, shopping list, weekly plan, excluded ingredients, saved tastes and servings | To personalize Sous Chef answers and recipes | Our backend and the AI providers | With Sous Chef messages and recipe requests | Yes |
| Recipe requests (the ingredients and meal type you choose) and the recipes created from them | To create the recipe; new recipes join the shared community library without your name | Our backend and the AI providers; recipe title and ingredients go to OpenAI to draw its picture | When you ask for a new recipe | Yes |
| Photos of your fridge or pantry | To list the ingredients the photo shows | Our backend, which passes it to the AI providers and doesn't store it | Only when you take or choose a photo in the Sous Chef | No |
| Voice recordings | To turn what you say into text for the Sous Chef | Our backend, which passes it to an AI speech service and doesn't store it | Only while you hold the microphone button | No |
| Your email address from Apple or Google | To sign you in and identify your account | Rork's sign-in service | Only if you sign in | Yes |
| Your name from Apple or Google, and the first name you type in the app when you save a backup | To show your account and restore your profile on another device | Rork's sign-in service; our backend for the backup | Only if you sign in, and for the backup only when you tap Guardar mis datos en la nube | Yes |
| A random ID created for this installation | To keep your daily recipe count, chat history and requests together without an account | Our backend | With every request to our backend | Yes |
| Your account ID when you're signed in | To keep your chat history, backup and daily count with your account | Our backend | Only if you sign in | Yes |
| A backup of your app data: first name, servings, pantry, recipe feedback, favorites, saved recipes, excluded ingredients, health conditions, weekly plan and shopping list | To bring your data to another device | Our backend | Only when you're signed in and tap Guardar mis datos en la nube | Yes |
| Whether you own any recipe pack | To lift the daily limit on new recipes; our server doesn't store it | Our backend | With every request to our backend | Yes |
| Reports you send about a community recipe (the reason you pick) | To hide and review problem recipes | Our backend | Only when you report a recipe | Yes |
| Saving or unsaving a community recipe (only a count is kept) | To show how many people saved a recipe | Our backend | When you save or unsave a community recipe | No |
We don’t sell your information, and it isn’t used for advertising.
Our server
Stored under your installation ID, or your account ID when signed in: daily counts of new recipes; your Sous Chef chat (both sides); and, if you tap Guardar mis datos en la nube, one backup of your app data including health conditions. New recipes the Sous Chef creates go into the shared community library with your ID, their tags (which can include your ingredients and marked conditions) and a picture. Recipe reports are kept with your ID and reason.
Where it runs: our backend (a Cloudflare Worker with Durable Objects, hosted by Rork at una-aplicacion-que-prepare-menus-de-comi-backend.rork.app). How long it’s kept: No automatic time limit. The chat keeps only the newest 200 messages and is erased when you tap Borrar conversación. The backup is replaced each time you save. Daily counts, community recipes and reports are kept with no set end date.
Services we use
These outside services receive data from Sazón Vital to make it work. Each handles that data under its own privacy policy.
- Rork and Cloudflare (hosting our backend)
- Runs our backend, which stores the data described in this policy. What it receives: Everything the app sends to our backend, plus normal request data such as your IP address. Stored data as described in this policy; request logs under their own policies.
- Rork Auth (sign-in service)
- Handles Sign in with Apple and Google and issues the app's sign-in tokens. What it receives: Your Apple or Google account ID, email address, name and profile picture, as shared by Apple or Google. Only if you sign in.
- Apple and Google (sign-in providers)
- Confirm who you are when you choose Sign in with Apple or Continuar con Google. What it receives: Your sign-in with them; they share your account email and name for the sign-in. Only if you sign in.
- Rork Toolkit (AI gateway)
- Forwards our backend's AI requests to the AI providers. What it receives: The content of each AI request (messages, kitchen details, health conditions, photos, voice, text to read aloud), sent under our key without your installation or account ID. When you use the Sous Chef, create a recipe, scan a photo or use voice. Under their own policy.
- Google (Gemini 2.5 Flash)
- Writes Sous Chef replies and recipes, checks recipes, and lists ingredients in pantry photos. What it receives: Chat messages, kitchen details, marked health conditions, recipe requests and pantry photos. When you use the Sous Chef, create a recipe or scan a photo. Under Google's own policy. Privacy policy: policies.google.com.
- OpenAI
- Draws recipe pictures; backup for chat, speech-to-text and read-aloud when the main service fails. What it receives: Recipe title and ingredients for pictures; as a backup, the same content Google or xAI would get. When a new recipe is created, or when a main AI service fails. Under OpenAI's own policy. Privacy policy: openai.com.
- xAI (Grok speech)
- Turns voice messages into text and reads Sous Chef replies aloud. What it receives: Your voice recordings; the reply text you ask to hear. Only when you use voice input or tap read aloud. Under xAI's own policy. Privacy policy: x.ai.
Artificial intelligence
Sous Chef chat, recipe creation and checks, pantry photo recognition, voice input, read-aloud and recipe pictures. It uses Google (Gemini 2.5 Flash), OpenAI (recipe pictures; backup for chat, speech-to-text and read-aloud) and xAI (Grok speech-to-text and text-to-speech) through our backend, then Rork Toolkit (toolkit.rork.com). When you use it, this is sent: Your latest chat messages, marked health conditions, excluded ingredients, pantry, shopping list, weekly plan and saved tastes; recipe requests; pantry photos; voice recordings; reply text you ask to hear. Recipe title and ingredients go to OpenAI for the picture. Your ID isn't sent to the AI providers. The service generates the answer and may keep request records under its own policy. Don’t include anything you wouldn’t want processed this way.
AI-generated text can be wrong or incomplete; see the Terms of Use.
Permissions
Sazón Vital asks for these only when you use the feature that needs them. You can change your answer at any time in the Settings app.
| Permission | Why |
|---|---|
| Camera | To photograph your fridge or pantry so the Sous Chef can list the ingredients. |
| Microphone | To talk to the Sous Chef while you hold the microphone button. |
Tracking, ads and analytics
Sazón Vital doesn’t track you: it doesn’t link information about you with information from other companies’ apps, websites or data brokers, and it doesn’t use an advertising identifier.
Sazón Vital doesn’t show ads.
It has no analytics or crash-reporting services. If you’ve chosen to share analytics with app developers in your iPhone’s settings, Apple may share crash reports with us; Apple doesn’t include your identity.
Accounts
You can use the app without an account, or sign in with Sign in with Apple and Google. Deleting your account: There's no in-app account deletion yet. Contact us to delete your account and the data kept under it. Signing out (Perfil ▸ Cuenta y sincronización ▸ Cerrar sesión) only removes the sign-in from this device.
Purchases
Sazón Vital offers one-time purchases through Apple’s App Store. Apple processes the payment and knows what you bought; we don’t receive your name, email address or payment details. The app checks what you’ve bought on your device with Apple’s StoreKit. Apple’s Privacy Policy applies to the purchase.
Children
Sazón Vital isn’t directed at children under 13, and we don’t knowingly collect personal information from them. Made for adults, including older adults; not directed at children.
How long data is kept, and deleting it
Information on your device stays until you delete it. You can delete it in the app: Chef ▸ ⋯ (Más opciones) ▸ Borrar conversación erases the Sous Chef chat on this device and on our server. There's no single control that erases everything; other data on the device is removed when you delete the app. Deleting Sazón Vital removes the information it keeps in its own storage on your device; copies in your backups remain until you delete those. If you've bought something, a random purchase identifier that the app keeps in the iOS Keychain can stay on the device after the app is deleted, so your purchases can be matched again; it doesn't identify you.
On our server: No automatic time limit. The chat keeps only the newest 200 messages and is erased when you tap Borrar conversación. The backup is replaced each time you save. Daily counts, community recipes and reports are kept with no set end date. Chat history: Borrar conversación in the app. The saved backup, daily counts, recipe reports and the link between you and recipes you created have no delete control in the app; contact us and we'll delete them. Account deletion is also by request.
Rork and Cloudflare (hosting our backend): Stored data as described in this policy; request logs under their own policies.
Rork Toolkit (AI gateway): Under their own policy.
Google (Gemini 2.5 Flash): Under Google's own policy.
OpenAI: Under OpenAI's own policy.
xAI (Grok speech): Under xAI's own policy.
Your rights
Depending on where you live (for example in the European Union, the United Kingdom or California), you may have the right to know what information we hold about you, to get a copy, to correct or delete it, and to object to how it’s used. To make a request or a complaint, email support@marketgence.com. You can also contact your local data-protection authority.
Changes to this policy
If we change how Sazón Vital handles information, we’ll update this page and its effective date, and list the change below.
- : First version on apps.marketgence.com. Replaces the earlier policy at 9ic36ti7ql5e6dy8nmap7-web.rork.live, which was wrong: purchases are checked on the device with Apple's StoreKit and RevenueCat isn't used; the app does use the camera and microphone; it sends chats, photos, voice and health conditions to AI services and keeps chat history on our server; sign-in is optional.
Contact
Marketgence Technologies LLC · support@marketgence.com