Contact

Talk to the people who build the lab.

Product questions, integration work, reader/router compatibility and security reports. Please do not send private keys, activation codes or raw card identifiers.

ProductIntegrationSecurity

Product & integration

Tell us the platform, reader, card type and the workflow you need. A concrete constraint is more useful than a feature list.

[email protected]

Security

Report a suspected secret leak, auth bypass or unsafe write path. Do not include the secret itself; describe the location and impact.

[email protected]

Platform preview

For iOS/macOS scope discussions, tell us which reader and card path you use on Apple hardware.

iOS direction

What to include

  • Platform and OS version.
  • Reader/CPE model and connection type (USB, PC/SC, serial, BLE).
  • Card type and whether it is a test or production card.
  • The exact action and the observed result; logs with secrets removed.
  • Whether any write path was enabled.

What not to send

Private keys, activation codes, tokens, full EID/ICCID/IMSI, raw authentication values, or unredacted SIP/WAV captures. If we need a private artifact, we will arrange a restricted channel.

Email addresses on this page are placeholders for the site scaffold. Replace them with the real mailboxes before publishing.
$simcat contact --safe
→include: platform · reader · card type · action
→redact: keys · tokens · EID/ICCID · raw auth
→attach: redacted logs only
$simcat contact --security
→describe location + impact, not the secret
✓ Redact first. Send second.