Telemetry
Sendexa SDKs collect anonymous usage telemetry to help us improve the developer experience. Here's exactly what is collected and how to opt out.
Opt-out is always available
| Data Point | Why We Collect It |
|---|---|
| SDK name and version | Track adoption across language ecosystems. |
| Runtime / language version | Prioritise compatibility fixes (e.g. which Node.js versions are in use). |
| API endpoint called | Understand which features are most used. |
| HTTP status code | Monitor error rates by endpoint. |
| Request duration (ms) | Detect latency regressions across SDK releases. |
| Country code (derived from API key region) | Understand regional usage patterns. |
All telemetry is aggregated and anonymised before storage. Individual events are never linked back to a specific API key or organisation.
Set the SENDEXA_TELEMETRY_DISABLED environment variable to 1 or true in any environment where you want telemetry suppressed.
# Disable for a single runSENDEXA_TELEMETRY_DISABLED=1 node app.js# Disable permanently in your shell profileexport SENDEXA_TELEMETRY_DISABLED=1# In a .env fileSENDEXA_TELEMETRY_DISABLED=1
Alternatively, you can disable telemetry programmatically when initialising the SDK client:
import { Sendexa } from "sendexa";const client = new Sendexa({apiKey: process.env.SENDEXA_API_KEY!,apiSecret: process.env.SENDEXA_API_SECRET!,telemetryDisabled: true,});
Aggregated telemetry events are retained for 90 days and then deleted. We do not share telemetry data with third parties.
Telemetry is governed by the Sendexa Privacy Policy. If you have questions, contact privacy@sendexa.co.