Privacy Policy

Our privacy commitments

• The mooola app has no user account or login and does not ask who you are.
• We do not collect or receive your bank statements, transactions, credentials, or other banking data.
• The app does not contain the Meta Pixel, X Pixel, Google tag, an advertising identifier, or any other advertising-tracking integration.
• The Google tag uses consent mode only on this website. Advertising storage, advertising user data, advertising personalisation, and analytics storage are denied by default. The website loads the Meta and X pixels and grants Google advertising consent only when you select Enable for optional cookies.
• Separate, limited app activity and sanitised diagnostics are off by default and reach us only when you choose to share them for development, support, and reliability. They do not include your identity or banking data.

Banking and app data stay on your device

Bank statements are imported and processed locally on your device. Statements, transactions, merchant descriptions, dates, amounts, balances, account details, categories, notes, and insights are stored in the app’s local database. mooola does not collect, receive, upload, store, or log your statements, transaction records, or the financial information produced from them. The app’s limited merchant-logo requests and platform-controlled device backups are described separately below.

The app does not ask for your online banking username, password, or other banking credentials. There is no mooola account, login, or cloud-sync service, and we cannot view, recover, or remotely access the banking data stored in the app.

The app does not tell us who you are

Ordinary use of the app does not provide mooola with your name, email address, phone number, account identity, advertising identifier, or persistent device identifier. Because there is no mooola account or login, we cannot connect the financial records on your device to a person or see who uses the app.

We may know who you are only if you deliberately identify yourself when contacting us, include identifying information in feedback, or previously submitted the separate website form for Android beta access. Those cases do not give us access to the banking data stored in the app.

No advertising use of app or banking data

We do not receive your banking data, so we cannot sell, rent, share, advertise against, or build a profile from it. We do not sell or rent the limited personal information that may reach us through deliberate support contact or a past beta request. App activity and diagnostics are not used to serve, personalise, or measure advertising or to profile you or your finances. The only advertising tracking used by mooola is the consent-based Meta Pixel and X Pixel and the consent-managed Google tag on this website; those technologies are not included in the app.

Optional basic development activity

Basic app activity sharing is off by default. If you explicitly enable it during setup or under Settings → Share basic app activity, mooola sends the event time, app version and build, and whether the platform is iOS or Android when the installation is first observed after you opt in. After a successful statement import, mooola sends the event time, selected bank, whether the import came from the document picker or sharing flow, app version and build, and platform.

These events do not include a name, email address, account or device identifier, advertising identifier, precise device model, filename, statement file or contents, transaction count, merchant description, date, amount, balance, account details, category, note, or banking credentials. No persistent identifier is included, so the events do not tell us who used the app and cannot be assembled into a history for a person or app installation.

We use this limited information only for development analytics and debugging: to understand whether new releases are being installed, confirm supported imports are working, prioritise development, and investigate reliability trends. It is never shared with Meta, X, or Google Ads or used for advertising. You can turn it off at any time in Settings. Turning it off stops new events and removes any unsent events still queued on your device; it cannot withdraw an event already sent.

We use service providers to receive, store, secure, and notify us about these events. Those providers may process ordinary network information, such as an IP address, to deliver and protect the service, but mooola does not add it to the activity event or use it to identify you. We restrict access to the developer and retain the events only for as long as reasonably necessary for the development purposes above.

Past Android beta requests

The Android beta access form is no longer available. If you previously used it, we received the full name, Google Play email address, and optional message you submitted.

We used that information only to add testers, manage beta access, provide related support, and contact participants. We retain our copy only until it is no longer needed for those purposes, unless a longer period is required by law. You may ask us to delete it sooner.

FormSubmit processed the website form on our behalf, forwarded submissions to us, and states that it retains form submissions for 30 days. Our email provider and Google handled the information needed to deliver the message and administer the beta under their own privacy terms.

Merchant logos and external requests

The app may download public merchant logos from Logo.dev. For an automatic match, the public brand or domain requested may be derived locally from a merchant description in your transaction data. The request therefore reveals the matched brand or domain, together with technical request information such as an IP address that is normally visible to an internet service. It does not include the original merchant description, statement file, transaction record, date, amount, balance, account details, or banking credentials.

Optional import diagnostics and feedback

The separate Help improve imports setting is off by default. If you explicitly enable it, the app automatically sends a sanitised report when an import fails. A report may include the app and build version, device platform and operating-system version, selected bank, import source and stage, error type, developer stack trace, parser version, bounded document measurements, and structural fingerprints. Local file paths, long numbers, account-number references, and unrecognised error messages are redacted.

If automatic reporting is off, a failed import may instead offer Send failure logs. The app shows the report disclosure first and sends that one sanitised report only if you accept. This does not enable automatic reporting for future failures.

The website’s local statement converter may similarly offer Help improve after a supported conversion failure. The report is created locally, shown to you on request, and sent only after you explicitly accept for that one failure and complete the anti-abuse security check. It does not enable future reporting.

Import diagnostics do not include your identity, an account or persistent device identifier, the statement file, raw statement text, filenames, transaction descriptions, merchant names, dates, amounts, balances, account or card numbers, banking credentials, categories, or personal notes. You can disable app reporting separately in Settings at any time.

If you deliberately submit in-app feedback, we receive the message you type together with its time, app version and build, platform, and operating-system version. We know only what you deliberately include in that message, so do not include banking data or other sensitive or identifying information.

Google Play may independently collect Android stability information, including crash and “app not responding” reports, from users who have enabled usage and diagnostics sharing on their device. Google controls that platform-level collection under its own privacy terms and may make technical reports available to app developers through Android vitals.

We use diagnostics and feedback only for development, troubleshooting, support, and improving import reliability. They are never shared with Meta, X, or Google Ads and are not sold, used for advertising, used to identify app users, or used to profile your finances. Access is restricted and the information is retained only for as long as reasonably necessary for those purposes.

Device storage, backups, and deletion

Your active mooola database is kept in the app’s private storage. Uninstalling the app removes that active local database. Your device operating system or backup provider may separately include app data in a device backup if backups are enabled in your device settings. Those backups are controlled by you and the platform provider, not by mooola.

Because mooola does not hold a server copy of your banking data, we cannot restore it if your local data is deleted or your device is lost.

Website advertising measurement and third-party services

The Meta Pixel, X Pixel, and Google tag are the only advertising-tracking technologies used by mooola. They exist only on this website and are never loaded by or connected to the mooola app. Website tracking does not enable app tracking or give these technologies access to anything stored in the app.

The Google tag loads when this website opens using Google Consent Mode. Before you make a choice, or if you select Disable, advertising storage, advertising user data, advertising personalisation, and analytics storage are set to denied. In this state Google does not use advertising or analytics cookies but receives limited cookieless consent-status and measurement signals. Those signals may include the consent state, page and event information, time, browser or device information, and ordinary technical request information such as an IP address.

If you select Enable, the website grants those Google consent settings and loads the Meta and X pixels. Meta, X, and Google Ads then receive website page views for advertising measurement. Meta also receives a content-view event on selected public product pages, a download-intent event when you select a mooola Google Play, App Store, or automatic download link, and a contact event when you select the mooola contact email link. X receives its own event when you select one of those download links. The Google tag is configured for advertising measurement and to create website audiences; mooola does not send it separate download-intent or contact events.

When optional cookies are enabled, ordinary browser and network information can include the page URL and title, referring page, time, browser and device information, IP address, advertising or cookie identifiers, and an advertising click identifier when one is present. Meta, X, and Google may use this information to attribute and measure advertisements, create website audiences, optimise advertising, and provide their services under their own policies.

A download-intent event records the selection of a store link, not whether the app was installed or used. A contact event records only that the link was selected, not the content of any message or the sender’s email address. These advertising technologies do not receive bank credentials, statement files, statement text, imported transactions, merchant descriptions, amounts, balances, categories, notes, app activity, or app diagnostics from mooola. We do not send Meta, X, or Google Ads names, email addresses, phone numbers, or banking information for advertising matching.

We store your choice in your browser so that the website can remember it. You can change it using Tracking choices in the website footer. Selecting Disable prevents Meta and X from loading on future page loads and returns Google’s consent settings to denied. You can also clear existing identifiers using your browser controls and manage advertising choices through Meta’s Privacy Policy, Meta’s Cookies Policy, X’s Privacy Policy, Google’s Privacy Policy, and Google’s advertising information.

Website hosting, content-delivery, and anti-abuse providers may separately process ordinary technical request data, such as an IP address, browser type, and request time, to deliver and secure the website and verify a failure-report security challenge. This operational processing is separate from advertising tracking. mooola does not add that address to a sanitised failure report. If you follow a link to Google Play, Facebook, LinkedIn, Discord, X, or another third-party service, that service’s own privacy policy applies.

Optional website acquisition analytics

When Google Analytics is configured for this website, it starts only after you select Enable for optional cookies. We use it to understand which public pages bring visitors to mooola, which product pages they visit, whether a browser conversion produces a CSV, and whether they select an app download link. These website analytics events are sent to Google Analytics, not to the Google Ads destination. Google signals and advertising personalisation are disabled for this analytics configuration.

Events include the public page path, page title, referring website host, and the first page observed in the consented session. Download-intent events also include the link placement and destination store or automatic download route. We omit URL query strings and fragments from the page and referrer values we send. A conversion-completion event says only that the batch produced at least one CSV: it contains no filenames, passwords, statement contents, transaction counts, amounts, balances or error reports.

After consent, the first observed page and referring website host are kept in browser session storage to connect website visits with download intent. This attribution expires after 30 minutes of inactivity and is removed when you disable optional cookies. Meta download-intent events also include this page and referral context. A store-link click does not establish an app installation. App activity and app diagnostics remain separate from website analytics.

When information may be disclosed

We may disclose the limited support or diagnostic information we hold when required by law, a valid legal process, or when reasonably necessary to protect the rights, safety, and security of mooola, our users, or others. We cannot disclose banking data that we do not receive or control.

Your choices and rights

You may ask whether we hold information about you and request that it be corrected or deleted by emailing contact@mooola.co.za. You may enable or disable optional website cookies and change that choice later through Tracking choices in the website footer. Because basic app activity events do not contain an account or persistent identifier, we may not be able to connect a particular event to you. Meta, X, and Google handle requests concerning information they control under their own privacy processes. We may need to verify a request before acting on it. You may also contact South Africa’s Information Regulator if you have a concern about how your personal information is handled.

Changes to this policy

We may amend, add to, or replace this Privacy Policy from time to time as mooola, our practices, or legal requirements change. The updated policy will be posted on this page with a revised “Last updated” date. Where reasonably practicable, we will provide additional notice before a material change takes effect. Changes do not allow us to use information collected under an earlier version in a materially different way without any notice or consent required by applicable law.

Contact

For privacy questions, requests, or complaints, contact us at contact@mooola.co.za.