Privacy Policy

Last updated: October 14, 2026

Maghna is a personal finance tracker. This page explains what data the app handles, where it's stored, and what you control.

What's stored

When you use Maghna, the following is stored on your device first, then backed up to your account:

Transactions, budgets, goals, accounts, and custom categories you create
App settings such as notification preferences
Your email address, used to sign in and identify your account
Receipt photos, only if you choose to attach one to a transaction

Your light/dark theme preference is device-only and never sent to the backup. Whether biometric lock is turned on does sync to your account (so it follows you to a new device) — but this is just an on/off flag, never your actual fingerprint or face data, which stays with your device's operating system.

On mobile, the on-device copy lives in a local SQLite database. On web, it lives in your browser's local storage. Either way, it's the copy the app reads and writes to directly — the backup exists so you don't lose it and so it can follow you to a new device.

Signing in

Maghna uses Clerk, a third-party identity provider, to handle sign-in — email and password, and Sign in with Apple or Google. Clerk stores your email address and authentication credentials on Maghna's behalf; Maghna's own servers never see or store your password. If you sign in with Apple or Google, Clerk receives the basic profile information that provider shares for sign-in, typically your name and email address.

Cloud backup

Maghna backs up your data to a Supabase-hosted database, including any receipt photos you attach, which are stored in a private file bucket. Every table and the receipts bucket have row-level security enabled, meaning the database itself enforces that a signed-in account can only ever read or write its own rows and files — not another user's, and not an anonymous request's. Supabase acts purely as infrastructure here: it stores the backup, it doesn't analyze or repurpose it.

Biometric lock

If you enable Face ID or Touch ID, that authentication happens entirely through your device's operating system. Maghna never receives, stores, or transmits your biometric data — it only receives a yes/no confirmation from the OS.

What Maghna doesn't do

No ads, and no ad networks integrated into the app
No selling or renting your data to anyone
No third-party analytics or behavioral tracking SDKs
No in-app purchases or subscriptions that would require sharing data with a payment processor beyond what the App Store or Play Store already handle

The one optional exception is crash reporting: if configured, Maghna can send crash and error reports to Sentry to help fix bugs. This is disabled by default in development and only activates if the app is built with a Sentry key configured — it reports technical error details, not your financial data.

Your controls

Export: export any or all of your transactions to CSV, or export a full JSON backup of your entire account, at any time.
Delete: deleting your account removes your data from the cloud backup and signs you out, from the Profile screen's account settings.

This is a straightforward description of how the app actually works, written by the developer — not a document reviewed by a lawyer. If you have specific questions about how your data is handled, reach out using the contact below rather than relying solely on this page.

Changes to this policy

If how Maghna handles data changes in a meaningful way, this page will be updated and the date at the top will change.

Contact

Questions about this policy or your data: support@maghna.net