Arveli is a voice-first cooking companion that helps you import recipes and cook them hands-free. This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices you have. Arveli is operated by Pariwesh ("we", "us").
By using the app you agree to this policy. If you do not agree, please do not use the app.
We collect only what the app needs to work:
When you use hands-free voice, audio is recorded on your device only while you hold the talk button. That audio is sent securely to our server, which forwards it to our transcription provider (OpenAI) to turn speech into text, and forwards the resulting text to our language-model provider (Anthropic) to interpret your command. Spoken cues you hear back are generated by OpenAI from recipe text.
Your audio is processed transiently to provide the feature. We do not store your voice recordings on our servers, and we do not build a voice profile of you. We keep only the derived number of voice seconds used, for cost and free-tier limits — never the audio or the transcript. These providers process the data under their API terms, which do not use content sent through the API to train their models; see their privacy policies for details.
When you import a recipe by URL, our server fetches that web page and sends its content to our language-model provider (Anthropic) to extract the recipe. The website you import from receives a request from our server. If you paste recipe text instead, that text is sent to the same provider to structure it into steps and ingredients.
You can also import a recipe by photographing a cookbook page or choosing a photo or screenshot from your library. That photo is sent to our language-model provider (Anthropic) so it can read the recipe out of the image and turn it into steps and ingredients. We do not store your photo on our servers: it is processed to create the recipe and then discarded, and only the recipe text we get back is saved to your account. That is different from the optional photo of the finished dish you can add once you finish cooking — that photo is stored on our servers, as described above.
Images on imported recipes are not copied to our servers. The app shows them directly from the original publisher’s website or image host, so when you view a recipe that has images, your device requests them from that publisher — which, like any site serving an image, can see your device’s IP address and the standard details every web request carries. This happens only while you are viewing such a recipe. We do not add tracking of our own to those requests. The exception is recipes that have no publisher — the ones the app generates for you from your own ingredients, and the ones you import from a photo: for those, an AI-generated cover photo (created by OpenAI from the recipe title and ingredients — never from anything about you, and never from the photo you submitted) is stored on our servers and deleted with the recipe or your account.
When you ask a question while cooking ("how much oil should I use?", "what can I use instead of butter?"), the transcribed question is sent to our server along with the identifier of the recipe you are cooking. The server looks that recipe up in your own account and sends its title, ingredients and steps, together with your question, to Anthropic so the answer can use the actual amounts in front of you. Ingredient substitutions are answered the same way. We do not store your questions or the answers.
We use the information above to:
We do not sell your personal information. We do not use it for advertising or for building marketing or behavioral profiles. We do not track you across other apps or websites, and the app contains no advertising or analytics software of any kind. The one third-party software development kit built into the app is a crash reporter, used solely to help us find and fix bugs — see "Crash reports" below for exactly what it receives.
We share data with the following providers only so they can perform their part of the service. Each processes your data under its own privacy terms:
If the app crashes or hits an unexpected error, a short technical report is sent automatically to Sentry, our crash-reporting provider, so we can find and fix the problem.
A crash report contains: the error and the exact place in our code where it happened; your device model and operating system version; the app version you are running; and a short trail of which of our own server endpoints had just run — for example, that a recipe-import request was in progress — not the data carried in those requests.
A crash report does not contain your name, email address, or any identifier that ties it to your account. We do not attach your IP address to it, and we have configured Sentry not to store one either. It never contains your recipe content, your photos, or your voice recordings, and there is no screen recording or screenshot of what you were doing — those features are switched off entirely. Any web address that appears in a report is cut down to which of our endpoints was called; everything after that — including any search text you typed — is removed before the report ever leaves your device.
We keep crash reports only as long as needed to diagnose and fix issues, and use them for that purpose only.
The app asks for four device permissions, all optional:
We keep your information until you delete it. You can delete individual recipes at any time, or delete your entire account from Settings → Delete account. Deleting your account permanently erases your account and all associated recipes, ratings, cooking history, dish photos, and stored generated recipe photos from our systems.
Deleting your account does not cancel an active App Store subscription — manage or cancel that in your Apple account settings. Your subscription and purchase records may be retained by Apple and by our payments partner (RevenueCat) under their own retention policies.
Data is encrypted in transit using HTTPS/TLS, and our infrastructure providers apply their own security measures. Your sign-in session is stored on your device. No method of transmission or storage is completely secure, but we take reasonable measures to protect your information.
Arveli is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us information, please contact us and we will delete it.
Depending on where you live, you may have the right to access, correct, or delete your personal information, or to object to or restrict certain processing. You can delete your data directly using in-app account deletion, or contact us to exercise your rights.
We may update this Privacy Policy from time to time. We will revise the effective date above and, for material changes, provide notice within the app.
If you have questions about this policy or your data, contact us at support@arveli.app.