India DLT Compliance Policy

Customers must obtain and maintain the applicable Principal Entity (PE) registration through the authorized DLT ecosystem where required for their traffic. The details submitted to Alert21 must match the customer's approved registration records.

Use only sender IDs or headers that are registered, approved and authorized for the customer and intended use case. Alert21 may restrict sending to headers mapped to the relevant account, entity or template.

Messages must use the applicable approved content template. The DLT Template ID submitted through the Alert21 API must correspond to the customer account, sender or header, message category and approved content. Alert21 may reject messages where the mapping is incomplete or inconsistent.

Dynamic values may be inserted only in approved variable positions and in the correct order. Alert21 may validate the number and characteristics of variables before routing. Variables must not materially transform an approved template into different, misleading, prohibited or unregistered content.

Customers are responsible for consent, preferences and recipient permissions where required, including applicable promotional or service communication rules and DND or opt-out requirements. Alert21 does not create permission to contact a recipient simply because a template or route is available.

Alert21 may map telemarketer, provider or other required routing information behind the API. Customers generally should not need to expose upstream provider credentials or provider-specific hashing logic in their application unless a particular regulatory workflow requires it.

Alert21 may reject, block or suspend traffic where a DLT mapping is missing, inactive, mismatched, prohibited or rejected by an upstream telecom, provider or DLT system. Repeated non-compliance may result in account restrictions or termination.

TRAI, telecom operators and DLT platforms may issue new regulations, directions, technical requirements or processes. Alert21 may update onboarding, validation, API behavior and sending rules as necessary to remain compatible with applicable obligations.