Version 2026-10-05.1. Effective when published and, for contract terms, accepted. Current beta operation; real-money billing is not available.
Reading-copy editorial notice (16 October 2026): this website reading copy incorporates a factual company-status correction only. THREADLINE LDA was incorporated in Portugal on 9 October 2026 (NIPC / matrícula 519681169). The title and version shown above identify the historical accepted document; this is not a new accepted version, agreement or novation, and the original accepted documents and acceptance evidence remain archived unchanged.
Release and privacy status for extension 1.7.110
Supplement ID 2026-10-08.3. Status confirmed on 8 October 2026; privacy controls unchanged from 2026-10-08.2.
Extension 1.7.110 retains the privacy controls described in supplement 2026-10-08.2. The update clarifies the existing insufficient-signal Reveal message when a credit has been refunded. It does not change data collection, permissions, research decisions, credit or refund rules, browser storage, or the user journey.
On 8 October 2026, Threadline's founder confirmed that Google had reviewed, accepted and published extension 1.7.110, and that the installed-extension checks for Reveal, refunded credit balances and refresh had passed. These release confirmations supersede earlier pending Store and live-check status notes. Google review is separate from LinkedIn authorisation and is not a blanket legal or security certification.
The founder also confirmed completion of the outstanding supplier agreement, retention and transfer evidence and implementation of the restricted human-access procedure. Necessary operational records and provider-specific retention still exist. Access to specific extension-derived data remains subject to the applicable documented Limited Use exception; the closure does not create broader human access or a promise of zero retention.
This is a dated documentation and release-status update. It leaves accepted contract bundle 2026-10-07.1, prior acceptance evidence, customer rights, the existing processing purposes and published storage rules unchanged. Earlier notices below remain as history where their status statements have been superseded. The pre-existing provider-transfer and real-payment activation gate remains; no payment activation is announced by this update.
For privacy requests, including requests from prospects without an account, contact [email protected].
Save this dated update: HTML copy · Text copy.
Earlier dated notices and accepted text
Privacy update — extension 1.7.109 and aggregate founder reporting
Supplement ID 2026-10-08.2. Current control description for extension 1.7.109. Earlier accepted versions and the earlier same-day checkpoint are historical.
This update describes extension 1.7.109 and the matching backend and founder-reporting controls deployed on 8 October 2026. It supersedes the earlier 2026-10-08.1 checkpoint for these controls. Earlier notices and accepted contract versions are preserved as historical records; this update does not change contractual rights or create a new acceptance record.
In extension 1.7.109, opening a supported LinkedIn profile or the Threadline research panel reads the current professional profile locally for the existing interface. It does not send that currently viewed prospect's URL, name, company, profile identifier or profile-reference hash to Threadline merely because the page or panel opened. Account authentication, vendor settings, language, credit checks and an account-level download of previously saved Reveal results can still contact Threadline. The extension matches the current profile against those saved results locally; the lookup does not identify which profile is currently being viewed.
When you explicitly request Reveal, the professional profile information and company context required for the existing research and drafting feature are transmitted and processed normally. Previously requested in-flight Reveals can resume. Saved results, sources, generated content, explicit feedback, account access and credit/refund rules remain available under their existing controls. The change does not mean that Threadline collects no data.
Routine founder Analytics now provides aggregate usage and account administration separately. It does not expose named individual usage counts, activity times, per-person costs, prospect browsing history, individual-activity views or individual-usage exports. Small usage groups are suppressed, and account/company labels cannot be used to filter usage into individual reports. Account identity and ordinary account administration remain identifiable. Necessary raw product records and restricted operational access remain; aggregation and suppression are not an unconditional guarantee of anonymity. Human access to extension-derived data must be confined to a documented applicable Limited Use exception, such as the user's explicit consent to read specific data, necessary security work or a legal obligation.
Older extension installations can still send the earlier passive profile payload until updated. The deployed database guard continues to discard new passive profile-view inserts from those clients. Distribution of the verified 1.7.109 download does not establish Chrome Web Store review, publication or automatic installation; check the installed version. Earlier passive records were not deleted and retain the existing 180-day activity cleanup. Product/workspace records, private reporting facts, provider logs and backups have their separate retention rules. This update does not claim zero provider logging, immediate backup deletion, EU-only processing or completion of outstanding supplier/transfer evidence.
Threadline limits extension-data use to its disclosed research and drafting purpose and the related operation and security of that service. It does not sell extension data, use it for advertising or use it to determine creditworthiness. Final Chrome Web Store package/declaration reconciliation remains a separate verification step; this notice is not Chrome approval or a blanket legal-compliance certification.
For access, correction, deletion, restriction or objection requests, including requests from prospects without a Threadline account, contact [email protected]. Existing rights and contact routes continue to apply.
Save this dated update: https://app.threadlinehq.io/legal/privacy-update-2026-10-08.2.html. Download text: https://app.threadlinehq.io/legal/privacy-update-2026-10-08.2.txt.
Historical checkpoint and earlier accepted notice — preserved text
Privacy update — 8 October 2026
Supplement ID 2026-10-08.1. The existing version shown above and saved by the earlier-copy buttons is retained as the historical contract/notice version. This supplementary notice describes the current privacy change.
This dated update supplements the earlier notices reproduced below. It describes the backend privacy change deployed on 8 October 2026; it does not replace previously accepted contract versions or change your contractual rights.
When the Threadline research panel opens on a supported profile, the extension can still send the current prospect's profile URL, name and company to Threadline before you request a Reveal. From the backend update on 8 October 2026, Threadline discards these passive profile-view events before inserting them into its activity database. Transmission therefore still occurs; the update does not mean that collection starts only after Reveal.
Requested Reveal processing, saved prospects and outputs, explicit feedback, authentication and credit accounting are unchanged. Future passive panel openings no longer supply new activity records for dashboard company ranking, refresh decisions or fallback history. Existing saved prospect records remain available to the dashboard.
Earlier activity records were not deleted by this update and remain subject to the existing 180-day activity cleanup. Saved Reveal/workspace records have their separate retention rules. Provider request logs and backup copies have separate lifecycles; absence from the activity database is not a promise of zero provider logging or immediate backup deletion.
Private founder Analytics still includes identifiable account-linked usage, including activity times, feature counts and costs. Its fact dataset does not copy full prospect URLs, prompts or message content. Restricting access to founders does not make these records anonymous. The outstanding Chrome disclosure/choice and Limited Use human-access questions are not resolved by this storage change or by publishing this notice.
For access, correction, deletion, restriction or objection requests, including requests from prospects without an account, contact [email protected]. The existing rights and contact routes continue to apply.
Save this dated privacy update · Download the text copy
Earlier notice — preserved text
1 Relationship to the main Terms
These terms supplement the Threadline Terms of Service for the browser extension, profile context, public-web research, AI features, monitoring, shared briefs and third-party services. They do not override mandatory consumer protections, the DPA’s processor obligations or applicable data-protection law.
2 Independent service and platform restrictions
Threadline is independent from LinkedIn and other content sources. Use of a browser, API, trademark or public page does not establish endorsement or permission.
LinkedIn’s current agreements restrict certain browser-plugin copying, scraping and overlays. A user clicking a button, low processing volume or publicly visible information does not guarantee an exception. LinkedIn may change its pages, restrict extensions or act against an account. Threadline does not promise platform approval or uninterrupted access.
3 Actual operation
The extension displays its interface on supported LinkedIn pages. Opening its panel can transmit a profile-view event including a prospect URL, name and company before Reveal. A requested Reveal processes selected professional context and company research. The service does not open other LinkedIn profiles in the background or automatically send LinkedIn invitations, messages, comments or likes.
The web app’s monitored announcements refresh public-web information for companies selected by the user. That scheduled company research is distinct from browsing additional LinkedIn profiles. The Privacy Notice and extension disclosure describe collection and retention.
4 Lawful use and source rights
Use only accounts and material you are authorised to access. Do not evade authentication, access controls, rate limits, paywalls, contractual restrictions or suppression instructions. A feature being technically available is not legal permission.
Professional names, roles and inferred interests can be personal data even when public. Customers who determine prospect purposes must document their basis, minimise data, give notices, handle rights and apply the relevant electronic-marketing rules. Public material may also be protected by copyright, database rights, confidentiality or contract. Verify what you may reuse.
5 AI and provider dependencies
AI output requires human review. Input can include personal and confidential business information; submit only what is authorised for the requested processing. Providers, categories and transfers are described in the Privacy Notice. No general promise of zero retention, EU-only processing or perfect accuracy is made.
Third-party outages or policy changes can affect research and generation. Threadline may limit, suspend or redesign a feature to address a legal, security or platform issue, while preserving applicable contractual and consumer remedies.
6 Sharing and collaboration
Shared briefs are accessible to anyone possessing the link until expiry or revocation. Recipients can forward the link or retain a copy. Minimise personal and confidential material before sharing. Revocation ends access to Threadline’s link but cannot recall downloads or copies.
Workspace roles determine access within Threadline. A user exporting material to another system is responsible for lawful use and downstream rights/deletion handling within that system.
7 Allocation of responsibility
Threadline remains responsible for its own conduct, product design, processing agreements and disclosures. User responsibilities do not transfer those obligations or legalise prohibited platform conduct. Customers remain responsible for their instructions and outreach decisions. The main Terms govern warranties, liability, suspension and disputes, subject to mandatory law.
Threadline is currently operated jointly by Diogo Baptista and Pedro Castro. Correspondence address: Rua Aristides Sousa Mendes n8 6o andar, 1600-413, Lisboa, Portugal. Contact: [email protected]. THREADLINE LDA was incorporated on 9 October 2026 (NIPC / matrícula 519681169); the effective transfer of the provider role to it has not yet been confirmed, so it is not the present contracting party.
Company case studies and use-case links — 26 October 2026
Supplement 2026-10-26.1
This notice describes the case-study library introduced with Threadline 1.7.146. It takes effect for this functionality when the corresponding app and backend are released. It does not change earlier accepted terms or record a new agreement.
When you generate your company profile, Threadline uses the company name, product or service category and website to find public customer stories and use-case pages on that website and through web search. You can also submit public page links. This work continues in the background and does not require uploading a document. The search and extraction use OpenAI; the saved library is held in Threadline’s Supabase backend. No additional provider or Chrome permission is introduced by this feature.
Threadline reads public pages and stores their source links, titles, customer and industry names, stated teams and responsibilities, a short description of the problem and use case, reported outcomes, a short supporting excerpt and source/check dates where available. Pages are processed to extract these facts; full source documents are not retained as library attachments. Public source material can contain professional names or quotations. Source facts and AI summaries may be incomplete or inaccurate. The source link remains available for review.
Your company library is associated with your account. In a managed Teams workspace, members use the workspace owner’s company library; the owner manages its links. The library is not a public directory. When you request a new message or regenerate one, Threadline may supply a limited set of previously read facts to the existing writing model. The model decides whether they are relevant. It does not search case-study pages during Reveal, and a missing or unavailable library does not prevent writing. Saving case studies or generating a draft does not send outreach.
You can remove links in the Library tab during setup or on the web app’s Library page. Removal excludes the related evidence from future library inputs and prevents a discovery job already in progress from adding that removed link back. It does not rewrite earlier saved messages or retract text you copied or sent. Changing the company identity replaces its active library. Account deletion removes the account’s library; providers’ logs and backups follow their separate retention schedules. Facts checked more than 90 days ago are excluded from writing, which is a freshness limit rather than automatic deletion. Regenerating a profile can refresh a library older than 30 days, and the Find links again control requests a refresh subject to service limits.
Existing rights, security controls, provider disclosures and contact routes continue to apply. Contact [email protected] for data-rights requests or concerns about a source.