Nummo Logo Nummo
Specification • Zero-Data-Collection Standard • Updated August 29, 2026

Privacy Policy & Security Specification

Nummo is an offline personal finance ledger engineered on a strict zero-ingestion premise: your financial transactions, balance sheets, categories, and cryptographic credentials reside exclusively in your physical device memory.

01. Core Architecture & Privacy Philosophy

Nummo ("the Software", "the App", or "the Service"), engineered and published by K Rajtilak, is an autonomous, standalone personal accounting ledger and mathematical budget tool.

Traditional personal finance applications frequently mandate remote account creation, scrape device SMS inboxes, harvest contact books, connect directly to open-banking APIs, or continuously upload ledgers to multi-tenant cloud databases. Nummo rejects this paradigm entirely. It operates as a closed-circuit, client-side offline appliance.

Architectural Guarantee: Nummo does not maintain backend servers, cloud databases, user authentication pipelines, or analytics endpoints. We do not possess the technical means to collect, view, decrypt, monetize, or transmit your financial ledger.

02. Data Classification Matrix

Classification Data Attributes Collection Status Storage Boundary Network Egress
Personal Identifiers (PII) Name, email, phone number, address, IMEI Not Collected None (Never requested) 0 Bytes
Financial Transactions Credits, debits, notes, timestamps, categories, balances Local Only Internal sandbox (EncryptedSharedPreferences) 0 Bytes
Banking / Cards Bank account numbers, cards, UPI IDs, PINs, OTP codes Never Accessed None (No banking integration) 0 Bytes
SMS / Messages SMS messages, notifications, call history, contacts Prohibited None (Permissions rejected) 0 Bytes
Biometrics & PIN 4-digit PIN hash, biometric authentication state Local Only Hardware Keystore / Titan Security Module 0 Bytes
Analytics & Tracking Crash dumps, telemetry, ad IDs, session traces Not Collected None (Zero tracking SDKs) 0 Bytes

03. On-Device Storage & Cryptography

04. Permissions Audit

Permission Identifier API Scope Technical Justification
USE_BIOMETRIC / USE_FINGERPRINT Hardware Authentication Invokes native biometric unlock dialog if App Lock is enabled.
Storage Access Framework (SAF) System File Broker Exports or imports local backup files chosen by the user.

Prohibited Permissions

Nummo omits all invasive permissions: READ_SMS, RECEIVE_SMS, READ_CONTACTS, READ_CALL_LOG, ACCESS_FINE_LOCATION, CAMERA, RECORD_AUDIO, and Advertising ID tracking.

05. Google Play Financial Disclosures

06. Statutory Frameworks

07. Data Lifecycle & Erasure

  1. In-App Purge: Execute a complete, irreversible wipe of all records via Settings → Danger Zone → Reset All Local Data.
  2. OS Storage Reset: Clear data anytime via Android Settings → Apps → Nummo → Storage → Clear Data.
  3. Uninstall: Deleting the app instantly destroys the local sandbox and all stored records.

08. Engineering Attestation & Contact

I, K Rajtilak, engineer and creator of Nummo, attest that this Privacy Policy accurately represents the architectural operation of the Nummo application.