Privacy and data handling
Financial planning inputs deserve a more specific answer than “we value privacy.” The storage boundary depends on the action you choose.
Stays in this browser by default
Calculator inputs are evaluated in the browser. Checkup drafts and named local snapshots use browser local storage on this device. They are not sent to analytics. Clearing site data, using another browser, or using private browsing can remove or isolate them.
Stored when you explicitly use an account feature
If you sign in and choose “save to account,” the named checkup or withdrawal scenario is stored in Know Plain’s Supabase database and tied to your authenticated user ID. Row-level security restricts normal account access to the owner. Authentication uses secure cookies needed to maintain the session.
Analytics and operational errors
The analytics boundary is deny-by-default. It accepts an allowlisted event name and coarse fields such as a tool slug, checkup step name, broad zero-result search category, or coarse application-failure class. It rejects arbitrary properties, raw error messages and stacks, URLs, raw search queries, balances, income, debt, spending, conversion amounts, scenario notes, and email addresses. Global Privacy Control suppresses analytics, performance beacons, and operational-error events.
Community data
Published forum threads and replies are public. New submissions can remain pending for moderation. Reports are tied to the reporting account and intended for moderation, not public display. Do not post account numbers, contact details, health information, or other sensitive personal data.
What we do not do
Know Plain does not sell personal data and does not use entered financial values for advertising profiles. External source, affiliate, and YouTube links leave this site and are governed by those services’ privacy practices.