Ruchi

Last updated 7 October 2026

Privacy Policy

Your pantry, recipes, meal plans, shopping lists and cooking history stay on your device. Some information leaves the app when you ask Ruchi to use an online feature. This policy explains what that means.

1. Who we are

Ruchi is made by Kornayas.

2. Information kept on your device

Your profile choices, pantry, shopping lists, meal plans, cooking history, notes, photos and recipes are stored inside the app on your device. Ruchi has no personal account system and does not receive a copy of this information during ordinary use.

Backups are saved or shared only where you choose. That destination is responsible for handling its copy. See cloud backups below for details.

3. Cloud backups and Google user data

Ruchi requests optional Google Drive access only when you select it in Backup & restore, including for automatic backups.

Ruchi requests the https://www.googleapis.com/auth/drive.file permission. This allows it to see, create, edit and delete only files it creates or that you explicitly choose to use with Ruchi. It does not give Ruchi permission to browse or access your entire Google Drive. Ruchi manages its dated .ruchi backup files in a folder named Ruchi.

What Ruchi accesses and why

  • Google sign-in provides your email address and basic account information, which can include your account ID, name and profile-picture address. Ruchi uses your email to show the connected account; it does not use your Google name or picture to fill in your Ruchi profile.
  • OAuth access tokens authorize requests to Google Drive. Folder and file IDs, names and modification dates let Ruchi find, list, update, restore and delete its backups.
  • Backup contents include your personal recipes and photos, pantry, shopping lists, meal plans, cooking history, saved, liked and skipped recipes, notes and recipe ordering, plus the backup date and app version. Your profile and dietary settings, subscription state and sign-in credentials are not included.

Storage, transfers and use

Backups are created on your device and transferred directly to or from Google Drive or OneDrive. The provider stores its copy. Restoring requires your confirmation before changing your kitchen. Kornayas servers do not receive or store backup contents or, for Google Drive, sign-in credentials, account information, file IDs or metadata.

File listings are held in memory. The selected provider, backup schedule, last-backup status and any provider error message are stored locally.

Google user data is used only to operate this connection and your backups. The backup flow does not send it to advertising, analytics or AI services, or use it to build advertising profiles. We do not sell it or share it with other providers. Once restored, your kitchen data supports Ruchi's normal on-device features; sharing or exporting it is your choice.

How Google user data is protected

Ruchi's requests to Google Drive use HTTPS (TLS) to encrypt data in transit. Google's sign-in software manages the connection and cached account information and credentials on your device. Ruchi obtains access tokens from it when needed; Ruchi does not keep its own Google refresh token or put tokens in its database or backups. Temporary upload and restore files are held in Android app-private cache storage and removed as described below.

Retention, deletion and disconnecting

  • After uploading, Ruchi keeps the newest three dated backups and deletes older ones. Another backup on the same date replaces that day's file. Backups otherwise remain in Drive until you delete them.
  • Delete cloud backups in Backup & restore permanently deletes Ruchi's dated backup files from the connected Drive folder, not your current kitchen or separately saved copies. These deletions do not move files to Drive's trash. You can also manage the files directly in Google Drive.
  • Successfully disconnecting Google Drive revokes Ruchi's access, signs out of its Google connection, clears its local cloud-backup status and removes Drive from automatic backups. You can also revoke access from your Google Account's third-party connections. Either route stops future authorized Drive operations without deleting existing backups or data already restored to your device.
  • Temporary upload and restore files are removed when the operation or restore preview finishes. An interrupted operation can leave a temporary file in the app's cache until that cache is cleared. Restored data remains in Ruchi until you remove it. Clearing Ruchi's app data or uninstalling removes its private local data, not Drive backups or Google's account-level authorization. Disconnect first or revoke access in your Google Account if you also want to remove that authorization.

Ruchi's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Information obtained through Google Workspace APIs is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models. Google handles your account and Drive storage under Google's Privacy Policy.

4. Online imports

When you ask Ruchi to import from a link, text, a photograph or a voice recording, the material you provide is sent to online services that process it and return the result. Ruchi does not add your pantry, meal plan, saved recipes or profile to that request.

Other companies involved in processing the request handle information under their own privacy terms.

Voice recording happens only after you press the microphone button. The app removes its temporary recording after sending it, whether the request succeeds or fails.

5. Technical information

Ruchi uses anonymous technical identifiers to operate online features, confirm subscription access, apply reasonable usage controls, prevent abuse and help diagnose failures. These identifiers are not your name, email address or advertising identity.

Limited service records may include when an online feature was used, which general feature and membership were involved, whether it worked, and basic performance and usage measurements. They do not include the recipe page, text, image, recording, prompt or result.

Ruchi may also report a normalized ingredient name that its built in dictionary could not recognize. Technical identifiers protect the submission but are not included in the stored ingredient report. These reports are used only to improve ingredient matching.

6. Purchases

Purchases and subscriptions are handled by the app store and payment services. Ruchi receives an anonymous customer reference and information about whether access is active. We do not receive your payment card details.

7. Internet requests

Online imports, subscription checks, recipe updates and app update checks use an internet connection. Like any internet request, the receiving service can see technical connection information such as an IP address. Ruchi does not use this information for advertising or to follow you across apps or websites.

8. How information is used

Information described here is used only to:

9. Sharing

Ruchi uses service providers to host online features, process requested imports, deliver updates and manage purchases. They receive only what is needed for their part of the service. Ruchi does not sell personal information, show advertising, or share information for targeted advertising.

These service-provider disclosures do not include Google authentication or Drive backup data, which is handled only as described in the cloud backup section.

10. Retention

Information on your device remains there until you remove it or uninstall the app. Ruchi does not deliberately retain the submitted page, text, photograph, recording, prompt or result of an online import after the request finishes. Technical records and counters are kept only for as long as reasonably needed to operate, protect and understand the service.

Minimal trial eligibility and subscription history may be kept longer than temporary service records to prevent repeated introductory access. These records do not contain your cooking information or payment card details.

11. Your choices and rights

You can view, change, export and delete the cooking information stored on your device. You can also choose not to use online imports or create voice recordings. For a question or request about information held by the online service, contact us.

Privacy rights differ by location. We will respond to valid requests as required by the laws that apply.

12. Children

Ruchi is intended for people aged 13 and over. We do not knowingly collect personal information from children below the age that applies where they live.

13. Security

Ruchi uses device protections, encrypted internet connections and limited access to service records. No method of storage or transmission can be guaranteed completely secure.

14. International processing

Companies that help provide Ruchi may process the limited information described here in other countries, where privacy laws may differ.

15. Changes

This policy may change as Ruchi changes. The date at the top shows the latest revision. We will notify you if we change how Ruchi uses Google user data. Other material changes to how information is handled will be communicated as required.

16. Contact

Email ruchidev@kornayas.com for privacy questions or requests.