Privacy in Lommepenge.
This page describes the currently verified Lommepenge development implementation. The app is not publicly released, and its deletion controls, release configuration and any future commercial model must be reviewed before use with real families.
A development privacy notice based on the current code.
This notice describes the current iPhone and iPad development implementation of Lommepenge, published by Steffen Aspe under the SABONEX brand. References to SABONEX mean Steffen Aspe operating under that brand.
Lommepenge is a local family allowance ledger. The verified build lets a family create child profiles, record allowance events and payouts, manage one-off and recurring chores, approve or reverse chore rewards, and configure a fixed weekly allowance.
The app is not publicly released. A savings-goal feature, including a possible local goal image, has been planned but is not implemented in the verified build and is therefore not current data handling. This page must be reviewed when that or any other new feature is implemented.
Visits to this page and the rest of the SABONEX website are covered separately by the SABONEX website privacy notice.
The family enters and creates the information used by the ledger.
The current local data model can store:
- Child profiles: a profile name, a selected colour, a selected avatar and technical identifiers and timestamps used by the app.
- Allowance history: positive and negative amounts in Danish øre, event type, the related child identifier and the time the event was recorded. The displayed balance is calculated from these entries rather than stored as a separate balance.
- Chores: title, reward amount, status and timestamps for creation, completion, approval, reversal or expiry, together with technical links to related ledger events.
- Recurring chore rules: title, reward, daily or weekly frequency, status and the child to whom the rule belongs.
- Fixed weekly allowance: the configured amount, rule status and audit records showing which child and ISO week received a ledger entry.
The current implementation does not ask for a child's date of birth, address, contact details, school, bank information or payment-card details. It does not collect a goal photo because the savings-goal feature is not implemented.
Information is used to show and maintain the family's allowance ledger.
Profile information distinguishes the children in the family's local app. Ledger events are used to calculate balances and show history. Chore information supports creation, completion, approval and reversal of rewards. Recurring chore and weekly allowance rules are used to create the relevant current-period entries without paying the same child and period twice.
The current app does not use this information to build advertising profiles, score children, compare families or decide whether real money should be transferred. It does not provide a SABONEX-hosted account or remote family dashboard.
Data is stored in the app's local SwiftData store on each device.
The verified implementation uses Apple's SwiftData technology to persist the family ledger in the app's local iOS or iPadOS container. There is no SABONEX backend, account, cloud sync, iCloud entitlement or cross-device synchronization in the current build. Data on one device is therefore not automatically copied to another device by Lommepenge.
SABONEX cannot view, retrieve or change the local ledger through a server. Access depends on physical or system-level access to the device and the operating system's app sandbox and device security. The current build does not provide its own PIN, Face ID or Touch ID lock and does not claim additional app-specific encryption beyond the protections supplied by the operating system.
A shared family iPad or an unlocked parent's device may therefore expose the displayed ledger to people who can open the app. Families should use the device controls that fit their situation and avoid entering information that is not needed for the allowance purpose.
Lommepenge records amounts; it does not move money.
The app stores values in Danish kroner and øre as a family ledger. It does not connect to a bank account, payment card or MobilePay, and it does not transfer, hold or pay out real money.
When the family records a payout, bonus, chore reward or weekly allowance, the app changes its local ledger only. Any real-world payment remains a separate action carried out by the family outside Lommepenge.
No advertising, analytics or third-party SDK in the verified implementation.
The current app has no networking, backend, account login, advertising SDK, analytics SDK, behavioural tracking, StoreKit purchase flow, notifications, widget, App Group or third-party dependency.
Because the verified app does not transmit its family ledger to SABONEX or another app service, there is no current app-service provider receiving that ledger. Apple and the device operating system provide the app platform and local storage technology under their own terms.
The local ledger remains on the device until it is changed or removed there.
The current build retains profiles, ledger entries, chores, recurring rules and weekly allowance audit records in its local SwiftData store so the family can keep history across app launches. Some financial history is deliberately append-only: for example, reversing an approved chore adds a correcting event instead of silently deleting the original event.
The verified build does not yet provide child-profile deletion or a complete in-app “delete all data” action. It also has no remote deletion path because there is no SABONEX account or server copy. Deletion and retention controls must be reviewed and completed before a public release or use with real family data.
SABONEX cannot erase the local ledger remotely. Users testing the development build should avoid real or sensitive family information and manage the test app and its local data directly on the test device.
Local app data and information voluntarily sent to SABONEX are separate.
If a person contacts info@sabonex.com, SABONEX may process the information they choose to include, such as name, email address, message content and attachments, to answer the enquiry, troubleshoot the development build and retain necessary follow-up or documentation. Depending on the context, that processing may rely on legitimate interests, steps requested by the person, an agreement or a legal obligation.
Do not send screenshots, exports or descriptions containing children's names, allowance history or other family information unless it is necessary for the support request. The current app has no automatic support upload.
Where privacy law applies, a person may have rights such as access, correction, deletion, restriction, objection and, in some cases, data portability in relation to personal data that Steffen Aspe/SABONEX actually holds. SABONEX cannot access the device-only ledger through a server. Privacy requests can be sent to info@sabonex.com. A complaint may also be made to the competent data protection authority; in Denmark, this is Datatilsynet.
This notice follows the implementation.
The page must be reviewed when Lommepenge adds savings goals or images, deletion controls, accounts, sync, networking, notifications, widgets, purchases, analytics or any other material data flow. Planned ideas are not described here as current processing.
The authoritative public version of this notice is available at https://sabonex.com/apps/lommepenge/privacy/.