thynkWISE Mobile Privacy Policy

About the app

thynkWISE Mobile 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, only if you switch it on. The app never asks for location on its own. If you enable “Share my location when I sign in” in Profile, the app takes a single approximate reading at sign-in and attaches it to that sign-in record. It is not collected while the app is closed or in the background, not collected during calls, and not tracked over time. You can switch it off in Profile at any time, and it is switched off automatically when you sign out.

We do not collect device contacts, precise location, photos, SMS messages, advertising IDs or Android call-log records. The optional 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

Location is optional and off by default. The app does not ask for it at startup or during a call; the only place it is requested is the “Share my location when I sign in” switch in Profile, and declining the Android prompt turns the switch back off. Only ACCESS_COARSE_LOCATION is declared. When enabled, the app takes one approximate reading at sign-in and sends it with that sign-in record; it registers no background listener and stores no location on the device. Turning the switch off stops it immediately, and signing out clears the choice so it does not carry over to the next person on a shared handset. Readings already attached to past sign-ins are kept as part of that historical record.

How it is used, and not used. The approximate location is attached to your sign-in record so your organisation's administrators can see when and roughly where their team was working. It is not sold, not used for advertising, not used to build a profile of you, and not shared with any third party — it is stored in your organisation's own database and is readable only by users in your organisation holding an administrator, manager or team-lead role. Ordinary users cannot see other people's sign-in locations.

How to turn it off. Profile → Location → “Share my location when I sign in”. Switching it off stops collection immediately and does not require you to change any Android setting. You may also revoke the permission in Android Settings › Apps › thynkWISE › Permissions.

How long it is kept. Sign-in records, including any approximate location attached to them, are retained for as long as your organisation's account exists. There is currently no automatic deletion schedule for them. They are removed or anonymised when an account-deletion request is processed — see the account deletion page, which also explains what may lawfully be retained afterwards.

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.

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 or use it for advertising. 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; core screens remain available, although declining phone permission prevents managed calling. 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.