This policy explains how CompilerX, operated by Klizo Solutions, collects, uses, stores, and shares information when you use our website, Chrome extension, account platform, and related services. It also explains the choices available to you. For privacy questions or requests, contact chrometeam@klizos.com.
1. Information we handle
- Account and authentication information. Your name, email address, account identifier, workspace membership, sign-in credentials or authentication tokens, and information returned by a sign-in provider. Google sign-in uses an authorization flow; CompilerX does not receive your Google password.
- Professional profiles and company research. Names, roles, employers, company details, professional locations, profile photos, website and LinkedIn links, visible posts or people cards you research, relationship signals, related recommendations, and the source and observation time of that research.
- Guest information. A random browser-installation identifier, your detected LinkedIn name, photo and profile URL, available business contact information, and research saved before you create an account.
- Workspace content and activity. Saved lists, notes, tags, follow-ups, research and enrichment requests, results, job status, timestamps, credit usage, and related operational records. Research URLs and timestamps identify supported pages used for these features; this is not a request for your complete Chrome browsing history.
- Billing and support information. Plan, purchase and subscription status, payment-provider identifiers, and information you choose to include in support requests. Payment details entered at checkout are handled by Stripe; the Chrome extension does not collect your card number.
- Technical information. Server requests may include IP address, browser or device information, request times, and diagnostic information needed to operate and secure the service. Professional location fields may come from researched profiles; the extension does not request device GPS access.
2. Chrome extension and automatic research
CompilerX reads supported page context to display company and contact intelligence. It uses LinkedIn’s account controls or Home/feed identity card to distinguish your own profile from a prospect you are researching. It does not treat an arbitrary open profile as your identity.
After you accept the welcome agreement, guest-profile detection and guest saving can happen automatically while the extension is in use, including before you create an account. Guest profile information is sent to CompilerX, and a configured contact-discovery process may look for and verify a business email associated with that profile. Guest research is stored so it can be restored when you later sign in through the same browser installation.
Authorized CompilerX team members can view guest profile and contact details for service support and product feedback. This does not subscribe you to promotional emails. Optional marketing communications require a separate choice.
Signed-in automatic research uses permitted LinkedIn pages and a workspace-scoped local cache. Other website access is requested for supported workflows when needed. We do not read LinkedIn messages or passwords, record arbitrary keystrokes, or automatically send LinkedIn, email, or WhatsApp messages.
3. Why we use information
We use information to authenticate accounts, enforce workspace permissions, prepare and organize research, find and verify contact details, display opportunity signals and recommendations, restore guest history, manage credits and subscriptions, provide support, request product feedback, and maintain the security and reliability of these features.
Contact data and verification results can be incomplete or become outdated. An opportunity score is a research aid. A verified mailbox does not establish a person’s current employment or guarantee delivery or a response.
4. Service providers and sharing
We use service providers for hosting, databases, authentication, transactional email, payment processing, contact discovery, verification, and enabled analysis features. These include Supabase, Render, Vercel, Mailgun, Stripe, and the contact-data or verification providers configured for a lookup. Providers receive information needed for the relevant operation, such as a profile URL, company domain, name, or email being checked.
Workspace information is available to members authorized by that workspace’s access rules. Saving research does not automatically publish it to other customers. Guest lead records are available to authorized CompilerX operators rather than to unrelated customer workspaces.
If you export data, share it with your team, or open a third-party action such as WhatsApp, information is handled by the destination you choose and its policies. We may also disclose information when required by law, to address fraud or security threats, or as part of a business transfer subject to applicable requirements and notices.
We do not sell extension user data, transfer it to data brokers for resale, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility.
5. Google sign-in and the separate Gmail pilot
Google sign-in provides the identity information needed to authenticate your CompilerX account. It does not itself authorize access to Gmail messages.
The optional Gmail add-on is a separate integration with its own Google authorization. When you use that integration, authorized message or contact context, such as sender details, signatures, or message-derived confirmation metadata, may be used for its contact research features. The Chrome extension can receive a contact handoff and related metadata, but its Gmail sidebar detection reads sidebar controls, not email bodies.
CompilerX’s use and transfer of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is limited to providing or improving the relevant disclosed features. Human access to Google user data is limited to user-authorized assistance, necessary security work, or legal requirements.
6. Storage, retention, and security
The extension stores settings, authentication sessions, bounded research caches, pending operations, and guest-history backups in Chrome storage. Server-side account and research data is stored through our service infrastructure. Website and extension sign-ins are separate sessions.
The signed-in local research cache is bounded and expires after seven days. Guest-history backups are bounded to up to 100 research records per browser session identifier. Server-side guest profiles and saved workspace records can remain until removed or a deletion request is fulfilled; uninstalling the extension does not by itself delete server records. Operational, billing, security, backup, and provider receipts may be retained where needed for reconciliation, legal obligations, or service protection.
We use HTTPS for service communications and apply authentication, workspace access controls, and restricted database access. No service can guarantee absolute security. Our service providers may process information in countries other than the country where you live.
Optional website and extension analytics
With your approval through Analytics preferences, we use Google Analytics 4 to measure visits to public website pages and clicks on Chrome Web Store buttons. With the same approval, anonymous visitor and session identifiers connect these visits to confirmed account creation, purchases, and paid upgrades. The server reports completed paid transactions after Stripe confirms them, including when checkout is closed before returning. Google receives a browser identifier, general device and traffic information, public page paths, the button placement, signup method, plan and seat count, purchase amount and currency, and an opaque transaction identifier. A first-party attribution cookie is shared across CompilerX subdomains for up to 24 hours. We exclude URL query strings and fragments, account and dashboard pages, account identifiers, contact details, researched profiles, and message content from these events. Advertising personalization and Google signals are disabled. CompilerX Recon is a separate analytics service that may connect approved signed-in visits to your contact record. You can decline or change your choice in the footer.
With the optional usage-analytics choice in the same welcome setup or in extension Settings, anonymous analytics also measures installation, first opening and guest use. The welcome page can reuse an approved website visitor identifier so these milestones connect to signup and a later paid upgrade. Direct installs without a matching website visit remain a separate cohort. This optional consent lasts up to 90 days. We keep the anonymous installation-to-account link privately to attribute later purchases; Google receives no account identifier, installation token, LinkedIn URL, contact information or research content. Leaving optional analytics off does not prevent core research; accepting the application’s research and data-use agreement is still required before those features start. Turning off extension analytics stops future linked reporting and cancels pending reports; previously delivered aggregate analytics may remain. Website analytics preferences are separate and a website decline overrides extension attribution for website checkout.
Chrome Web Store links contain campaign and button-placement tags so the Store can attribute listing visits and installations. Google operates the Store and its analytics separately. See Google’s Privacy Policy for how Google handles information.
Application agreement and essential storage
The welcome page explains core research, personalization, guest-history continuity, and support or product-feedback access before you accept. One welcome-page action records the agreement version and time in the extension’s protected local storage: “Accept & allow analytics” also enables optional analytics, while “Continue with essentials” leaves it off. The app does not require separate agreements for each internal component. Essential session, security, preference, workspace and research storage supports the features you request; optional analytics has its own on/off choice in that same setup.
Your own LinkedIn account or Home profile can help personalize research and avoid confusing you with a prospect. Related professional profile and company suggestions may support recommendations. This does not authorize reading private LinkedIn messages, sending messages, or using unrelated browsing history. Separate Google/Gmail or browser permissions are requested only when needed for the feature you choose. Purchases require confirmation at checkout; accepting the welcome page does not authorize payment or automatic refills. See our Terms of Use for research responsibilities, credits and billing.
7. Your choices and requests
- Withdraw the application agreement in extension Settings to pause research, or use the research controls to pause signed-in automatic LinkedIn research. The guest-history switch controls saving guest research; guest-profile detection is a separate feature.
- Manage website access in Chrome’s extension permissions. Removing the extension stops its future activity on that browser.
- Manage lists and research through your authorized workspace. Use the account platform to manage account and subscription settings.
- Use the website’s Analytics preferences control to change optional analytics choices. Optional website analytics is separate from operating your account.
- Contact chrometeam@klizos.com to request access, correction, deletion, or assistance with privacy choices. Include the relevant account email or LinkedIn URL so we can locate the record. We may need to verify your identity or workspace authority before acting.
Depending on your location, applicable law may provide additional rights concerning access, correction, deletion, portability, objection, or restriction. Legal and security obligations may require us to retain some information.
8. Changes and contact
We may update this policy when features or data practices change. The date above identifies the latest version. Material changes will be communicated through appropriate website or product notices.
CompilerX / Klizo Solutions
Privacy and extension support: chrometeam@klizos.com
Visit CompilerX Support