Product and access
Onboarding, product fit, and evaluation questions.
hello@useeventstack.comContact
Get in touch
Choose the route closest to your question and include only the context needed to assess it. Never email passwords, API keys, access tokens, private keys, or confidential event payloads.
Technical support
Reproducible integration issues, SDK or API questions, and product defects.
support@useeventstack.comSecurity
Potential vulnerabilities and security-sensitive product concerns.
security@useeventstack.comInvestor inquiries
Product, architecture, roadmap, and company diligence requests.
investors@useeventstack.comTechnical reports
Provide evidence without exposing sensitive data
A compact, sanitized report is easier to assess than a raw log export. Preserve your own evidence and incident process.
When submitting a technical report, include reproduction steps, the SDK or API version, and the approximate UTC time of the issue. Remove credentials and customer data before sending.
- Include
- Expected and observed behavior, a minimal reproduction, route or SDK version, environment, approximate UTC time, and non-secret identifiers.
- Remove
- Credentials, tokens, private customer data, full event payloads, and unrelated logs.
- Response boundary
- These public mailboxes do not establish a guaranteed response, remediation, disclosure, or support timeline.
Send a message
We'll get back to you within 2 business days
Check the documentation first
The quickstart and API references answer many setup and integration questions without sharing account details.
Open documentation