Authentication
Customer and admin areas require authenticated sessions. Admin accounts can use multi-factor authentication where enabled.
SECURITY
Layered controls for customer access, business records, licensing data, and operational workflows.ضوابط متعددة المستويات لحماية وصول العملاء وسجلات الأعمال وبيانات التراخيص وسير العمل.
Customer and admin areas require authenticated sessions. Admin accounts can use multi-factor authentication where enabled.
Administrative, customer, support, and product workflows are separated by role and authorization checks.
Passwords are stored with server-side password hashing. Plain-text passwords are not stored by E31.
Sensitive operational secrets, mail credentials, and e-invoice archives are protected with encryption where configured.
Backup schedules depend on the deployment plan. Local deployments and hosted deployments can use different retention policies.
Important events such as login, activation, trial, support, and e-invoice actions can be recorded for review.
Security logs, rate limits, and activity records help identify unusual sign-in or request patterns.
Retention is scoped by customer agreement, legal needs, support requirements, and deployment model.
E31 can review logs, disable affected access, rotate credentials, restore backups, and coordinate remediation with the customer.
Security practices depend on deployment scope, hosting environment, customer configuration, user access policies, integrations, and support agreement. E31 can provide a security review before production rollout.