Prospect Data Notice and Customer Template

Version 2026-11-03.1 — 3 November 2026

Current reading copy · 3 November 2026

Version 2026-11-03.1. This document contains a public explanation and a customer-specific notice template. Complete the responsible controller’s details and deliver the appropriate notice; publishing a general page is not proof that Article 14 notice was given to a person.

1 Why your information may appear in Threadline

A customer may select your professional profile or provide information about you to prepare relevant business research and a possible communication. Threadline can process your name, job, employer, professional location, profile URL, biography, work history and related public-web/company information, plus generated summaries or inferences. Sources can include the profile visible to the customer, company websites, public news and the customer. Signed-in professional sources are not necessarily public to everyone.

Public professional information remains personal data. An AI inference can be incorrect; it is not a verified statement about you.

2 Who is responsible

The organisation or person deciding to research or contact you is normally controller for that purpose. They must identify themselves, explain their lawful basis and interests, give required notice and handle your rights. Threadline processes customer workspace data on documented instructions under its DPA.

Threadline is separately controller for its own service security and other purposes it determines, described in its Privacy Notice. It cannot use a customer’s controller role to avoid its own obligations. Threadline is provided by THREADLINE LDA, a Portuguese sociedade por quotas, NIPC / commercial-registration number 519681169, registered with Conservatória do Registo Comercial R.N.P.C., with share capital EUR 1,000. Registered office: Rua Aristides de Sousa Mendes, 8, 6º frente, 1600-413 Lisboa, Portugal. Contact for service, privacy, contracts and complaints: [email protected].

THREADLINE LDA handles its own controller obligations, separately from customers’ responsibilities for the purposes they determine.

3 Purposes lawful basis and recipients

Customer prospect research and outreach require a specific lawful basis. If legitimate interests are used, the controller must identify the interest, show necessity, assess reasonable expectations and risks, and apply safeguards. A user’s acceptance of Threadline’s Terms is not your consent. Electronic marketing also has separate channel and country rules; an email address displayed for work does not automatically permit unsolicited marketing.

Threadline’s backend and AI providers can process selected context to create the requested research and drafts. Authorised workspace users can see relevant records. If a customer creates a public brief, anyone holding its link can view it until expiry or revocation and can retain copies. The customer must explain actual recipients, transfers and safeguards relevant to its processing; the Threadline Privacy Notice describes the platform’s providers and retention.

4 Retention and your rights

The customer must state a specific period or meaningful retention criteria for its prospect records. Threadline’s saved workspace records do not have a universal inactivity expiry. Short-lived caches and raw job records have separate shorter schedules; deleting one cache does not remove every saved output, public brief or exported copy.

You can ask the responsible controller for access, correction, deletion, restriction, portability where applicable, or object to legitimate-interest processing. You can object at any time to direct marketing and related profiling. If consent was used, you can withdraw it without affecting earlier lawful processing. You may complain to the CNPD or your competent supervisory authority.

No Threadline account is required to contact [email protected]. Provide the profile URL or enough context to locate your data. Threadline will handle its own controller obligations and assist or direct the request to the customer where it is processor. We use proportionate verification and do not routinely require an identity-document copy.

5 Timing and delivery

The responsible controller provides Article 14 information within a reasonable period and no later than one month after obtaining the data, at the first communication if earlier, or before first disclosure if earlier. Document the date, recipient, notice version and method of delivery. Public-source collection is not itself an exception. Any claimed exception requires a specific recorded legal assessment and safeguards.

6 Customer notice template

Complete every bracketed item before use. This is a template, not a notice ready to send. Do not send a marketing message merely to deliver privacy information if the marketing itself is not permitted.

Controller: [legal name, postal address and privacy contact; DPO contact if applicable]. We obtained your [specific professional data categories] from [specific source and whether publicly accessible] on [date]. We use it for [specific research/contact purpose] on [lawful basis]. If relying on legitimate interests, our interest is [specific legitimate interest and brief explanation].

We use Threadline to organise the selected information and produce AI-assisted research/drafts. Recipients are [actual internal recipients and service providers]. Processing may take place in [actual countries]; the relevant safeguards and how to obtain them are [details/link]. We keep these records for [period or meaningful criteria]. [Describe any relevant automated decision-making, or state that none with legal or similarly significant effects takes place, only if true.]

You may request access, correction, erasure, restriction or portability where applicable and object to relevant processing by contacting [privacy contact]. You can object to direct marketing at any time. [If consent is used, explain withdrawal.] You may complain to [competent authority]. More information: [complete customer privacy-notice link].

Short first-contact layer: [Controller legal name] obtained your [data] from [source] for [specific purpose]. Our full privacy information is at [link]. Contact [privacy contact] to exercise your rights or object. Include the full information through an accessible second layer within the applicable deadline.

7 Suppression and correction

A marketing objection must stop the relevant processing for that purpose. Keep only the minimum suppression identifier and context necessary to prevent repetition, with restricted access and periodic review. Assess corrections or erasure across source records, generated inferences, saved drafts, shared briefs, customer exports and provider copies; record recipients notified where Article 19 requires it.

This template does not prove that a legitimate-interest assessment, notice-delivery process or suppression control has already been implemented.

Current feature storage and processing

Signing in connects the extension to your Threadline account. One active extension session is authorised per account; another extension sign-in replaces it. Dashboard sessions are separate. Tokens and the connection credential are held in local Chrome extension storage, not Chrome sync. Signing out, revocation or account deletion ends the relevant authorisation. Signing in or reconnecting does not grant extra credits.

Working drafts are scoped to the account. They can include generated or edited messages, emails, translations, selected research context and language choices. They expire after seven days from last save or next access, are bounded locally, and are cleared on sign-out or account change. They are not ordinary cross-device draft sync. Saving or editing a draft alone does not create a new Reveal; requested generation or translation sends the relevant text and context to the AI processing service.

Library entries contain public company case-study/use-case links or manually entered titles and text. Customers can review, remove or refresh links and choose whether manual content may be used by AI. Enabled content can be used as seller context in requested research and drafts, including through the disclosed AI provider. Library evidence is not proof of a claimed outcome for the current prospect. Do not enter material you are not entitled to disclose.

The optional call playbook uses the selected prospect/signal and your call settings to prepare text. It is not a call recorder or automatic dialler. The current simplified flow keeps the user in control and uses the same disclosed research and AI processing chain.

Older installed extension versions can still send the former passive profile payload until updated; the database guard discards new passive profile-view inserts. Historical activity records retain the existing cleanup schedule. Saved research, explicit feature actions, provider logs and backups have separate lifecycles described in the Privacy Notice.

Earlier wording and dated notices

Earlier operational descriptions are retained below as history. The current explanations above incorporate their later corrections. Accepted contract versions and customer rights are unchanged.

# Prospect Data Notice and Customer Template
Version 2026-11-03.1. This document contains a public explanation and a customer-specific notice template. Complete the responsible controller’s details and deliver the appropriate notice; publishing a general page is not proof that Article 14 notice was given to a person.
## 1 Why your information may appear in Threadline
A customer may select your professional profile or provide information about you to prepare relevant business research and a possible communication. Threadline can process your name, job, employer, professional location, profile URL, biography, work history and related public-web/company information, plus generated summaries or inferences. Sources can include the profile visible to the customer, company websites, public news and the customer. Signed-in professional sources are not necessarily public to everyone.
Public professional information remains personal data. An AI inference can be incorrect; it is not a verified statement about you.
## 2 Who is responsible
The organisation or person deciding to research or contact you is normally controller for that purpose. They must identify themselves, explain their lawful basis and interests, give required notice and handle your rights. Threadline processes customer workspace data on documented instructions under its DPA.
Threadline is separately controller for its own service security and other purposes it determines, described in its Privacy Notice. It cannot use a customer’s controller role to avoid its own obligations. Threadline is provided by THREADLINE LDA, a Portuguese sociedade por quotas, NIPC / commercial-registration number 519681169, registered with Conservatória do Registo Comercial R.N.P.C., with share capital EUR 1,000. Registered office: Rua Aristides de Sousa Mendes, 8, 6º frente, 1600-413 Lisboa, Portugal. Contact for service, privacy, contracts and complaints: [email protected].
THREADLINE LDA handles its own controller obligations, separately from customers’ responsibilities for the purposes they determine.
## 3 Purposes lawful basis and recipients
Customer prospect research and outreach require a specific lawful basis. If legitimate interests are used, the controller must identify the interest, show necessity, assess reasonable expectations and risks, and apply safeguards. A user’s acceptance of Threadline’s Terms is not your consent. Electronic marketing also has separate channel and country rules; an email address displayed for work does not automatically permit unsolicited marketing.
Threadline’s backend and AI providers can process selected context to create the requested research and drafts. Authorised workspace users can see relevant records. If a customer creates a public brief, anyone holding its link can view it until expiry or revocation and can retain copies. The customer must explain actual recipients, transfers and safeguards relevant to its processing; the Threadline Privacy Notice describes the platform’s providers and retention.
## 4 Retention and your rights
The customer must state a specific period or meaningful retention criteria for its prospect records. Threadline’s saved workspace records do not have a universal inactivity expiry. Short-lived caches and raw job records have separate shorter schedules; deleting one cache does not remove every saved output, public brief or exported copy.
You can ask the responsible controller for access, correction, deletion, restriction, portability where applicable, or object to legitimate-interest processing. You can object at any time to direct marketing and related profiling. If consent was used, you can withdraw it without affecting earlier lawful processing. You may complain to the CNPD or your competent supervisory authority.
No Threadline account is required to contact [email protected]. Provide the profile URL or enough context to locate your data. Threadline will handle its own controller obligations and assist or direct the request to the customer where it is processor. We use proportionate verification and do not routinely require an identity-document copy.
## 5 Timing and delivery
The responsible controller provides Article 14 information within a reasonable period and no later than one month after obtaining the data, at the first communication if earlier, or before first disclosure if earlier. Document the date, recipient, notice version and method of delivery. Public-source collection is not itself an exception. Any claimed exception requires a specific recorded legal assessment and safeguards.
## 6 Customer notice template
Complete every bracketed item before use. This is a template, not a notice ready to send. Do not send a marketing message merely to deliver privacy information if the marketing itself is not permitted.
Controller: [legal name, postal address and privacy contact; DPO contact if applicable]. We obtained your [specific professional data categories] from [specific source and whether publicly accessible] on [date]. We use it for [specific research/contact purpose] on [lawful basis]. If relying on legitimate interests, our interest is [specific legitimate interest and brief explanation].
We use Threadline to organise the selected information and produce AI-assisted research/drafts. Recipients are [actual internal recipients and service providers]. Processing may take place in [actual countries]; the relevant safeguards and how to obtain them are [details/link]. We keep these records for [period or meaningful criteria]. [Describe any relevant automated decision-making, or state that none with legal or similarly significant effects takes place, only if true.]
You may request access, correction, erasure, restriction or portability where applicable and object to relevant processing by contacting [privacy contact]. You can object to direct marketing at any time. [If consent is used, explain withdrawal.] You may complain to [competent authority]. More information: [complete customer privacy-notice link].
Short first-contact layer: [Controller legal name] obtained your [data] from [source] for [specific purpose]. Our full privacy information is at [link]. Contact [privacy contact] to exercise your rights or object. Include the full information through an accessible second layer within the applicable deadline.
## 7 Suppression and correction
A marketing objection must stop the relevant processing for that purpose. Keep only the minimum suppression identifier and context necessary to prevent repetition, with restricted access and periodic review. Assess corrections or erasure across source records, generated inferences, saved drafts, shared briefs, customer exports and provider copies; record recipients notified where Article 19 requires it.
This template does not prove that a legitimate-interest assessment, notice-delivery process or suppression control has already been implemented.

## Additional service notices

The following dated notices preserve the service disclosures and history. Earlier statements about the provider, beta billing or a pending company transition are superseded by the company agreement above.

## Privacy update — extension 1.7.109 and aggregate founder reporting — dated supplement 2026-10-08.2

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.

Saveable copy: https://app.threadlinehq.io/legal/privacy-update-2026-10-08.2.html

## Release and privacy status for extension 1.7.110 — dated supplement 2026-10-08.3

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 incorporation 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].

Saveable copy: https://app.threadlinehq.io/legal/privacy-update-2026-10-08.3.html

## Spoken call playbooks and personal call settings — dated supplement 2026-10-28.1

From extension 1.7.151, the cold-call playbook has Open, Ask then listen, Brush-off and Close. Rep dialogue is separate from hypothetical prospect answers and coaching. The existing AI writing request generates the message and its playbook together. Regenerating a message also updates its playbook. An explicit playbook refresh uses the full current LinkedIn draft, supplied profile and signal, seller evidence, and available account intelligence. It preserves that draft. Existing bounded provider/error recovery still applies. These are generated suggestions, not verified prospect statements or guaranteed outcomes.

My opener is optional personal text saved to the signed-in Threadline account in Supabase and displayed verbatim. It is not generated, included in the playbook AI request, or included in a shared brief. The rep can replace it or save an empty value. It is available when the same account opens a brief on another device.

The optional sent declaration records that the rep says they sent a specific LinkedIn message, with a chosen date. Copying, generating or editing a draft does not mark it sent. The saved record contains account and prospect identifiers, a SHA-256 message fingerprint, sent date, revision and update time; this new table does not retain another copy of the message body. It is account-scoped and draft-specific. Clearing the declaration removes the date while retaining the fingerprint and revision to prevent stale writes. The declaration does not verify delivery and does not send, read or monitor LinkedIn messages.

Saved call settings and declaration records persist until replaced or account deletion; they are included in the existing account export and removed by the account purge/deletion flow. Previously generated drafts, shared copies, provider records and backups retain their existing lifecycle. Sent status can affect the opening and email brush-off only after the rep explicitly refreshes the playbook. Refresh is available on Starter and above under the existing regeneration entitlement.

This update adds no Chrome permission, provider, automatic outreach, live call recording or microphone access. Existing privacy and AI disclosures continue to apply. Accepted contract text and acceptance history remain unchanged. Contact [email protected] for privacy assistance.

Saveable copy: https://app.threadlinehq.io/legal/call-playbook-update-2026-10-28.1.html

## Simplified call playbook — dated supplement 2026-10-28.2

From extension 1.7.153, the cold-call playbook displays only Open, Ask then listen, Brush-off and Close. My opener, the sent-message checkbox/date, save controls and separate playbook refresh controls are removed. The updated extension does not read or write those personal call settings. Opening the playbook or editing a draft does not trigger an extra AI request. Normal message generation and regeneration continue to generate the message and playbook together.

New playbook generation does not use saved sent declarations or claim that a message was already sent. Existing saved wording is retained until normal regeneration. Earlier opener and sent-declaration records are not deleted by this interface update; they retain the existing account-scoped protection, export and account deletion/purge lifecycle described in supplement 2026-10-28.1. Older installed versions may still expose their previous controls until updated.

This supplement supersedes the earlier description of available call settings in the updated extension. It introduces no new provider, data category, purpose, retention period, Chrome permission, outreach automation, pricing or contract acceptance. AI output remains suggested wording for the rep to review.

Saveable copy: https://app.threadlinehq.io/legal/call-playbook-update-2026-10-28.2.html

## Manual Library use cases — dated supplement 2026-10-29.1

From Threadline 1.7.156, the Library also accepts a title and plain text for a case study or use case that is not available online. A public link, uploaded document and team tags are not required. Threadline stores the supplied text in its Supabase backend. Saving or editing this text does not ask an AI model to extract or rewrite it. Ready means saved and available for generation; it does not mean independently verified. Manual entries are labelled Added by you.

The existing writing model may receive saved manual entries alongside public Library evidence when you request a new message or regenerate one. Their contents are seller-supplied information, not instructions. A general use case does not establish an actual customer relationship or achieved result. Only add information you are entitled to use, and anonymize anything you do not want included in generated outreach. Library text can contain business-confidential information or professional personal data if you choose to enter it. The Library is not a public directory, but details used in a draft may appear in text you copy, send or deliberately share. Saving an entry does not send outreach.

An account controls its own Library. In a managed Teams workspace, members can use the owner's Library and only the owner can add, edit or remove entries. Manual entries are stored separately from website discovery and are not overwritten by Find links again. Unlike retrieved public facts, they do not expire after the public evidence freshness interval; the owner maintains them until removal, replacement of the active company identity, product-data purge or account deletion. An account's own Library is included in its data export. Provider logs and backups retain their existing schedules.

Edits and removals affect future Library inputs. They do not rewrite saved drafts, cached signal packages or previously shared snapshots, and do not retract copied or sent text. To use changed Library information in an existing draft, request normal regeneration where available. The feature introduces no new AI provider, Chrome permission, outreach automation, price or acceptance event. It supplements the URL-only Library description in notice 2026-10-26.1; earlier accepted contract text and acceptance records remain unchanged. Contact [email protected] for data-rights requests.

Saveable copy: https://app.threadlinehq.io/legal/manual-use-cases-update-2026-10-29.1.html