Security at SkyeFire

01Overview

Security is a first-class design goal across the SkyeFire platform, including Axiom, Atlas, Ascenda, and related products. Our approach follows the principle of least privilege, defense in depth, and accountability through traceability.

This document is written to be understood by operators and decision-makers, not just security specialists. Where our controls are still maturing, we say so honestly rather than overstate them.

02Access Control

Every account operates under a defined role. Access is scoped to responsibility so that people see and change only what their role permits.

• Role-based access control (RBAC). Administrator, Operator, Customer, and View-only roles govern permissions across the platform.
• Least privilege. New accounts start with the minimum access required and are elevated deliberately.
• Authentication. Access requires authenticated sessions. Administrative and destructive actions are gated behind additional confirmation and, where enabled, approval steps.
• Session integrity. Sessions use secure, HTTP-only cookies with same-site protections to reduce cross-site risk.

03Encryption & Credentials

We protect data in transit and handle credentials so they are never exposed to the browser or stored in plain text.

• In transit. Traffic to our web properties is served over HTTPS/TLS. Our marketing site enforces HSTS and a strict Content-Security-Policy.
• Passwords. Account passwords are hashed and salted — never stored in readable form.
• Secrets. API keys, tokens, and integration secrets are held server-side and are never shipped to client-side code.

04Data Handling

We collect and process only the data needed to operate the services you use, and we handle it according to our Privacy Policy.

• Purpose limitation. Operational and contact data is used to run the service you signed up for and to respond to you.
• Ownership. Your data is yours. We do not sell it.
• Separation. We keep product lines and customer environments logically separated so data does not bleed across contexts.

05Backups, Recovery & Integrity

Operational data is backed up so it can be recovered, and high-impact actions are protected against accidental or unauthorized change.

• Backups. Operational data is backed up to support restoration.
• Protected destructive actions. Deletes and bulk changes require confirmation and, where configured, approval before they take effect.
• Audit trails. The platform is built for traceability so that key actions can be reviewed — supporting accountable operations in manufacturing and field-driven environments.

06Application & Infrastructure Security

We apply modern web-security controls at the application and hosting layers.

• Hardened web delivery. Our sites set security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy.
• Dependency hygiene. We keep platform dependencies current and remove unused surface area.
• Managed hosting. Production runs on managed, reputable infrastructure providers with their own physical and network security controls.

07Incident Response

If a security incident affects your data, we act to contain it and communicate honestly.

• Containment first. Our priority in any incident is to contain impact and preserve evidence.
• Notification. Where an incident affects your data, we will notify affected parties without undue delay and in line with applicable law.
• Remediation. We investigate root cause and apply corrective measures to reduce recurrence.

08Compliance Posture

As the platform matures, we are aligning our processes toward widely recognized security and privacy frameworks.

• Framework alignment (in progress). We are aligning internal practices toward the control objectives found in standards such as SOC 2 and ISO/IEC 27001. Alignment is not certification, and we do not represent that we are certified.
• Privacy rights. We honor core data-subject rights consistent with the GDPR and CCPA/CPRA, as described in our Privacy Policy.
• Roadmap transparency. Enterprise and pilot partners can request current details on our controls and roadmap.

09Responsible Disclosure

We welcome reports from security researchers and users who identify potential vulnerabilities.

• Report suspected vulnerabilities to skyefire.ramsey@gmail.com with enough detail to reproduce the issue.
• Please give us a reasonable opportunity to investigate and remediate before any public disclosure.
• Act in good faith, avoid privacy violations and service disruption, and do not access or modify data that is not yours.

10Contact

For security questions, vulnerability reports, or to request details on our controls for a pilot or enterprise engagement, contact skyefire.ramsey@gmail.com.