FINUXIPrivate betaReturn to sign in

Trust and data use

Privacy Policy

This policy explains what FINUXI processes, why it is needed for the accounting workflows you request, and the controls that remain with you.

Effective August 30, 2026

1. Scope

This policy applies to the FINUXI private beta, its hosted application, and the accounting integrations you choose to connect. FINUXI is designed as an organization-scoped accounting workspace; one organization’s records are not intentionally made available to another organization.

2. Information we process

We process account and organization information, membership roles, accounting records, transactions, documents, imports, review decisions, reports, and audit events that you provide or create in FINUXI.

When you connect Gmail, FINUXI may read email metadata, message content, and attachments needed to find vendor invoices for the workflow you request. Gmail access is read-only: FINUXI does not use that permission to send, edit, or delete email. When you connect QuickBooks, FINUXI reads the accounting records needed for deterministic comparison and displays the resulting evidence for your review.

3. How information is used

We use information to authenticate users, provide requested accounting workflows, protect tenant boundaries, detect workflow failures, generate user-approved reports, maintain audit evidence, and improve the reliability and security of the private beta. We do not sell connected-account data, use it for advertising, or use Google user data to train general-purpose AI models.

4. Google API data

FINUXI’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only to provide or improve the user-facing Gmail invoice workflow that you initiate. Human access is limited to security, support, legal, or reliability needs and only when permitted by that policy.

5. Service providers and security

FINUXI uses hosted infrastructure and integration providers to operate the private beta. Credentials and provider tokens are kept in server-side systems rather than the browser bundle. We use access controls, private document storage, row-level database policies, audit records, and encryption provided by our hosting platforms. No system can guarantee absolute security, but suspected unauthorized access is investigated and contained.

6. Retention and your choices

Beta data is retained while it is needed to provide the service, preserve required accounting and audit evidence, meet legal obligations, or resolve security issues. You may disconnect an integration or request access, correction, export, or deletion by contacting us. Some audit or accounting records may need to remain where deletion would conflict with legal, security, or integrity requirements.

7. Contact and changes

Questions or privacy requests may be sent to getfinoxa@gmail.com. We may update this policy as the beta changes and will revise the effective date when we do.