Passwords are not stored in readable form
Treata account passwords are stored using PHP password hashing rather than as plain-text passwords. Account sessions use server-side controls and can be invalidated when credentials change.
Security & Data Protection
Protecting access, information, and trust across Treata Scholars.
Our security approach is based on proportionate technical controls, restricted administrative access, careful handling of account and support data, and transparent communication about what our systems do and do not claim.
Treata ScholarsSecurity
Our approach
Security is part of the publishing infrastructure
Academic platforms handle identities, editorial communication, support requests, and links to external journal systems. We aim to reduce unnecessary exposure while keeping access controls understandable and maintainable.
Administrative areas are role restricted
Administrator and internal account functions require authenticated access. Public users cannot self-assign Administrator or Journal Staff roles.
Anti-abuse controls protect public entry points
Public forms use layered anti-spam measures such as honeypots, rate controls, and Cloudflare Turnstile where it has been configured.
Authentication state is handled deliberately
Login sessions use secure cookie settings where HTTPS is available, HTTP-only cookies, SameSite controls, session regeneration, and session-version invalidation.
State-changing account actions use CSRF protection
Account and administrative forms use anti-CSRF tokens to reduce unauthorized cross-site form submissions.
Application data is separated from ordinary public pages
Account application files and ticket-storage areas use server access restrictions. Sensitive configuration is not intended to be served as public website content.
Data handling
Collect what is needed for the service
Account information is used for authentication, role management, profile functionality, and Treata Scholars services. Support-ticket information is used to route, investigate, and respond to the request. Users should avoid submitting passwords, authentication codes, or unnecessary sensitive information through ordinary support channels.
Profile privacy
Public profile information is separated from private account information
The academic profile system includes visibility controls for profile fields. The account login email is not automatically treated as a public contact address, and private telephone information is not intended for public display.
Transport & hosting
Use secure website connections
Treata Scholars should be accessed over HTTPS. Hosting-level transport security, server maintenance, backups, and infrastructure controls also depend on the hosting environment and its configuration. We do not describe those controls as a certification unless the relevant certification has actually been obtained.
Third-party security services
External protection can be used where appropriate
Treata Scholars can use Cloudflare Turnstile on public forms to distinguish legitimate users from automated abuse. When a third-party security service is enabled, that service may process technical verification data needed to perform the security check.
Security reporting
Report a suspected security issue responsibly
If you believe you have identified a security problem, contact Treata Scholars with the affected URL, a concise description, and steps that reproduce the issue when safe to do so. Do not access, alter, retain, or disclose data that is not yours, and do not perform destructive testing.
Security contact: admin@treatascholars.com or the support ticket system.
Transparency
What this page does not claim
Treata Scholars does not claim ISO 27001, SOC 2, PCI DSS, or another security certification solely because technical safeguards are implemented. If a formal certification, audit, or independent assurance is obtained in the future, it should be identified separately with its actual scope and status.