Security

Built for private artist business data.

TourLedgers is designed around protected accounts, server-side sessions, D1 data storage, and careful handling of buyer-facing reports.

Password handling

  • TourLedgers uses PBKDF2-SHA256 password hashing with per-user salts.
  • Plain text passwords are not stored by the application.

Sessions

  • Login sessions use HTTP-only cookies so client scripts cannot read the session token.
  • Production cookies are marked Secure and SameSite=Lax.

Protected routes

  • Dashboard and admin routes require a valid session before private app data is shown.
  • Private beta deployments should keep Cloudflare Access or Pages password protection active for additional control.

Data storage

  • Account and product data are stored in Cloudflare D1.
  • File storage uses Cloudflare R2 through the ASSETS_BUCKET binding.

Operational safety

  • Authenticated API routes check ownership before returning or changing account data.
  • Admin APIs require Philip-only administrator access.

Responsible disclosure

  • Report security issues to Philip@philipstengelpresents.com with a clear description, affected route, browser, and steps to reproduce.
  • Do not access, alter, or disclose data that does not belong to your account.