Mobile App Documentation
Android companion setup, permissions, sync, push, app lock, DocuVault, and lost-device response.
Audience: AccountHouse users working from supported mobile devices. · 5-page PDF · v6.26.1
How to read this document
Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.
- Point lists call out operator-visible behaviour.
- Callouts mark warnings, limitations, or important qualifications.
- Worked examples use round numbers so you can reproduce the arithmetic by hand.
Purpose
The mobile app provides authenticated access to household and Split workflows using the same account and permission model as the web experience.
- Capture expenses
- Use Split and reminders
- Receive push notifications
- Access protected documents where permitted
Installation and sign-in
- Install only from an official distribution path.
- Keep the app and operating system current.
- Verify the intended account and household.
- Configure 2FA and recovery channels.
Device permissions
Grant only permissions needed for selected features. Notification, biometric, camera, and storage behavior depends on platform controls.
Sync and offline expectations
Network availability and server state affect freshness. Confirm that a save completed before relying on another client.
Visible state concept
Authorized server state + completed sync + local presentation
App and device security
- Use device lock.
- Enable supported app lock or biometrics.
- Do not share an unlocked device.
- Review downloaded files.
- Revoke lost-device sessions.
Push notifications
Push is a convenience channel and can be delayed or hidden by operating-system policy.
Open the source
Verify payment, Split, reminder, and security details inside the official app.
Lost-device response
Phone is lost
- Use another trusted client.
- Revoke the mobile session.
- Change credentials if exposure is possible.
- Secure email and mobile accounts.
- Review recent activity.
The account is contained even when the device cannot be recovered.
Troubleshooting
- Check network.
- Refresh authentication.
- Review permissions.
- Update the app.
- Confirm household role.
- Contact official support with non-secret diagnostics.
Privacy, advice limits, and what we do not publish
AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.
- Household data is scoped to your household; other families cannot see your ledger.
- Public documentation explains product behaviour and calculation concepts, not proprietary internals.
- Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
- Mobile security depends partly on device integrity, operating-system updates, and user handling.
Intellectual property boundary
This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.