Support
How to get help with SenseCrypt — the in-product contact form, the enterprise-support path for production and self-hosting, and how to report a security issue.
Need a hand? Here's how to reach us, and which path fits your question.
Contact us
The quickest way to get in touch is the contact form in the admin console. Fill in your name, email, subject, and message, and it's delivered straight to the SenseCrypt support team. We reply directly to the address you enter, so keep an eye on that inbox — hitting Reply on our response comes back to us.
Use the contact form for product questions, account and billing queries, integration help, and bug reports. When you write in about an integration issue, it helps to include:
- The tenant (issuer hostname) you're working with.
- The protocol and operation involved (for example, the OIDC token exchange, a SAML SSO POST, or a SCIM provisioning call).
- What you expected versus what happened, and any error code or response body you received. SenseCrypt returns machine-readable error codes — see Troubleshooting — and quoting the exact code speeds up diagnosis.
Before you write in, it's worth a look at the Troubleshooting reference and the Concepts pages — many integration questions come down to resolving endpoints from discovery or the default-closed access gate, and those are covered there.
Enterprise support
Running SenseCrypt in production — or self-hosting it in your own infrastructure — is best done with our team alongside you. Enterprise support covers production hardening, capacity planning, zero-downtime upgrades, backup strategy, key rotation, and day-two operations.
If you're planning a self-hosted deployment, start with the Self-Hosting guide for the install steps and essential configuration, then reach out through the admin console to engage enterprise support for the production rollout.
Reporting a security issue
SenseCrypt is a security product, and we take vulnerability reports seriously. If you believe you've found a security issue, please report it privately rather than opening it in a public channel or filing it as an ordinary bug, so we can investigate and ship a fix before details are disclosed.
Reach out through the admin console contact form with a subject that flags it as a security report, and include enough detail to reproduce the issue. Please give us a reasonable window to remediate before any public disclosure. For background on the guarantees SenseCrypt is built to uphold — biometric blindness, per-tenant key custody, and tenant isolation — see Security.
Related
- Troubleshooting — common problems and their fixes.
- Self-Hosting — install, configure, and run SenseCrypt yourself.
- Security — the security model and its guarantees.
Security
SenseCrypt's security model — biometric blindness, per-tenant issuer isolation, encryption at rest for signing keys, the device-trust model, anti-enumeration design, and compliance posture.
Changelog
Release notes for SenseCrypt — how the product is versioned and where notable changes are recorded.