Notifications Documentation
In-app, email, and push notification preferences, delivery limits, privacy, and troubleshooting.
Audience: Users configuring household, Split, reminder, and security alerts. · 4-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
Notifications bring attention to product events without replacing the underlying ledger, due date, or security screen.
- Choose relevant channels
- Control non-essential noise
- Keep critical account channels available
Channels
- In-app activity
- Email where supported
- Mobile push on registered devices
- Client-specific presentation
Preferences and scope
Preferences form a matrix: each notification kind can be switched on or off per channel (email and push) independently. Household permissions still determine whether the underlying item is visible.
- Kinds include budget warning and exceeded, spending spikes, the monthly summary, payable and calendar reminders, chat mentions and messages, calls, Split activity, broadcast alerts, recurring-expense approval prompts, and login-detected alerts.
- A notification history lets you review what was sent and when.
- A test-send checks a channel end to end before you rely on it.
Delivery and deduplication
Network, provider, device, mailbox, operating-system, and suppression conditions can delay or prevent delivery.
With more than one AccountHouse-family app installed on the same handset, routing delivers each alert to exactly one best app rather than duplicating it across all of them. Security notices are the deliberate exception: they reach every installed app.
Do not rely on alerts alone
Open AccountHouse and authoritative external accounts for deadlines, payments, and security review.
Privacy on lock screens
- Use private preview settings.
- Avoid sensitive details in notes that may enter alerts.
- Protect registered devices.
- Review shared email access.
Troubleshooting
Push is missing
- Confirm in-product preference.
- Confirm OS permission.
- Check network and battery restrictions.
- Refresh device registration.
- Inspect the in-app event.
The event and channel configuration are checked separately.
Security messages
Some security or service messages may be handled differently from optional product notifications. Exact internal triggering and suppression thresholds are not published.
Delivery concept
Eligible event + enabled channel + reachable destination − delivery failures
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.
- Notification delivery is not guaranteed and previews can expose metadata on shared devices.
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.