Trust Center

How we protect your event data

CredsNow handles attendee data on behalf of event organizers. This page summarizes how we secure the platform and the data our customers trust us with.

Hosted on Azure (USA)SOC 2 Type 1 — In progressEncryption in transit & at restMFA for administrative access

Overview

CredsNow is an event credentialing and badge-printing platform. We handle attendee data on behalf of event organizers, and we treat protecting it as a core part of the product. This page summarizes how we secure the platform and the data our customers trust us with.

Hosting & infrastructure

CredsNow is hosted on Microsoft Azure in the United States, with a disaster-recovery replica in Western Europe. We use Azure's managed services rather than running our own servers. Database access is restricted to Azure-hosted services and named, authorized personnel.

Encryption

All data in transit is encrypted with TLS 1.2 or higher. Customer data at rest, including databases and backups, is encrypted with Azure-managed encryption. Application secrets are stored in Azure Key Vault or encrypted Azure App Service settings, never in source code.

Access control

Access to production systems is limited to the people who need it for their role. Administrative access requires multi-factor authentication. We review access quarterly and remove it promptly when someone changes roles or leaves. Code changes require review by a second person before they reach production.

Monitoring & threat detection

We monitor the platform continuously with Microsoft Defender for Cloud and Microsoft Defender for SQL. Database activity is audited, and audit logs are kept for one year.

Vulnerability management & penetration testing

We run vulnerability scans quarterly and fix findings based on their severity. Our first annual third-party penetration test is scheduled for Q4 2026.

A summary of results will be available under NDA once complete.

Backups & disaster recovery

Databases are backed up automatically with point-in-time restore, and long-term backups are kept monthly. Production databases replicate to a second Azure region, so we can fail over if the primary region has an outage. We test restores at least once a year.

Incident response & breach notification

We have a documented incident response plan with defined roles and escalation steps. If a security incident affects customer data, we notify affected customers without undue delay and within 72 hours of confirming it.

Data retention & deletion

Event and attendee data is deleted about six months after the event, unless the customer's agreement says otherwise. Customers can ask for earlier deletion by contacting us.

Compliance

We're undergoing a SOC 2 Type 1 audit (Security and Availability) with Prescient Assurance, with a Type 2 audit to follow. Our security program is supported by written policies that are reviewed and approved at least once a year.

Once the SOC 2 report is issued, it can be shared under NDA on request.

Service providers

We use a small number of trusted providers to deliver the service:

  • Microsoft Azure: hosting and infrastructure
  • Auth0: user authentication
  • SendGrid: transactional email
  • Stripe: payment processing (card data never touches CredsNow servers)
  • HubSpot: customer relationship management

Contact

To report a vulnerability or security concern, or to request security documentation, email security@credsnow.com.