Security at Darkstar

Last updated: October 30, 2026

1. Principles

Darkstar holds order, customer, subscription, and payout-relevant data for ecommerce merchants. The security model has three rules:

  • Card data belongs to processors. We keep cardholder data out of our database so a Darkstar incident cannot expose card numbers.
  • Least privilege by default. Every dashboard user gets a scoped role; every API key gets a scoped permission set.
  • Measurable, boring controls. HTTPS, HSTS, CSP, bcrypt, rate limiting, audit logs. No security theater.

2. Data protection

In transit

Every page and API call is TLS 1.2 or higher. Strict-Transport-Security is set with a two-year max-age, includeSubDomains, and preload, so browsers refuse to talk to Darkstar over plain HTTP.

At rest

The production database is PostgreSQL with encryption at rest, hosted on Railway. Processor API keys and secrets live only in server-side environment variables and are never sent to the browser.

Card data

On processor-hosted paths (Whop, Stripe), card fields are collected by the processor and Darkstar stores only tokens and display metadata. On merchant-gateway (NMI) stores, Darkstar stores card numbers encrypted at rest, as the store's service provider, with access controlled and logged. See PCI DSS Compliance for the full matrix.

3. Application security

  • Content-Security-Policy: operator surfaces use a per-request nonce with strict-dynamic; API responses ship default-src none; shopper surfaces allow only what checkout needs (processor iframes and merchant pixels).
  • Framing: dashboard and checkout deny or restrict cross-site framing to prevent clickjacking.
  • Session cookies: httpOnly, Secure, SameSite=Lax JWTs; 2FA available on operator accounts.
  • Passwords: bcrypt with cost factor 12.
  • Rate limiting: login and auth endpoints are rate-limited per IP with automatic lockout windows.
  • Injection: all database access is through a typed ORM with parameterized queries; no raw SQL.
  • XSS: merchant-supplied HTML code blocks are sanitized (scripts, event handlers, and javascript: URLs stripped) before render.
  • SSRF: server-side proxies are authenticated and scoped; AI clone and statement-studio proxies require per-job tokens.
  • Secrets hygiene: processor credentials stored per store, referenced server-side only.

4. Access control

Access to production is limited to the Darkstar team members who need it, on a least-privilege basis. In the product, every merchant controls:

  • Team members and their roles per store.
  • API keys with scoped permissions and revocation.
  • Audit logs of consequential actions.

Internal access to merchant data is logged. On processor-hosted paths, card data exists only as processor-owned tokens. On merchant-gateway stores, stored card data is encrypted and access is restricted to authorized Darkstar personnel on a need-to-know basis (supporting charges, rebills, recovery, and requested exports), and every export is logged.

5. Hosting and infrastructure

LayerProviderNotes
Application hostingRailwayIsolated environments, encrypted networking
DatabasePostgreSQL on RailwayEncryption at rest, automated backups
Checkout domainsDarkstar pay domains on RailwayHSTS preload, TLS 1.2+
Card processingWhop, Stripe, NMILevel 1 validated service providers
EmailResend / ZeptoMail (merchant choice)Transactional email only

6. Monitoring and uptime

Checkout availability is measured externally every minute, and results are published on the SLA page, including the credit table when a month misses the 99.9% target.

Application errors are surfaced to the team in real time. Failed order-sync jobs (Shopify mirror, tracking sync) retry automatically and are surfaced in the Orders page rather than failing silently.

7. Vulnerability disclosure and incidents

Report a vulnerability

Email security@darkstarpay.com with details and reproduction steps. We acknowledge within 72 hours and keep you posted until it is fixed. Please avoid automated scanning that could degrade checkout for live merchants.

Incident notification

If a confirmed incident affects merchant or buyer data, we notify affected merchants within 72 hours with scope, data affected, and remediation. On processor-hosted paths card numbers live only in processor vaults; on merchant-gateway stores, stored card data is encrypted at rest.

8. What we ask of merchants

  • Keep your Darkstar dashboard credentials private and enable 2FA.
  • Rotate processor API keys on a schedule and when staff leave.
  • Confirm your connected processors' PCI status annually (see the PCI page).
  • Never collect card numbers on your own storefront before the Darkstar handoff.
  • Use HTTPS on your storefront; the checkout requires it.