Rost Privacy Policy

2026-11-11 · Rost 1.4.3
FructoseLabs · fructoselabs@gmail.com

Local financial data

Publisher: FructoseLabs. Support and privacy: fructoselabs@gmail.com. Financial records, categories, plans, bills, goals, loans and budget currency are stored in the app’s private space on your phone. Calculations, suggestions and notification analysis run locally. No account, bank connection or online AI is used. Budgeting and notification analysis do not send analytics or automatic crash reports. Advertising SDK data is described below. Rost does not read SMS, contacts or photos, request device location permission, or use accessibility services. Internet is used for optional exchange rates and advertising; the budget and payment recognition still work offline.

Optional notifications

Notification features are off by default. Quick entry saves the amount and optional merchant you type in Rost’s own notification and immediately changes the balance. It does not need access to other apps’ notifications. An unknown category can be chosen later without a second deduction. Detection requires explicit agreement in Rost, selected source apps and separate Android notification access. Android grants broad access; Rost checks the source before reading content and ignores unselected apps. The picker shows launcher apps visible to Rost. Nothing is selected automatically. Detection is inactive in demonstration mode and does not monitor NFC itself.

Processing and retained fields

For selected apps, notification titles, ordinary and expanded text, and text lines are combined temporarily on the phone, in bounded background work. Repeated display copies are removed when identifiable. Local rules analyse the surrounding context to distinguish a payment amount from a balance, currency equivalent, fee or other numbers. This is a local context-based analyser, not a generative language model, and it does not use an online AI service. Original notification fields are never saved to files, logged or sent online. Hidden or unsafe content, ineligible transactions and amounts that cannot be determined reliably are ignored. A recognised payment must match the budget currency; Rost does not perform an implicit currency conversion. Identified balances and currency equivalents are not retained. Compatibility with every bank, wording or device is not guaranteed. Rost retains the payment amount, merchant when identifiable, date, category, opaque record identifier, entry origin and, for proposals, a possible-duplicate flag. If the amount can be identified but the merchant cannot, a proposal can be retained with an empty merchant field for manual review; Rost does not invent a merchant.

Review and automatic saving

By default, detected payments are proposals and affect the balance only after confirmation. You can correct a proposal’s amount and explicitly link it to a matching unpaid planned bill. Automatic saving is a separate option, off by default, with its own agreement. It records an expense immediately only for a clearly completed payment, an identifiable merchant whose category you previously confirmed, no possible duplicate and no matching unpaid planned bill. General keyword or history suggestions alone do not qualify. Other recognised payments remain for review; notifications with foreign equivalents and payments without an identifiable merchant remain proposals. Automatically recorded expenses can be edited or deleted in Activity. Your confirmed category creates a local merchant rule only when the merchant is known.

Technical local data

A separate duplicate register stores up to 2,000 SHA-256 identifiers and processing times. Entries older than seven days are pruned on the next use or capture, not by a timer while the app is unused. Opaque identifiers attached to drafts or transactions remain with those records. App selection, feature switches and a random token preventing repeated quick replies are separate preferences. Diagnostics retain only the latest processing status code and its time, without notification text, amount, merchant or source. Listener connection state is transient. Theme and language preferences are local. Quick notification restoration after reboot or an app update uses RECEIVE_BOOT_COMPLETED and the existing enabled setting; this does not enable detection. Android may let you dismiss ongoing notifications.

Currency, backups and protection

Language does not change financial amounts. One currency applies to the whole budget. For an existing budget, a currency change requires a preview and confirmation; all stored financial amounts are converted and rounded to two decimals. The optional online lookup sends only the source and target currency codes to https://api.frankfurter.dev over HTTPS. The provider and its network operators necessarily receive the device’s public IP address and technical request metadata. Rost sends no amounts, merchants, notifications, financial records, account identifier or advertising identifier to the rate service. These are daily reference rates, not guaranteed bank or transaction rates. The rate date is displayed; invalid, future or more than 10-day-old quotes are rejected. No persistent rate history is kept. No connection means an error message and no automatic conversion; manual rate entry remains available. Provider information: https://frankfurter.dev/. Provider-side technical retention is controlled by the provider, not Rost; we cannot promise immediate deletion of its access logs. JSON schema 10 includes financial data, currency, proposals, merchant rules and duplicate identifiers/times. It excludes notification settings, selected apps, diagnostics, Android permissions, theme and language. CSV includes transactions and currency. Android automatic backup is disabled. You choose export destinations; files are plain text, without app-provided encryption. Import replaces financial data after confirmation. Cloud destinations have their own terms. There is no separate app PIN or biometric lock; protection relies on Android and your device. We cannot recover lost data without your backup.

Control and deletion

Stop detection in Settings and revoke access separately in Android. Turning an option off keeps earlier expenses and proposals. Delete a proposal or transaction, or forget explicit merchant choices; history-based suggestions may still apply. Delete all data clears financial records, proposals, merchant rules, duplicate records and diagnostics, disables notification options and clears selected apps. Language and theme may remain. Clearing Android app storage or uninstalling also removes local preferences. Delete exported copies separately.

Support and changes

If you email us, Gmail receives your address, message and attachments; Rost does not send its database automatically. We use correspondence only to resolve your request. After resolution, we delete received messages, replies and attachments from our account and Trash, without a separate archive or downloaded copies. Copies in your account and Google’s temporary retention are outside our control. Contact us to request information or deletion of correspondence. Avoid sending banking details or full backups unnecessarily. We will update this policy and the in-app explanations when data practices change, including before adding synchronisation or other online services.

Advertising and privacy choices

Rost 1.4.3 uses Google Mobile Ads (AdMob) for banner placements on Home, Reports, Monthly plan and Transactions, and Google User Messaging Platform (UMP) for privacy choices. All ad requests use Google’s teen protections, which disable personalized ads and remarketing. Rost does not ask for or store your age. The advertising SDK may collect and share the device’s IP address (which can indicate approximate location), app and ad interactions, diagnostic information, and device or account identifiers, including the Android advertising ID and app set ID, for advertising, measurement and fraud prevention. Data sent by this SDK is encrypted in transit using TLS. Rost does not supply financial records, amounts, merchants, budgets or notification content to advertising requests. Where required, Rost presents a consent message before requesting ads. When available, use the advertising privacy options in Settings to review or change your choices. You can also reset or delete the advertising ID in Android settings. Google handles its data and retention under https://policies.google.com/privacy; deleting local Rost data does not delete data already handled by Google. Intro and theme settings are stored locally.

Planning assistant

this device-only setting is off initially. When enabled, it prepares proposals from completed budget periods for your review. Only explicit acceptance adds estimates; existing manual amounts are protected. Disabling it hides new history proposals and pace projections, and keeps saved plans unchanged. The preference is not included in financial backups.

Funding and repayments

amounts used from external reserves, cards or other sources, their labels, dates and recorded repayments stay only in the local financial file and JSON backup. They do not connect to a bank or initiate payments. Funding affects available cash separately from income; repayment does not count the original purchase again. The CSV export contains transactions only.