Who we are
Line1 is operated by NO4MAT, a French société par actions simplifiée with share capital of €100, registered at the RCS of Dax under SIREN 985 134 931 (SIRET 985 134 931 00023, VAT FR75 985 134 931). Its registered office is at 10 Avenue des Baïnes, 40510 Seignosse, France. The publication director is Paul-François Goriaux.
NO4MAT is the data controller for the marketing site and account administration, and a data processor for personal data handled on behalf of customers in their workspaces. Customers are responsible for the purposes and lawful use of that workspace data. Contact [email protected] for privacy questions or a data processing agreement.
Data we collect and use
- Account data: name, email, authentication identifiers, workspace membership, and role, to provide and manage access to Line1.
- LinkedIn session and browser data: the extension collects all cookies available to it for the linkedin.com domain, including subdomains, not just a single login cookie. It also sends profile identity and session context, including browser type, language, timezone, and display information. Line1's servers and the extension use them to make read-only requests to LinkedIn on the member's behalf.
- Posts and engagement: the member's own posts, the reactions and comments on them, aggregate impressions, and available profile viewer information.
- Messages and network: LinkedIn messages the member sends and receives, including message content, sender and recipient identities, conversation identifiers, and timestamps; invitations the member sends; accepted invitations; and new connections.
- Profiles and companies: names, profile links, photos, job titles, employers, location, work and education history, skills, and company details from LinkedIn and enrichment services, to match people to HubSpot contacts and companies.
- Business contact lookup: the extension uses the LinkedIn profile URL you visit to look up a business email through MoltSets and match the person to HubSpot. The card shows names, business emails and company details from HubSpot or enrichment providers, not profile content read from the page.
- HubSpot data: the HubSpot connection credentials, the contact, company, and owner records Line1 reads to match people, and the identifiers of the records and events it writes.
- Operational data: request and error logs, account activity, IP addresses, and browser information, to troubleshoot the service and detect abuse.
Line1 only reads from LinkedIn. It does not post, react, comment, send invitations, or send messages.
Data we write to HubSpot
Line1 writes the activity above to the HubSpot account the workspace connects.
- Contact timeline events: each interaction, with the member's name and email, the person's name and LinkedIn profile URL, a link to the LinkedIn post or conversation, the reaction type, and, for comments and messages, the full comment or message text. Messages are written only to contacts that already exist in HubSpot.
- Company timeline events: the same names, email, profile URL, and link, without comment or message text.
- Contact properties: dates of the last LinkedIn activity, invitations, and message, the LinkedIn connection status, and reaction and comment counts.
- Automatic new contacts: for interactions other than messages, when the person's profile has been enriched, their company is in HubSpot or meets the workspace's company creation rules, the member who had the interaction matches one HubSpot owner by email. The contact stores the person's name, job title, LinkedIn profile URL and LinkedIn identifier, is associated with that company, and is owned by that member.
- New companies: automatic creation requires the workspace to enable it. The company must match its industry or sector, company size and headquarters-country rules, and the person's job title must match its title keywords. The company stores its name, website domain, LinkedIn page and a Line1 identifier.
- Contacts added from the card: when you click Add to HubSpot, Line1 can create a contact with their business email, name, title and LinkedIn identifiers, owned by your mapped HubSpot user and linked to their company. This bypasses automatic creation settings, but waits for profile and company enrichment before creating missing records. Linking an existing contact writes its LinkedIn URL and known LinkedIn identifier.
Session access and storage
LinkedIn session cookies are sent over HTTPS and encrypted on Line1's servers for storage. They are decrypted only to make read requests to LinkedIn on the member's behalf. The extension also stores connection credentials, status, and session context locally in your browser.
From the time a member connects LinkedIn, Line1 reads their new LinkedIn activity until the member disconnects. When a member connects, Line1 also reads the previous 90 days of their LinkedIn activity. Every workspace syncs that history to HubSpot when a rep connects.
Disconnecting through the extension clears stored session credentials from the active account record. You can also revoke the session in LinkedIn's settings. Previously collected messages, profiles, and engagement data are separate from the session and are not deleted by disconnecting. Records already written to HubSpot stay in that HubSpot account.
Service providers and sharing
Service providers process data for hosting, database storage, authentication, background tasks, enrichment, and email. Providers used by Line1 include:
- Clerk — authentication and workspace membership.
- Cloudflare R2 — storage and delivery of profile photos.
- Inngest — background task processing.
- Fetchin — profile enrichment, including current company, using LinkedIn profile identifiers.
- MoltSets — GetEmails LLC d/b/a MoltSets, Austin, Texas, US, is a subprocessor for business email lookup from a LinkedIn profile URL.
- Resend — the email that tells a member their LinkedIn session expired.
Company identifiers are also sent to a company-data enrichment service to retrieve company profiles. Workspace members can access data according to their permissions. Captured activity is sent to the HubSpot account the workspace connects. If you use the API or the MCP server, workspace posts and contacts can be read by the tools you connect.
Deletion and your rights
Business contact lookup results are kept in Line1's shared cache for 30 days when found and 7 days when no match is found, then deleted within a day. To request erasure, send the LinkedIn profile URL or business email to [email protected]. HubSpot privacy-deletion notifications also remove cached lookups for known LinkedIn profile URLs.
To request deletion of account or workspace data, write to [email protected]. Disconnecting a LinkedIn account or ending a subscription is not a request to delete all associated data. Some records may need to be retained to meet legal obligations. Data written to HubSpot is stored in the customer's HubSpot account; the customer deletes it there.
Subject to applicable law, you may request access, correction, erasure, restriction of processing, and data portability, or object to processing. Where processing relies on consent, you may withdraw it. You may also complain to the CNIL or your local data protection authority.
Contact us at the address above to exercise your rights. For data we process on a customer's behalf, we may need to refer the request to that customer as controller.
Policy changes
Material changes are announced in-app and to workspace admins by email before they take effect.