Effective September 24, 2026. This prelaunch policy describes the current Flask application.
You may use the planner without an account. In that mode, plan inputs are stored in your browser's local storage and submitted to this server only to perform calculations.
If you create an account and explicitly save a plan, we store your name, email address, password hash, retirement-plan inputs, analysis summary, and progress snapshots. Passwords are never stored in readable form.
When you click a tracked demo call to action, we record the originating IP address and limited campaign information to measure site performance and protect the service. Raw IP addresses are restricted to the private administrator view and cleared after 30 days.
If enabled, optional Google Analytics runs only after you choose “Allow analytics” in the household planner. It measures anonymous planner use and completed analyses. We do not send financial inputs, retirement results, names, email addresses, or account identifiers to Google Analytics.
Data is used to operate the planner, save requested plans, secure accounts, process subscriptions, and provide support. The application does not sell personal information or use advertising trackers. Google Analytics is used only for the optional, consent-based product measurement described above. Stripe processes subscription payments when billing is enabled; card details are handled by Stripe and are not stored by this application. The optional AI feature connects only to the locally configured Ollama service.
Cloud data remains until you delete individual plans or your account, subject to limited billing, security, and legal records that a payment processor may retain. Account deletion removes the account, cloud plans, and progress snapshots. Browser-local data must be cleared separately using “Clear saved data” in the planner or your browser controls.
The app hashes passwords, uses protected session cookies, validates state-changing requests, limits request sizes, and sends defensive browser headers. Public deployments require HTTPS, protected backups, production monitoring, and a managed secret key.
Privacy questions: retiremappro@gmail.com.