Privacy Policy

Account data: your name, work email address, role and department, the account's status, and a password stored only as a salted hash. A company's administrators can also record employment information such as job title, manager and start date.

Sign-in data: one-time sign-in codes and links, which devices you have trusted, and — where an account requires it — a time-based authenticator secret and single-use recovery codes.

Usage data: counts of the records each metre bills (for example active accounts, attendance punches, stored items), rendered into monthly invoices. These counts are aggregate.

Technical data: the audit trail of changes made through the app (who changed what, when), and server logs containing the request, the account and an address, kept for security and troubleshooting.

To provide the service and keep accounts secure (performance of the agreement), to invoice for usage (performance of the agreement and our legal obligations), to detect and prevent abuse (our legitimate interest in a secure service), and to answer support requests. Sales tax on card payments is handled by our merchant of record, not by us.

Records your company enters — customers, invoices, stock, payroll-adjacent attendance data, files — are processed on the company's instructions. The company decides who inside it can see them, and it is the company's controller position that governs them. We access them only to run and support the service, and access by our own staff is limited and audited.

We share data with the suppliers that run the platform, under contract and only as far as needed: our hosting and database provider, our mail provider (which delivers sign-in codes and service notices), and Paddle, which acts as merchant of record for card payments and therefore receives the billing contact and transaction details for those payments. We do not sell personal data, and we do not use it for advertising.

A company's workspace can be linked to another company it trades with — a supplier or a customer — through an explicit, revocable connection. Only the documents both sides agree to exchange cross that link; nothing else is shared.

The app uses browser storage for the things that make it work: a session token for the signed-in user, a first-paint cache of that person's table preferences, and a record of their display choices.

The public marketing site offers optional analytics through Google Analytics 4. It loads only after you press Accept analytics, and never inside a signed-in workspace. If you decline, no analytics script is loaded and the site works normally. You can change the decision at any time with Cookie settings in the footer. We use the measurement to understand which pages are read; we do not use it for advertising, and we do not share it with an ad network.

Account data is kept while the account exists. Audit records and invoices are kept for as long as the law requires them to be kept for accounting and tax. Server logs are kept for a short operational window. When a workspace is cancelled it becomes read-only for 30 days so it can be exported, and is then deleted; backups roll off on a short schedule after that.

Subject to the law where you are, you can ask for a copy of your personal data, ask for it to be corrected or deleted, object to a particular use, or ask for it in a portable form. Write to admin@nxta.app. A request about records inside a company workspace is normally handled by that company; we will help them.

A material change to this policy is notified by email to workspace administrators before it takes effect, and the effective date above changes with it.

Privacy questions and requests: admin@nxta.app. General contact is on the contact page.