Built for controlled client access and responsible data handling.

Bring your own data

RiskAtlas is designed as a bring-your-own-data analytics platform. Client portfolio files remain in client-controlled storage environments. The platform stores connection configuration, model artifacts, chart definitions, validation outputs, and operational metadata required to run analytics workflows.

What we store

• User account credentials (hashed) and access metadata
• Portfolio, datasource, model, and chart configuration
• Training, validation, and analytics run results generated inside the platform
• Website contact and access-request submissions

What we do not store by default

• Full copies of client raw portfolio files on RiskAtlas infrastructure
• Payment card or banking information through this website

Access control

Client application access is provided through authenticated sign-in. New users are onboarded through a reviewed access-request process. Administrative approval is required before account registration.

Transport security

Public website and client application traffic is served over HTTPS. Credentials and session tokens should only be transmitted through the official RiskAtlas client application domain.

Operational practices

Production services run on isolated infrastructure with restricted administrative access. Database backups, monitoring, and change control are managed as part of normal platform operations.

Questions

For security or data-handling questions, contact us through the contact form.