This policy explains how GEOPOLY (“ClientDesk”, “we”, “us” or “our”) handles information through the ClientDesk Android application (the “App”), licence services, and support services (together, the “Services”).
1. Scope and business use
ClientDesk is a business productivity and customer-relationship tool for authorised personnel. A subscribing business generally decides why customer and prospect information is entered, imported, contacted, exported, or shared. That business is responsible for notices, consent, lawful messaging, opt-outs, and responses to requests concerning its CRM records.
2. Information the App handles
Stored on the device
- Call history, including telephone number, contact name when available, date, time, duration, and call type.
- CRM details entered by users, including outcome, priority, category/model, lead stage, notes, callback details, campaign information, and do-not-contact entries.
- Messaging details, including recipient, message or template, channel, time, status, provider response or error, and manual-send confirmation.
- Settings and credentials, including company and licence details, automation settings, preferred SIM, WhatsApp configuration, SMS endpoint, sender and DLT identifiers, API credentials, and templates.
- Trial and licence information, including installation time and a device identifier used to administer access.
The local CRM database remains on the device unless a user exports, shares, backs up, or restores it, or a device/operating-system service accesses it under the user’s settings.
Permissions
- Call logs display recent calls and support CRM records, reports, and selected post-call workflows.
- Contacts display names associated with telephone numbers.
- Phone state detects call-state changes for post-call workflows.
- Phone calls are used when a user chooses a direct-call action.
- Receive SMS detects a licence message addressed to the device and extracts licence activation details. It is not used to read the user’s SMS inbox.
- Notifications, alarms, and display over other apps support callback reminders, licence notices, and post-call prompts.
- Internet and network state support licence verification and optional messaging APIs.
The App does not request location, camera, microphone, READ_SMS, or SEND_SMS. Manual SIM messages are prepared in the device’s messaging app for the user to review and send.
3. Information sent from the App
Customer CRM information and licence information are handled separately. Customer call history, contacts, lead notes, callback records, and locally stored CRM records are not sent to the ClientDesk licence server.
- Licence verification: licence key, company name, valid-from and valid-until dates, licence status, Android device identifier, App/package or version information, and verification time are sent to the configured licence service. The connection may also provide an IP address.
- WhatsApp: when enabled, recipient numbers, approved template content, and related message data are sent to Meta using credentials supplied by the subscribing business.
- Bulk SMS: when enabled, recipient numbers, content, sender/DLT identifiers, and authentication details are sent to the SMS provider configured by the business.
- Manual messaging: recipient and prepared content are passed to the selected SMS or WhatsApp application, which applies its own privacy terms.
- Exports and backups: reports and backups may contain CRM data. The user chooses the destination and is responsible for securing the file.
4. Licence administration records
These records are kept separately from customer CRM information. The licence administration service may store company name, the mobile number used by the administrator to manage or deliver a licence, internal licence code, hashed activation or renewal keys, licence dates and status, a hashed device identifier for one-device enforcement, activation time, verification history, and connection IP addresses. It does not receive the user’s call history, contacts, lead notes, callback records, message content, or local CRM database.
A strictly necessary session cookie keeps authorised administrators signed in. The current website does not use advertising cookies or analytics.
5. Purposes
Information is used to provide CRM, calling, reminders, reporting, and messaging features; verify licences and prevent unauthorised use; maintain security; diagnose errors; provide support; enforce agreements; and comply with law.
6. Sharing
Information may be shared with the subscribing business and its authorised users; licence-hosting providers; messaging providers selected by the business; applications, destinations, and recipients selected by the user; professional advisers; and authorities when required by law. We do not sell personal information or use it for third-party behavioural advertising.
7. Security and retention
App settings and credentials are encrypted with a key held in Android Keystore. The CRM database is stored in private App storage. Network services should use HTTPS. Android backup or transfer services may handle encrypted preferences under the user’s settings; the CRM database is excluded from configured automatic cloud backup, although a user can create a manual backup.
Local information remains until a user removes it, replaces the database, clears App data, or uninstalls the App, subject to backups and exports. Licence and security records are kept only as long as reasonably needed to administer licences, prevent abuse, resolve disputes, and meet legal or accounting duties. No system is completely secure.
8. Choices and rights
Users may deny permissions, although related features will not work. Automation and API channels can be disabled in Settings. Users must respect do-not-contact requests. Depending on location, individuals may have rights to access, correct, delete, restrict, or object to processing, withdraw consent, or complain to a regulator. CRM requests should normally be sent to the subscribing business that contacted the individual; licence and support requests may be sent to us.
9. Children
The Services are business tools, are not directed to children, and must not knowingly be used to collect or contact children contrary to applicable law.
10. International processing
Service providers and message recipients may be outside the user’s country. The subscribing business is responsible for lawful communications and transfers through providers it selects.
11. Changes
We may update this policy to reflect changes to the Services or law. We will revise the effective date and provide additional notice where required.
12. Contact
GEOPOLY
Privacy: adsonmobile.in@gmail.com
Support: adsonmobile.in@gmail.com