Privacy policy

Account information includes your email address, optional name, authentication records, and plan. Relationship information includes the LinkedIn profile URL and ID, basic profile details visible on the page you choose to visit, the notes you write, interaction dates, tags, and reminders.

ContactLore does not ask for or store your LinkedIn password. It does not store complete LinkedIn page HTML, crawl connection lists, or browse profiles automatically.

The Chrome extension loads on LinkedIn so it can detect client-side navigation from the feed or another page to an individual profile. It stays inactive away from profile pages. On a profile page it reads the visible name, headline, company, profile image URL, and canonical profile URL so you do not have to retype them.

When you are signed in and open a LinkedIn profile page, the extension asks ContactLore whether you already saved that person, which sends that profile URL to our servers even if you never save a note. This lookup is what lets your existing note appear on the page. It is not used to build a browsing history, and we do not retain these lookup URLs beyond the short-lived request logs our hosting providers keep. If a profile is already saved and the visible name, headline, company, or image has changed since you saved it, the extension updates those fields on your saved contact so the record does not go stale.

Notes save to your ContactLore account after you pause typing. If a new note is blocked by the Free contact limit, the draft stays in Chrome extension storage on that device until it is saved, replaced, or local browser storage is cleared.

We use this information to authenticate you, display and search your saved contacts, sync notes between the extension and dashboard, enforce plan limits, provide Pro features, process billing, diagnose failures, prevent abuse, and operate the service.

We do not sell relationship notes or use them to create public profiles. ContactLore has no public note feed and does not show one user's notes to another user.

ContactLore uses Supabase for authentication and database hosting, Stripe for subscription billing, Vercel for application hosting, and Sentry for error diagnostics when Sentry is configured. These providers process the information needed to perform their services under their own privacy terms.

We may disclose information when required by law, to protect users or the service, or as part of a business transfer. We do not receive or store full payment-card numbers; Stripe handles payment details.

Application access controls and database row-level security separate user accounts. Server credentials are kept out of the browser and extension. Data is encrypted in transit by the hosting providers.

No online service can promise absolute security. Authorized operators and service providers may access limited data when necessary for support, security, legal obligations, or service operation.

You can edit or delete individual contacts from the dashboard. You can delete your account and its ContactLore data from Settings. Billing records and security logs may be retained when required for accounting, fraud prevention, dispute handling, or legal obligations. Provider backups can persist for a limited restoration period.

Signing out from the extension removes its saved session. Local drafts remain until they are saved, replaced, cleared from extension storage, or removed by uninstalling the extension. You may also contact Blackjay LLC through the link below with a privacy or data-access question.

You do not need a ContactLore account to be written about, so there is a route for people who are not users. Use the notes about you page to ask us to remove notes about you, tell you what exists, or correct something wrong. Notes are private to whoever wrote them, and we may ask you to confirm your identity before acting so that this route cannot be used against someone else's record.

ContactLore is a professional productivity service and is not directed to children under 13. If you use the service outside the United States, information may be processed in the United States and other locations where our providers operate.

We may update this policy when the product or legal requirements change. Material changes will be identified by a new effective date on this page.