FinanceOS

Cookies and storage

Cookie Policy

How FinanceOS uses cookies, local storage, and similar technologies in your browser. Last updated: April 2026.

Summary

FinanceOS is a web application. Like most sites, it stores data in your browser so the app can remember your session, your workspace inputs, and basic preferences. We do not use third-party advertising cookies in the product shell. Optional privacy-friendly analytics may load if your deployment configures them (see Analytics below).

Authentication (Supabase)

When you sign in, our authentication provider (Supabase) uses cookies to keep your session secure and to coordinate sign-in across page loads. These are first-party or provider cookies required for the service to function.

Local storage and session storage

Much of your planning workspace (salary inputs, balances, budget sliders, chart preferences, onboarding progress, and similar fields) is stored in localStorage so pages load quickly and can work offline within the browser. If you use cloud sync while signed in, structured copies may also be stored in our database. Clearing site data in your browser removes local copies on that device.

Theme and UI preferences

We may store theme (light or dark), dismissed banners, and similar UI choices in local storage so your experience stays consistent between visits.

Payments (Stripe)

When you open Stripe Checkout or the billing portal, Stripe may set cookies or use storage as described in Stripe's own policies. We do not control those cookies.

Analytics

If the deployment sets NEXT_PUBLIC_PLAUSIBLE_DOMAIN, Plausible Analytics may load a small script from plausible.io to record aggregated page views and custom events. Plausible is designed to avoid invasive tracking and does not use advertising cookies.

Managing cookies and storage

  • Use your browser settings to block or clear cookies and site data.
  • Sign out on shared devices after use. Signing out does not always erase all local workspace data until you clear site data.
  • For questions, contact details in the Privacy Policy apply.

Privacy Policy · Terms of Use

Navigation

Jump to any page