Certifications
Badge holds three independent ISO certifications, all issued on 2023-12-11:
Each certification covers the design and operation of TalkValue’s product, infrastructure, and supporting business processes. For an audit copy or the certificate PDFs, contact security@trytalkvalue.com.
Encryption
Data is encrypted everywhere it lives and everywhere it moves:- In transit. All traffic to
eventsbadge.com, the Badge API, and the public docs atdocs.eventsbadge.comis served over TLS 1.2 or higher. HTTP traffic redirects to HTTPS at the edge. Internal service-to-service traffic in our infrastructure is encrypted as well. - At rest. Application databases, file storage, and backups are encrypted at rest using industry-standard AES-256 (or equivalent) symmetric encryption. Encryption keys are managed by the cloud provider’s key-management service and rotated on the provider’s schedule.
Access controls
Access to your workspace data is enforced at three layers:- Workspace isolation. Every request is scoped to the workspace in the caller’s session, so data belonging to another workspace is never reachable. Within a workspace, the Admin and Member roles determine which surfaces the app exposes — billing and member management are Admin surfaces. See Roles and permissions for the full capability matrix.
- Authentication. Badge supports email code and Google sign-in. Both use industry-standard identity protocols. There is no shared-secret password to leak. See Login methods.
- Internal access. Badge staff access to production systems is restricted to a small on-call team, gated by role-based access in our identity provider, and logged. Access to customer data is granted only on documented support need, with the customer’s consent where the request originates from the customer.
Subprocessors
TalkValue uses a small set of subprocessors. Each holds its own certifications appropriate to its function:- Cloud hosting and database. Production infrastructure and storage.
- Identity provider. Sign-in flows and session tokens for email code and Google.
- Payment processor. Card data, billing, and invoicing. Badge holds only the payment-method reference, never raw card numbers.
- AI provider. Powers the in-app AI assistant. Workspace data is processed under terms that prohibit training on customer content.
- Email delivery. Magic-link codes, invitations, billing receipts, and Badge welcome emails to attendees.
- Customer support tooling. Routes incoming support conversations.
- Product analytics. Usage signals used to improve Badge, no workspace content.
Customer data ownership
Workspace data (events, attendees, badges, templates, leads) belongs to your workspace. Badge is the data processor, not the data owner. You can export it any time (see Export your data).Responsible disclosure
Report security issues directly to security@trytalkvalue.com. Include a description of the issue and its impact, reproduction steps, and your suggested severity. We acknowledge reports within 2 business days and follow up with remediation timing once reproduced. Researchers are credited by name on request once the issue is resolved. When investigating, don’t run automated scanners againsteventsbadge.com without coordinating first, access customer data beyond the minimum needed to demonstrate the issue, or disclose publicly until we’ve confirmed a fix.
Status and incidents
For live operational status, see status.trytalkvalue.com. Post-incident summaries are posted there once resolved.Related
- Export your data. Pull a workspace copy any time.
- Roles and permissions. In-product access control.
- Login methods. How authentication works for end users.
- Delete your account. End-of-life for account-level identity data.