Security

Duebill needs to read your invoices and create claim invoices. It asks for nothing more, and keeps what it holds for as short a time as it can.

The Stripe key

Only restricted keys (rk_live_ or rk_test_) are accepted. A full secret key is refused with instructions.
Permissions: Invoices: Write (read overdue invoices and create the separate claim invoice), Customers: Read (show which customer each claim belongs to). Everything else stays at None. If a key can do more, Duebill warns you to narrow it.
Keys are encrypted at rest with AES-256-GCM and masked in every log line.
Disconnecting deletes the key immediately, in the same transaction as its settings.

Only separate claim invoices, each marked with its claim id. Your original invoices are never updated, voided or marked.
Every Stripe call carries an idempotency key, so a retry can never create a second claim.
Automatic sending is off by default and needs a second confirmation. A global kill switch can stop all automatic sending at once.
Partial payments, refunds after payment and invoices marked paid by hand always go to manual review.
Every approval, skip and send is written to an audit log: who, when and how much.

No passwords: sign-in is a one-time e-mail link that expires in 15 minutes and is stored only as a hash.
Session cookies are HttpOnly, Secure and SameSite; every form post must come from this site.
Hosted in the EU, served over HTTPS only. Daily encrypted-key database backups are kept for 7 days.

E-mail support@atesensoftware.com. Security reports are answered within two business days.