Last updated: September 12, 2026
Simply Family Budget is a manual budgeting and household-planning service. We do not currently connect directly to banks or financial institutions, and we do not currently run third-party advertising or cross-app tracking.
Please read this Privacy Policy together with our Terms of Service, Security Notice, and Delete Account page.
This Privacy Policy explains how Simply Family Budget collects, uses, stores, and discloses information when you use our landing site, web app, mobile app, integrations, and read-only public API.
When we say "we," "us," or "our," we mean Simply Family Budget and the people operating the service. When we say "you," we mean the person using the service or, where applicable, the family or household workspace that person manages.
We collect information you provide directly to us, including when you:
Depending on how you use the service, this may include:
The service does not require or intentionally collect highly sensitive information such as full payment card numbers, banking credentials, one-time passwords, or government-issued identifiers. Please do not provide this type of information through the service.
We also process limited technical information needed to operate, secure, and troubleshoot the service. This can include IP address, browser or app information, device identifiers generated by the service, request metadata, authentication events, rate-limit events, error logs, and mail-delivery diagnostics.
For public API requests, security records can include the token identifier, issuing user and family identifiers, requested route, response status, latency, and throttling outcome. We do not intentionally log authorization headers, plaintext tokens, transaction notes, or response bodies in public API request logs.
If you choose Trust this browser for 30 days, we create a persistent browser credential and store a server-side trusted-browser record containing an opaque browser identifier, your IP address and browser or user-agent information, the original authentication time, last-use time, fixed expiry time, and a link to the related web session. We use this information only for secure session continuation, browser-access inventory and revocation, abuse detection, troubleshooting, and security notifications. The sign-in control is unchecked by default and should be selected only on a private browser; you can revoke access later in Settings.
The service also stores some information on your devices:
Because browser and device storage is under your control, cached copies can remain on your own devices until the app clears them, you sign out, or you remove the app or browser data.
We use the information we collect to:
We do not sell your personal information. We do not currently use your budgeting data for advertising profiling.
We use our own API to record limited landing-page views, signup or iOS-download button clicks, and authenticated product-session starts. These records help us understand acquisition and exact-day retention without third-party trackers, advertising pixels, fingerprinting, or persistent device identifiers.
Landing records contain a random 30-minute browser-session identifier, page path, referring domain, allowlisted campaign fields, and a stable button identifier and page location when you click a signup or download button. Authenticated session records contain your account and family identifiers, client type and version, family-local activity date, and signup-day offset. These analytics do not contain transaction amounts, balances, merchant or transaction descriptions, wallet names, notes, or other budgeting content.
The iOS app asks for your permission before collecting Rapid Capture product analytics. Collection remains off unless you choose Share Anonymous Analytics, and you can withdraw consent at any time in Settings. Turning it off deletes analytics events that have not yet been sent.
When enabled, we record only whether Rapid Capture opened or finished and limited product-interaction attributes such as the entry source, text or voice mode, app language and version, parser path and result, outcome, names and count of corrected fields, autosave flags, offline status, duration bucket, and failure stage.
We do not include commands, speech transcripts, amounts, merchants, categories, wallets, notes, other financial values, names, email addresses, family or user identifiers, installation or device identifiers, IP addresses, authentication tokens, or user-agent strings in the analytics table. Authentication and network information may be processed transiently to prevent abuse but is not persisted with these events. A random capture identifier links an opened event to its finished event.
Raw anonymous product events are retained for up to 90 days. After that period, only de-identified daily aggregates may be retained. These events are not shown in individual-user activity timelines and are not used for tracking or advertising.
We disclose information only as reasonably necessary to operate the service, comply with law, or protect rights and safety. This may include:
Some service providers may process information outside your province, state, or country. Information handled by those providers may be subject to the laws of the jurisdictions in which they operate.
If you interact with Simply Family Budget through a third-party platform such as ChatGPT, that platform may also process data according to its own privacy policy.
If you configure a third-party system such as Home Assistant to use a public API token, that system receives and processes the API data at your direction under its own privacy, retention, display, and security practices.
We retain information for as long as reasonably necessary to provide the service, maintain security, resolve disputes, enforce agreements, and satisfy legal obligations.
A trusted-browser record expires after a fixed period of no more than 30 days and is deleted earlier when you sign out of that browser, revoke it in Settings, reset account credentials, use sign out everywhere, or delete your account. Restoring a session does not extend the record's fixed expiry.
Public API tokens expire after 365 days and can be revoked earlier in Settings. Revocation or account deletion deletes the active token credential; limited creation, revocation, and security records may remain as described below.
When you delete your account:
Limited records may remain for a period of time in system logs, queued mail records, security records, or encrypted backups. Information stored locally on your own browsers or devices may remain there until cleared by the app, the browser, or you.
We use commercially reasonable technical and organizational measures designed to reduce risk, including encrypted transport, authentication controls, family-scoped authorization, and rate-limiting on sensitive endpoints.
We also design the service to minimize the amount of personal and financial data processed wherever reasonably possible.
No software or infrastructure is perfectly secure. We do not guarantee absolute security, uninterrupted availability, or recovery of all data in every circumstance. Please review our Security Notice for more detail.
Subject to applicable law and practical limitations, you may:
Some requests may be limited where we need to verify identity, protect another person's rights, preserve shared family data for remaining members, or comply with law.
Simply Family Budget is not directed to young children. Do not use the service if you are not old enough to enter into a binding agreement in your jurisdiction, unless a parent or legal guardian has authorized and supervises the use.
If you choose to interact with Simply Family Budget through ChatGPT or a similar integration, some information may be transmitted to us so we can fulfill your request and return a response through that integration.
We process only the information reasonably necessary for that interaction, and you control what information you choose to share when using those tools.
When you create a public API token, you direct us to make the documented read-only family data available to requests authenticated with that bearer token. You are responsible for choosing, securing, and configuring the receiving system.
We may update this Privacy Policy from time to time. When we do, we will post the updated version here and update the "Last updated" date above. Material changes may also be communicated through the service or by email where appropriate.
If you have privacy questions, support requests, deletion requests, or security concerns, contact: