Security at SCADALGERIA
Security is built into how SCADALGERIA is designed to operate. We give teams controlled access, clear accountability, and dependable continuity across the systems they supervise. SCADALGERIA is pre-launch, and we are transparent about the principles that guide the platform.
Scope and status
This page covers the public SCADALGERIA website and platform. The platform is pre-launch, and our security practices and documentation will continue to mature as it moves toward deployment and independent assessment.
Controlled access
Role-based permissions and authentication controls are designed to help ensure that people reach only the workspaces and actions assigned to them. Teams stay in control of who can view information, make changes, and participate in each operational context.
Clear accountability
Important activity is designed to remain traceable. This gives teams the context to understand changes, review operational decisions, and maintain confidence in how their systems are supervised.
Continuity by design
SCADALGERIA is designed to respond carefully when trust, entitlement, or connectivity conditions change. Local buffering and controlled recovery are intended to help teams preserve operational continuity and avoid acting on stale or unreliable information.
Supervision with clear boundaries
SCADALGERIA is supervisory software. It works alongside independent plant safety systems, emergency shutdown systems, and the engineering and operational controls required for each site. Clear boundaries help teams use the platform with the right expectations and responsibilities.
Report a security concern
If you identify a security concern affecting SCADALGERIA, contact us using the address below with a clear description, affected page or component, reproduction steps, and potential impact. We aim to acknowledge good-faith reports within five business days.
Responsible research
We welcome responsible, good-faith research that respects privacy and avoids disruption. Please do not access another person’s data, impair availability, use social engineering, or test accounts and systems you do not own. Do not test physical equipment, plant networks, PLCs, HMIs, operational control systems, or production environments. Security testing must remain limited to assets you own or are explicitly authorized to assess, and must never affect live operations. Stop testing if requested by SCADALGERIA.
Updates
We may update this page as the platform, our disclosure process, and our security practices evolve. Last updated: 25 August 2026.