Monee privacy & your data

Your ledger stays with you.

How Monee handles your information. Features and defaults depend on your installed version, as described below.

Updated 18 November 2026

Settings in version 1.0.10 and later

When no choice has been saved, supported app preferences start on: app analytics, private cloud sync, Android M-Pesa capture and quick capture, widget amount visibility, bill reminders, and comeback, weekly check-in and unfinished-setup reminders. An existing saved off choice stays off. You can change these preferences in Settings. A default preference does not grant a phone permission, connect a provider account or confirm an unfinished setup. SMS access, display over other apps, notification permission and cloud-provider access remain under your control.

If you add a Home Screen widget, amounts can be visible when its amount preference is on. Turn Show amounts on widgets off to hide them. A saved hidden choice is preserved, and an unreadable widget preference keeps amounts hidden. Bill reminders also need notification permission from your phone.

Setup-answer sharing has a separate final submission action, explained below. A preselected switch does not by itself authorize an answer upload. Skipping onboarding sends no setup answers and does not enable the separate legacy setup-activity stream.

Your financial records

Transactions, amounts, categories, merchant details, notes, budgets and imported messages are stored on your device. Monee does not automatically upload your Personal ledger to its account service. Records you explicitly add to a shared account are handled separately below. Records remain until you remove them or remove the app's local storage. Optional cloud sync is separate from Monee sign-in and is described below.

Optional cloud sync

Starting with iOS 1.0.2 (6), cloud sync is on by default. You can turn it off in Settings; an existing off choice stays off on upgrade or sign-in. Earlier releases require you to enable sync. Availability depends on your installed store or testing build. When sync is on and provider access is available, Monee stores parsed transactions and budgets in your private iCloud storage on iPhone and iPad, or Monee's hidden Google Drive app-data folder on cloud-enabled Android builds. This includes amounts, merchants, fees, balances, categories, notes, transaction references and dates. Raw SMS messages, Monee sign-in sessions and measurement preferences are not included. Personal cloud-sync records do not go to Monee's account backend. Explicitly shared records are handled separately, as described below.

Sync works with or without a Monee account. Signing up or signing out keeps the active ledger and its existing cloud connection. Google Drive authorization is separate from Monee sign-in and is limited to Monee's own app-data folder, not your other Drive files. Google may require account selection and permission before syncing; Monee does not open permission prompts in the background. Your cloud-provider identifier and, on Android, the selected account's email stay locally to keep the connection tied to the same cloud account.

Use the same cloud account on each device. With automatic sync enabled, opening Monee checks for and merges saved records, including after reinstall, before uploading changes. iCloud syncs between Apple devices and Google Drive between Android devices; the two services do not sync with each other. Edits and deletions sync too. Concurrent edits converge to one version, not a recoverable version history.

Apple or Google processes and stores cloud copies under its own policies and storage limits. Monee does not claim application-level end-to-end encryption. Sync runs after changes and when Monee opens, with morning and evening background opportunities. Your operating system controls background timing; connectivity, battery restrictions and force-quitting can delay it. Reopen Monee after force-quitting to resume. Check the last successful sync before changing devices and keep an Excel export as a separate readable copy.

Optional sign-in

You can use the core app without an account. If you choose Apple or Google sign-in, the provider verifies your identity. Monee's account backend, hosted by Convex, stores a keyed hash of the provider's account identifier, rather than an automatically collected name, email or photograph. Names you choose for shared membership are stored separately, as described below. This identifier still represents an account; it is not anonymous.

The app keeps a session token in secure device storage. The backend stores a hash of it, with a 30-day session expiry. Signing out revokes the current session. On this phone, sign-in links your guest ledger to your account. Signing out keeps the active ledger available offline; different accounts use separate local ledgers. Monee sign-in is not required for cloud sync or restoring financial records.

Google sign-in can include your name, email address and profile-image URL in its authentication response. Monee processes that response temporarily to complete verification; it does not save those profile fields in its account database or download the profile photograph. The stored account identifier and session hashes support account access and security, not advertising. Choosing guest mode avoids this optional account collection.

Messages and permissions

On iPhone, Monee processes messages you explicitly paste or share, and selected new text forwarded by a Shortcuts automation you configure as described below. Monee cannot browse the SMS inbox or history. On Android, the M-Pesa capture preference starts on in version 1.0.10 and later when no choice has been saved; an existing off choice is preserved. Capture still requires SMS permission from your phone. After you grant SMS access, Monee imports today's supported confirmations into Uncategorized once and recognises new incoming confirmations locally. Older messages are read only through the separate, optional history import. Notifications require a separate permission. Raw SMS messages are not uploaded to Monee's servers. You can revoke permissions in your phone's settings.

Optional iPhone message automation

In iOS testing builds from 1.0.3 (11), on iOS 17.2 or later, you can add a prepared Monee shortcut and configure an Apple Shortcuts Message automation to pass selected incoming text to Monee's Capture M-Pesa message action. This does not give Monee access to your SMS inbox or message history. You choose the matching rule and whether the automation runs immediately in Shortcuts.

Monee checks text delivery after a supported M-Pesa confirmation has been parsed and saved on this device. An optional device-specific setup test can also check delivery without creating a payment. The app cannot inspect your saved automation or detect whether you later disable or delete it. A successful connection test does not promise every future message will arrive.

Only supported M-Pesa confirmations are imported. Raw matching text is kept in a protected, device-local queue excluded from backup, then removed after a successful ledger import. Parsed records enter your Personal ledger and follow your existing private cloud-sync and reporting choices. Shared accounts receive nothing automatically. In builds that offer Record in, you can explicitly select a shared account while reviewing an eligible captured payment; only the reviewed fields are shared, and an ignored private source record prevents replay in Personal. Setup and test receipts remain on this device.

Set up later continues onboarding without enabling capture. You can return through Settings > Automatic M-Pesa messages. Pause capture in Monee to stop new captures, or remove or disable the automation in Shortcuts. Pausing keeps already captured messages and saved records. Shortcuts availability, a device restart before its first unlock, force-stopping, storage and system restrictions can delay or prevent capture.

Optional Android quick capture

Quick capture starts on in version 1.0.10 and later when no choice has been saved; an existing off choice is preserved. Earlier versions start off. Only when M-Pesa capture is enabled and Android's Display over other apps permission is granted, a new supported M-Pesa confirmation can show its amount, merchant and category choices over the app you are using. Monee does not inspect that other app. Select a category and tap Save to keep the choice locally, or dismiss the sheet and review the message later in Monee. The sheet is not shown while the phone is locked and closes when the screen turns off. Turn quick capture off in Monee Settings or revoke its display permission in Android Settings. The raw-message queue stays on the device. Parsed Personal transactions and their categories are included when private cloud sync is on. In builds that offer Shared account in quick capture, choosing it opens Monee for account selection and an explicit Save; the overlay never writes shared financial records. Only the fields you confirm in Monee are sent to that shared account, as described below.

Shared accounts

In supported testing builds, you can create or join a shared account with up to three people including its owner. Each person signs in separately. Joining or creating does not upload your Personal ledger. You explicitly choose contributions, expenses or individual personal records to add.

Monee stores the account name, chosen member display names, membership and invitation status, and shared amounts, fees, dates, categories, descriptions, notes and budgets in its Convex service. These records are linked to members' Monee identities. All approved members can see and export the full shared history, including records created before they joined. New members require the owner's approval. Monee records money; it does not hold or transfer it.

Invitations expire after seven days and can be revoked. Invitation tokens are stored as hashes. The web invitation page reads a code from the URL fragment on your device; it does not send that code or financial records to the website or analytics. Do not forward an invitation to someone you do not intend to join.

Shared records are separate from Personal cloud sync, Home Screen widgets and combined usage reporting. In builds that offer Record in, you explicitly choose the account when adding, importing or reviewing a payment. Automatic capture never chooses a shared account just because it is open. Choosing Shared account in Android quick capture or the iOS share sheet asks you to complete account selection and Save in Monee. Only the reviewed amount, fee, date, category and any note or description you enter are shared; raw messages, references, balances and phone numbers remain private. After a successful shared save, an ignored parsed source record stays in private Personal storage for replay protection, excluded from Personal totals. An already categorized Personal record is kept when you explicitly copy it. Unsaved forms can be kept as device-local drafts. Shared records already loaded may stay visible offline until the app reconnects or the session expires. Signing out clears shared drafts and cached records on that device.

Leaving or removal stops future access but preserves accepted entries for the remaining members. Identity deletion removes the membership's account link and replaces its display name with Former member; accepted entries, descriptions and notes remain, so avoid adding unnecessary personal details. Owners must transfer ownership or close the account before deleting their identity. A closed account is read-only for 30 days, then queued for deletion from the live service. Deleting its owner's identity ends that recovery window. Deleted entries and detailed activity are queued for removal after 30 days. Cleanup runs in bounded hourly batches, so large deletions may take additional runs. Exported files, screenshots and offline copies held by members cannot be remotely erased. Provider security logs and backups have separate retention schedules; we do not promise immediate erasure from every backup.

Reports you export

Excel reports are created on your device. They leave it only when you choose a sharing or storage destination. Exported files can contain financial and personal information. The recipient or storage provider controls those copies.

App analytics in version 1.0.8 and later

Monee uses PostHog to understand first opens, onboarding progress, automatic capture setup, successful capture, category confirmation, viewing a spending summary and useful return visits. These are bounded event names and choices, not your financial records or questionnaire answers. Events include a random consent-period identifier, event time, platform and app version. We do not attach your Monee account, name, email, phone number, financial amounts, merchant, categories, message text, push token or attribution identifier. Session recording, automatic screen or touch recording and person profiles are disabled. Network providers still process connection information to deliver and secure requests; Monee requests no location enrichment for these analytics events.

App analytics starts on when no saved off choice applies. A saved off choice is preserved. Turn App analytics off in Account & privacy to stop future analytics and discard unsent events. Turning it on again uses a new consent-period identifier and does not backfill earlier activity. The app remains usable without analytics or sign-in. These versions do not upload the older combined financial usage reports described below; earlier installed versions may continue under their own controls. Setup-answer sharing remains separate and requires the final submission action described below; its switch is preselected in version 1.0.10 and later when no saved off choice applies.

The PostHog project is hosted in the United States on its Free plan, with a one-year event retention period. Expired events are removed in batches and may remain longer; provider backups and operational logs follow the provider's schedules. Opting out stops new collection and does not recall data already accepted by a provider. Because these analytics identifiers are not linked to your sign-in account, deleting that account does not automatically locate this separate data. Contact hello@pesastack.co for privacy requests; do not send financial messages. See PostHog privacy and event retention.

Installation and acquisition measurement

On Android, AppsFlyer measures one eligible installation or first launch and available referral information when app analytics is enabled. AppsFlyer processes app and installation identifiers, app and device technical information, timestamps, referral or campaign information and connection information, including IP-derived approximate location. Monee disables advertising-ID collection and does not send financial records, account identifiers, product event streams, revenue or category information to AppsFlyer. Partner postbacks to advertising networks are disabled in this release configuration. Paid advertising is managed separately and cannot be started by opening the app or opting into reminders.

Turning app analytics off stops future Android acquisition work and permanently retires measurement for that installation; turning it back on does not replay the installation. Information already accepted is not removed by this switch. AppsFlyer's raw-data retention depends on the integration, applicable requirements and partner terms; its raw-report access window is different from retention, and aggregate reports may be retained for up to 25 months. See AppsFlyer's service privacy policy and retention information. Privacy requests can be sent to hello@pesastack.co; we do not join attribution records to your financial ledger to identify you.

On iPhone, Monee keeps the AppsFlyer SDK inactive and uses Apple's privacy-limited aggregate installation attribution instead. When app analytics is enabled, Monee can ask the operating system to register a fixed installation-only conversion value of zero. No spending, category, account, budget or engagement values are encoded. Apple controls whether and when delayed, privacy-limited reports reach eligible advertising networks or their reporting providers. Monee does not request IDFA or use a fingerprinting fallback. Switching app analytics off prevents future registration, but cannot recall a report already dispatched by the operating system. Store download totals remain separate aggregate reports.

Optional reminders

In version 1.0.10 and later, comeback reminders, weekly check-ins and unfinished-setup reminder preferences start on when no choice has been saved, with a shared limit of at most weekly. An existing saved off choice stays off. Earlier versions start off. Delivery still requires notification permission from your phone; Monee does not grant that permission or open its permission prompt in the background. A limited rollout means not every eligible installation will receive a reminder immediately. You control the common weekly or monthly frequency limit and quiet hours in Account & privacy. Reminder text is general and contains no financial details.

When reminders are on and notification permission is available, Monee sends a push-routing token, a random installation routing reference, platform and native build version, your reminder preferences (including the saved time zone) and one overwritten genuine last-app-open time to its Convex reminder service. If unfinished-setup reminders are on, Monee also sends whether setup is incomplete, without reasons or answer values. This stream is separate from PostHog, account identity and financial records. It can operate when app analytics is off; the last-open value is then used only to time reminders and is not sent to analytics. Monee does not inspect other apps, phone usage, Wi-Fi networks or your location to choose reminder times.

Expo routes notifications through Apple Push Notification service or Firebase Cloud Messaging. These providers process routing tokens, notification contents and delivery information. Routing subscriptions have a 180-day lease renewed by genuine app activity; delivery records expire after seven days and are removed by periodic cleanup. After reminders are turned off, a token-hash frequency guard and last submission time has a 30-day expiry to enforce the shared cap and is removed by periodic cleanup. A token-hash marker can remain without a configured expiry after an unfinished-setup reminder has been sent, so it is not sent again. Other hashed retired-token and capability suppression records can also remain without a configured expiry to prevent unintended reuse. These markers do not contain notification content or financial records. Turning reminders off stops local enrollment and requests server removal when connected. Offline changes and messages already handed to the phone's notification service may take time to stop. Quiet hours control submission time; the operating system and network determine eventual delivery and display. See Expo's push privacy explanation.

Optional measurement

When Share combined usage totals is on, Monee sends daily counts and combined KES amounts for payments you track and categorize to our Convex reporting service. Reports are sent after the day ends. We do not send raw SMS, merchants, transaction references, categories, notes, balances, fees or income in these reports. Enabling reporting does not backfill your existing transaction history. Financial reports contain a random retry receipt and authorization permit, not an account or reporting identifier.

Activity is counted separately when you track and categorize a payment on the same day. Guest-enabled versions generate a random reporting identifier on your device; the backend stores its hash. If you sign in, this identifier is associated with your Monee account so retained daily activity is counted once, including overlapping reports from your signed-in devices. Signing out preserves the identifier and your reporting choice. This identifier is pseudonymous, not anonymous, and is not included in financial reports or private cloud sync. Earlier versions support reporting only after sign-in.

New app updates turn reporting on by default when no choice has been saved. A saved off setting stays off. Earlier versions may start with reporting off. The app works without reporting or an account. Turn it off in Settings > Account & privacy to stop new uploads and clear unsent reports. Account deletion removes linked reporting identifiers. Unlinked identifiers and inactive links expire after 90 days without use; temporary activity and retry receipts expire within 32 days of receipt. Daily combined totals are retained to measure product use and cannot be separated back into individual contributions. Guest devices and reinstalls cannot be recognized as the same person until sign-in; expired activity receipts cannot be retroactively consolidated. Independent devices may contribute overlapping financial totals, so these are self-reported product metrics, not audited financial statistics.

Our public website displays rounded combined counts of payments tracked and categorized, and the combined KES amount tracked, over the previous 30 complete reporting days. The amount is rounded down in KES 10,000 steps. These counters use optional Personal KES usage reports and can include overlapping records from independently used devices; they are not unique-user, download or audited transaction counts. Public counters do not include exact financial amounts, individual records, identities or daily breakdowns. Combined amounts are self-reported recording totals, not money processed by Monee.

We do not use these reports for advertising or cross-app tracking. Aggregation is not a guarantee of anonymity: small totals may reveal information, and hosting providers process network metadata for service operation and security. Private iCloud or Google Drive sync remains separate from this optional reporting.

Service providers and this website

Apple or Google processes sign-in requests, Convex operates the account backend, Cloudflare serves this website and our email provider delivers support messages. These services may process network details, such as IP addresses, request times and security diagnostics, under their own policies. We do not add advertising trackers or analytics scripts to this website.

If you email us, your email address and the information you send are processed to respond to your request. Please do not include unnecessary financial details or full SMS messages.

Deleting your account

Use Settings > Account & privacy > Delete account. The app requires verification through the same provider, revokes the provider grant and removes live account and session records. Deleting an account unlinks this phone's active ledger and keeps its records available without an account. Removal of live account data does not imply immediate removal from service-provider backups or security logs.

Account deletion details

Remove cloud records

Deleting a Monee sign-in account or turning off sync does not erase cloud records. First turn sync off on every connected device, then remove Monee's app data using iCloud storage settings or Google Drive Settings > Manage apps. Remove local app data separately when no longer needed. A device that retains its ledger can upload it again if sync is re-enabled. Exported files and provider backups have separate retention rules.

Your setup answers

Monee saves your onboarding answers and preferences on your device. Sharing them with us is optional. In version 1.0.10 and later, Share setup answers is preselected when no saved off choice applies. You can turn it off before finishing. Selection alone does not authorize or queue an upload. Signing in or using the app does not by itself send answers, and sharing is not required to use Monee's tools. Earlier versions start this selection off.

At the final onboarding step, sending answers requires the clearly labelled Agree and share setup answers action, or Agree and share in the separate confirmation shown before continuing with Apple or Google. These actions send your current selected answers to Monee through our service provider, Convex, to help us improve onboarding. Turning the selection off lets you finish without sharing. Skip setup never submits answers, and no skipped answers are invented. You can also explicitly submit, review or stop sharing later in Settings → Account & privacy → Setup answers.

Answers are fixed choices rather than free text. They can describe your goals, tracking habits, usual payment methods, recording preferences, areas of interest, planning or check-in habits, experience, household arrangement and preferred guidance. If you select them, an income pattern or approximate monthly spending range is included. These are self-reported preferences; they are not verified income, an automatically calculated spending profile or your actual transactions. Skipped choices are not invented or filled from your records.

Setup answers use their own random research key. They are not joined to your Monee sign-in, account session, combined-usage reporting ID, ledger or separate setup-activity key. We do not include your name, email address, raw messages, merchants, phone numbers, account or card credentials, balances, transaction amounts or calculator values in this submission. Our hosting and network providers may process connection metadata needed to operate and protect their services, so a separate research key is not a promise that all network activity is anonymous.

Shared answers expire within 180 days of their last update, and their authorization can expire sooner. They are used to improve Monee's onboarding, not for advertising, tracking across other companies' apps or websites, or selling data.

Separate setup activity

Setup activity is a different sharing choice and is off by default. The required onboarding and the version 1.0.10 preference defaults do not enable this legacy research stream or collect past steps retrospectively. If an older saved choice is already on, only future step names, event types, timing and first-record or return milestones are eligible for that separate stream. It does not contain answer values or financial record details. Raw setup activity expires within 30 days and does not outlive its authorization. An existing activity choice can be stopped in Setup answers.

Change your choice or remove shared setup data

Open Settings → Account & privacy → Setup answers to review your local answers, turn answer sharing off, stop an existing setup-activity choice or choose Remove shared setup data. Removing shared setup data turns off both research choices and requests deletion of the corresponding shared data. Your saved local preferences, completed onboarding, transactions, budgets and account remain intact. This does not reopen onboarding.

Pending uploads and deletion requests are stored locally and retried when Monee is active, when you return to it or after relaunching with a connection. While disconnected, a deletion can remain pending. A minimal hashed deletion marker prevents a delayed upload from restoring deleted setup data until its authorization expires. Monee does not promise a background retry while iOS has suspended the app.

Questions about your data

Contact the Monee team at hello@pesastack.co. We can help with access, correction or deletion questions. Do not send passwords, PINs or sign-in codes.