Terms of use

An invoicing tool. It creates invoices, quotes, retainer templates and payable records; it totals them; it generates PDFs; it sends emails when you ask it to; and it shows you the balances your own entries produce.

You are responsible for the accuracy of everything you enter, for the tax treatment of your own work, and for collecting payment from your own clients. FluxPay does not move money: it records payments you tell it about.

Not an accountant, a bookkeeper, a lawyer or a tax adviser, and not a payments processor. It does not hold client funds, it does not make lending decisions, and it cannot tell you whether a figure is tax-deductible in your jurisdiction. Consult a qualified professional for those.

Keep your sign-in credentials secure. Activity under your account is your responsibility unless it was caused by a defect in the service. You are responsible for the accuracy of the email addresses your share links and emails are sent to.

FluxPay is in public beta and free to use. There is no subscription, no trial countdown, and no feature held behind a payment wall. No paid plan is active or purchasable.

Beta means the software can change without notice, data can be migrated between versions, and features described in the product may be renamed or withdrawn. Export anything you need before a change lands.

There is no service-level agreement, no uptime commitment and no response-time promise. There is no support desk during the beta.

The service depends on third parties, and it names them rather than disclaiming them in the abstract: Firebase for authentication, database, storage and functions, Google Fonts for typography, and an outbound email provider for invoice, quote, share and reminder messages. Each can change, throttle or fail independently of this application. Where business continuity matters, keep your own exports.

This is not yet an enforceable agreement. It names no legal entity, no registered address, no governing law and no jurisdiction, because none has been established for this project and inventing them would create obligations against a party that does not exist. Those are the open items, and they will be filled in before any paid plan becomes purchasable.