PyroCore

Security

PyroCore treats security as an operational requirement for specialty-retail systems — authentication boundaries, data protection principles, deployment integrity, and responsible disclosure. This page states principles, not unearned certifications.

Principles

How PyroCore approaches security

Factual posture for evaluators — without unearned certification claims.

No invented certifications

This page does not claim SOC 2, ISO, PCI, or other certifications unless and until they are earned and approved for public statement.

  • Secure authentication architecture

    Customer Portal authentication and the operational application remain separate from the public marketing website. Marketing forms do not create authenticated sessions.

  • Data protection principles

    Collect only what a workflow needs. Lead forms use validation, honeypot protection, and delivery adapters that stay disabled in production until destination, privacy, and ownership are approved.

  • Operational reliability

    Platform Health and deployment visibility exist so operators can see warnings and failed work instead of assuming silence means safety.

  • Update and deployment integrity

    Deployment Center is designed for controlled releases to locations and device fleets. Integrity depends on visible job status — not hope.

  • Public website hardening

    The public site ships security headers, input validation, and secrets kept out of client code. Third-party scripts stay minimal until approved.

Responsible disclosure

Responsible disclosure

Report issues privately with reproducible detail.

Contact

If you believe you have found a security issue affecting PyroCore.net or related public surfaces, contact hello@pyrocore.net with enough detail to reproduce the issue. Do not include customer secrets or private operational data in public channels.

  • Email: hello@pyrocore.net
  • Do not post exploits publicly before coordinated disclosure
  • Do not include customer secrets in reports

Evaluate with confidence

Request a demo to discuss architecture boundaries, or review Privacy and Terms drafts.