Skip to content

Cookie Policy

Last updated: 2 October 2026

1. How FinanceOS uses browser storage

Cookies and similar local-storage technologies keep the service secure, remember preferences, record your consent and—only when you allow it—measure visits and advertising. Visitors in the EU/EEA, the UK and Switzerland are asked for consent before any analytics or advertising cookies load, and optional Google and Meta code does not load before they accept. Visitors elsewhere have analytics and advertising measurement on by default and can switch it off at any time in Cookie settings in the footer.

2. Essential storage

  • financeos.consent: your analytics and marketing choices, their date and the notice version; kept until changed or browser storage is cleared.
  • FinanceOS authentication session storage: access and refresh information needed to keep you signed in and secure your account; expires or refreshes with the session.
  • Preference keys for display currency, layout, setup and install prompts: kept until changed or browser storage is cleared.
  • financeos.attribution: first-touch UTM fields, gclid/fbclid, landing path and referring site; expires after 90 days.
  • financeos.signup_tracked.<account-id>: prevents duplicate signup measurement in the same browser; kept until browser storage is cleared.

3. Analytics storage

If Google Analytics is configured and you enable Analytics, Google may set cookies such as _ga and related measurement identifiers, commonly retained for up to 2 years. FinanceOS sends page paths and basic site events, not names, emails or account financial records. Google Analytics is currently disabled when its configuration ID is empty.

4. Marketing storage

If you enable Marketing, the Meta Pixel may set _fbp, commonly retained for about 90 days, and use an incoming fbclid to measure ad visits and signup/trial events. If Google Ads is configured, Google may use advertising cookies and consent signals for conversion measurement. No optional tracker loads when its ID is empty.

5. What we send

Consent-gated events are limited to public page views, account creation, checkout starts and trial starts, with plan/tier and list price where relevant. We do not send client details, invoice contents, documents, names, email addresses or figures from your financial records to Google or Meta.

6. Change or withdraw consent

Rejecting optional cookies does not block the app. You can change your choice at any time; withdrawal stops future optional measurement but does not make earlier consented processing unlawful. Browser controls can also delete stored data, but blocking essential session storage may sign you out.

7. Third parties and updates

Google and Meta process data under their own privacy terms when enabled. We may update this policy if storage names, purposes or providers change; a material consent change will prompt a fresh choice.