On this page
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, saved-account and active-workspace session state, security, fraud prevention, load balancing, language, market, billing, invoice and membership payment flows, checkout return state, consent records, support, and core product operation. Blocking them may prevent sign-in, account switching, checkout, or other features. They operate where reasonably necessary and are not disabled by optional analytics or advertising choices.
3. Preferences and local storage
We may store language, market, theme, accessibility and display choices, remembered selections, saved-account references, active-workspace selection, privacy choices, attribution, and other convenience settings in the browser or application. Optional Meta identifiers and click attribution require the separate advertising permission described below. Some settings remain until deleted; others expire or end with the session. Do not save additional accounts on a shared or untrusted device.
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. Optional Meta advertising technologies
Where the dataset or Pixel has been verified and the feature configured, Meta Pixel may load only after separate affirmative advertising permission. It uses optional first-party browser identifiers such as _fbp and, when associated with a genuine Meta click, _fbc or fbclid to measure and attribute FacturaOS advertising and help optimize ad delivery. Meta also receives IP address, browser user agent, reviewed non-sensitive public-page and referrer context, and limited verified trial-start events with opaque event identifiers. Tracking is limited to reviewed public marketing and conversion pages and excludes private application records and URLs, authentication or checkout tokens, and customer forms. FacturaOS does not enable advanced matching or provide emails, phone numbers, or operational Customer Data for it.
These identifiers are optional advertising data, not necessary login or billing cookies. Meta may match them to activity on its services and process them under its own terms and privacy notice at https://www.facebook.com/privacy/policy/. These signals can be linked to a person and used for advertising, and attribution may be incomplete. If it is not configured or you decline permission, optional Meta technologies do not load and events are not sent.
You can withdraw permission through the public site's privacy choices. Withdrawal stops future optional Meta events and clears first-party Meta cookies and optional click-attribution storage accessible to FacturaOS. It cannot remove Meta's own third-party cookies or retract information already transmitted to Meta. You can also use browser controls and Meta's privacy controls.
6. Payment, authentication, and communications providers
Stripe components may use cookies or similar technologies for payment processing, authentication, fraud prevention, risk analysis, connected accounts, invoice checkout, and recurring customer-membership Online Checkout. On iOS, Apple StoreKit and RevenueCat's software development kit use an app user identifier plus limited product, transaction, subscription, entitlement, device, app, storefront, environment, and technical information necessary to present App Store subscription options, validate and restore purchases, and synchronize access. Evertec or ATH Móvil payment components may use browser, device, session, authentication, or similar technologies to present a supported payment flow, authorize and verify a transaction, prevent fraud, and return status. 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.
YouTube videos embedded in Notes remain unloaded until you choose to open them. Loading a video contacts the provider through its privacy-enhanced embed domain; the provider may use device information or similar technologies according to its policies. The FacturaOS optional analytics setting does not control the provider's video player.
Provider technologies are governed by the provider's policies in addition to this Statement.
7. 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.
Public-site privacy choices let you permit or decline Meta advertising separately from Google Analytics and change that choice later. Analytics permission alone never enables advertising. Global Privacy Control (GPC), Do Not Track (DNT), and an applicable account opt-out, including turning optional product analytics off, override advertising permission. Declining or withdrawing optional advertising does not affect signup, checkout, trial access, or other product access. Meta permission does not change Google's disabled advertising-personalization settings.
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.
8. 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.