Security

Security choices built into the workflow.

File Tools Platform is designed to keep ordinary file work direct and limited in scope. These measures describe the current application, not a guarantee that no system can ever be compromised.

HTTPS and protected sessions

Production requests can be forced over HTTPS. Signed-in sessions use HTTP-only cookies, SameSite protection, strict session settings, CSRF tokens, and session ID regeneration after authentication-sensitive changes.

Browser-first processing

Most PDF, image, and utility tools process files in the browser. Those originals are not uploaded to this application. Server-backed conversion tools are separate and are identified by their workflow.

Payments

Online payments can use Paystack. Payment verification is performed server-to-server, and the application stores transaction records rather than raw card details.

Account protection

Passwords are stored as one-way hashes. Password reset links use hashed, single-use, time-limited tokens. Administrative actions are permission-checked server-side and recorded in the activity log.

Report a suspected security issue through Contact rather than attempting to access another account or bypass a control.