Security approach
Skarion aims to use practical, layered safeguards appropriate for a public career-services website. Current protections include input validation, request-size limits, abuse throttling, bot verification for public forms, restricted browser permissions, security-focused response headers, and controlled server-to-server form handoffs.
Protecting form submissions
Public contact and assessment forms use multiple anti-abuse controls rather than relying on a single check. Sensitive server credentials are intended to remain server-side, and production form verification is designed to fail closed when required protection is not configured.
Data and service providers
Skarion should limit access to personal information to people and service providers who need it for legitimate operational purposes. Production systems should use least-privilege access, strong account security, encrypted transport, controlled secrets, and vendor settings appropriate to the information being handled.
Responsible reporting
If you believe you have found a security issue affecting Skarion, please report it privately to hello@skarion.com with enough detail for the team to understand and reproduce the problem. Do not access, alter, download, or retain data that is not yours, and do not disrupt the service while investigating.
Skarion should acknowledge valid reports and coordinate remediation based on severity and operational impact. A dedicated security mailbox and disclosure policy can replace this placeholder process later.
No absolute guarantee
No website or security program can guarantee that an incident will never occur. This page describes Skarion's intended approach and should not be interpreted as a warranty of perfect security. Security controls and this notice should be updated as the service evolves.