Privacy policy
Last updated 2026-08-15.
What we process
Lyncera processes: (1) account data — email, name, locale, timezone, your own LinkedIn profile if you save it, and your calendar feed URL; (2) contact data you save — name, title, company, location, the public summary, experience, skills and job changes of profiles you analyze, your notes, and a copy of each profile photo, stored rather than linked; (3) a work email address, if your deployment enables discovery; (4) AI analysis results; (5) usage metadata for billing; (6) your IP address, for rate limiting; (7) a mailbox credential, if you connect a mailbox.
User-triggered processing only
The browser extension reads a LinkedIn page only when you press an explicit action on a page you opened yourself. We never crawl, queue, or collect profiles in the background, and never store raw page HTML. Nothing sends mail automatically or in bulk: if you connect your own mailbox, one message goes out per press of send, and no endpoint accepts a list. Connecting a mailbox stores a send-only credential, encrypted at rest — it grants permission to send, not to read your mail.
Data retention and your rights
Your workspace's retention setting (default 365 days) sweeps analysis history, research runs, audit logs, the usage ledger and AI-run metadata. Saved contact records — people, their experience, skills, job changes and stored photographs — have no expiry; they stay until deleted. Owners and admins can export workspace data as JSON: the file covers 17 tables and does not include skills, job changes, saved segments, notifications, audit logs or the stored photographs. You can delete your account, including workspaces you solely own, from Settings → Privacy & data.
Subprocessors
Live today: Supabase (database, authentication, storage), Vercel (hosting), Anthropic (AI processing) and Stripe (payments). AI providers do not train on your data under our agreements. Five more are built but switched off unless a deployment enables them: OpenAI as an alternative AI provider, Hunter.io for work email discovery, Google (Gmail) for sending from your own mailbox, HubSpot for contact sync, and Resend for the weekly digest. The full list is in the product documentation.
Data you send to your own tools
Settings → Developers lets you create an outbound webhook or an API key. When you do, Lyncera sends workspace events to the URL you chose, as they happen — eight event types, and the payloads carry the contact data each event is about. `job_change.detected` sends the person's name, their previous and new employer, and their new job title. That destination is yours and not ours: we do not control it, it is not one of the subprocessors named above, and you are responsible for what it does with what it receives. Webhooks send nothing until you create one, only ever carry events from the single workspace they were created in, and can be deleted at any time.
Website analytics
The public pages of the Lyncera website are measured with Vercel Web Analytics — which page was opened, where the visit came from, the country, and the kind of device. It sets no cookie and builds no profile of you across other sites, which is why you are not asked to consent to one. The signed-in application is excluded: those page views are dropped in your browser before anything is sent, so how you use the product is not measured here. The figures are aggregate and are not linked to your account.
Chrome Web Store Limited Use
Lyncera's use of information received through the Chrome extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. What the extension reads is used only to provide the features you triggered — the analysis, the score and the draft you asked for — and to keep the records you chose to save. It is never sold, never transferred to anyone but the subprocessors named above, never used for advertising or ad targeting, and never used to build a profile of anyone for anybody but you. No human reads it, except with your permission, for support you have asked for, where it is necessary to investigate abuse or a security incident, or where the law requires it.
Contact
Questions about privacy: support@lyncera.ai