Version 2026-11-03.1. Effective on publication and, for contract terms, acceptance. Provider: THREADLINE LDA.
1 Scope and contact
Threadline uses a Chrome extension, static web application, Supabase backend and external service providers. This overview describes supported controls and their limits. It is not an independent security certification or guarantee.
Report a security concern to [email protected]. Include the affected URL or version, safe reproduction steps and likely impact, without unnecessary personal data, passwords or tokens. Do not access other users’ information or disrupt the service. A separate security mailbox or 24-hour response service is not claimed unless confirmed.
2 Identity and access
The service uses Supabase authentication, account/session checks, short-lived pairing/device authorisations, workspace roles and row-level database access policies. Server-side plan and entitlement controls protect paid functions. Private avatar objects use controlled access and signed links.
The private Analytics application is restricted to authorised founders with email-based sign-in and a secure HttpOnly, SameSite session cookie. Its privileged data access occurs on the server. Restricted access does not make identifiable analytics anonymous or automatically resolve privacy and Chrome Limited Use obligations.
3 Transport storage and application controls
Application and provider traffic use HTTPS. The app uses security headers and relevant backend validation, rate/spend guards, idempotency and operational logging. Privileged service credentials are managed on the server; public client configuration is not a substitute for access control.
Browser and extension storage can contain session tokens. It is not end-to-end encrypted. A compromised device, account or same-origin script can expose data. Public brief links can be forwarded; anyone with the link can access the brief until it expires or is revoked.
Supabase’s observed primary project region is London, UK. AI, email, hosting, network and support processing can involve other countries. We do not claim that all data remains in the EU.
4 Data lifecycle
Daily scheduled cleanup applies to temporary records and class-based activity/observability history. Different records have different periods, explained in the Privacy Notice. Saved workspace content has no universal inactivity-deletion timer. Private Analytics and internal email copies require their own retention and rights handling.
Account export covers product, private Analytics, notification, consent and consumer billing records. A full privacy request can still require separate mailbox or provider records; narrowly necessary unresolved withdrawal and billing records can survive account closure. If a control fails, contact [email protected]. Deletion from active systems does not imply simultaneous deletion of provider logs, legal records, backups or recipients’ copies.
5 Incident handling
A personal-data incident must be assessed for confidentiality, integrity, availability, affected people and risk. When acting as processor, Threadline must notify the affected controller without undue delay after awareness. As controller, it must notify the competent supervisory authority within 72 hours where the GDPR requires it and inform affected people where the applicable high-risk test is met. Notifications may be supplemented as facts emerge.
The internal incident playbook records ownership, escalation, containment, evidence, decisions and communications. Publishing this overview does not certify that a tabletop, on-call arrangement or recovery test has been completed.
6 Assurance limits
Threadline does not claim an independent penetration test, ISO 27001 certification, SOC 2 report, bug-bounty programme, 24/7 security operations, fixed recovery objective or verified backup window that has not been established. Provider certifications are not Threadline certifications.
The Chrome extension’s Cyber Resilience Act classification and any applicable incident-reporting obligations require a specific assessment. Security controls do not establish compliance with LinkedIn’s contractual rules or replace privacy, consumer and marketing obligations.
7 Ongoing review
Security, dependency, access and supplier reviews should follow changes in the service and risk. Any new public assurance must be supported by current evidence and an accountable owner. Contact [email protected] for relevant customer assurance information.
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].
Extension account activation
New extension registrations are activated immediately without verifying mailbox ownership. An acknowledgement email is informational. Internal reporting distinguishes these accounts from mailbox-confirmed web registrations; an activation timestamp alone must not be treated as identity proof. Both surfaces share the same account and ordinary password login. Existing billing account checks permit these activated accounts; upgrading does not constitute mailbox verification.
Signup uses a server-only administrative authentication call after legal-version, invitation-policy and rate-limit admission. It cannot change an existing account password or confirm an existing account. The service never exposes its administrative key to the extension. Password forms run on the Chrome-owned extension origin, with a dedicated message sender boundary. The pending session is kept separate from the paired research session until the existing device-claim protocol succeeds. Registration does not change plan entitlements or replenish credits on reconnect.
Google authentication controls
Optional Google sign-in uses a server-side authorization-code exchange, verified Google token signatures, expected issuer/audience, expiry and nonce checks, exact allowed return addresses, a browser-held verifier and single-use 10-minute intent records. The server validates the supported notice version, action, surface and displayed contract before starting; an acceptance cannot be supplied solely by a callback parameter. Older installed clients retain their actual checkbox method. Current or explicitly compatible contract checks prevent an unrelated outdated agreement from provisioning an account. Signup records are captured once with server-owned document hashes and time; editable profile metadata is not an authorization source. Returning sign-in does not manufacture a new acceptance. Marketing grants are disabled server-side, including from older clients. The OAuth client secret remains on the server. Google API tokens are not returned to clients as reusable credentials.
Google identity linking reuses the existing Threadline account where safely supported. An existing password account explicitly marked as lacking mailbox-ownership proof is blocked from automatic Google linking, including at the authentication identity-write boundary. Acknowledgement delivery and a password reset are not treated as a completed account-linking operation. Normal Threadline session, device and entitlement controls continue to apply. These controls do not imply an independent penetration test or certification.
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.
# Security at Threadline Version 2026-11-03.1. Effective on publication and, for contract terms, acceptance. Provider: THREADLINE LDA. ## 1 Scope and contact Threadline uses a Chrome extension, static web application, Supabase backend and external service providers. This overview describes supported controls and their limits. It is not an independent security certification or guarantee. Report a security concern to [email protected]. Include the affected URL or version, safe reproduction steps and likely impact, without unnecessary personal data, passwords or tokens. Do not access other users’ information or disrupt the service. A separate security mailbox or 24-hour response service is not claimed unless confirmed. ## 2 Identity and access The service uses Supabase authentication, account/session checks, short-lived pairing/device authorisations, workspace roles and row-level database access policies. Server-side plan and entitlement controls protect paid functions. Private avatar objects use controlled access and signed links. The private Analytics application is restricted to authorised founders with email-based sign-in and a secure HttpOnly, SameSite session cookie. Its privileged data access occurs on the server. Restricted access does not make identifiable analytics anonymous or automatically resolve privacy and Chrome Limited Use obligations. ## 3 Transport storage and application controls Application and provider traffic use HTTPS. The app uses security headers and relevant backend validation, rate/spend guards, idempotency and operational logging. Privileged service credentials are managed on the server; public client configuration is not a substitute for access control. Browser and extension storage can contain session tokens. It is not end-to-end encrypted. A compromised device, account or same-origin script can expose data. Public brief links can be forwarded; anyone with the link can access the brief until it expires or is revoked. Supabase’s observed primary project region is London, UK. AI, email, hosting, network and support processing can involve other countries. We do not claim that all data remains in the EU. ## 4 Data lifecycle Daily scheduled cleanup applies to temporary records and class-based activity/observability history. Different records have different periods, explained in the Privacy Notice. Saved workspace content has no universal inactivity-deletion timer. Private Analytics and internal email copies require their own retention and rights handling. Account export covers product, private Analytics, notification, consent and consumer billing records. A full privacy request can still require separate mailbox or provider records; narrowly necessary unresolved withdrawal and billing records can survive account closure. If a control fails, contact [email protected]. Deletion from active systems does not imply simultaneous deletion of provider logs, legal records, backups or recipients’ copies. ## 5 Incident handling A personal-data incident must be assessed for confidentiality, integrity, availability, affected people and risk. When acting as processor, Threadline must notify the affected controller without undue delay after awareness. As controller, it must notify the competent supervisory authority within 72 hours where the GDPR requires it and inform affected people where the applicable high-risk test is met. Notifications may be supplemented as facts emerge. The internal incident playbook records ownership, escalation, containment, evidence, decisions and communications. Publishing this overview does not certify that a tabletop, on-call arrangement or recovery test has been completed. ## 6 Assurance limits Threadline does not claim an independent penetration test, ISO 27001 certification, SOC 2 report, bug-bounty programme, 24/7 security operations, fixed recovery objective or verified backup window that has not been established. Provider certifications are not Threadline certifications. Production backup/PITR coverage, storage-object backup arrangements, restore tests, staff MFA and access-review evidence require confirmation in the readiness register. A documented policy is not proof that the control operates. The Chrome extension’s Cyber Resilience Act classification and any applicable incident-reporting obligations require a specific assessment. Security controls do not establish compliance with LinkedIn’s contractual rules or replace privacy, consumer and marketing obligations. ## 7 Ongoing review Security, dependency, access and supplier reviews should follow changes in the service and risk. Any new public assurance must be supported by current evidence and an accountable owner. Contact [email protected] for relevant customer assurance information. 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]. ## Extension account activation New extension registrations are activated immediately without verifying mailbox ownership. An acknowledgement email is informational. Internal reporting distinguishes these accounts from mailbox-confirmed web registrations; an activation timestamp alone must not be treated as identity proof. Both surfaces share the same account and ordinary password login. Existing billing account checks permit these activated accounts; upgrading does not constitute mailbox verification. Signup uses a server-only administrative authentication call after legal-version, invitation-policy and rate-limit admission. It cannot change an existing account password or confirm an existing account. The service never exposes its administrative key to the extension. Password forms run on the Chrome-owned extension origin, with a dedicated message sender boundary. The pending session is kept separate from the paired research session until the existing device-claim protocol succeeds. Registration does not change plan entitlements or replenish credits on reconnect. ## Google authentication controls Optional Google sign-in uses a server-side authorization-code exchange, verified Google token signatures, expected issuer/audience, expiry and nonce checks, exact allowed return addresses, a browser-held verifier and single-use 10-minute intent records. The server validates the supported notice version, action, surface and displayed contract before starting; an acceptance cannot be supplied solely by a callback parameter. Older installed clients retain their actual checkbox method. Current or explicitly compatible contract checks prevent an unrelated outdated agreement from provisioning an account. Signup records are captured once with server-owned document hashes and time; editable profile metadata is not an authorization source. Returning sign-in does not manufacture a new acceptance. Marketing grants are disabled server-side, including from older clients. The OAuth client secret remains on the server. Google API tokens are not returned to clients as reusable credentials. Google identity linking reuses the existing Threadline account where safely supported. An existing password account explicitly marked as lacking mailbox-ownership proof is blocked from automatic Google linking, including at the authentication identity-write boundary. Acknowledgement delivery and a password reset are not treated as a completed account-linking operation. Normal Threadline session, device and entitlement controls continue to apply. These controls do not imply an independent penetration test or certification. ## 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 ## Extension sign in and account connections — dated supplement 2026-10-12.1 Extension 1.7.111 lets you sign up or log in directly with Google or your email and password. After required account setup and agreement steps, the extension connects automatically. You do not generate or paste a pairing code in this version. Your web dashboard uses the same Threadline account and can remain signed in separately. Threadline authorizes one active extension login session per account. Signing in through another extension replaces the previous extension session and revokes its refresh session. Protected extension requests must match the currently authorized session. Multiple tabs in the same Chrome profile share that extension session. Teams members use their individual accounts and seats. You can sign out the active extension from Connection in the dashboard without signing out the dashboard. Account-level session revocation and deletion controls remain available. Work already started may finish; signing out does not erase information already displayed or copied. To maintain this connection, the extension keeps its Auth access and refresh tokens and a random connection credential in local Chrome extension storage. Newly created connection credentials are not placed in Chrome sync storage. The existing internal storage key my_pairing_code now holds that opaque credential, not a code the user must enter. During unfinished setup, the pending Auth session and its activation credential are stored locally until connection completes or setup is signed out. A transient Chrome session-storage preference remembers whether you chose Sign up or Log in; it contains no credentials. The server stores a hash of the connection credential, the associated Auth session identifier, account identifier, connection status and timestamps. These are necessary authentication and account-access records; this change does not add hardware fingerprinting, location tracking or browser-history collection. Active authorization is checked against the live Auth session. It ends when replaced, signed out, revoked, deleted with the account or no longer backed by a valid Auth session. Daily cleanup removes expired temporary handshakes and ended connection records while preserving a live connection. The old two-minute code lifetime does not expire an active extension login. Older extension versions retain a compatibility handshake during rollout and should be updated. A connection created before session binding may require a fresh sign-in; the account, company profile, plan, credits and saved research are preserved. This control limits active login sessions. It does not identify a physical person or guarantee that deliberately copied authentication credentials cannot be shared. Keep your account credentials private and use the individual accounts or seats required by your plan. Signing in, reconnecting or repeating setup neither consumes a Reveal nor grants another Free allowance. This release does not change prices, plan entitlements, credit/refund rules, AI providers or prompts, extension permissions, professional-data collection, marketing choices, customer rights or the separate real-payment activation gate. Accepted legal bundle 2026-10-07.1 and its acceptance history remain unchanged. This dated update supplements the previous authentication, storage and security descriptions; earlier notices remain historical where superseded. For account or privacy assistance, contact [email protected]. Saveable copy: https://app.threadlinehq.io/legal/extension-signin-update-2026-10-12.1.html ## Research context and saved working drafts — dated supplement 2026-10-19.1 When you explicitly request research, Threadline uses the visible professional profile, including the current role's responsibilities and relevant professional posts, together with your seller profile. Research starts with the person's responsibilities and then considers their team and company. Facts and source qualifications remain separate from suggested outreach hypotheses. Default writing instructions are shorter; an edited custom prompt remains authoritative. AI results still require your review. When you save edits or apply a translation, the extension keeps the original and recent working versions in Chrome extension local storage, isolated by your Threadline account. The saved text includes the message or email subject and body, its language, and identifiers that associate it with the prospect, signal and channel. A prospect-specific writing-language choice is saved for that person, not their company. The account writing-language setting remains separate. These local copies are not synchronized to your other browsers or devices, and saving a working draft does not publish or send it. Working drafts and prospect-specific language choices expire seven days after their last save and are removed on the next access. Storage is bounded to 40 drafts, 100 prospect language choices and approximately 2 MB of draft data; older copies may be removed sooner. Signing out or changing extension accounts clears this local cache. Browser storage is not end-to-end encrypted. Already copied, sent, exported or explicitly shared content has its own lifecycle; clearing local drafts does not delete those copies. Translate previews a separate version. Use translation applies that version to this draft; Save edits saves the source text. Account language applies to new drafts across prospects, unless a prospect override is selected. Existing drafts are not automatically translated when a setting changes. The established Pro/Teams writing entitlements and Reveal credit rules remain unchanged. This dated notice supplements the existing storage and professional-data descriptions. It does not change the accepted contract version or its acceptance history, permissions, AI provider, marketing choices, prices or payment activation. For privacy assistance, contact [email protected]. Saveable copy: https://app.threadlinehq.io/legal/working-drafts-update-2026-10-19.1.html ## Company case studies and use-case links — dated 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. Saveable copy: https://app.threadlinehq.io/legal/vendor-case-studies-update-2026-10-26.1.html ## Message language and immediate draft translation — dated supplement 2026-10-26.2 From extension 1.7.150, Languages contains Interface language and Message language. Message language applies to new drafts across prospects. Prospect-specific language controls are removed, and previously saved prospect language choices are ignored. Existing messages and emails are not translated when an account setting changes. Custom writing prompts and examples remain saved. These controls are available on Free, Starter, Pro and Teams. Selecting a language in the draft’s Translate dropdown requests translation immediately through the existing AI service and applies the successful result to that working draft. For email, both subject and body are translated. There is no separate Translate or Use translation button. The original remains available through Restore original. An unsuccessful request or save keeps the current draft. Translation does not send or publish a message or start another Reveal. Saved working versions remain isolated by account in Chrome extension local storage. They contain text, language and prospect/signal/channel identifiers, expire seven days after the last save on next access, and are bounded to 40 drafts and approximately 2 MB. Legacy prospect-language entries, capped at 100, may remain until expiry or cache clearing but no longer control generation. Sign-out and account changes clear the local cache. Drafts are not synchronized between browsers or end-to-end encrypted. Copies already sent, exported or shared retain their own lifecycle. This supplement supersedes the control descriptions in supplement 2026-10-19.1. It changes no accepted contract text or acceptance history, provider, permission, data purpose, payment activation or Reveal credit accounting. Existing privacy and AI disclosures continue to apply. For privacy assistance, contact [email protected]. Saveable copy: https://app.threadlinehq.io/legal/working-drafts-update-2026-10-26.2.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