Security & Data Protection

Security & Data Protection

DubLedger uses standard web security controls for sessions, transport, and access.

Authentication and sessions

Session management

• Staff sessions use HMAC-signed tokens via the Web Crypto API.
• Sessions expire after 30 days.
• Shopper sessions are separate from staff sessions.
• Magic-link login tokens for shoppers expire after 30 minutes.

Password policy

• Minimum password length is configurable.
• Requirements for uppercase, lowercase, numbers, and symbols can be enabled.

Network security

CSRF protection

• State-changing requests validate the origin.
• Webhooks are exempt and use HMAC signatures instead.

Rate limiting

• In-memory IP-based rate limiting.
• Default: 60 requests per minute.
• Configurable per endpoint.

Security headers

• Content-Security-Policy (CSP).
• Strict-Transport-Security (HSTS).
• X-Content-Type-Options.
• X-Frame-Options.
• Referrer-Policy.
• Permissions-Policy.

WWW redirect

• www.dubledger.com traffic redirects to dubledger.com with a 301 redirect.

Data encryption

At rest

• Database data is encrypted by the hosted provider.
• API keys and secrets are encrypted with AES-256.
• Sensitive keys are never displayed in full after entry.

In transit

• All connections use HTTPS (TLS 1.2+).
• WebSocket connections use WSS.

Access controls

Role-based access

• Employee permissions are stored as booleans and enforced in API routes.
• Location access limits employees to assigned locations.

What is not included

• Two-factor authentication (2FA) is not implemented.
• There is no separate immutable audit-log feature; transaction records are the operational record.
• Because DubLedger does not process live payments, PCI DSS scope is not applicable.