Reference

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.

What Is Collected
Data PointWhy We Collect It
SDK name and versionTrack adoption across language ecosystems.
Runtime / language versionPrioritise compatibility fixes (e.g. which Node.js versions are in use).
API endpoint calledUnderstand which features are most used.
HTTP status codeMonitor 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.

What Is Never Collected
Phone numbers, email addresses, or any message content.
API keys, secrets, or any credential material.
Your application source code or stack traces.
User identifiers or personal data of your customers.
IP addresses of your servers or end-users.
Opting Out

Set the SENDEXA_TELEMETRY_DISABLED environment variable to 1 or true in any environment where you want telemetry suppressed.

Bash
# Disable for a single run
SENDEXA_TELEMETRY_DISABLED=1 node app.js
# Disable permanently in your shell profile
export SENDEXA_TELEMETRY_DISABLED=1
# In a .env file
SENDEXA_TELEMETRY_DISABLED=1

Alternatively, you can disable telemetry programmatically when initialising the SDK client:

TypeScript
import { Sendexa } from "sendexa";
const client = new Sendexa({
apiKey: process.env.SENDEXA_API_KEY!,
apiSecret: process.env.SENDEXA_API_SECRET!,
telemetryDisabled: true,
});
Data Retention & Privacy

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.