thynkWISE Mobile Privacy Policy
Last updated: 16 October 2026
About the app
The ColdCall Android app is an employer-provided business application for authorised sales users. It displays assigned leads, starts work calls through the Android phone system, records call outcomes, supports callbacks and provides personal work reporting. It has no public or anonymous mode.
Data we collect
- Account identity: name, work email, user ID, tenant, role and authentication tokens.
- Lead data supplied by your organisation: prospect name, business contact details and campaign context.
- Work-call activity: number dialled, timestamps, duration, coarse call state, outcome, callback and notes you enter.
- Operational information needed to securely synchronise queued work and diagnose failures.
- Sign-in records: when you signed in, on which surface (app, dashboard or browser extension), the device type and operating system reported by your device, and the approximate city derived from your network address. Your organisation uses these to see when their team was working.
- Approximate location for workspace access. If your workspace administrator activates the SDR evidence service pack and requires it for your role, a location check is required before you enter work screens. The app explains this before you tap “Share current location” and before the Android permission dialog. It refreshes every five minutes while the app is visible. If a check fails or expires, work screens lock; a pending call outcome can still be completed. No location is collected in the background. Outside this requirement, the separate “Share my location when I sign in” switch in Profile remains optional and off by default.
- Optional screenshots of a screen or app you choose. If your administrator enables screenshots and configures storage, you may tap “Start sharing” and choose the screen or app in Android's own dialog. A visible sharing indicator and notification provide a Stop control. One compressed screenshot is sent immediately and then every five minutes while ColdCall.in is visible. Sharing stops when the app goes to the background, you sign out, the OS ends sharing, or the policy is disabled. It never captures audio and does not start without this selection.
We do not collect device contacts, precise location, SMS messages, advertising IDs or Android call-log records. The app does not read your photo library; the optional screen images above are generated from your chosen sharing session. Location above is coarse only — the app requests ACCESS_COARSE_LOCATION, which is accurate to roughly a city area. It never requests ACCESS_FINE_LOCATION or background location.
Location permission
Your workspace administrator controls the evidence requirement for your role. When it applies, approximate location is required for protected work screens, with a fresh check every five minutes while the app is visible and a six-minute validity period. A failed check or no internet connection locks those screens. Existing call outcomes remain finishable so your draft is preserved. Permission is requested only after the explanation and your “Share current location” action. Only ACCESS_COARSE_LOCATION is declared; there is no precise or background location permission.
Outside this requirement, “Share my location when I sign in” in Profile is optional and off by default. Its explanation appears before the Android dialog, and declining leaves it off. When enabled, it attaches one approximate reading to your sign-in record. Signing out clears this preference.
Approximate location helps your organisation see roughly where work was performed. Evidence-service readings are available to workspace administrators. Historical sign-in records may also be available to authorised managers and team leads. Location is not sold, used for advertising or sent to Firebase. You can revoke permission in Android Settings. If your role requires location, ask your workspace administrator to change that requirement; declining it keeps protected work screens locked.
Location records are retained according to your organisation's policy and applicable audit duties. Use the account deletion process to request deletion; that page explains what may lawfully be retained.
Screenshot storage and choices
Screenshots are optional and can be stopped at any time using “Stop sharing” in the app or Android notification. Android 14 and later may offer a single app; older supported Android versions offer full-screen sharing. The OS controls the available choices. A fresh selection is needed after sharing ends. Screenshots are resized to at most 1280 pixels on the longest edge and compressed to at most 60 KB. Images are not saved to the device or queued for later upload.
Images are sent over HTTPS to the Google Drive folder configured by your workspace administrator. Workspace administrators can review them through authorised access. Existing sharing on that Drive folder also applies, so your administrator must choose an appropriate private folder. The service stores image metadata and a private file reference, not a public link or image bytes in its database. The folder owner controls retention and deletion of Drive files; there is no automatic image deletion claim. Screen images are not sent to Firebase or used for advertising.
Phone and microphone permissions
Phone permissions are used only to place a work call and observe coarse connection state. Notification permission supports ongoing-call and pending-wrap-up notices. The app does not record calls. It requests no microphone permission, contains no audio-capture code, and cannot start a recording.
Call recordings saved by your phone
Some Android handsets record calls with their own built-in dialer and save the files to a folder on the device. thynkWISE does not create those files and does not switch that feature on. If your organisation enables recording, you may choose to sync them: you switch on Sync my call recordings in Profile, and then pick the folder yourself in the Android system folder picker.
Only then does the app read that folder. It reads audio files there, sends them to your organisation’s workspace so they can be attached to the matching call, and does nothing else with the folder. It never deletes, renames or modifies any file in it, and it never reads any other folder on the device. Sync is off until you switch it on, sends over Wi-Fi only unless you change that, and you can withdraw the folder access at any time in Android settings or by switching sync off — after which no further files are read.
Recordings you sync are stored encrypted, are visible to authorised people in your organisation, and are deleted on your organisation’s retention schedule. Where your organisation’s configuration or your local law requires callers to be told that a call is recorded, that obligation rests with you and your organisation; the platform will refuse a recording where its policy requires an announcement and none was reported. Recording law differs by country and state — do not enable this without confirming what your jurisdiction requires.
App analytics and ad measurement
The Play Store version of the app uses Google Analytics for Firebase, provided by Google, for one purpose: to tell us whether the app was installed or opened after someone saw one of our Google ads, so we can measure whether that advertising works.
It collects a random app-instance identifier that Firebase creates for this installation, the fact that the app was first opened, app sessions and updates, and the fact that a sign-in completed (with the method used — browser sign-in or restore key). Google also receives the device model, Android version, app version and an approximate location (city or region) derived from your network address. It does not receive your name, email, organisation, leads, phone numbers, call details, recordings or location from Profile, and the app sends none of those to Firebase.
The Android advertising ID is removed from the app and is never collected, and ad personalisation is switched off: this data measures our ads and is not used to show you personalised ads or to build advertising audiences. Google processes it under its own privacy policy and keeps it for the retention period configured for our Analytics property.
How we use and share data
Data is used to authenticate users, provide assigned work, prevent duplicate calls, synchronise outcomes, enforce calling policy, produce authorised reports, secure the service and resolve support incidents. We do not sell personal data and do not use it to show you personalised ads; the only advertising use is the install and sign-in measurement described above. Data may be processed by service providers acting for thynkWISE or your organisation only where needed to operate, secure or support the service, or where required by law.
Storage, security and retention
Network traffic uses encrypted HTTPS. Authentication tokens are stored using Android encrypted storage. Unsynchronised work may be kept temporarily on the device so it can be retried after connectivity returns. Signing out clears local credentials and tenant work data. Server records are retained according to the customer organisation's policy and applicable legal, security and audit obligations, then deleted or anonymised.
Your choices and deletion rights
You may decline optional permissions. Declining phone permission prevents managed calling. If your workspace requires location, protected work screens remain locked until a fresh check succeeds or your administrator changes the requirement. Screenshot sharing remains optional. For access, correction, export or deletion, contact your organisation's thynkWISE administrator or follow our account and data deletion process. Some audit or legal records may be retained where required by law.
Children
This employer-provisioned business application is intended only for users aged 18 or older and is not directed to children.
Contact
For privacy, support or deletion requests, email partner@thynkwise.co.in.
