Français
Privacy Policy
Last updated: November 14, 2026
1. Overview
Ribh ("the app"), published by Anas Youala (individual seller, brand Apogee Labs), is an inventory and profit tracking app for online sellers. This policy explains what the app and our servers do with your data. It covers the Ribh apps for iPhone and for Android, up to and including version 1.1.5. Where a version or the two apps differ, we say so (for example, some notes below are about Android version 1.1.1 only). The voice log and the photo studio, described in section 7, are new in version 1.1.5 of the iPhone and Android apps.
We do not sell your data. The app shows no ads and includes no ad network SDK. On iPhone, Firebase Analytics is the version that could read Apple's advertising identifier, but the app does not ask for tracking permission, so it cannot read it. We do use outside services for sign-in, cloud storage, analytics, crash reports, purchases, AI features, email, voice and photo features. Each one is named below with what it receives and why.
This policy is about the app. It does not describe the ribh.ma website in detail.
2. Data on your device
Your items, sales, orders, expenses, credit records and customer details are saved in a database on your phone. Product photos you take or pick stay on your phone and are not uploaded by cloud sync. (Photos you send to an AI feature are covered in section 7.) Evening profit reminders are scheduled on your phone itself. We do not use a push notification service. On iPhone, your answers in the Plan Advisor quiz are not saved or sent.
This data stays on your phone until you uninstall the app. Deleting your account does not erase it from the phone.
Your phone's own backup (for example iCloud on iPhone or Google backup on Android) may also copy the app's data, depending on your phone settings. Android version 1.1.1 does not exclude anything from Android backup. Later Android versions still include the shop database (which holds the analytics install ID from section 5) but exclude the device-record ID from section 3 and the saved sign-in session.
3. Account and cloud sync
You can try the app without an account. After you save your first product, sale or order, the app asks you to sign in or create an account. You can tap "Not now" once. From your third saved record on, the app asks again without a "Not now" option, so you should expect to need an account to keep adding records. It also asks before a purchase, a restore, an export or sync (and on iPhone, before you open the Invite screen or redeem a code).
Sign-in options:
- Email. A one-time code, or email and password, with confirmation and password reset emails. Your email address is stored by Supabase, our sign-in and database provider. Passwords are stored by Supabase as hashes.
- Google sign-in. Offered on Android, not on iPhone. Google's account chooser runs on your phone and gives Supabase a sign-in token. Supabase then stores your Google email address, name and profile picture link.
- Phone number. Android version 1.1.1 shows a phone number option. It is switched off on our server and does not work today. If it were switched on, your phone number would be stored with your account.
- Sign in with Apple is not offered.
Supabase also keeps session tokens, sign-in times, and the IP address and device or browser details (user agent) of each sign-in session. These are removed when your account is deleted. We keep a profile record for each account: email address, plan and plan expiry, whether the plan is billed by Apple, Google or on the web, the product bought, app language, your shop and your role in it.
At first launch, both apps try to create an account with no email, just a random ID, when there is no session. At the time of this update our server refuses this, so cloud sync starts after you sign in with an account. If we ever allow it, your data would be backed up under that random ID before you add an email.
Cloud sync has no on/off switch and is not limited to paid plans. While you are signed in, the app copies your business data to our database, which is hosted by Supabase in Frankfurt, Germany (EU). This is used for backup, restoring on a new phone, using several phones and working with a team. The number of phones you can use at the same time depends on your plan. The copy includes:
- items (name, SKU, barcode, notes, buying price, amount paid, shipping-in cost, purchase date, stock, supplier and category), variants (with any price you set) and purchase batches;
- sales (item, quantity, sale price, cost, date) and expenses (labels, amounts, dates, categories);
- orders, including customer name, phone and city, notes, courier, cash-on-delivery amount, fees, status dates, order lines and payments;
- customers who owe you money (name, phone) and the credit entries (amount, note);
- suppliers (name, phone, notes), couriers (fees) and categories;
- your shop name, your team, the app language, and the ID of the account that created each record.
The app also keeps a device record for each signed-in phone: a random device ID, the device name (for example "Samsung Galaxy A14" or an iPhone model code), the platform, the time it was last seen, and whether it was revoked. It is updated each time you open the app and is used to apply your plan's device limit.
When you delete a record in the app, it is marked as deleted on our server and the row stays there until your account is deleted.
4. Team members and invites
A shop owner or manager can invite people by email and give them a role (owner, manager or staff). We store the invited email address and the role. Supabase creates a sign-in account for that address, and an invitation email is sent through our email provider (section 10). At the time of this update, the person is added to the shop right away. We may change this so that the person has to accept the invitation in the app first. Team members can see shop data according to their role, and the records they add carry their account ID.
5. Analytics and crash reports
These run for every user, signed in or not, on every plan. There is no consent screen and no setting in the app to turn them off.
- Our own events table (Supabase, Frankfurt). Each install makes a random install ID. The app sends it with an event name, small values such as counts and labels (for example onboarding step, payment method, number of order lines, what triggered a sign-in request, notification permission yes or no), the app version, the platform and the time. Events include app open, onboarding steps, first product, first sale, products and orders added, orders delivered, quick sales, paywall shown and dismissed, purchase button taps, account requests, trial start, help screens opened, and a return on day 1 and day 7. This table does not hold your account ID, email, product names, prices or customer details. Our server receives your IP address with each request, as any server does, but it is not stored in that table. We use this to understand how sellers use the app and to measure our own campaigns.
- Campaign tags. At first launch the app may record which campaign, source or link brought you: on Android from the Google Play install referrer, on iPhone from the link that opened the app. If there is none, it records a label such as "organic".
- Google Firebase Analytics. Both apps include it. Many of the events above are also passed to it, with the same kind of small values (counts and labels). From version 1.1.4 (and so in 1.1.5) the business events it receives carry counts only: when you add a product, the quantity; when you restock, the quantity added; when you create an order, the number of lines and the payment method; when an order is delivered, no values; and the sign-in method when you sign up or log in. They do not include product names, prices, cash-on-delivery amounts, courier names, customer names or phone numbers, and the app does not send your email or account ID with them. Note about iPhone 1.1.3 and Android 1.1.1: those older builds may still send product names, prices, cash-on-delivery amounts and courier names in these events. We have not confirmed whether Firebase collects all of this on every phone. It may also collect standard information on its own, such as an app instance ID, device model, operating system and app version, language and approximate country.
- Sentry (crash reports). When the app crashes or hits an error, it sends a report to Sentry's German (EU) servers: the error type and message, the technical trace, the app version, operating system, device model, language and device state, and session start and end to count crash-free use. The app does not attach your email or account ID. Error messages can occasionally include a short piece of text the app was handling, for example from a file you import. Sentry may also give each install a random identifier. Sentry receives the IP address of the request, as any server does, and we have not confirmed whether it keeps it.
On Android we remove the advertising ID permission from the app. On iPhone the app does not show Apple's tracking permission prompt.
6. Purchases and subscriptions
Pro and Expert subscriptions are paid through the Apple App Store or Google Play. We do not receive or store your card or other payment details. Apple and Google handle the payment under their own policies.
The app uses RevenueCat to manage plans. RevenueCat is set up each time the app starts, for every user, including free users. When you are signed in, RevenueCat identifies you by your Ribh account ID, a random ID that is linked to your account. Before you sign in it uses its own random ID. RevenueCat receives the purchase receipt, product, purchase times and store country from the store, and the standard technical data its software collects, such as IP address and device, operating system and app version. The app does not send your email address, name or phone number to RevenueCat. Our server also asks RevenueCat about your subscription, using your account ID, to confirm your plan.
RevenueCat sends purchase events to our server. We store each full event (account ID, product, store, price, currency, country, transaction IDs and times) in a log, and we save your plan, plan expiry, billing store and product on your profile.
If you buy a plan on the ribh.ma website, the order is handled by Paddle, which is the merchant of record and reseller for web payments. Paddle receives your name, email address, country and payment details, and handles the payment, invoices and refunds itself under its own privacy policy (https://www.paddle.com/legal/privacy). Ribh does not receive or store your card or payment details. We keep your Paddle customer and subscription IDs on your profile.
7. AI features
The app has several AI features: the voice log, the photo studio, the help chat, a daily tip, Ask Ribh, reading a pasted customer message, reading a chat screenshot, reading a product photo or delivery photos to add stock, and matching the column names of a CSV file. Which ones you can use depends on your plan. The app sends your request to our server (Supabase Edge Functions), which sends it on to Google Gemini. We keep the Gemini key on the server.
What is sent:
- Help chat: the question you type and your language.
- Daily tip: a summary of your shop (profit for the month, number of sales, top earning item, biggest cost, low stock items and counts). The app requests it automatically when a Pro or Expert user opens the dashboard.
- Ask Ribh: the same summary plus the name, units sold, units left, profit and cost of every item, the total your customers owe you, and the question you type.
- Pasted message: the text you paste, up to 8,000 characters.
- Chat screenshot, product photo, delivery photos (up to 3): the image itself.
- Voice log and photo studio: see the two sections below.
- CSV import and courier reconciliation: the column header names, not the rows.
Voice log (version 1.1.5)
The voice log lets you say a sale, a purchase, an expense or a cash-on-delivery order out loud instead of typing it. It uses the microphone only after you tap the mic button, and only while the recording runs. The recording is stopped automatically after about 20 seconds. Ribh never listens in the background.
- What is sent: the audio clip (up to about 20 seconds, compressed), your language, and, for a sale, purchase or expense, the names of up to 60 of your products (never their prices) so that what you say can be matched to your stock. For a spoken order, no product names are sent, only the names of up to 30 of your couriers. If you say them, the clip contains a customer's first name, phone number and city, and the courier.
- Where it goes: from your phone to our server (Supabase Edge Functions), then to Google Gemini (our server may first count the clip's size with Google, and may retry on a second Gemini model if the first fails), which listens to the clip and returns a draft: item, amount, and for an order the customer name, phone, city, courier, products and cash to collect. You check the draft before anything is saved.
- Google as processor: Google processes the clip on our behalf under the paid terms of the Gemini API. Under those terms Google does not use it to train its models.
- Retention: our server does not store the audio. It is held in memory for the length of the request and dropped. No file, table or log line of ours contains it. The phone deletes its own temporary copy as soon as the call ends. The draft you save is stored like any other sale, expense or order (sections 2 and 3). We keep a count of voice requests per account and day to apply your plan's limit.
- Google's own retention: Google may keep requests for a short time under its own terms, for example to detect abuse. We have not set that period and have not confirmed it.
Photo studio (version 1.1.5)
The photo studio turns a photo of a product into a clean shop photo. The first time you use it, the app tells you that the photo is sent to Google Gemini and asks you to agree.
- What is sent: one photo you pick or take, reduced on your phone to at most 1280 pixels on its longest side with its location and other metadata removed, and the style you chose. Our server removes any remaining metadata again. No text you type reaches the prompt.
- Google Gemini: the photo goes through our server to a Google Gemini image model, which makes the new photo. Google's own terms apply to how it handles the photo. We have not confirmed whether Google keeps it or uses it for anything else. Do not use a photo you do not want to share.
- Retention: our server does not store the photo or the result. They are held in memory for the request and dropped. The new photo is returned to your phone. It is saved to your photo library only if you save it, and your original photo is not changed. We keep a count of studio uses per account to apply your plan's limit. This count follows your email address, as a hashed value, so that deleting and re-creating an account does not give a new allowance.
- Google's own retention: set by Google and not confirmed by us.
Your control and deleting
Both features are optional. Nothing is recorded or sent unless you tap the mic or send a photo to the studio, and you can refuse the microphone permission in your phone settings (the rest of the app keeps working). Because we do not keep the audio or the studio photos, there is nothing of them to delete on our side. To delete what you saved from them (a sale, an order, a customer) delete the record in the app, or delete your account as described in section 15. Clips and photos already processed by Google fall under Google's retention above. We cannot see or delete them.
Pasted messages and chat screenshots can contain your customers' names, phone numbers and cities. The app asks for your agreement the first time you send a photo or screenshot, and remembers your answer unless you clear the box. It also asks the first time you use the voice log or the photo studio. It does not ask before it sends typed help questions, pasted message text, CSV column names, the daily tip or Ask Ribh.
Our code does not save the content you send or Gemini's answers in our database. It saves a count of requests per account, day, feature and plan, and a daily count of photo searches per account to limit abuse. Our server logs (for example error logs) can hold short pieces of request data, such as an invited email address, an account ID, or up to a few hundred characters of a Gemini reply when the reply cannot be read. How long Google keeps this content, and where Google processes it, is set by Google. We have not confirmed those details.
8. Lookups, WhatsApp and sharing
- Open Food Facts. When you scan or type a barcode to fill in a product name, the app sends the barcode straight from your phone to Open Food Facts. It sees the barcode and your IP address.
- Online product photos. During setup (this option is on unless you turn it off) and when you tap "Find photos online", the app sends the product name, and sometimes the category name, to our server. Our server asks public catalogues (iTunes, Open Library, Nintendo, Steam and Openverse, and eBay or Google image search when we have them switched on) for a picture. Your phone then downloads the picture from the website that hosts it, which sees your IP address.
- WhatsApp reminders and sharing. When you tap a credit reminder, the app opens WhatsApp with your customer's phone number and a message that can include the amount owed and your payment instructions. If there is no phone number, it opens the share sheet instead. When you export, print or share a file, it goes to the app you choose. Those apps receive that content under their own policies. We do not see it.
9. Free-month codes, trials and invites
In the iPhone app, from version 1.1.3, when you open the Invite screen, start the Expert trial (14 days from version 1.1.4, 7 days in 1.1.3) or redeem a code, the app proves to our server that the request comes from a genuine device. It sends your platform, a device identifier, and a check from Apple (App Attest and DeviceCheck). Our server verifies this with Apple. Android version 1.1.1 does not do this. Android from version 1.1.4 does the same check using Google Play Integrity.
Our server stores scrambled (hashed) versions of the device identifier, your IP address and your email address, the App Attest public key, and the account IDs involved. This is used to stop one person claiming several free months or referral rewards. We have not set an expiry for these records.
10. Emails we send
We send sign-in codes, confirmation and password reset emails, and team invitations from hello@ribh.ma. They are sent through Resend, which receives the recipient address and the message. We have also sent a one-time email, through Resend, to people who had signed up with an email and stopped using the app. If you write to contact@ribh.ma, we receive your address and your message.
11. Phone permissions
- Camera: to scan barcodes and photograph products. The app can be installed on Android phones that have no camera.
- Microphone: asked the first time you tap the mic in the voice log (version 1.1.5), to record the short clip you speak. It is used only while you record. iPhone shows: "Ribh listens when you tap the mic to log a sale, a purchase or a cost by voice. Ribh does not keep the clip." On Android the app declares the record audio permission. The app works without it, and the microphone is not required to install.
- Photo library (iPhone): to attach photos to items, and to save studio photos when you choose to. Android uses the system picker.
- Notifications: asked after your first sale, for evening profit reminders. On Android the app also uses the "receive boot completed" permission to restore those reminders after a restart.
- Internet: for sync, sign-in, AI features, purchases and lookups.
- Location: the iPhone app contains a text about location, but it does not ask for or use your location.
The app does not request access to your contacts. It uses the microphone only for the voice log, as described above.
12. Who receives data
- Supabase: sign-in (including the IP address of sign-in sessions), your synced business data, profile, devices, our events table, purchase logs and AI request counts. Why: to run your account and backup.
- Google Firebase Analytics: the events in section 5 (counts and labels only, from version 1.1.4). Why: product analytics.
- Sentry: crash and error reports. Why: to find and fix crashes.
- RevenueCat: purchase and plan data. Why: to unlock the right plan.
- Google Gemini, through our server, as our processor: the AI content in section 7, including voice clips (with customer name, phone, city and courier if you say them) and studio photos. Why: to run the AI features.
- Apple and Google: payments and receipts; Apple App Attest and DeviceCheck, and Google Play Integrity, for the checks in section 9; Google sign-in.
- Resend: email addresses and email content. Why: to deliver our emails.
- Open Food Facts and the photo catalogues in section 8: barcodes or product names. Why: to fill in product names and pictures.
- Paddle: merchant of record for web plan payments, if you buy on ribh.ma (name, email, country and payment details, handled by Paddle).
13. Where data is processed
Our database and sign-in service run in Frankfurt, Germany (EU). Sentry reports go to Sentry's German region. We have not confirmed where Google (Firebase and Gemini), RevenueCat, Resend and the lookup services process data, or where our server functions run. Some of them may process data outside the EU and Morocco.
14. How long we keep data
- Your account and synced business data are kept until you delete your account. Records you delete in the app stay marked as deleted until then.
- Voice clips and studio photos are not stored by us (section 7). Google keeps them under its own terms, which we have not confirmed.
- Our events table has no automatic deletion schedule.
- Purchase logs have no automatic deletion schedule.
- A daily request counter table, which also holds IP addresses from older versions of our AI features, has no automatic deletion schedule.
- Hashed records for the checks in section 9 have no expiry.
- Firebase, Sentry, RevenueCat, Resend and Google keep data under their own settings and policies. We have not set the periods ourselves.
- Our hosting provider may keep backup copies for some time.
15. Data deletion
The message in the app says "all your cloud data". The list below is the full picture, including what is not deleted.
To delete your account, sign in, then go to Settings, then Account, then Delete account. This deletes your sign-in account, your profile, the shops you own and all their data, and your device records and AI request counts from our database.
What is not deleted:
- If you own a shop with team members, deletion is refused unless the shop has a co-owner. If it has one, ownership passes to the co-owner and the shop stays. If deletion fails, contact us.
- Records you added to someone else's shop stay there, no longer linked to your account.
- We may keep a hashed version of your email address and the hashed device records in section 9, so that a free month cannot be claimed again.
- Purchase logs, which include your account ID, stay in our logs. Other server log lines that contain an account ID or an invited email address are not edited either.
- The studio allowance record, which follows a hashed email address (section 7) and the daily request counter table in section 14 are not cleared when you delete your account.
- Events already sent to our events table (they carry an install ID, not your account), to Firebase and to Sentry are not removed. Your RevenueCat record is not removed automatically.
- Voice clips and studio photos held by Google fall under Google's own retention. We cannot see or delete them.
- Local data on your phone stays until you uninstall the app.
- Backups kept by our hosting provider may still hold your data for some time.
- Your Apple or Google subscription is not cancelled. Cancel it in your store account. If you have a web plan, deletion may cancel it.
You can also email contact@ribh.ma and ask us to delete your data. We can ask RevenueCat to remove its record. Firebase and Sentry data is not linked to your account, so we cannot find it to delete it.
16. Your rights
Under Moroccan Law 09-08 and, if you are in the EU or EEA, the GDPR, you may have the right to access, correct or delete your personal data, to object to how it is used, and to get a copy of it. You can edit your records in the app and export them as CSV or text files. If you have no account yet, exporting asks you to sign in first. To use any right, email contact@ribh.ma from the address on your account. Events in our own table carry a random install ID that is not linked to your account in our database, so we cannot find them by your email and may not be able to delete them. The same goes for data that Firebase and Sentry hold. If you are in the EU or EEA you may also complain to your local data protection authority.
17. Children
Ribh is a business tool and is not directed at children under 13. We do not knowingly collect data from children. Analytics run for every user and we do not know the age of a user. If you believe a child has given us data, contact us.
18. Changes to this policy
We may update this policy when the app or our services change. We will change the date at the top of this page when we do.
19. Contact
Questions? Email us at contact@ribh.ma