1. Introduction
Contact Intelligence Tracker ("CIT", "the Extension", "we", "our" or "us") is a Chrome browser extension designed to support the manual verification, capture and management of professional contact information from LinkedIn profiles.
The Extension is intended for authorised company employees participating in a contact verification and quality assurance workflow.
This Privacy Policy explains what information the Extension handles, how that information is collected, stored, used, transmitted, shared and protected, and what choices are available to users.
By installing and using the Extension, users should review this policy and the disclosures presented during setup and before data collection.
2. Information We Collect and Process
Depending on the features used, the Extension may collect or process the following information.
2.1 Professional profile information
Information obtained from LinkedIn profiles during the manual verification workflow may include:
- Professional name.
- LinkedIn profile URL.
- Professional location displayed on the profile.
- Follower count.
- Connection count.
- Current company name.
- Current job title.
- Employment start month, where available.
- Approximate tenure in the current role.
- Whether the person is currently employed in the displayed role.
- Verification flags, notes and review information.
This information is used only to support the professional contact verification purpose.
2.2 Employee information
The Extension may process:
- Employee name.
- Employee identification code or employee ID.
- Employee activation status.
- Employee and device association.
- Verification activity records.
- Relevant timestamps.
2.3 Activation and authentication information
During employee activation, the Extension may process:
- Date of birth, where required by the configured activation workflow.
- Employee activation code.
- Device identifier.
- Device session token.
- Session status and related activation information.
Activation information is transmitted to the configured company backend for validation and device activation.
Authentication information, including session tokens, is not intended to be publicly displayed.
2.4 Screenshot evidence
The Extension supports screenshot evidence capture as part of the manual profile verification process.
Screenshots are intended to capture relevant visible professional profile information, such as the person's company name and job title, when the employee performs the applicable verification workflow.
Screenshots may be stored temporarily in a local upload queue before being transmitted to the configured company backend.
Users should avoid capturing unrelated personal information or browser content.
2.5 Activity and technical information
The Extension may process:
- Verification action events.
- Profile capture timestamps.
- Synchronisation status.
- Upload status.
- Device and session status.
- Technical information required to maintain the Extension's operation.
Activity information is limited to the contact verification workflow. The Extension is not designed to perform general keystroke logging or monitor unrelated browsing activity.
3. How Information Is Collected
Information may be collected through the following activities:
- Employee setup and activation.
- Manual interaction with the Extension.
- Opening and manually verifying a LinkedIn professional profile.
- Capturing relevant professional profile information.
- Performing the screenshot evidence workflow.
- Synchronising pending records with the configured backend.
- Retrying interrupted uploads when connectivity becomes available.
The Extension does not collect LinkedIn passwords, private LinkedIn messages, personal emails or unrelated website content as part of its intended functionality.
4. How We Use Information
Information processed by the Extension is used for the following purposes:
- Employee activation and device association.
- Professional contact verification.
- Recording relevant professional profile details.
- Maintaining verification records.
- Supporting quality assurance and review workflows.
- Associating screenshot evidence with the relevant verification record.
- Synchronising records with the company backend.
- Maintaining synchronisation and upload status.
- Troubleshooting technical issues and maintaining service security.
Information will not be used for advertising, unrelated profiling, creditworthiness assessments or lending decisions.
5. Local Storage and Backend Processing
5.1 Local Chrome storage
The Extension may store relevant operational information locally in Chrome, including:
- Employee setup information.
- Device and session information.
- Captured profile records.
- Synchronisation status.
- Extension preferences.
- Pending upload information.
5.2 Local screenshot queue
Screenshot evidence may be temporarily stored in the browser's local IndexedDB storage while awaiting upload.
The queue supports the completion of uploads when connectivity is interrupted.
5.3 Company backend
The beta version communicates with the configured Supabase staging backend.
The backend is used for:
- Employee activation.
- Device and session validation.
- Submission and synchronisation of verification records.
- Screenshot evidence uploads.
- Related operational backend requests.
The Extension communicates with the configured backend through encrypted HTTPS connections.
5.4 Privacy policy hosting
This privacy policy is hosted using Cloudflare Pages.
Cloudflare Pages is used to make the policy publicly accessible. It is separate from the Extension's contact verification backend.
6. Information Sharing and Access
6.1 Backend service provider
Information is transmitted to the configured Supabase staging backend to provide the Extension's activation, synchronisation and screenshot evidence functionality.
Supabase acts as a technical service provider for these operations.
6.2 Authorised company personnel
The intended company workflow permits authorised Team Leaders and Team Coaches to review relevant verification records through the company Admin Dashboard.
Access to individual records must be limited to authorised personnel and must be supported by appropriate notice and affirmative user authorisation for human access to the relevant data.
The company intends to enforce access through company-account verification, an administrator-managed email allowlist and role-based permissions.
These access controls must be configured and verified before the dashboard is used for operational access to personal data.
6.3 Other third parties
We do not sell, rent or provide user data to advertising networks, data brokers or unrelated third parties.
Information may be disclosed where required by applicable law or where necessary to protect the security of the Extension and its users.
7. Data Retention and Deletion
Information may remain in local Chrome storage, the local screenshot queue or the configured backend for as long as it is required for the contact verification workflow and associated operational purposes.
Local records may remain available until removed through the relevant browser or Extension data controls.
Backend records are subject to the configured company data management and retention procedures.
Users who require correction or deletion of records should contact the Extension operator or their authorised company administrator.
No fixed retention period is promised in this policy. Retention and deletion arrangements should be reviewed periodically and limited to what is necessary for the stated purpose.
8. Security
We take reasonable measures to protect information handled by the Extension.
These measures include:
- HTTPS communication with the configured backend.
- Controlled employee activation.
- Device and session validation.
- Restricted backend access.
- Protection of authentication information.
- Separation of the beta staging environment from the production environment.
- Appropriate access restrictions for company administration.
No internet transmission or electronic storage method can be guaranteed to be completely secure.
Users should not share their activation credentials or device session information with other people.
9. User Choices and Responsibilities
Users should:
- Review this Privacy Policy before using the Extension.
- Review the information displayed during employee activation.
- Provide only information necessary for the verification workflow.
- Avoid capturing unrelated personal or confidential information.
- Protect their activation credentials and device access.
- Contact the Extension operator if they identify an incorrect record or have a privacy concern.
Where a feature involves collection or human review of personal data, the required notice and affirmative authorisation must be obtained before that activity takes place.
10. Children's Privacy
Contact Intelligence Tracker is a professional business productivity tool and is not intended for children.
The Extension is not designed to collect children's personal information.
11. Changes to This Privacy Policy
This Privacy Policy may be updated when the Extension's functionality, backend services, data handling practices or applicable requirements change.
The latest version will be made available through the published privacy policy website.
Users should periodically review this page for updates.
Material changes to data collection or use should be disclosed to affected users before the changed practices begin.
12. Contact Information
For questions, privacy concerns, data correction requests or deletion requests, contact:
Prashant Sadbhaiya
Email: Prashant.Sadbhaiya@Gmail.Com
13. Chrome Web Store User Data Policy – Limited Use
Contact Intelligence Tracker's use of information received through the Extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information is collected, used and transmitted only to provide the Extension's disclosed professional contact verification functionality and its necessary operational services.
We do not sell user data, use it for personalised advertising, transfer it to data brokers or use it for creditworthiness or lending decisions.
Human access to individual user data is restricted to the permitted purposes and requires the appropriate user authorisation or another applicable exception under the Chrome Web Store User Data Policy.