FacturaOS Privacy Policy

1. Scope and our roles

This Policy applies when you visit FacturaOS sites, create or use an account, join a workspace, use the mobile application, contact support, subscribe, or interact with a FacturaOS-operated payment page, public form, or communication.

J.R.SOSA & CO. LLC controls personal information used for accounts, billing, product operations, security, analytics, optional advertising, support, and our business. For client, invoice-recipient, form-respondent, supplier, employee, contractor, and similar personal information submitted by a business customer, that customer generally determines the purpose and FacturaOS generally acts as its processor or service provider under the Data Processing Addendum.

2. Information we collect

Depending on how you use FacturaOS, we may collect the following categories:

• Account and identity: name, email address, authentication provider, user identifier, language, role, profile settings, saved-account and active-workspace selections, and login or invitation records.
• Business and workspace: business name, merchant registration number, contact details, logo, external links, operating market, tax and invoice settings, locations and images, addresses, service model, service and delivery areas, working hours, professional-license records, members, invitations, and permissions.
• Optional business setup response: where you heard about FacturaOS, if you choose to answer. We use this answer for internal analysis of signups and outreach channels. Skipping it does not affect setup or access, and answering does not subscribe you to marketing communications.
• Operational Customer Data: client first and last name, email, phone, photograph, optional birth date or year and gender, address, precise location captured with device permission, internal notes, estimates, invoices, line items, service and product categories, catalog images, appointment dates and status, assigned staff, blocked time, working hours and exceptions, cart and sale records, membership plan and sold-term snapshots, included benefits, redemption and status history, evidence files, templates, inventory consumption, suppliers, purchase orders, routes, reports, exports, support tickets, and related records.
• Notes data: note titles, structured content, author, visibility setting, linked client, supplier, invoice or project references, uploaded images, YouTube video references, and creation or update timestamps.
• Documents data: user-created documents and templates, imported PDFs, uploaded images, custom variables, recipient addresses and messages, delivery status, response fields, submitted signature names and consent, timestamps, and limited technical evidence associated with a completed signature.
• Forms data: form titles, questions, settings, published versions and sharing-link records; respondent answers and any contact information submitted; links to workspace client records chosen by authorized users; submission timestamps; and limited abuse-prevention records.
• Project and task data: titles, descriptions, client associations, status, priorities, dates, team and manager selections, task assignees, tags, subtasks, resource links, linked Notes, comments, and activity identifying the member and changes. These internal records follow workspace membership, plan, role, and Note visibility controls; project team and task assignments do not independently grant organization access.
• Time Tracking data: work dates, member identity, linked projects and tasks, manual and timer-recorded durations, timer state and timestamps, notes, tags, billable status, hourly rates and currency, invoice associations, billed status, record and week locks, and creation or update timestamps. These internal records follow workspace membership, plan eligibility, and role controls.
• Billing and payments: plan, seats, billing interval, billing contact, product and transaction identifiers, purchase and expiration dates, trial and renewal status, entitlement status, storefront and environment, cancellation, billing-issue, refund or revocation events, limited saved-payment-method metadata such as provider identifier, brand, type, last four digits, expiration, and status, connected-account and customer-membership status, renewal dates, payment method category, owner confirmations of externally collected payments, disputes, and risk signals. Stripe receives and stores full credentials for direct and customer-saved payment methods and eligible Online Checkout transactions through its components; FacturaOS does not receive or store the full card number or security code. Apple receives Apple Account and payment information for App Store purchases; FacturaOS and RevenueCat do not receive the full App Store payment credentials. If a workspace activates ATH Móvil Business, FacturaOS processes the merchant integration credentials and transaction information needed to connect to Evertec and initiate and verify supported invoice payments. For a manually recorded sale or membership payment, FacturaOS stores the business user's entry but does not receive independent proof of payment unless a supported provider event is also available.
• Device and usage: IP address, browser, device, operating system, application version, approximate region, pages or features used, timestamps, referral or campaign data, diagnostic logs, crash information, and privacy preferences.
• Optional Meta advertising attribution, only where configured and separately permitted: real Meta browser and click identifiers such as _fbp, _fbc, and a genuine fbclid; IP address and browser user agent; reviewed public-page and referrer context; consent preferences; and verified FacturaOS trial-start events with an opaque event identifier. These are limited acquisition signals, not workspace operational Customer Data.
• Mobile permissions you choose: contacts selected for import, photographs or files selected for upload, camera access, and precise location captured for a client address, route, business location, or other location feature.
• Communications: support messages, email-delivery status, survey or feedback responses, legal requests, and records of notices or consent.

3. Sources of information

We receive information directly from you; workspace owners and members; your device or browser; clients, invoice recipients, or membership purchasers interacting with a payment or checkout link; respondents using a business's public form; authentication, hosting, analytics, email, subscription-management, application-store, and payment providers; public sources; and integrations you choose.

If someone adds you to FacturaOS, sends you an invoice, or provides your information through a workspace, that business user is responsible for giving required notices and ensuring lawful collection.

4. How we use information

We use information to:

• Create accounts, authenticate users, operate workspaces, and provide requested features.
• Store, organize, generate, export, send, and display business records; operate client profiles, locations, service areas, catalogs, working hours, reports, and routing under customer instructions.
• Process FacturaOS subscriptions, validate App Store transactions, synchronize entitlements, manage seats and plan changes, process invoices and connected payments, support customer-membership checkout and renewal status, record owner-confirmed external collections and benefit redemptions, handle refunds where FacturaOS is authorized to do so, and provide billing support.
• Secure the service, prevent fraud and abuse, troubleshoot, monitor reliability, and enforce agreements.
• Provide support, send service communications, respond to privacy requests, and maintain audit records.
• Measure privacy-safe usage, attribution, performance, and product quality where optional analytics are enabled.
• Where configured and you separately permit it, measure and attribute FacturaOS advertising and help Meta optimize ad delivery using the limited optional advertising information described in Section 8.
• Comply with law, legal process, tax and accounting duties, and protect rights, safety, and property.
• Develop and improve features using aggregated, de-identified, or appropriately minimized information.

5. Legal grounds where required

Where applicable law requires a legal basis, we process information to perform our contract; follow your instructions; comply with legal obligations; pursue legitimate interests such as security, support, fraud prevention, service improvement, and business administration; protect vital interests; or based on consent. You may withdraw consent for future processing where consent is the basis, without affecting earlier lawful processing.

6. How we disclose information

We may disclose information in these circumstances:

• Within a workspace according to roles, permissions, invitations, and actions chosen by workspace administrators. For Notes, Only Me limits ordinary workspace access to the creator; All Team permits access by authorized workspace members.
• When you choose to load a YouTube video embedded in a Note, your browser sends the provider the video request and the network or device information needed to display it under the provider's policies. Merely saving the video reference does not load the embedded video.
• To recipients selected by a business when it emails a Document PDF or signature request. Unsigned PDF emails may include an attachment or a time-limited link to a private PDF; signature requests use a recipient link. A person with a link may be able to open it until it expires or the document is removed.
• When a business publishes a Form, anyone with its valid sharing link can view the published form content. The link does not provide access to stored response history. Responses are available under the owning workspace's permissions, and the business can choose to connect a response to a client record. The business determines the questions and is responsible for required respondent notices and lawful collection.
• To service providers and subprocessors that support hosting, databases, storage, authentication, analytics, diagnostics, email, support, billing, subscription-entitlement management, and security, subject to appropriate obligations.
• To Meta for optional advertising measurement, attribution, and ad-delivery optimization only where configured and separately permitted, using the limited information and controls described in Section 8. Meta's role and further processing depend on its applicable terms and privacy notices; it is not automatically a FacturaOS subprocessor.
• To RevenueCat for App Store transaction validation, subscription-entitlement synchronization, purchase restoration, lifecycle events, and related support.
• To Stripe, Evertec and ATH Móvil, banks, card networks, payment methods, and financial partners for direct subscription billing, connected accounts, customer-membership Online Checkout, merchant authentication, identity verification, fraud prevention, payment initiation and verification, recurring billing, settlement, refunds, disputes, and compliance.
• To Apple for App Store purchases, subscription management, refund processing, application distribution, and Sign in with Apple when you choose that service; or to Google or another authentication provider when you choose that login method.
• To professional advisers, auditors, insurers, financing sources, and transaction parties under confidentiality safeguards.
• To authorities or other parties when reasonably necessary to comply with law, legal process, protect rights or safety, investigate abuse, or enforce our agreements.
• In connection with a merger, financing, reorganization, sale, bankruptcy, or transfer of all or part of the business, subject to applicable law.

7. Billing, App Store purchases, connected accounts, and memberships

When you start an iOS in-app subscription, Apple collects the Apple Account, payment, device, storefront, tax, and transaction information needed to complete and manage the purchase under Apple's terms and privacy notices. FacturaOS receives limited product, transaction, subscription, renewal, cancellation, billing-issue, refund, revocation, environment, and entitlement information from Apple through RevenueCat. RevenueCat uses an app user identifier and that store information to validate purchases, restore access, and synchronize entitlement status on behalf of FacturaOS. Neither FacturaOS nor RevenueCat receives full App Store payment credentials or independently controls Apple Account charges, renewals, plan changes, cancellations, refund decisions, or refund timing; Apple handles those matters under its terms and privacy notices.

Stripe independently collects payment credentials, identity documents, tax identifiers, bank details, device information, and transaction information needed for its services. For an eligible customer membership sold through Online Checkout powered by Stripe, Stripe also receives the customer, price, recurring authorization, payment-method, invoice, renewal, cancellation, refund, and dispute information needed to manage that connected-business payment. Stripe may act as an independent controller for regulated payment, verification, fraud, and compliance purposes. Its privacy policy, connected-account terms, and checkout disclosures apply in addition to this Policy.

If a workspace activates ATH Móvil Business, FacturaOS sends Evertec or ATH Móvil the merchant credentials, business and invoice identifiers, amount, description, and transaction data needed to initiate, verify, reconcile, secure, and support the payment. Evertec's payment component may separately collect payer or phone, device, network, authentication, and risk information directly under its terms. Evertec and participating financial institutions handle the payment service under their terms and privacy notices and may act independently for those purposes.

Evertec webhook payloads may include payer name, email, phone number, item descriptions or metadata, device or network information, and transaction details. FacturaOS may receive those fields transiently but is designed to retain only the limited identifiers, status, amount, reference, and audit data needed to correlate and verify the payment.

FacturaOS receives payment and connected-account identifiers, readiness or restriction status, limited account and transaction details, callbacks, webhooks, and provider-lookup results needed to provide billing and payment features. We do not intentionally store full card numbers or card security codes. See https://terms.facturaos.com/en/payment-services, the ATH Business Terms and Conditions at https://ath.business/en/terminos, and the Evertec privacy notice at https://ath.business/en/politica_privacidad.

8. Analytics, optional advertising, cookies, and mobile diagnostics

FacturaOS may use Google Analytics for optional website and product measurement and Firebase Analytics and Crashlytics for optional mobile analytics and diagnostics. Our implementation is designed to avoid sending client names, invoice contents, contact details, addresses, search text, document contents, or full URLs containing record identifiers as analytics event values.

Optional Meta Pixel advertising tracking remains disabled unless the applicable dataset or Pixel is verified and the feature is configured. Where enabled, it requires separate affirmative advertising permission before Meta technologies load or events are sent. Permission for Google Analytics does not enable Meta tracking, and Meta permission does not change Google's disabled advertising-personalization settings. Declining optional advertising does not affect signup, checkout, trial access, or other product access.

With that permission, Meta may receive real _fbp and _fbc browser cookies or a genuine Meta click identifier (fbclid), IP address, browser user agent, reviewed non-sensitive public-page and referrer context, and limited verified trial-start events after checkout. Events use an opaque event identifier and may include a public plan, billing interval, or operating market. FacturaOS does not enable advanced matching or supply email addresses, phone numbers, client profiles, invoice or document contents, search text, private application URLs, authentication or checkout tokens, or raw user, workspace, subscription, or invoice identifiers for this tracking.

Meta may match these signals to activity on its services, measure and attribute advertising, and use them to optimize advertising and for other purposes permitted by its terms and privacy notices. These signals can be linked to a person, and attribution may be incomplete. Meta's privacy notice is available at https://www.facebook.com/privacy/policy/.

You can decline or withdraw advertising permission through the public site's privacy choices. Global Privacy Control (GPC), Do Not Track (DNT), and an applicable account opt-out, including turning optional product analytics off, take precedence over advertising permission. Withdrawing stops future optional Meta events and clears the 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. Browser controls and Meta's own privacy controls may also apply. See the Cookie Statement for these choices.

RevenueCat's iOS software development kit is a necessary subscription technology, not optional advertising or product analytics. It processes the app user identifier and limited App Store subscription information described above when the Apple purchase feature is configured or used.

Signed-in users may turn optional product analytics off in Account settings. Mobile users may use the corresponding privacy setting. Browser or device privacy controls may also apply. Necessary authentication, security, fraud-prevention, billing, entitlement, support, and service logs continue because they are required to operate and protect the service. See the Cookie Statement.

9. Optional client profile and precise location data

A business user may choose to store optional client birth information, gender, a profile photo, address, precise coordinates, and internal notes. FacturaOS provides fields and device controls for those records but the workspace owner determines why they are collected, who may access them, and how they are used. The business must provide any required notice, obtain consent or another lawful basis, respect device permissions, and avoid collecting information that is excessive for its purpose.

Precise location may be captured only after a user invokes a location feature and the device or browser grants permission. It may then be stored in the applicable workspace record and visible to authorized workspace members. FacturaOS does not use client birth information, gender, or precise location to infer characteristics for advertising. Individuals seeking access, correction, or deletion of workspace-controlled profile information should ordinarily contact the business that collected it.

10. Data retention

We retain information only as long as reasonably necessary for the purposes described, including the life of the account or workspace and any additional period needed for legal, tax, accounting, payment, security, backup, fraud-prevention, support, and dispute obligations.

Retention varies by category. Active Customer Data generally remains until deleted by an authorized user or the workspace is deleted. Removing a sent Document from the workspace list disables its recipient link but retains its frozen delivery snapshot, any imported or stored delivery PDF, and signature evidence for audit; retained files continue to count toward Documents storage. Drafts without a delivery may be deleted with their source files. Owned-workspace or account deletion removes Documents data subject to the limited retention and provider-cycle exceptions in the Account and Data Deletion Policy. Sold-membership term snapshots, redemption history, account, consent, billing, payment, abuse, and legal records may remain longer when needed for customer, accounting, tax, fraud, or dispute obligations. Backups and provider systems may take additional time to cycle out. We may retain aggregated or de-identified information that cannot reasonably identify a person.

Deleting a Note removes it from ordinary workspace access and prevents new signed links for its private images. The stored Note and images may remain until the workspace or the Note creator's account is deleted, subject to the Account and Data Deletion Policy. Image links issued before deletion can remain valid briefly until they expire.

11. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect personal information, including access controls, encrypted transmission, private storage controls, environment separation, logging, and provider security measures. No method is completely secure, and we cannot guarantee absolute security.

Workspace owners are responsible for user access, device security, exports, recipient addresses, and lawful handling after information leaves FacturaOS. Report suspected incidents promptly to privacy@facturaos.com.

12. Privacy choices and rights

Depending on your location and our legal role, you may request access, correction, deletion, portability, restriction, objection, or withdrawal of consent, and may appeal a denied request where law provides. You may also update many account and workspace fields directly, turn off optional analytics, and decline or withdraw optional advertising permission.

Send requests to privacy@facturaos.com. We may verify identity, authority, workspace role, and jurisdiction. If FacturaOS processes information for a business customer, we may direct you to that business or assist it in responding. Authorized agents must provide legally sufficient authority. We will not discriminate for exercising applicable privacy rights.

13. U.S. state privacy notice

The categories collected, sources, purposes, and recipients during the preceding 12 months are described in Sections 2 through 9. FacturaOS does not sell personal information for money. Where configured and separately permitted, the limited optional Meta advertising disclosure described in Section 8 may constitute sharing for cross-context behavioral advertising or processing for targeted advertising under applicable law.

Before that optional use, we provide a separate choice to permit or decline it. You can withdraw permission or opt out through the public site's privacy choices; supported GPC and DNT signals and an applicable account opt-out override permission. We will provide any additional legally required control before a changed use that creates a right to opt out of sale, sharing, or targeted advertising.

We use and disclose sensitive personal information only for permitted business purposes or as directed by a business customer, and not to infer characteristics for advertising. We do not use workspace operational Customer Data for Meta advertising.

14. International processing and transfers

FacturaOS and its providers may process information in the United States and other countries where they operate. Those countries may have different privacy laws. Where required, we rely on contractual protections, provider transfer mechanisms, consent, or another lawful transfer basis.

The Subprocessors and Other Providers page identifies current direct subprocessors and separately describes role-dependent or independently controlled services. Business customers needing additional transfer documentation may contact privacy@facturaos.com.

15. Children and restricted information

FacturaOS is not directed to children under 13 and is not intended for anyone under 18 to open an account. An optional birthday field for a business's client record does not make FacturaOS a service directed to children. We do not knowingly collect personal information directly from a child under 13. A business that records information about a minor is responsible for appropriate authority, notices, consent, minimization, and lawful service. Contact us if you believe a child submitted information directly to FacturaOS without appropriate authorization.

FacturaOS is not designed to store HIPAA-regulated protected health information, full payment-card credentials, or other specially regulated data unless we expressly agree in writing. Business users must avoid submitting restricted information and are responsible for their own legal obligations.

16. Changes and contact

We may update this Policy as services, providers, or laws change. The date above shows the latest revision. We will provide additional notice or consent for material changes where required.

Privacy questions and requests may be sent to privacy@facturaos.com or by mail to J.R.SOSA & CO. LLC, 2125 Biscayne Blvd, Ste 204 #24427, Miami, Florida 33137 US. General support is available at contact@facturaos.com.