Back to overview
Full document

FacturaOS Cookie and Similar Technologies Statement

This Statement explains cookies, browser storage, application identifiers, analytics, diagnostics, consent choices, and necessary technologies used across FacturaOS.

Last updated: July 13, 2026privacy@facturaos.com
On this page
  1. 1. Technologies covered
  2. 2. Necessary technologies
  3. 3. Preferences and local storage
  4. 4. Optional analytics and diagnostics
  5. 5. Payment, authentication, and communications providers
  6. 6. Your choices
  7. 7. Duration, changes, and contact

1. Technologies covered

FacturaOS may use cookies, local or session browser storage, authentication tokens, pixels or tags, software development kits, application-instance identifiers, device information, logs, and similar technologies. Some are set by FacturaOS and others by providers operating a service for us.

2. Necessary technologies

Necessary technologies support authentication, security, fraud prevention, session state, load balancing, language, market, billing, payment flows, consent records, support, and core product operation. Blocking them may prevent sign-in or other features. They operate where reasonably necessary and are not disabled by the optional analytics setting.

3. Preferences and local storage

We may store language, market, display choices, remembered selections, privacy choices, attribution, and other convenience settings in the browser or application. Some remain until deleted; others expire or end with the session.

4. Optional analytics and diagnostics

Where enabled, Google Analytics may use first-party identifiers to measure visits, sessions, approximate region, device or browser type, referral source, and privacy-safe product events. Firebase Analytics may use an application-instance identifier for optional mobile usage measurement. Firebase Crashlytics may process application identifiers, device and crash diagnostics to help identify reliability problems.

Our event allowlists are designed to avoid client names, invoice content, contact details, addresses, search text, document content, and full record URLs. Providers may receive IP address and device information as part of network operation under their own terms.

5. Payment, authentication, and communications providers

Stripe components may use cookies or similar technologies for payment processing, authentication, fraud prevention, risk analysis, connected accounts, and checkout. Google or Apple may use technologies when you choose their sign-in services. Supabase supports authentication and session handling. Resend processes email delivery and related delivery events.

Provider technologies are governed by the provider's policies in addition to this Statement.

6. Your choices

Signed-in users can turn optional product analytics off in Account settings, and mobile users have the corresponding privacy control. The public marketing site also honors its available analytics preference and supported browser privacy signals. You can delete browser storage or adjust browser and device permissions.

These choices do not disable necessary security, billing, payment, authentication, support, or fraud-prevention processing. Where law requires prior consent or an opt-out for a non-essential technology, we will provide the applicable control.

7. Duration, changes, and contact

Session technologies end when the session or browser closes; persistent technologies remain for a defined period or until deleted. Provider retention varies and may be controlled by our provider settings. See the Privacy Policy for broader retention information.

We may update this Statement when technologies or providers change. Questions may be sent to privacy@facturaos.com.

Questions about this document?

Contact us and include the document name so we can route your question correctly.

Privacy contact