Privacy Policy
MixiCash:Smart Manager
This policy explains how this application handles information and how to contact us about privacy.
Information we process
MixiCash stores the monthly income you enter, transaction amounts, types, categories, dates and notes, budget allocations and limits, savings goals, contributions, debt terms and payments, health-score history, currency and date settings, and notification preferences locally using SwiftData. It does not connect to banks or request account, contact, location or advertising identifiers. Optional sync sends an AES-GCM encrypted snapshot of this ledger to our backend together with a random installation identifier and modification timestamps. The encryption key and installation authorization secret are stored in device-only Keychain. The server stores a hash of the secret, not the secret itself. When you use sync or visit this policy, Railway infrastructure receives request information such as your IP address, request time and route, and may maintain operational logs. Financial snapshot contents are not written to application logs.
How we use information
Local data powers transaction history, monthly budgets, savings and debt planning, estimates, the financial health guide, charts and a text summary that you choose to export. Notification preferences are used to schedule local budget-threshold alerts. Optional encrypted snapshots allow the same installation to synchronize its stored ledger. Installation credentials authorize access to that installation only. Request metadata is used to operate the service, enforce rate limits and diagnose failures. There are no advertising, analytics, mailing or support-ticket integrations.
Service providers and sharing
The backend and its PostgreSQL database are hosted on Railway, which processes encrypted snapshots, installation metadata and network or operational information as the infrastructure provider. The app uses Apple system services for Keychain, device storage, local notifications and the file destination you choose for export. There are no third-party analytics or advertising SDKs in the app. We do not sell financial data. A summary saved to an external or cloud file destination is handled by that destination under its own terms. If you independently contact the public privacy email, your email provider and the recipient email provider process that communication; the app itself does not send email.
Data retention
Local records remain until you reset them, remove them individually or remove the app data. Keychain items may remain after uninstalling; they are device-only and are not a portable recovery service. The backend retains the latest encrypted snapshot until it is overwritten or you request its deletion. The installation identifier and hashed authorization record remain so the same installation can authorize future requests after snapshot deletion. Rate-limit counters are kept temporarily in server memory. We do not promise a fixed Railway infrastructure-log or backup retention duration because no such duration has been established for this product. Infrastructure backup copies, if present, may retain previously stored encrypted information until the provider removes or overwrites them; the app cannot instantly erase those copies.
Deleting your information
Delete server snapshot in Settings sends an authorized deletion request for this installation and switches sync off after success, while preserving your local ledger. Reset all local and server data first requests server-snapshot deletion and then clears the local ledger; if deletion cannot be confirmed online, no local reset is performed. Turning sync off alone does not remove an existing server snapshot. Deleting local records while sync is off does not change a previously stored server copy. Removing the app alone does not request server deletion. Exported files must be deleted separately from their chosen destination. The authorization record and infrastructure logs are not erased by snapshot deletion. Without the installation secret we cannot authenticate a request to recover or delete a particular encrypted snapshot; do not rely on recovery after loss of the device or key.
Permissions and your choices
MixiCash requests notification permission only when you enable budget alerts. Alerts reflect threshold crossings in transactions you record; the app has no background bank feed. You may switch alerts off in the app or withdraw notification permission in iOS Settings. Core finance features remain available without notification permission. The app does not request location, camera, microphone, contacts or photo-library permissions. Export uses the system file picker so you choose a destination.
Your privacy rights
Depending on your location, you may have rights to access, correct, export, delete or restrict processing of your information. You can edit local transactions, export a text monthly summary, disable sync and request server-snapshot deletion through Settings. For privacy questions or requests contact cuthwin.tattershall@icloud.com. This address is a public privacy contact, not an account identifier or an in-app email-delivery service. The backend cannot decrypt your financial snapshot and cannot associate a lost installation credential with a named person.
Security
The app encrypts snapshots on the device with AES-256-GCM before transmission and uses HTTPS for the public API. Each installation has an independently generated authorization secret, stored in device-only Keychain alongside a separate encryption key. The server checks the installation identifier and a cryptographic hash of the secret before allowing snapshot access; it does not have the device encryption key. Local data uses the operating system storage protections and is not separately encrypted by MixiCash. Rate limits, bounded requests and database constraints reduce abuse. No system can guarantee absolute security, and an unlocked or compromised device may expose locally accessible information.
Children’s privacy
MixiCash is intended for adults managing their own finances and is not directed at children under 13. We do not knowingly solicit personal information from children. If you believe a child has supplied information, contact cuthwin.tattershall@icloud.com. No date of birth or age-verification account is collected.
Changes to this policy
We may update this policy when application behavior, infrastructure or processing practices change. The current policy and effective date are published at this public privacy page and linked from Settings. Material changes will be reflected in the updated policy and, where appropriate, the application release information. Review the policy before enabling optional sync after an update.