Skip to main content
    Back to Home

    Security

    Last updated: October 28, 2026 · Prepared for professional review

    PCI-Compliant Payments

    Payment processing through Stripe (Level 1 PCI compliant)

    Encrypted Data

    HTTPS protects browser connections; infrastructure safeguards depend on the hosting provider.

    Enterprise Infrastructure

    Hosted on enterprise-grade cloud infrastructure

    1. Our Commitment to Security

    At KingdomTix, security is foundational to everything we do. We understand that you trust us with sensitive information—personal data, payment details, and event information—and we take that responsibility seriously. This page describes implemented account and ticketing controls and third-party services, not a KingdomTix certification or a guarantee of security.

    2. Payment Security

    2.1 PCI DSS Compliance

    All payment processing is handled by Stripe, a PCI Level 1 Service Provider—the highest level of certification in the payment industry. This means:

    • Your credit card information never touches our servers
    • All payment data is encrypted and tokenized
    • We only store transaction references, never full card numbers
    • Stripe undergoes annual third-party audits

    2.2 Fraud Prevention

    Payment and event-risk controls include:

    • Payment status and transaction references
    • Stripe payment review subject to connected-account settings
    • Organizer-configured ticket availability and purchase limits
    • Event reporting and support channels
    • Administrator review of reported concerns

    3. Data Protection

    3.1 Encryption

    Encryption in Transit

    The public website uses HTTPS. Supported TLS versions and transport policies depend on the host; this page does not assert a specific version or HSTS configuration.

    Encryption at Rest

    Storage and backup safeguards are managed by infrastructure providers. Encryption algorithms, backup coverage and retention require provider verification.

    Key Management

    Payment secrets and privileged service credentials belong on the server, not in browser code. Provider key-rotation settings require separate verification.

    3.2 Data Access Controls

    • Row-Level Security (RLS): Database policies scope access to buyers, relevant organizers, staff and administrators; policy coverage still requires testing
    • Principle of Least Privilege: Administrative and event-team roles separate access; operational staff access requires periodic review
    • Audit Logging: Selected operations have audit records; complete access logging is not claimed
    • Multi-Factor Authentication: Administrative MFA enforcement has not been verified; this page does not claim it is required

    4. Infrastructure Security

    4.1 Cloud Infrastructure

    Hosting-provider controls and operational settings must be checked individually. This page does not certify the following:

    • Data centers operated by major cloud providers that maintain their own independent security certifications
    • Geographic redundancy with automatic failover
    • DDoS protection and mitigation
    • Web Application Firewall (WAF)
    • Continuous vulnerability scanning

    4.2 Network Security

    • Provider-managed network controls
    • Provider incident-detection coverage, subject to verification
    • Independent penetration testing remains an operational review item
    • Monitoring coverage and response staffing require owner confirmation

    4.3 API Security

    • Some endpoints have abuse checks; comprehensive rate limiting is not verified
    • JWT-based authentication
    • Request validation is implemented in application paths; complete endpoint coverage requires review
    • CORS limits browser cross-origin access; it is not a substitute for authorization

    5. Application Security

    5.1 Secure Development

    • Security-focused code reviews
    • Static application security testing (SAST)
    • Dynamic application security testing (DAST)
    • Dependency vulnerability scanning
    • Developer security-training practices require owner confirmation

    5.2 Authentication & Authorization

    • Secure password hashing using bcrypt
    • Hosted sign-in abuse and lockout settings require verification
    • Session management with secure tokens
    • Role-based access control (RBAC)
    • Two-factor enrollment and enforcement are not verified in account settings

    6. Ticket Security

    6.1 Anti-Fraud Measures

    • Unique QR Codes: Ticket codes identify issued tickets; keep codes private
    • One-Time Scan: Online check-in records ticket use; offline scans require synchronization
    • Real-Time Validation: Online scans validate stored ticket status and access; offline scans can have stale information
    • Transfer Tracking: Ticket transfers have recorded status; complete audit coverage requires review

    6.2 Scalping Prevention

    • Purchase limits per customer
    • CAPTCHA availability and enforcement are not verified
    • Bulk-purchase abuse protections require further testing
    • Account verification requirements

    7. Compliance

    GDPR

    We support GDPR data subject rights, including access, correction, and deletion requests

    CCPA

    We support CCPA/CPRA rights and honor Global Privacy Control opt-out signals

    PCI DSS

    Payment processing through PCI Level 1 compliant provider

    ADA

    We work toward WCAG 2.1 AA accessibility and welcome reports of barriers

    8. Incident Response

    Incident response procedures and staffing require owner confirmation, including:

    • Monitoring coverage and response staffing require owner confirmation and alerting
    • Defined escalation procedures
    • Incident containment and remediation processes
    • Communication protocols for affected users
    • Post-incident analysis and improvement

    Any required incident notifications depend on applicable law, the incident and the affected audience. A universal 72-hour user-notification promise is not made.

    9. Vulnerability Disclosure

    We welcome responsible disclosure of security vulnerabilities. If you discover a security issue, please report it to:

    Security Team

    Email: support@kingdomtix.org

    Include reproduction steps without passwords, payment details or other people's personal data. Do not access unauthorized records, disrupt the service or run payment tests against live orders. No fixed response time or bounty is promised.

    10. Security Best Practices for Users

    We recommend the following security practices:

    Use Strong Passwords

    Create unique passwords with at least 12 characters including letters, numbers, and symbols.

    Beware of Phishing

    We will never ask for your password via email. Always verify emails come from @kingdomtix.org.

    Protect Your Email Account

    Use your email provider's security options and keep recovery methods current. KingdomTix account MFA availability is not verified.

    Keep Software Updated

    Ensure your browser and devices are running the latest security updates.

    11. Important Disclaimer

    This page describes our security practices for informational purposes only. It is not a warranty, guarantee, or contractual commitment, and it does not constitute a certification of any third-party standard on our behalf. No system can be made completely secure. Our practices may change as the platform evolves, and any references to third-party providers describe their published programs, not ours. Nothing on this page expands the obligations or liability set out in our Terms of Service, which continue to apply in full, including the limitation of liability. Security of events, venues, staffing, and on-site safety is the responsibility of the event organizer.

    12. Contact Security Team

    For security-related questions or concerns, please contact us:

    KingdomTix Security Team

    Email: support@kingdomtix.org

    For vulnerability reports: support@kingdomtix.org