Privacy Policy

1. What Money Autopilot does

The app helps users:

• review a current balance and spending plan;
• track transactions as expenses or income;
• set savings goals and monitor progress toward target amounts;
• view forecast scenarios and projected spending outcomes; and
• complete a local onboarding setup flow to save basic preferences.

Money Autopilot is not currently a cloud-backed banking, login, or account system. The app is built as a local static web app and a Capacitor Android wrapper.

2. Information collected and stored

Based on the current implementation, the app stores information locally on the device where it is used. The app may save the following values in browser localStorage and sessionStorage:

• money-autopilot-startup: onboarding status, selected setup stage, and startup completion state;
• money-autopilot-financial: chosen currency and balance values;
• money-autopilot-goals: savings goals, amounts saved, monthly contribution values, target dates, and goal names;
• money-autopilot-transactions: transaction names, notes/details, type (income or expense), and amount values; and
• money-autopilot-scroll:<page>: page scroll position for preserving the last viewed state on the current device.

Users can enter cash balance, currency choices, transaction history, and goal data. These values are designed to stay on the device and are not tied to an account or user profile.

3. What the app does not do

As currently implemented, the app does not:

• create user accounts or require login;
• connect to a bank account, credit card, or payment network;
• send financial information to a backend server;
• use Firebase, Supabase, or analytics tools; the Android app includes Google Mobile Ads for banner advertising;
• send financial entries to Google's ad request code; or
• store user data in a remote database.

There is no current backend account system, no remote financial API, and no cloud sync feature in the codebase reviewed for this app.

4. Local device storage and data use

Money Autopilot uses browser localStorage and sessionStorage to remember setup state, balances, saved transactions, and goals. This allows the app to keep a local personal dashboard experience without a backend database.

The app uses this data only to:

• display the current balance and spending summary;
• render the transaction history;
• calculate safe-to-spend guidance and forecast outcomes;
• show goal progress and projected completion dates; and
• resume onboarding and app state on the same device/browser.

Because the app stores data locally, the data remains on the device unless the user clears browser data or deletes the app data from the device.

5. Financial information transmitted to any server

Financial information entered into Money Autopilot is kept in device storage. The Android app's Google Mobile Ads requests do not include the user's balance, transaction entries, or savings goals.

When the app is loaded in a browser, the browser may connect to the domain serving the app and may also load web fonts from Google Fonts. Those requests are for the app’s presentation and are not a remote account or financial-data system.

6. Third-party sharing and analytics

The Android app uses Google Mobile Ads SDK to request banner ads on the dashboard. Google states that the SDK automatically collects and shares device IP address, ad and app identifiers, ad interactions, and diagnostic information for advertising, analytics, and fraud prevention. The SDK encrypts transmitted data in transit.

The app requests consent information through Google's User Messaging Platform and displays a consent form when Google reports one is required and available. Ads are requested only when the consent SDK indicates they may be requested. The web version does not load the mobile ad SDK. Google Fonts may also receive normal connection information when fonts are loaded.

7. Cookies and browser storage

Money Autopilot uses browser storage mechanisms such as localStorage and sessionStorage. It does not currently rely on cookies for app functionality. Cookies are not used as a user account system or for tracking.

8. Data retention

Data stored in the app remains on the device until the user clears it or deletes the app data. There is no remote retention system in the app today, so there is no server-side retention period managed by Money Autopilot.

9. How users can delete local data

Users can delete the app’s local data in the following ways:

• clear browser site data for the Money Autopilot domain in the browser settings;
• delete the app’s data from the Android app settings screen; or
• open the browser developer tools, go to Application/Storage, and remove the localStorage keys beginning with money-autopilot-.

The app also includes a transaction clearing control on the Transactions screen for deleting saved transaction history from local storage.

10. Security

Money Autopilot stores user data on the local device/browser rather than in a remote database. This reduces exposure to server-side breaches, but it also means the user’s browser or device security settings are the primary protection for this information.

We are not making guarantees beyond reasonable efforts to protect local device data and the current app architecture. The app does not currently implement server-side security controls because no server-side personal data storage is in place.

11. Children’s privacy

Money Autopilot is a personal finance planning tool and is not directed to children under the age of 13. The app does not create accounts or collect personal information from children in a remote system. It stores local planning data only on the device being used.

12. Changes to this Privacy Policy

If the app’s functionality changes—such as the introduction of a backend, account system, analytics, or third-party services—this Privacy Policy will be updated to describe the new implementation accurately.

13. Contact information

For privacy questions, contact: bendreorg21@gmail.com