Privacy Policy
Jigro CRM
1. Introduction
Welcome to Jigro CRM. Jigro CRM is a customer relationship management mobile application designed to assist sales professionals, tele-calling representatives, and commercial teams in organizing sales leads, facilitating outbound calls, tracking follow-up tasks, and monitoring team sales workflows.
This Privacy Policy describes how information is collected, used, stored, transmitted, and handled through the Jigro CRM mobile client application.
This policy applies specifically to the mobile application operated by Jigrotech Solutions Pvt. Ltd. ("we," "us," or "our").
2. Information We Collect
Jigro CRM collects and processes information necessary to provide CRM functionality across the following categories:
A. User and Account Information
When you access or authenticate your account, the application processes:
- Full name
- Work email address
- Contact phone number
- Assigned organizational role (e.g., Sales Executive, Team Leader, Admin, Super Admin)
- Assigned squad or team name
- Account operational status (active or inactive)
- Internal system user identifiers
B. Lead and Customer Information
The application processes contact and business information regarding prospects and clients, either manually entered by users or imported via spreadsheet files:
- Lead full name
- Primary and secondary telephone numbers
- Email address
- Company or organization name
- Job title or professional designation
- Pipeline stage and status
- Priority classification
- Lead acquisition source
- Customer requirements and specifications
- Custom operational fields configured for your organization
C. Profile Information
You may view and update:
- Your display name
- Your contact telephone number
- A profile avatar image selected from your device's photo library or file storage
Note: The application does not access or use a device camera.
D. Call and Telephony Information
When outbound calls are made to leads through the device's native dialer, the application accesses device telephony logs to capture:
- The dialed telephone number
- Call timestamp
- Call duration (talk time in seconds)
- Ringing duration (in seconds)
- Call connection status (e.g., connected, busy, missed, or failed)
E. Sales Notes and Activity Information
The application collects notes and activity records generated during sales operations:
- Scheduled follow-up dates and times
- Interaction notes and tele-caller remarks
- Stage change audit trails and activity history
F. Business and Property Information
Where applicable to client inquiries and recorded by sales representatives, the application processes:
- Budget estimates or investment allocations
- Property preferences or commercial requirement descriptions associated with specific lead records
G. Technical Information
During active use, the application processes:
- Device network connectivity status
- API request and response status codes
- Runtime network diagnostic payloads logged locally on the device
3. How We Use Information
The information collected by Jigro CRM is used solely to provide core CRM services:
- Managing sales pipelines, lead distribution, and team assignments
- Launching outbound calls through your device dialer and recording call duration from device call logs into corresponding CRM records
- Scheduling follow-up reminders and tracking prospect communication deadlines
- Authenticating user credentials and enforcing role-based permissions
- Importing lead contacts from user-provided spreadsheet files
- Enabling users to update their profile information and avatar photo
4. How We Share Information
Information handled by Jigro CRM is shared only in the following contexts:
- Within Your Organization: Lead data, call duration logs, follow-up notes, and user profile information are synchronized with the central server infrastructure and are accessible to authorized team members, team leaders, and administrators based on role hierarchies.
- Backend Service Infrastructure: Application data is transmitted to the dedicated server infrastructure hosting the application programming interface (API).
- Commercial Data Sharing Policy: [Company Legal Name] does not sell, rent, or trade your personal information or your leads' data to third-party data brokers or advertising networks.
- Legal Compliance: Information may be disclosed if required by applicable law, regulation, valid court order, or governmental authority.
5. Phone Calls and Call Log Data
Jigro CRM incorporates tele-calling workflows under the following parameters:
- Native Dialer Integration: The application does not conduct Voice-over-IP (VoIP) calls within the app. When placing a call, the application opens your mobile device's native phone dialer with the prospect's number pre-filled. The call is placed through your standard cellular carrier.
- Android Call Log Access (READ_CALL_LOG): On Android devices, the application requests access to read device call history. This access is used solely to verify recent calls placed to the dialed number, retrieve talk duration and connection status, and log these metrics directly against the active CRM lead record.
- No Call Audio Recording: Jigro CRM does not record phone conversations, monitor voice calls, or capture audio. The application does not request microphone permissions (RECORD_AUDIO) and contains no audio recording services.
6. File and Media Access
The application requests access to device storage and media files for specific, user-initiated actions:
- Profile Image Selection: Access to image files is requested solely to allow users to select an existing photo from their local photo gallery to use as an avatar. The application does not request camera permissions and cannot capture photos directly from a camera.
- Spreadsheet Lead Import: Access to device storage is requested when a user chooses to import .xlsx (Excel) or .csv files containing lead contact records from their device storage.
- The application does not scan, index, or access unselected files, documents, or personal media.
7. Location Information
- No GPS or Real-Time Location Tracking: Jigro CRM does not request or access GPS, fine location, or coarse location permissions. The application does not monitor your physical coordinates, travel routes, or device location.
- Manually Entered Address Information: Any street address, city, state, or postal/pincode information contained within the application consists entirely of business contact data manually typed by sales representatives or imported via spreadsheets for business contact records.
8. Data Storage
- Local Device Storage: To maintain active user sessions between app launches, the application stores the following authentication and profile values locally on the device:
- Session authorization tokens (access_token, member_token)
- User identifiers (member_id, userName)
- Session login state and UI display flags
*Notice: Local device storage is maintained in standard application storage without custom local database encryption.*
- In-Memory Temporary Storage: Active lead lists, daily queues, and transient query results are held in volatile device memory while the application is running. This temporary cache is erased whenever the application is closed or restarted.
- Backend Server Storage: Lead records, user profiles, and call metrics are transmitted to and stored on the backend server infrastructure.
9. Authentication
Access to Jigro CRM requires authentication using a registered work email address and password submitted to the backend API.
Upon verification, the server issues an authorization token (access_token), which is included in the HTTP Authorization header on subsequent API requests.
User sessions remain active on the device until the user explicitly signs out or local application data is cleared.
10. Data Retention
- On the Mobile Device: Locally stored session tokens and user identity values remain on your device until you select "Sign Out" or clear application data through your device settings. Signing out purges the session tokens and cached user profile from the device.
- In-Memory Cache: Temporary lead caches and daily operational metrics held in device memory are erased immediately when the app process is terminated.
- On Central Servers: Retention schedules, archival policies, and deletion procedures for lead records, call logs, and user accounts stored on backend servers are governed by [Company Legal Name / Data Retention Policy Placeholder].
11. User Rights and Choices
Jigro CRM provides the following choices regarding your data:
- Review and Profile Updates: You can review and update your display name, contact phone number, and avatar image through the in-app Edit Profile view.
- Session Termination: You may end your active session and delete local credentials from your device at any time by selecting "Sign Out" in the Profile menu.
- Permission Management: You can grant or revoke device permissions (Call Logs and Storage/Media) through your device's operating system settings at any time. Revoking permissions will disable corresponding features, such as automatic call duration retrieval or spreadsheet file importing.
- - In-App Feature Limitations:
- *Account Deletion:* The mobile application does not currently feature a self-service in-app account deletion button. Requests for account deactivation or data erasure should be directed to your organization's administrator or to [Privacy Email].
- *Data Export:* Self-service exporting of lead databases directly from the mobile app to external files is not currently implemented in the mobile application.
12. Children's Privacy / Age Policy
Jigro CRM is a business-to-business sales application intended exclusively for commercial business use by sales representatives and working professionals. The application is not directed to children, and we do not knowingly collect personal information from individuals under the age of [Minimum Age Placeholder, e.g., 18].
13. Third-Party Services and Dependencies
The application directly integrates the following third-party runtime libraries and system APIs:
- Google Fonts: Used for typography rendering (Poppins font family).
- System URL Launcher: Used to open the device's native phone dialer and default email client.
- System File Picker: Used to select images from the gallery and spreadsheet files from device storage.
- Android Telephony APIs: Used to read recent cellular call duration and talk time from device call records.
- Dio Client and Logging: Used for network communication and runtime network diagnostics.
The application does not embed third-party advertising networks, commercial analytics tracking SDKs, or social media tracking plugins.
14. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect operational, legal, or technical modifications. When changes are made, the "Last Updated" date at the top of this document will be revised. Material updates will be communicated through [Notice Method Placeholder, e.g., in-app notifications or corporate communications].
15. Contact Information
For questions, requests, or privacy inquiries concerning this Privacy Policy, contact:
- Company / Controller: Jigrotech Solutions Pvt. Ltd
- Privacy Email: info@jigrotech.com
- Support Phone: 8826239980
- Data Protection Contact: [Data Protection Officer / Contact Person]
16. Governing Law and Jurisdiction
This Privacy Policy and any disputes arising from or relating to your use of the application shall be governed by and construed in accordance with the laws of [Governing Jurisdiction,India], without regard to conflict of law principles. Any legal actions or proceedings arising hereunder shall be brought exclusively in the competent courts located in [Jurisdiction /Jaipur, Rajasthan, India].