Contact SigID¶
Use [email protected] for product evaluation, enterprise requirements, and commercial questions. Include the organization name, the application or agent workflow you are evaluating, expected environments, and any compliance or deployment constraints. Do not send passwords, bearer tokens, API keys, private keys, recovery codes, payment-card data, or production personal data by email.
Use [email protected] for privacy questions and data-rights requests, [email protected] for legal questions, and [email protected] for responsible vulnerability disclosure. A security report should include safe reproduction steps, affected endpoints, observed impact, and a way to contact the reporter. Do not use destructive techniques against production or access another tenant's information while preparing a report.
For an API failure, include a timestamp, the affected endpoint, HTTP status, and a redacted x-request-id. Keep tokens and secrets out of logs and attachments. Account-specific issues should begin in SigID Identity, while application and tenant setup questions should begin in the Developer overview or Workspace administration.