Secure access
Passwords are cryptographically hashed, sessions are protected, and role-based authorization separates user workspaces from administrative functions.
Waraq uses layered safeguards to protect accounts, uploaded Arabic works, OCR text, translations, and reference material.
Passwords are cryptographically hashed, sessions are protected, and role-based authorization separates user workspaces from administrative functions.
Projects and reference pairs are associated with their owners. Application policies prevent users from opening or modifying another user work.
Production deployments should use HTTPS so files and account data are encrypted while traveling between the browser and Waraq.
Files are processed only by services required for OCR, translation, storage, and platform operation. Access should follow least-privilege principles.
Security depends on maintained infrastructure, restricted administrative access, software updates, backups, monitoring, and incident-response procedures.
If you believe you have found a security issue, report it privately through the Waraq contact form with enough detail for investigation.