Privacy Policy — Budget Studio

What this policy covers

This policy covers the Budget Studio website, installable web app, and native iOS beta. Budget Studio is operated by an individual developer. It is not a bank, financial institution, or financial adviser.

Because this is a beta, features and service providers may change. If a change materially affects how personal information is handled, this page will be updated before or when that change reaches users.

Information the app handles

Account information

If you create an account, Supabase Auth stores your email address, authentication record, and optional display name. If you choose Google sign-in, Google and Supabase also handle the identity information needed to complete that sign-in. Passwords are handled by Supabase Auth; the Budget Studio operator does not receive your plaintext password.

Budget information

The app stores what you choose to enter, including amounts, categories, transactions, pay schedules, recurring items, savings goals, and notes. This information can reveal details about your finances, so avoid putting unrelated sensitive information in free-text fields.

Shared budgets

If you create or join a shared budget, the app stores the shared budget, membership records, invite information, and transaction author identifiers. Other members of that budget can view and edit its contents.

Information on your device

The web app keeps an offline cache in browser storage. The iOS app keeps local budget data and session information on the device. After a password sign-in on a supported iOS device, the current beta saves your email and password in Apple Keychain and enables biometric re-entry. Biometric matching is performed by iOS; Budget Studio does not receive your face or fingerprint data.

Receipt scanning in the iOS beta uses Apple Vision on the device. The selected image is used to suggest transaction fields and is not uploaded or saved by Budget Studio. Any transaction details you choose to save are handled like other budget data.

Technical and support information

Hosting and authentication providers may receive standard request information such as an IP address, device or browser type, timestamps, and requested pages. If you email for support, the operator receives your email address and whatever you include in the message.

How information is used

To create and secure your account.
To save, sync, display, export, and restore your budget.
To let invited members use a shared budget.
To provide offline use and reconnect changes when service returns.
To investigate bugs, abuse, security issues, and support requests.

Budget Studio does not sell or rent personal information. As of this update, it does not use advertising trackers or a separate product analytics service.

Who can see budget information

A personal budget is available through your signed-in account. The app operator has administrative access to the Supabase project and may access stored data when reasonably needed for support, maintenance, security, or legal obligations.

A shared budget is visible and editable by its members. An invite link should only be sent to someone you trust. Members can copy or export information they can access; Budget Studio cannot erase copies another member already made.

Service providers

These services support the current beta. They process information under their own terms and privacy notices and are expected to protect it consistently with their obligations and applicable law.

Supabase: Authentication, database storage, and shared-budget updates. Supabase privacy
GitHub Pages: Static website hosting. GitHub privacy
Google: Web fonts and, if you choose it, Google account sign-in. Google privacy
jsDelivr: Delivery of the Supabase web library used by the website. jsDelivr privacy

Security

The beta uses HTTPS, Supabase Auth, database row-level access rules, and device storage provided by the browser or iOS. These measures reduce risk, but no beta or online service can guarantee absolute security or uninterrupted access.

Use the beta with care. Keep your own export, use a unique password, sign out of the web app on shared devices, avoid the iOS beta on a shared device, and do not put passwords, government identifiers, or full payment-card details in notes.

Retention and your choices

Export your budget as CSV or JSON from Settings.
Update your display name and budget entries in the app.
Use Settings → Delete cloud data to remove your personal budget. If you own a shared budget, this also deletes it for its members; if you are a member, it removes your membership.
Contact the operator to request deletion of the remaining Supabase Auth account or to ask what account information is associated with your email.

On iOS, turning off Face ID stops biometric unlock but the current beta keeps the saved login in Apple Keychain so the feature can be turned back on. There is not yet a separate in-app control to erase that Keychain item. Avoid the iOS beta on a shared device until that control is added.

Signed-in data remains until you delete it, the account is deleted, or the service is discontinued. Provider security logs and backups may remain for a limited period under provider retention practices. The operator may ask you to verify a deletion request from the email connected to the account.

Leaving a shared budget creates a personal copy that keeps your own and unassigned entries while removing partner-attributed transactions. The owner and other members may retain their own copies or exports.

Children

Budget Studio is not directed to children under 13, and the operator does not knowingly collect personal information from children under 13. If you believe a child provided account information, email the operator so it can be removed.

Contact and policy changes

Questions, access requests, corrections, or deletion requests can be sent to mcl.labss@gmail.com.

The “Last updated” date will change when this policy changes. Continued use after an update means the revised policy applies going forward; material changes will not be applied retroactively without a lawful basis.