Privacy Policy
Last updated 2026. This policy explains how PageInvoice handles personal and business data on this invoicing install.
1. Who runs this copy
PageInvoice is software that stores records on the machine or host where it is installed. The operator is the Dev who set up this copy. They decide hosting, backups, and mail. If you are a user on someone else’s install, that operator is the party that holds your data.
2. Data we keep
Account: name, username, email, password hash (never the raw password), role, and optional avatar. Profile: business name, contact, address, currency, tax default, invoice prefix. Clients: name, company, email, phone, address, notes. Catalog: offers (products and services), categories, rates, draft/active/archived status. Invoices: numbers, line items, tax, dates, status, paid time, notes. Expenses: SN, title, description, amount, category, vendor, method, dates, status. Support notes you send. Session cookies so you stay logged in. Optional last-magic marker for Dev on this machine only.
3. Why we keep it
To run your ledger: create and send invoices, track due and paid, record expenses, report income versus spend, remind Dev of overdue invoices by email when configured, and let the assistant answer questions about your own books. We do not sell client lists or invoice histories.
4. Client data you enter
When you add a client, you are the controller of that person’s data. You must tell them if the law requires it, keep only what you need to bill and support them, and delete or correct records when they ask—using Settings, Clients, and invoice tools, or by asking Dev. PageInvoice retains those records until you or Dev remove them from this install. Retention length is yours to set for tax and contract rules in your country (often years after the last invoice).
5. Who can see what
A logged-in user sees only their own clients, invoices, expenses, and catalog. Dev can see every account on this install for operation. Guests see public pages and the assistant greeting; they cannot load your books. We do not share one user’s records with another user.
6. Mail and the assistant
If SMTP is set, invoice PDFs and overdue digests go through that mail host to the addresses you choose (client email, Dev email). Pay Invoice opens Stripe Checkout. Stripe processes the card and we never store card numbers. If the assistant is on, xAI (or the configured model host) receives your question and a scoped snapshot: your profile, clients, invoices, expenses, and totals—not passwords, keys, sessions, or other users. Dev’s snapshot may include all users on this install. Do not type secrets into the assistant.
7. Cookies and sessions
A strict same-site session cookie identifies you after login. It lasts up to seven days or until you Exit. Magic links expire in minutes and are not meant to be forwarded. We do not use advertising cookies.
8. Storage and security
Records live in this install’s data store. Avatars sit as files on the host. Passwords are hashed. Traffic uses browser security headers. No method is perfect. Dev should restrict host access, keep backups private, and use HTTPS on a public domain. Deploy keys and model keys must never be published.
9. Your rights
You may access and update your profile in Settings, correct client and invoice data in the app, download or print invoices, and ask Dev to delete your account where the install allows. Clients of yours should contact you first; you can then edit or remove their row. If required by law, Dev may keep copies for disputes, tax, or security.
10. Children
PageInvoice is for business use. It is not directed at children under 16. Do not store a child’s personal data unless you have a lawful reason and the right consents.
11. Changes and contact
This page will be updated when the product’s data practices change. Continued use after a change is acceptance. Privacy questions: Support or [email protected].