d3 d3cima
Applications Contact
FR EN
Contact us
Legal NoticePrivacy PolicyTerms & SalesData Deletion
Home /Privacy Policy / Privacy Policy — TelePing

Privacy Policy — TelePing

Complete disclosure of Android runtime permissions, on-device processing, and user-configured webhooks for the TelePing line-monitoring utility.

Android App · Specific Disclosure Last updated: November 16, 2026

On this page

  1. 1. Purpose of TelePing
  2. 2. Android Permissions Breakdown
  3. 3. User-Configured Webhooks
  4. 4. Local Storage & Deletion
Key privacy facts for TelePing
  • Zero d3cima cloud servers: TelePing never transmits phone numbers, call logs, or SMS content to d3cima.
  • 100% on-device execution on your dedicated Android monitoring device.
  • Check results (up/down status and timestamp) are sent exclusively to the HTTP/HTTPS webhook endpoints that you configure yourself (e.g., Home Assistant).

1. Purpose of TelePing

TelePing is a specialized telecom monitoring utility designed to verify cellular 4G/VoLTE/GSM line availability in a closed loop (TelePing emitter and TelePong receiver) without consuming voice minutes. It is built for system administrators and home-automation users.

This app-specific disclosure supplements the d3cima General Privacy Policy.

2. Android Permissions Breakdown

TelePing only uses permissions directly required for the monitoring features enabled by the user:

Android Permission Purpose inside TelePing External Transmission
CALL_PHONE / ANSWER_PHONE_CALLS / READ_PHONE_STATE Initiate automated test calls to the user-configured target line, detect ring/call state, and hang up automatically in closed-loop mode. Never sent to d3cima. Target number stays on-device.
SEND_SMS / RECEIVE_SMS / READ_SMS (if SMS mode is used) Exchange automated technical Ping/Pong probes between authorized monitoring lines when SMS probe mode is explicitly enabled. Personal messages are never exported. Never sent to d3cima.
FOREGROUND_SERVICE & SCHEDULE_EXACT_ALARM Run scheduled line checks reliably with a persistent, user-visible Android foreground service notification. None.
INTERNET & ACCESS_NETWORK_STATE Deliver check status payloads (success/failure, timestamp) to the user's own webhook URL. Sent strictly to the endpoint configured by the user.

3. User-Configured Webhooks

When you configure an HTTP/HTTPS webhook URL (such as your own Home Assistant server or monitoring platform), your Android device sends status payloads directly to that endpoint.

d3cima never proxies, intercepts, or stores your webhook URLs, authentication headers, or probe history.

4. Local Storage & Deletion

All TelePing settings (target phone numbers, schedules, webhook URLs, and recent local check logs) are stored solely in Android's private application storage on your device.

Uninstalling TelePing or clearing its storage in Android Settings immediately and permanently deletes all local data. For support inquiries, contact contact-apps@d3cima.com.

© 2026 d3cima — Mobile application development studio.
Legal Notice Privacy Policy Terms & Sales Data Deletion contact-apps@d3cima.com