Trust and transparency
Privacy and browser storage
What the current browser app stores locally and what to consider when using a hosted website or public contact channel.
The current planner has no account sign-in. Its browser code stores a saved demo plan and language and theme choices in local storage where available; the planning profile can include financial details such as amount, contribution, time horizon, reserve months, income stability and loss tolerance. The reviewed browser app sends these values to no application API, but the website host or CDN may process ordinary connection and security logs.
Browser data
The saved plan uses the browser key `takacompass-last-demo-plan`; language and theme preferences use separate local-storage keys. Local storage persists on the device and browser profile until cleared and may be accessible to someone who can use that browser profile. It can also be removed through the browser's site-data controls. Private browsing or storage restrictions may prevent persistence.
Network and hosting
The reviewed web application contains no app API call for planner inputs and no configured analytics integration in its browser code. Loading the public site still requires network requests for the site, and its hosting, CDN, security or DNS providers may process technical request data under their own policies. This page cannot make a blanket promise that no network data is recorded.
Your choices and public reports
You can remove local data using your browser's site-data controls. Do not put personal financial details, screenshots or saved plan data into public GitHub issues; anyone may read or copy them. The source repository has no account profile or in-app account deletion flow because the current app has no user accounts.