Privacy Policy
Méxi-Cash Efectivo y finanzas
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Méxi-Cash stores the financial records you enter on your iPhone using SwiftData: pay-period income and dates, budget allocations, debt names and terms, payment history, savings goals and contributions, small-expense categories, amounts and dates, payment obligations, and saved loan comparisons. Language, reminder and backup preferences are stored locally. A randomly generated installation secret is stored in the iOS Keychain with device-only accessibility. There are no user accounts, passwords, bank connections, advertising or analytics SDKs. Optional backup sends an encrypted financial snapshot, the installation credential over HTTPS, and protocol revision information to our backend. The backend stores a SHA-256 hash of the credential, the encrypted snapshot, revision and creation/update timestamps; it does not store the credential itself. Requests to the API or public website also expose network metadata such as IP address, time, requested path and response status to Railway infrastructure. The application uses hashed network identifiers and counters in memory for abuse limits. A device-only Keychain flag records whether server registration may have occurred so that deletion can be completed safely.
How we use information
Local records provide budgeting, loan estimates, debt schedules, savings progress, expense totals and the financial-health planning indicator. The installation secret authorizes access to that installation's backup and derives its snapshot-encryption key. Optional backups are manually saved or restored from Settings and do not block offline work. Notification permission is used only for local payment reminders. Network metadata and temporary rate-limit counters support service delivery, reliability and abuse prevention. We do not use financial records for advertising, marketing, credit decisions or selling personal information.
Service providers and sharing
The backend and public privacy page are hosted by Railway, which processes encrypted snapshots, credential hashes and request metadata as our infrastructure provider. The app sends an installation credential to the backend for authorization over HTTPS; the server code hashes it and does not log credentials or snapshot contents. Infrastructure operators may process request and diagnostic logs in operating their systems. No advertising, analytics, email-delivery or bank-data service is integrated. Local reminders are handled by iOS and may display the obligation name and amount on the lock screen according to your notification settings. Apple device backups may include local application data according to your device settings; the device-only Keychain secret is not intended for migration to another device.
Data retention
Local financial records remain until you edit them, use Delete all my data, or remove the app, subject to iOS storage and backup behavior. The Keychain may retain this installation's secret after app removal; removing the app alone does not request server deletion. The server keeps the most recent encrypted snapshot and installation metadata until the snapshot is overwritten or the installation's data is deleted. There is no application-defined automatic expiry or snapshot-history archive. Rate-limit windows reset after one minute; hashed counter entries are removed during bounded-map cleanup or process restart. Railway controls any infrastructure log and platform-backup retention; this application does not set or promise a fixed duration for those provider records. Deletion from active storage does not guarantee immediate removal from provider backups or device backups, which follow their own lifecycle.
Deleting your information
In Settings, Delete all my data clears local financial records and, if backup has been used, makes an authenticated request to delete this installation's server record and encrypted snapshot. A network connection is required for server deletion; if it fails, local records are retained so you can retry. The backend deletes the active database row with secure deletion enabled and truncates its database journal. The app cancels its pending and delivered local reminders. The installation secret is retained in the device Keychain and can be reused for a new empty installation record; no financial snapshot remains in the active server record after successful deletion. Turning backup off stops optional transfers but does not delete an existing server snapshot. Restoring a snapshot requires the same installation secret, and we do not promise recovery or server-data identification if you lose it. Device and infrastructure backups may retain older copies until their respective lifecycle removes them. After confirmed server deletion, the remote-registration flag is cleared; a later reset can remain local when no new registration has been attempted.
Permissions and your choices
The app asks for notification permission only when you enable payment reminders. You may turn reminders off in the app or withdraw permission in iOS Settings; the app then stops scheduling its reminders. iOS controls how reminder content appears on the lock screen. No location, contacts, camera, photo-library, tracking or geographic-map permissions are requested. Optional backup can be disabled in Settings, and budgeting, editing and calculations continue to work without a network connection. Disabling backup does not itself delete a previously saved copy.
Your privacy rights
You can view and correct your financial records directly in the app, change preferences, disable backup and reminders, and delete your records through Settings. For privacy questions or requests concerning your information, contact Wystan14Somerville@icloud.com. This is a public privacy contact, not an account or email-delivery feature in the app. Applicable privacy rights may depend on where you live. Because we do not operate accounts or collect an email identity, a contact email alone cannot identify an installation's encrypted backup; authenticated in-app deletion is the direct way to remove it. Do not send your installation secret or sensitive financial details by email.
Security
The app generates a separate random 32-byte secret for each installation, keeps it in the iOS Keychain with device-only accessibility, derives a snapshot key using HKDF-SHA256, and encrypts snapshots with AES-GCM before upload. Network requests use HTTPS. The server stores only a credential hash, enforces authorization on private endpoints, limits request sizes and rates, and uses revision checks to reject conflicting writes. The database is stored on a persistent Railway volume. App-side financial data uses iOS application storage; its protection and any device backups also depend on device security settings. The application avoids logging credentials and financial payloads. These measures reduce risk, but no device, network or storage system can be guaranteed completely secure.
Children’s privacy
Méxi-Cash is intended for adults managing personal budgets and credit obligations. It is not designed for children and does not intentionally solicit children's information. No age or identity information is requested. If you believe a child has provided information through this application, use the in-app deletion controls where possible or contact Wystan14Somerville@icloud.com without sending installation secrets or unnecessary personal details.
Changes to this policy
We may update this policy when the application's processing or service arrangements change. The current policy is published at this page and is linked from the app's Settings. The effective date identifies the current version. Material changes will be reflected in the policy and, where appropriate, in an app update or an in-app notice. Review this page periodically for the current practices.