DE · FI
ixnodes

ixnodes / Legal / security

Security & PCI compliance

Last updated: 26 May 2026

PCI DSS scope

ixnodes never stores, processes, or transmits cardholder data on infrastructure we operate. Card details are entered directly into Stripe Elements (an iframe served by Stripe's PCI Level 1-certified infrastructure) and a tokenised reference is the only thing that ever crosses the wire to us. This puts us firmly in scope of PCI DSS SAQ A — the lightest of the self-assessment questionnaires, appropriate to fully-outsourced e-commerce merchants.

Our SAQ A is reviewed annually and signed by ixnodes' managing director. We'll share the dated attestation under NDA with enterprise customers.

Encryption

  • In transit: TLS 1.2 minimum, TLS 1.3 preferred. We follow Mozilla's “intermediate” compatibility profile and rotate certificates via Let's Encrypt with 60-day renewal cadence.
  • At rest (control-plane database): Postgres data files live on encrypted LUKS volumes. Backups are encrypted with age before leaving the host.
  • At rest (customer VPS): we don't encrypt the underlying NVMe by default — the customer controls the VM and can enable full-disk encryption via cloud-init or post-install. For regulated workloads we recommend you do.
  • Secrets: application secrets (Stripe webhook keys, GoWallet HMAC keys, cookie-signing keys) are stored as systemd-creds-encrypted units, never as plain environment variables in the deploy manifest.

Export control on cryptography

ixnodes ships standard open-source cryptographic libraries (OpenSSL, libsodium via Node and the kernel's native KEM/AEAD primitives). We do not develop or export controlled cryptography under the EU Dual-Use Regulation (Reg. 2021/821), the U.S. EAR Cat. 5 Part 2, or the UAE Federal Decree-Law No. (28) of 2021. Customers running export-controlled software on top of our infrastructure are responsible for their own compliance.

Vulnerability disclosure

Report security issues to [email protected]. We acknowledge within 1 business day and target a fix-or-workaround commitment within 7 days for high-severity reports. We do not currently offer a paid bounty but we credit finders publicly on this page where they prefer that to private acknowledgement.

Our GPG fingerprint and security.txt live at ixnodes.com/.well-known/security.txt.

Breach notification SLA

If we discover a personal-data breach affecting ixnodes customers, we notify affected customers within 72 hours of becoming aware, per GDPR Art. 33(2) and UAE PDPL Art. 9. The notification will state the scope, the data categories involved, and the mitigation we've applied. Enterprise customers under DPA receive notification within 24 hours in addition to the customer-wide announcement.