English text. A reviewed translation is not yet available for this language.

Privacy policy

Notice date: 2026-09-30. Version: draft-2026-09-30-r2.

Thomas Scheiber is responsible for the personal data processed for between paydays. His postal address and support email appear below. This notice describes TestFlight version 0.1.0, build 1, and identifies services planned for a later public build. In the current build, purchase, advertising and support delivery are disabled.

Your budget entries, settings and recovery checkpoints are stored in the app on your device. The app has no bank connection and does not send your budget database to the publisher. You choose what to enter and can correct your records. Reset clears the active budget after saving a local checkpoint. Removing the app through iOS can remove its local data, but is not a way to erase copies you exported or kept in a device backup.

If you export JSON, CSV or a support message, the file can contain the information you chose to save. A file is also created in the app cache for sharing. The app cannot delete a copy saved to Files, email, another app or an Apple backup. You control those destinations and their sharing and deletion settings. Device backups may contain app data according to your Apple settings.

Widgets use a committed budget snapshot in the app's shared storage on the device. Monetary values are hidden by default; revealing them can make financial information visible on your screen. Optional reminders are scheduled locally. Their text omits names and amounts. You can change widget privacy and reminder choices in Settings.

The saved local copy of a support message remains until you explicitly discard it. Sending or exporting creates additional copies and does not clear the stored local message. It contains your title, description, category and language. You can add a reply email and opt to include the app version and platform. The app does not automatically attach financial records. Details you type yourself can still be personal or financial. An unsent message is no longer restored after 30 days when Support next opens; receipt-backed messages have a separate lifecycle.

If support delivery is enabled in a later build, Cloudflare will process the report for delivery and abuse protection, and GitHub will hold it in a private issue tracker accessible to authorized support operators. Hostinger hosts the support mailbox. Email also passes through your own email provider. The intended purpose is to answer requests, investigate faults and protect the support service. Proposed legal bases are performance of the service contract for support and legitimate interests in resolving faults and preventing abuse. Optional diagnostics are proposed on the basis of consent. Sending will remain optional and will not be required for budgeting.

The planned relay uses opaque receipt identifiers, secret hashes and keyed network hashes to limit abuse. Its proposed receipt period is 90 days. The intended tracker cleanup removes visible personal text after 90 days from issue closure or following a verified deletion request. Unresolved delivery or deletion may require longer, reviewed follow-up. These periods describe the planned service, not a verified live deletion guarantee. Mailbox retention, provider logs, backups and edit history need a separate final notice before support is enabled. Removing visible issue text does not establish erasure from every provider copy.

If purchases are enabled, Apple will handle App Store payment and refund processing. RevenueCat will process purchase history and an app user identifier to check and restore Plus access. The publisher will not receive your card details. If Free-tier ads are enabled, Google AdMob and its consent tools may process identifiers, approximate location derived from IP, ad interactions and diagnostic data. Applicable consent choices must appear before advertising starts. Budget records will not be attached to those services. The final public notice will identify the enabled services, their lawful bases, retention and international transfer safeguards before they start processing.

The planned support database is in Cloudflare's EU jurisdiction, but that alone does not establish that all processing stays in the EU. GitHub, RevenueCat, Google, mailbox services and their subprocessors may involve processing outside the EEA. No claim of EU-only processing is made. The final release notice must describe the actual provider arrangements.

Where applicable, you can request access, correction, deletion, restriction or portability, and object to processing based on legitimate interests. You can withdraw consent without affecting earlier lawful processing. Contact the publisher below. The publisher cannot change records held only on your device or erase another provider's independently controlled records. You can complain to a competent supervisory authority, including the Austrian Datenschutzbehörde, Barichgasse 40-42, 1030 Wien, dsb@dsb.gv.at, or the authority where you live or work.

Publisher contact

Thomas Scheiber
Universumstrasse 50, 1200 Wien, Austria
support@thomasscheiber.com