Privacy Policy — Yebalabs Identity

1. Who we are and what this policy covers

Yebalabs operates Yebalabs Identity at my.yebalabs.com, a shared authentication and account service for Yebalabs products and participating businesses in the Yebalabs ecosystem. Yebalabs is the controller of personal data used to operate the identity service.

This policy explains how Yebalabs accesses, collects, uses, stores, protects and shares personal data when you create an account, sign in, manage your profile or use Yebalabs Identity with a connected service.

Individual Yebalabs products and ecosystem businesses may provide additional notices for information they collect within their own service.

2. Information we collect

Information you provide

your name, email address, phone number and profile image;
account credentials or one-time verification codes, where those sign-in methods apply;
the business or organisation you join, your role and account permissions;
support requests, account changes and communications with us.

Information from connected sign-in providers

If you choose Google sign-in, we receive your Google account identifier, verified email address, name and profile picture. We do not receive your Google password.

Security and technical information

We process session identifiers, client application identifiers, sign-in events, IP address, device and browser information, and security logs needed to prevent abuse and maintain reliable access.

Information from ecosystem businesses

A participating business may provide membership, role or subscription information so we can give you the access that business has authorised.

3. How and why we use information

We process personal data only where it is necessary for a disclosed purpose and supported by consent, performance of a contract, compliance with law, or another lawful basis under Rwanda law. We use it to:

create, verify, secure and manage your Yebalabs account;
authenticate you and maintain sign-in sessions across approved Yebalabs services;
connect you to the ecosystem business or service you selected;
apply roles and permissions and prevent unauthorised access;
send essential account, verification and security messages;
detect abuse, investigate incidents, maintain audit records and comply with legal obligations;
respond to support requests and exercise or defend legal rights.

We do not use your personal data for unrelated advertising and do not sell it.

4. Google user data

Google sign-in is optional where another sign-in method is offered. When you use it, Yebalabs validates the Google identity token and uses the resulting account identifier, verified email address, name and profile picture only to authenticate you, create or link your Yebalabs account, prevent duplicate accounts and display your profile.

Yebalabs does not request access to your Gmail, Google Drive, contacts, calendar or other Google service content through the identity service. Google user data is not sold, used for advertising or transferred for unrelated purposes. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

You may remove Yebalabs access from your Google Account. Removing access stops future Google sign-in but does not automatically delete the Yebalabs account already created; you may request account deletion as described below.

6. Storage, international processing and security

Identity records are kept on access-controlled Yebalabs production infrastructure. Some Yebalabs products may use Cloudflare R2 to store files or content that users upload; R2 is not the primary database for Yebalabs Identity. A product using R2 remains responsible for giving any additional notice required for that content.

If infrastructure or a service provider stores or processes personal data outside Rwanda, Yebalabs will do so only subject to Rwanda’s applicable authorisation, contractual and security requirements. We assess providers and limit the information made available to them.

Our safeguards include HTTPS in transit, signed authentication tokens, access controls, least-privilege service accounts, protected secrets, security logging, rate limiting and encrypted off-site backups. No system can guarantee absolute security, but we review safeguards and respond to identified risks.

Cookies

Yebalabs Identity uses only cookies or similar storage needed for sign-in, session security and fraud prevention. We do not use advertising cookies on this website.

7. How long we keep information

We retain personal data until the purpose for which it was collected has been fulfilled. We may keep it longer where Rwanda law permits or requires it, where a contract requires it, to protect the service, investigate misuse, resolve disputes or enforce a court order.

When information is no longer required, we delete, anonymise or securely isolate it. Limited copies may remain temporarily in protected backups until their normal replacement cycle completes.

8. Your rights

Subject to Rwanda’s Law Nº 058/2021 and applicable limitations, you may request:

access to your personal data and information about its processing;
correction of inaccurate or incomplete information;
erasure or restriction of processing;
an objection to certain processing;
portability of personal data;
withdrawal of consent where processing relies on consent;
review of a decision based solely on automated processing.

We may need to verify your identity before completing a request. You may also raise a complaint with Rwanda’s supervisory authority for personal data protection.

9. Children

Yebalabs Identity is not designed for a child to create an account independently. Where a Yebalabs product is lawfully offered to a child, the responsible product and business must obtain any consent or authorisation required by Rwanda law before the child’s data is processed.

10. Changes to this policy

We may update this policy as our services, providers or legal obligations change. The current version will always appear at this address with its effective date. If a change materially affects how we use personal data, we will provide additional notice where appropriate.

Mubazi app

This section applies to Mubazi, the expense tracking app published by Yebalabs for Android and iOS. It adds to the rest of this policy for information the Mubazi app handles.

What stays on your device

Without an account. Your expenses, recurring bills, incomes and savings goals are kept on your device. Nothing is sent to Yebalabs until you sign in.
Always on the device only. Whether or not you sign in, these are never sent to Yebalabs: the photos you attach to expenses, the payment channels you name (such as an app you paid with), your recurring bills, incomes and savings goals, your language, theme and notification choices.
Photos. When you attach a photo, you scan it with your phone’s own document scanner or camera, or pick it with your phone’s own photo picker, and Mubazi only receives that one photo. It is resized and saved as a new image, which removes its location and other metadata. Any text in it, such as a receipt’s details, is read on your device and added to the expense’s description, which you can edit. The photo itself stays on the device, and is deleted with its expense or when you clear local data. A description is synced like the rest of the expense if you sign in, so remove anything you do not want saved.
Device backups. On Android, Mubazi’s data is left out of Google backup and of transfers to a new phone. Expense photos are also left out of iCloud backups. On iOS, your iPhone’s own iCloud backup can otherwise include Mubazi’s data on the device, such as your records and settings, if you have it turned on; that backup is held by Apple under your account with them, not by Yebalabs. Sign-in tokens are never included. If you sign in, your synced records come back when you sign in on the new phone, but photos, named payment channels, recurring bills, incomes and savings goals do not.
Signing out. When you sign out, or your session ends, your account’s records are hidden on the device: Mubazi shows them again only when the same account signs in. Records not yet synced wait on the device until then. To remove them from the phone, use Settings → Account → Clear local data.
Records from earlier versions. Earlier versions of Mubazi kept debts, mobile money confirmations, pinned phone numbers, payment codes and shortcuts on the device. Current versions no longer use them; they stay on your phone until you clear local data or remove the app.

What is synced when you sign in

After you sign in, the following are backed up and synced to the Mubazi service so they are available on your devices, linked to your account email and user identifier:

Expenses: amount, title, optional description, date, and whether you paid by cash or bank if you said so. When you mark a recurring bill as paid, Mubazi records an expense with the bill’s name as its description, which is synced like any other expense.
Income and wallet amounts recorded with earlier versions of Mubazi stay in your account until you delete it, although current versions no longer show or add them.

Debts recorded with earlier versions of Mubazi stay in your account until you delete it, although current versions no longer show or sync them.

Who can see your records

Your records belong to you. We keep them only so you can back them up and use them on your devices. We do not read them, analyse them or build profiles from them.

No browsing. Yebalabs staff do not look through individual records. A small number of authorised engineers can reach the database, and only to fix a problem you report and ask us to investigate, to protect the service from abuse, or when the law or a court order requires it.
No other use. Your records are not used for credit scoring, lending decisions, advertising or market research. They are not shared with banks, lenders, employers or data brokers, whether named or in combined statistics.
Protected in transit and in backups. Records travel over HTTPS, are stored on access-controlled infrastructure and are copied only into encrypted backups.
Your choice to sync. If you prefer that your records do not leave your phone, use Mubazi without signing in. Tracking works fully on your device, and your records are only uploaded if you later sign in.

Spending report by email

If you are signed in and ask for a PDF spending report, the Mubazi service builds it from your synced expenses for the date range you chose and emails it to your account email address only, through our transactional email provider. The report is not kept after it is sent, and its contents are not written to our logs.

Country

When you first open Mubazi, it works out your country. It reads the country of your SIM card, mobile network or device region setting on the device and, if needed, asks the Mubazi service for the country of your network address. Only a two-letter country code is stored (on your device and, once you sign in, with your account); your IP address is not stored. You can change the country in Settings.

Sign-in and profile

Mubazi signs you in with a one-time code sent to your email. On Android you may instead use Google sign-in, as described in section 4. Sign-in tokens are kept in encrypted device storage and are excluded from device backups. If your account has a profile picture, such as your Google picture, the app loads it from where it is hosted and keeps a copy in its image cache, which is cleared when you sign out or delete your account.

Device permissions

Notifications. Optional reminders and daily summaries are written and scheduled on your device, using your records. Mubazi does not use push notifications or send reminder content to a server. Like any notification, they can appear on your lock screen.
Camera. Used only when you choose to take a photo of a receipt; on iPhone, Mubazi asks first.
App lock. If you turn it on, your phone’s own Face ID, Touch ID, fingerprint, PIN, pattern or passcode check unlocks Mubazi. The phone only tells Mubazi whether the check passed; Mubazi never receives your biometric data or passcode.
No other permissions. Mubazi does not ask for access to your contacts, messages, calls or photo library. Library photos reach it only through the system picker described above.

Usage analytics

To understand which features are used and fix what does not work, Mubazi sends usage events to Google Analytics for Firebase, a service of Google that processes the data for us and may process it outside your country, including in the United States.

Events Mubazi sends. Opening the app; finishing or skipping the introduction; allowing notifications; recording an expense; signing in (email or Google); sharing Mubazi; and turning usage data on or off.
Collected by Firebase itself. App-instance and Firebase installation identifiers, first open, sessions and time in the app, app updates, device model, operating system, language, app version, and approximate country or region derived from your network address. On Android, when the app is first opened, Mubazi reads the Google Play install referrer and records its campaign tags (source, medium and campaign) so we know which link or campaign led to the install.
What is never sent. Amounts, balances, titles, descriptions, notes, photos, your email address or your names. Analytics are not linked to your Mubazi account, and the advertising identifier is not collected.
Your choice. Usage analytics are on by default. You can turn them off at any time under Settings → Preferences → Share usage data; Mubazi then stops sending events.
Retention. Usage events are kept by Google for the retention period set for the Mubazi project, at most 14 months, and are then deleted. Because they are not linked to your account, deleting your account does not delete them; turning off usage data stops new ones.

Sharing from the app

When you share Mubazi, the message is created on your device and handed to the app you choose. Yebalabs does not send, receive or see what you share or who you share it with; only the fact that you shared, without the content, is counted in usage analytics if they are on.

Payments

Mubazi records what you enter. It does not make, receive or process payments, does not connect to your bank or payment apps, and is not a bank or payment service.

What we do not do

Mubazi contains no advertising and does not track you across other companies’ apps or websites. Apart from the usage analytics described above, which you can turn off, it uses no third-party analytics or crash-reporting services, and your financial records are not sold or shared for marketing.

If you are in the EU, the EEA or Norway

The EU General Data Protection Regulation applies to Mubazi when you use it there, in addition to the rest of this policy. Yebalabs is the controller of your Mubazi data.

Why we process your data. We process your account and synced records to provide the service you asked for (performance of a contract). We process security and technical information, and usage analytics, for our legitimate interests in keeping Mubazi secure and improving it; you can turn analytics off in the app at any time. We keep records where the law requires it (legal obligation).
Your rights. You may ask for access to your data, correction, erasure, restriction, portability, and object to processing based on legitimate interests. Where processing relies on your consent, you may withdraw it at any time. To use these rights, write to apps@yebalabs.com; you can also delete your account in the app.
Complaints. You may complain to the data protection authority where you live or work.
International transfers. Yebalabs is based in Rwanda, so synced data is processed outside the EU and the EEA. Where the law requires it, we protect such transfers with appropriate safeguards, such as the European Commission’s standard contractual clauses. You can ask us for details at the address above.
No automated decisions. Mubazi makes no decisions about you based solely on automated processing.

Deleting your data

You can delete your account in the app under Settings → Account → Delete account. After you confirm with an emailed six-digit code, your profile and all your records are deleted from the Mubazi service and from the device. Records kept only on your device (without an account) are removed when you delete the app or its data; copies in your phone’s own backup follow that backup’s settings. You can also write to apps@yebalabs.com.

11. Contact us

For privacy questions, account deletion or a rights request, contact:

Yebalabs
Kigali, Rwanda
apps@yebalabs.com

To help us respond, include the Yebalabs product you use and the email address associated with your account. Do not send passwords or one-time codes.