Last updated: November 4, 2026
Sumora is developed by ZonLab. Contact dascaz3000@gmail.com about privacy or data handling. This policy covers the current Android app and optional account service. Older app versions may offer only local records and independent backups.
Your choice of local or account use
Normal finance tracking works without a Sumora account. Local mode stores records on your device; it does not send financial records or saved contacts to Sumora servers. Optional account mode uses Google identity through Firebase Authentication. When you connect account data, saved changes are sent automatically while online and account updates are downloaded to a complete local copy. Offline changes are delivered after reconnection. Sumora-managed account data is stored on servers in Singapore and is readable by Sumora; it is not end-to-end encrypted. Keeping an independent backup remains advisable.
Information handled
Financial data includes fund names, descriptions, amounts, transaction notes, dates, transfers and activity history. Account data includes Google/Firebase account identifiers, name, email, account timestamps and ordinary app preferences. Device sessions include installation/session identifiers, device/app information, last contact, acknowledgments, and security/revocation information. These support authentication, delivery, device management and troubleshooting.
Contacts saved in Sumora can include selected names, photos, phone numbers, email addresses and links to individual financial records. Sumora uses the Android contact picker and does not import the whole address book. On affected Android versions, the optional Contacts permission enables selected details/photos; refusing it leaves available manual/name-based alternatives. Phone contact edits or deletion do not update the saved Sumora copy. Contact data can be included in independent backups; sending it to the account service requires the separate contact-upload agreement.
Backups, restore and sharing
Manual backups contain a complete portable data copy and are encrypted with your chosen password before export through Android. Sumora cannot recover that password. Optional Google Drive backups are sent to the selected Google account, which can differ from the Sumora account. Drive backups have no separate Sumora password. Up to seven app-created automatic files are retained; Android controls when background work runs. Google governs Drive storage and access.
Restoring a backup replaces device data after confirmation and preserves the current Sumora login and Drive connection. If signed in, the app asks before importing restored data into the account; it does not upload the restored copy automatically. Backups exclude account credentials and device session bindings. You choose the destination for manual exports and shared diagnostic files.
Diagnostics and service providers
The app keeps a sanitized local troubleshooting log. Settings → Diagnostics lets you export that log or a data-integrity check; the integrity check excludes amounts and notes. Review files before sharing them. Separately, Sentry receives automatic minimized crash/error and app-stability information, including app/OS version, error stacks and technical workflow context. Production configuration disables performance tracing, session replay and default personal-information sending; application filtering removes account identity, request data, arbitrary context and sensitive text patterns. Diagnostic reporting does not require choosing account mode. Sentry is configured to scrub sensitive data and prevent storing IP addresses in new events. Network providers necessarily process connection information such as IP addresses to deliver requests.
Google provides sign-in, Firebase identity and optional Drive storage; AWS hosts the account service; Sentry provides error monitoring. These providers process information to deliver those services. Sumora does not sell data, display advertising, or use financial records for advertising. Error monitoring and operational service metrics are distinct from advertising or behavioral profiling.
Retention and deletion
Local records remain until you delete them, clear device data or remove the app. Signing out keeps a local copy. While signed out, clearing data affects that device. While signed in, account-wide clear uses the reported clear-time cutoff: edits reported newer can survive, including from a device that reconnects later. Device-reported edit times and server receipt times are distinct; reported history is not independently verified.
Delete a Sumora account in Settings → Account → Delete Sumora account, or use the authenticated web deletion page. Google verification and explicit confirmation are required. Account deletion erases the Firebase identity for this Sumora service and its managed account data, financial/contact graph, history and sessions without a recovery period. Linked clients erase their local copy after receiving the deletion. Offline devices may receive it later; already signed-out copies and independent backups remain. This does not delete your Google account or phone address book. Revoking a device session prevents further account access but does not promise erasure of an independent local copy.
Manual and Drive backup files remain under your control until you delete them from their storage location. Disconnecting Drive or deleting the Sumora account does not delete those files. Minimized error reports are not linked to a Sumora login and follow the monitoring service’s configured retention. Contact support with privacy questions about diagnostics; do not send passwords or authentication tokens.
Website and help pages
Help and privacy pages are hosted on the ZonLab WordPress website. Opening them sends the page address and ordinary network/browser information, including an IP address, to the website and its hosting services. In JavaScript-enabled browsers, WordPress/Jetpack site statistics may use page visits, referring pages, browser information and country inferred from the IP address. See Jetpack Stats privacy information. The app’s embedded help viewer disables JavaScript, persistent web storage and third-party cookies; the site’s JavaScript-based statistics do not run in that viewer. Opening a page in an external browser uses that browser’s own settings. Website hosting and traffic information are separate from financial account records.
Security and your controls
Account requests use HTTPS, verified Google identity, per-install signing sessions, ownership validation and replay protection. Installation keys do not prove that a device, firmware or client is unmodified. Protect your device and Google account. No storage or transmission method is completely secure. Use Account to manage sessions, Contacts to manage saved copies, and Backup and restore for independent files. Changes to this policy will be published here with an updated date.