Privacy Policy

Who is responsible

Emmanuel Nsikan-David, based in Nigeria, operates Cibo and is responsible for its handling of personal information. Send support or privacy questions and requests to support@getcibo.com. This policy covers Cibo and its connected service. External platforms and apps have their own privacy policies.

Information Cibo handles

Depending on the features you use, Cibo handles:

Account details: email, display name, password authentication information or verified provider identifier, sessions and your photo. Google may provide a name and photo; Apple may provide a name and email, including a relay address. Cibo does not receive your Google or Apple password.
Source URLs, captions, audio and video content needed for imports; generated instructions, ingredients, equipment and media; your edits, favorites, collections, grocery lists and purchased checkmarks, and import usage.
Push tokens, notification permission information, and account and recipe identifiers needed to deliver and open alerts.
Subscription information, including your Cibo account identifier, purchased products, transaction status, renewal and expiry information needed to verify Premium. Cibo does not receive your full payment-card details.
Operational information including request identifiers, source platform, extraction stages, timings, outcomes, provider usage and errors. Hosting and security providers also handle network information such as IP addresses to deliver requests and protect the service. Authorized administrators can inspect extraction performance and associated recipe results to diagnose problems.
Product usage information such as screens opened, signup progress, recipe-import outcomes, Focus Mode use, grocery actions and purchase actions, associated with an account identifier or an anonymous identifier.
Information included in support or privacy correspondence.

Why information is used

We use information to authenticate accounts, import and organize recipes, deliver requested alerts, enforce allowances, answer requests, diagnose failures and maintain security and performance.

Depending on purpose and applicable law, processing relies on providing the service you request, consent, legal obligations or legitimate interests such as preventing abuse. You may withdraw consent where processing depends on it; the affected feature may stop working.

Information saved on your device

Sign-in credentials use device secure storage. Recent searches, timer deadlines and preferences such as whether you have seen the Focus Mode introduction are stored locally.

Checked cooking steps and your last viewed Focus Mode step are saved on this device for up to 500 recipes. They are isolated to your account and service, do not sync between devices and are cleared on logout. Start again clears progress for that recipe without stopping running timers. Clearing app data or uninstalling the app also removes this local progress.

Up to 100 grocery lists and pending purchased checkmarks can be saved on your phone for offline shopping. They are scoped to your account and API service and cleared on logout or an account change. Grocery lists stay in your account until you delete them, even if their original recipe is deleted. Text and structure for up to 100 recently opened recipes are cached for faster reopening. Entries expire after 30 days without opening. This cache belongs to your account and API service and is cleared on logout or an account change. It does not automatically download original videos or step clips. Normal playback can use temporary operating-system or library media caches.

Saved text can be read offline. Edits, favorites and other server changes need a connection and are not silently queued. Uninstalling can remove local data.

AI processing of imports

Cibo uses Google Gemini to turn source content into recipes. Imports can send captions, audio and selected images to Google. Do not submit private, confidential or sensitive material or content you lack permission to process.

Cibo uses a paid Gemini API project for recipe processing. Under Google’s paid-service terms, prompts and responses are not used to improve Google’s products. This does not mean that processing involves no retention: Google may retain information for service operation, security and abuse monitoring under its applicable terms. These protections do not cover content separately shared with Google through optional feedback or data-sharing programs.

Providers and other recipients

Information is shared as needed with:

Google for sign-in and Gemini processing, and Apple when you use Sign in with Apple.
Expo’s Push Service and Google Firebase Cloud Messaging on Android or Apple Push Notification service on iOS. Delivery includes the push token, message and routing identifiers.
Resend for verification, password recovery and account-related email, including the recipient address and message content. Messages sent to support@getcibo.com are forwarded through Cloudflare Email Routing to an inbox hosted by Google Gmail, so those providers handle your address, message and attachments.
RevenueCat and your app store to process purchases, restore access and verify subscriptions. RevenueCat receives your Cibo account identifier, transaction information and technical device information. We do not send recipe content to RevenueCat.
PostHog US Cloud to understand feature use and improve Cibo. Analytics includes account or anonymous identifiers, screen names, action counts, import outcomes and technical app/device information. We do not intentionally send recipe contents, source links, names, email addresses, passwords or verification codes to PostHog. Session replay is disabled.
DiceBear for a Voxel Art avatar using an opaque identifier rather than your email or display name. Image requests still share ordinary network information such as IP address with the provider.
Source platforms and media resolvers, including TikWM when resolving TikTok content.
Oracle Cloud for hosting; MongoDB Atlas for account and library storage; Upstash Redis for background jobs and request limits; and Cloudflare R2 for recipe media and uploaded photos. Cloudflare also handles DNS and proxied API traffic, including network information needed to route and protect requests.
Telegram for operational error alerts sent to the operator. Alerts contain sanitized error details and identifiers such as request, background-job and recipe identifiers. Filtering is designed to exclude credentials, email addresses, source links and recipe content.
Apps and recipients you select through your device’s share sheet.
Authorities or others when legally required or necessary to address security, fraud or legal claims, subject to applicable law.

Notifications and permissions

Cibo asks for notification permission when you start a timer or import a recipe. Denying it or changing it in phone settings does not remove access to recipes.

Timer alerts are scheduled locally. Recipe-ready push alerts are sent when instructions are ready, even if videos are still processing. Alerts can show recipe titles on your lock screen; control message previews in phone settings.

Choose profile photos through the system photo picker. Recipe imports do not need contacts, precise location, camera or microphone. Audio comes from linked videos, not from recording your phone.

Retention and deletion

Account and library information is retained to provide your account until deleted or no longer needed, subject to legal obligations. Deletion disables access and queues removal of the library, sessions, notification registrations, provider grants and owned media. Shared culinary catalog assets remain available to others.

Temporary extraction files are cleaned up after processing. Push registrations expire after 60 days without refresh and are invalidated by global logout or password reset. Detailed extraction performance records have a 90-day expiry and daily summaries a 365-day expiry. These limits do not cover every log or backup; cleanup may not happen at the exact expiry time.

Deletion runs in the background and does not guarantee immediate disappearance of every copy. Backup, provider and legally required records can have different rules. Contact us about a specific record or request.

Your choices and rights

Edit your name or photo in Your Profile → Edit profile. Delete recipes, collections and grocery lists in your library, or request account deletion in Your Profile → Delete your Account and confirm. You can also email support@getcibo.com for deletion or assistance.

Depending on applicable law, you may request access, correction, deletion, portability or restriction, object to processing, or withdraw consent. We may ask for information to verify that a request concerns your account. You may complain to the Nigeria Data Protection Commission or your local authority.

Uninstalling does not delete the server account. Turning off notifications does not delete your account or stop you using Cibo.

Security and international processing

Cibo uses access controls, password hashing and protected session storage to help secure accounts. No system guarantees complete security. Protect your device and contact us about suspected unauthorized access.

Cibo and providers can process information outside Nigeria or your country. Locations and data-handling rules can differ. Contact us about international processing and applicable rights.

Children

Cibo is intended for adults aged 18 or older. Contact us if you believe a child has provided personal information so we can investigate and take appropriate action.

Policy updates

We update the revision date when this policy changes and give notice of material changes where required. Send questions to support@getcibo.com.

Have a question?

Contact support@getcibo.com.