Security, privacy and data

Where your data lives #

Everything is in your hosting account: the database, nob_data/docs/ (uploaded documents, issued invoices and quotes, signatures), nob_data/backups/, nob_data/config.php (credentials and secrets, permission 0600) and nob_data/logs/. None of it is inside the web root, so nothing can be fetched by URL without logging in.

What leaves your server #

• To the license server: key, domain, fingerprint, version, integrity summary — once a day.
• To Google, only if you chose Google AI Studio: the text of documents being read, your questions to Savia, texts to draft or translate.
• To public registries you query: GUS (NIP lookups), the Ministry's biała lista, VIES, NBP rates, the Sejm's ELI API — no personal data of yours beyond the identifiers you look up.
• To Stripe, if configured: checkout sessions for your clients.
• E-mail you send.

Nothing else. There is no telemetry.

Access security #

Passwords hashed with Argon2id, optional TOTP two-factor authentication (strongly recommended), CSRF protection on every form, rate limiting on login, sessions stored outside the web root, security headers (CSP, HSTS, no framing), authenticated downloads of documents, an audit log of sensitive actions.

AI security #

Everything external that reaches the AI (documents, client messages, tool results) is wrapped as data with an explicit instruction that it is not to be obeyed. Inputs are normalised (invisible characters removed) and classic manipulation patterns are detected and logged. AI tools are a closed, read-only catalogue filtered by company. Drafts are sanitised before they reach a page.

Public pages #

Quote pages use unguessable tokens; acceptance forms carry signed tokens; client messages are rate-limited and never rendered as HTML. Only quote, payment-return and Stripe webhook routes are public.

Backups and restore #

Nightly, 30 days kept, downloadable by administrators. To restore on a new server: install NOB, then import the SQL dump and copy docs/ into the new nob_data/.

Exporting your data #

Ledgers, VAT register and KPiR export from their screens; every invoice has PDF and XML; the database dump in each backup is a complete export in open SQL. Your data is never held hostage.

Deleting #

To delete a company's data completely, remove its database rows and its nob_data/docs/<company-id>/ folder, or simply drop the database and folders when uninstalling. Backups older than 30 days are removed automatically.

NOB 0.9.0-beta.7 · Something unclear or wrong in this page? Write to biuro@nob.holapolska.pl.