Access Control Policy

Last updated: May 2, 2026

This Access Control Policy describes how Tradesera limits access to production assets, administrative systems, sensitive data, service credentials, and vendor tools. This policy supports Tradesera's Information Security Policy and applies to employees, contractors, administrators, service accounts, and third-party systems used to operate the platform.

1. Access Control Principles

• Access is granted based on least privilege and business need.
• Production access is limited to authorized personnel and approved service integrations.
• Administrative access is separated from ordinary customer or trader access.
• Access to sensitive systems is reviewed periodically and removed when no longer needed.

2. Role-Based Access Control

Tradesera uses role-based access control within the platform. Standard users are assigned trader-level access, while administrative functions are restricted to users with an admin role. Administrative endpoints and internal operations screens are protected by authenticated sessions and role checks.

3. Production and Vendor Access

Access to production infrastructure, source code repositories, DNS, database services, email delivery, payment providers, payout providers, and other operational vendors is limited to authorized administrators. Where supported by the provider, multi-factor authentication is enabled for administrative access.

4. Non-Human Authentication

Tradesera uses provider-issued API keys, OAuth tokens, webhook secrets, deployment credentials, TLS certificates, and environment variables for non-human authentication between services. Service credentials are stored in managed secret or environment-variable systems and are not intended to be exposed in public repositories, client-side code, screenshots, or support communications.

5. Multi-Factor Authentication

Tradesera supports email-based multi-factor authentication for customer portal access and sensitive actions. Tradesera also uses multi-factor authentication for critical administrative systems where available, including infrastructure and vendor dashboards that support production operations.

6. Access Reviews

Tradesera performs periodic access reviews for production systems and sensitive vendor accounts. Reviews may include the Tradesera admin dashboard, Render, GitHub, Cloudflare, Resend, payment processors, payout providers, database access, and other systems that can affect customer data, payment workflows, or production availability.

Access reviews are intended to confirm that each active user, role, credential, service token, and integration remains necessary and appropriate for current operational responsibilities.

7. Deprovisioning and Access Changes

When personnel, contractors, vendors, or service integrations no longer require access, Tradesera manually removes or modifies access in the relevant systems. Access may also be removed or restricted when suspicious activity, role changes, termination, vendor changes, or security risk is identified.

8. Service Credential Rotation

API keys, webhook secrets, encryption secrets, and service credentials may be rotated when required by a vendor, when compromise is suspected, when access is no longer needed, or as part of operational maintenance. Credentials are replaced carefully to avoid service disruption while reducing unauthorized-access risk.

9. Logging and Auditability

Tradesera records selected authentication, registration, payment, webhook, wallet, payout, and administrative events to support fraud prevention, security review, troubleshooting, and compliance. Access to logs is limited to authorized personnel and systems based on operational need.

10. Policy Review

Tradesera reviews this Access Control Policy periodically and updates it as the platform, vendors, personnel, integrations, and security practices evolve.

11. Contact

Access control or security questions may be sent to [email protected].