Data & security
KSeF Kit touches two sensitive things: your invoices and your KSeF access.
What we store
- Stripe invoices and credit notes — we store the finalized invoice payload as an immutable source document. We never mutate it after acceptance; each send attempt is its own record.
- Company profile — the NIP, name, and address from onboarding. These become the seller details on the FA(3) invoice.
- KSeF connection — your KSeF token or XAdES material (certificate + private key), the chosen environment (TEST/PROD), and the connection status.
- UPO — the signed official receipt for every accepted invoice, plus the KSeF number issued.
We do not store card details. Subscriptions run through Stripe Billing — payments never pass through us.
How we protect tokens
In our database your KSeF token and certificate with private key are encrypted at rest (Active Record Encryption). If you connect through the Stripe app, the token lives in Stripe's Secret Store instead and the database only tracks status, method, and environment.
The secret fields in connection settings are write-only — the form always renders them blank. Leaving a field blank will not overwrite the stored secret, so routine edits can't accidentally wipe a working token. When you switch authentication method, we discard the other method's material so an unused secret never lingers encrypted in the row.
TEST is completely safe
The TEST environment is the Ministry of Finance sandbox: no legal effect whatsoever. An invoice filed to TEST does not enter the official record.
That's why:
- The environment choice is the first and deliberate step of connecting, with TEST preselected.
- Switching to PROD requires an explicit confirmation — these are irreversible legal effects.
- The app clearly marks whenever you're on TEST, so you never confuse environments.
Details: Connecting KSeF.
Account isolation
Every account is a separate tenant. One account's invoices, corrections, connections, and UPOs are tightly isolated from every other — there's no way to see another account's data.
Error monitoring
When something breaks, the hosted edition reports the error to Sentry so we can fix it. Those reports are deliberately thin: the exception and its stack trace, plus identifiers — your account id, the plan, the KSeF environment, the Stripe invoice id, the KSeF number, the filing status.
They never include your KSeF token or XAdES material, your Stripe keys, the invoice payload, the UPO, or buyer names, addresses, and NIPs. Those are stripped before a report leaves the server, and request bodies, form parameters and cookies are never collected at all. The self-hosted edition reports nothing unless you configure your own Sentry.
Want full control?
In the self-hosted edition you keep everything yourself: the app, the database, and the keys. See Self-hosting.