Privacy
This legal text is provided in English only. Translating privacy policies can change their legal meaning; contact support if you need clarification in another language.
Last updated: 2026-11-20 · Draft for owner legal review (not legal advice). Written with Canadian PIPEDA, EU/UK GDPR-style rights, and common US / African privacy expectations in mind.
Who we are
Nazux Ledger is a personal budgeting product operated by Nazux for this instance at ledger.nazux.com. Privacy contact: privacy@nazux.com.
What we store
Nazux Ledger stores the personal budgeting data you enter: accounts, categories and monthly budget envelopes, transactions (including descriptions and notes), recurring items, savings goals, bank import profiles, and auto-categorization rules. We also store your auth user id and email so we can isolate your ledger and let you sign in. If you enable two-factor authentication, Supabase Auth stores MFA factor metadata (not the codes themselves). Optional support tickets and feedback you submit are stored so we can respond.
Lawful basis (EU/EEA/UK and similar)
Where GDPR or similar laws apply, we process data to perform the contract (provide the budgeting service you signed up for), based on legitimate interests (security, abuse prevention, service reliability, anonymized deletion accountability), and where required with your consent (for example optional feedback). You may withdraw consent where processing is consent-based without affecting prior lawful processing.
Where it is stored & processors
Authentication is provided by Supabase Auth (email/password and optional Google sign-in; optional TOTP MFA). Application data lives in Supabase-hosted Postgres (project region Canada Central). The public Supabase Data API is locked down with row-level security; the app reads and writes through a server-side Prisma connection. The web app runs on Google Cloud Run (GCP project used for this site, region us-east4) and may use Google Cloud Logging / Error Reporting for operational diagnostics. Nightly database dumps may be stored in a private Google Cloud Storage bucket (lifecycle delete after about 30 days). Operational logs are sanitized and do not intentionally include balances, transaction details, or secrets.
Sub-processors for this instance typically include: Supabase (auth + database) and Google Cloud (hosting, logs/errors, optional backup storage). Google sign-in also involves Google as identity provider when you choose that option.
International transfers
Your data may be processed in Canada (Supabase project region), the United States (Google Cloud services used for this deployment), and other locations where those providers operate infrastructure. Where cross-border transfer rules apply, we rely on the providers' contractual safeguards and your need to use the service. Users in the EU, UK, US, and African jurisdictions should expect that data may leave their country of residence to deliver the product.
How we use it
Data is used only to provide the budgeting product to you: display your ledger, run imports/exports, keep you signed in, enforce security (including staff MFA), and handle support/feedback you send. We do not sell your data. We do not use your financial data for advertising.
Your rights
Depending on where you live, you may have rights to access, rectify, export (portability), erase, and object to certain processing. While signed in, open Account to download a full JSON export (or a CSV bundle) of your Nazux Ledger data, or download a transactions CSV from Import / Export. To correct data, edit it in the app or email privacy@nazux.com. To object or raise a complaint, email privacy@nazux.com; EU/UK users may also contact their local supervisory authority.
Retention, export, and deletion
We keep your ledger while your account is active. Requesting deletion from the Account page starts a 14-day grace period: you are signed out, but your data remains until that period ends (or you sign back in and cancel). After 14 days the deletion is permanent — ledger data and your Supabase Auth user for this app are removed. If you need deletion sooner, contact privacy@nazux.com; support may complete an immediate erasure after identity verification (staff actions require MFA).
We keep a minimal anonymized deletion audit log (timestamp, one-way subject/actor hashes, reason, optional feedback, outcome such as success/cancelled/failure, and a method flag for scheduled vs staff-assisted deletion) so we can demonstrate that erasure requests were handled — not your email, name, or financial data. Target retention for that audit log is at least 24 months. Encrypted database backups, when enabled, are retained about 30 days then deleted by bucket lifecycle; a deleted account may still exist in those backup snapshots until they expire.
Cookies
We use essential cookies only to keep you signed in (Supabase Auth session cookies) and, in automated test environments, short-lived impersonation cookies. We do not use advertising, analytics, or other non-essential cookies, so this site does not show a cookie consent banner. Security headers (including Content-Security-Policy and X-Frame-Options) reduce common web risks. Auth email and OAuth redirects always use this site's public URL.
Contact
Privacy questions, access/export/erasure requests, or concerns: privacy@nazux.com. We aim to respond within a reasonable time consistent with PIPEDA and, where applicable, GDPR timelines for small organizations.
Draft notice: This wording is a working draft for the product owner's legal review. It is not a substitute for counsel and may need jurisdiction-specific edits before you rely on it.
Dates and currency follow each user’s region and account settings. See also the Terms of use.