Fintex · User Testing, LLC
PRIVACY POLICY
This is a company books system. The records in it belong to User Testing, LLC. Access is a privilege, not a personal account, and it does not create a consumer privacy relationship with the people who sign in.
Effective Aug 31, 2026
Who this covers
User Testing, LLC (“we,” “us”) operates Fintex as a single-tenant bookkeeping and invoicing application for our own business. This policy describes information processed in that application: identity used to sign in, the books themselves, stored files, and the audit trail of who changed what.
Fintex is not a consumer product, a public website, or a marketplace. People who sign in do so as our staff, contractors, advisors, or other invitees. Customers, vendors, employees, and other parties whose details appear in the books are not “users” of Fintex; their information is business-record data we keep in order to operate, invoice, pay, and retain books.
What we collect
| Kind | Examples | Source |
|---|---|---|
| Sign-in identity | Email address, display name, provider subject identifier, and that the provider marked the email verified | Google or Microsoft when you sign in. We do not store a password. |
| Access records | Role (Owner, Staff, or Viewer), invite history, allowed email domains, last activity, revocation | This application, configured by an Owner |
| Books and documents | Customers, vendors, people, employees, invoices, bills, payments, credits, expenses, journal entries, reports, schedules, and related memos | Whoever has access and enters or generates them |
| Stored files | Contracts, receipts, and other files attached to records | Whoever uploads them |
| Audit trail | Who changed which record, when, and the before-and-after values we retain for that change | Written automatically on every successful save. Contact details in the log are shortened; a tax ID is not written to the log at all. |
| Technical data | IP address as seen by the proxy, request path, method, and a request identifier | The HTTP request itself, used to operate and secure the service |
On a local (unsigned-in) copy, there is no sign-in identity. The books, stored files, and audit trail still exist and are attributed to the local owner of that installation.
How we use it
We use this information to run our books, authenticate people we have authorized, attribute work, keep an audit trail, take backups, restore a copy we control, host the application, and meet recordkeeping, tax, insurance, and legal duties. We may also use it to investigate misuse, enforce the Terms of Use, and defend our rights.
We do not use Fintex data to advertise. We do not sell personal information. We do not share it with data brokers. There is no “personalized ads” setting because there are no ads.
How long we keep it
The books are business records. We keep them for as long as we need them to operate the business and to satisfy tax, insurance, contract, and other legal retention rules — typically at least seven years, and often longer. Party records (customers, vendors, employees, people) are retired, not deleted. Retiring keeps the row and its history. That is a product rule, not a setting, and a privacy request does not override it.
The audit log is kept for the retention period configured for this instance (seven years unless an Owner has set a different period, including keep-forever). Entries inside that window cannot be edited or removed. Stored files sit with the books and follow the same backups. Backups exist so a restore is possible; a backup is not a second live copy we edit on request.
When we revoke a person’s access, we keep the account row and the audit history that names them. We do not erase the work they did in the books.
What you can ask for
If you sign in, you can ask us to confirm the email and role we have on file for you, or to revoke your own access. You do not have a right, as against User Testing, LLC, to a copy of the books, an export of customers or documents, deletion of records you entered, or deletion of the audit trail. Those records are ours. An Owner may export or restore a portable bundle of this instance; that is an operator function, not a user right.
If your personal details appear in the books because you are a customer, vendor, employee, or other party — not because you sign in — you may write to us using the contact below. We will consider a correction of contact details we actually control. We will not delete a party record, an invoice, a payment, or any other bookkeeping document because someone asked. Legal retention and the integrity of the books come first.
Nothing in a consumer-privacy statute that does not apply to this internal business system is waived into existence by this page. Where a law does apply and cannot be limited, we will meet that law and nothing more.
Security
The application binds to this machine only. Hosted public access is a reverse proxy with TLS. Sign-in, when enabled, is OpenID Connect — we never store a password. Writes are same-origin checked and, in hosted mode, carry a per-session token. We take backups of the books and stored files. None of that is a guarantee. Transmission and storage carry residual risk. Use of Fintex is at your own risk, as the Terms of Use say.
Children
Fintex is not directed at children. We do not knowingly collect sign-in identity from anyone under 16. If we learn that we have, we will revoke that access.
Changes
We may change this policy by publishing a new version at /privacy. The effective date at the top is the date that version took effect. Continued access or use after that date is acceptance of the new policy. We do not have to notify you individually.
Contact
Privacy questions go to User Testing, LLC, SC. That is also the address for any legally required privacy notice.
The companion document is the Terms of Use.