Privacy policy
How ThreadCue handles information
This policy describes the public website and the current ThreadCue desktop application, including the Reddit and Threads features now available in the product.
1. Who operates ThreadCue
ThreadCue is operated by GLOBALCARD NETWORKS LIMITED (UK company registration number 15534843), registered at 71-75, Shelton Street, Covent Garden, WC2H 9JQ, United Kingdom. Privacy questions can be sent to getthreadcue@gmail.com.
2. Website and waitlist data
GLOBALCARD NETWORKS LIMITED is responsible for personal data collected through the ThreadCue website, waitlist, and hosted product services. Workspace information that remains only in the desktop application is not received by GLOBALCARD NETWORKS LIMITED.
When you join the waitlist, the website stores the email address you enter, a normalized copy used to prevent duplicate entries, the UTC submission time, the consent-policy version, and the page that submitted the request. The website does not intentionally store a raw IP address with the waitlist record.
In-memory rate limiting, an invisible form field, and a necessary security cookie help protect the waitlist. No advertising or analytics service is installed, and the site does not set marketing cookies. Ordinary security logs may contain an IP address, user agent, requested path, response status, and request time; they are access-restricted and retained only as needed for security and operations, ordinarily for no more than 30 days.
3. Purposes and lawful bases
The waitlist email address is used for ThreadCue development updates, early-access invitations, and necessary messages about the waitlist. It is not sold. This processing is based on the consent given with the waitlist form, which can be withdrawn at any time by contacting us.
Security, fraud prevention, rate limiting, and essential service operation are based on GLOBALCARD NETWORKS LIMITED's legitimate interests in protecting and operating ThreadCue. Information may also be processed where needed to provide an early-access service, take steps at your request, or comply with a legal obligation.
ThreadCue does not use connected-source data for advertising or unrelated profiling.
4. Desktop workspace data
The desktop application stores project profiles, onboarding conversations, project briefs, source and scan settings, opportunities, drafts, reminders, activity history, connection details, and temporary source snapshots in the local workspace on the user’s device. The local workspace is not encrypted in the current development build.
You choose which accounts to connect and which projects to scan. The product currently supports one connected account per platform. Removing the local workspace removes this locally stored project and source data; the data deletion instructions describe the current limits.
5. Reddit account and public-content data
When you connect Reddit, ThreadCue may receive the connected account’s profile details, followed communities, and matching public posts, comments, and community information. It uses that data to identify opportunities, show source context, and prepare reviewable drafts.
ThreadCue does not publish, vote, save, join communities, send private messages, read account history, or moderate on Reddit. Reddit processes account and public-content data under its own terms and privacy policy when you connect the service.
6. Threads account, source, and publishing data
When you connect Threads, ThreadCue may receive the connected account’s profile details and relevant public posts, replies, mentions, links, publication times, and visible engagement information. Search terms are derived from the project’s goals, interests, audience, offering, description, and generated brief; Threads is a destination for the project, not a separate strategy.
ThreadCue uses Threads information to discover opportunities, provide source context, prepare original posts or replies, and carry out the exact text action you approve. For a supported publication, ThreadCue records the selected account, exact text, action type, review and schedule choices, result, and enough status information to show what happened, prevent duplicate work, cancel queued work, and enforce the project’s daily limit. Replies always require final review. Unattended activity is limited to original text after the project has earned access and a user explicitly enables a daily limit.
Threads data is used only for the features you choose. It is not sold or used to build unrelated advertising profiles. Meta may process account and platform data under its own terms and privacy policy. You are responsible for reviewing those terms and for having permission to connect and use the account.
7. Planned Facebook integration
Facebook is a documented product direction, not a feature in the current ThreadCue application. No Facebook account can currently be connected, and ThreadCue does not currently collect or process Facebook Page, Messenger, advertising, or lead data.
If a Facebook connector is enabled later, the intended starting boundary is a Page the user is authorized to manage and only the Page interactions or lead features the user explicitly enables. ThreadCue will publish the exact permissions, purposes, retention, disconnect, deletion, external-provider, and action-review terms before collecting Facebook data. Planned functionality does not include personal profiles, Facebook Groups monitoring, broad Facebook search, scraping, cold automated outreach, or automatic advertising decisions.
8. Optional AI features
You may choose to use an external AI feature for eligible project context or drafts. The product shows the feature and provider before use, and the provider receives only the material needed for that request.
Live Reddit and Threads source text is not sent to an external AI provider by default. If Facebook data becomes supported later, it will follow the same separate purpose, disclosure, user-direction, and provider-review requirement rather than being eligible for external AI merely because an account was connected. A local or demo mode does not silently transfer live platform content.
9. Retention
Live Reddit and Threads source snapshots are removed after 48 hours by default; the current product supports a configured range of 24 to 168 hours. Derived opportunities, tasks, and drafts can remain after a snapshot is removed, with the source relationship cleared so your work is not silently destroyed.
Disconnecting an account stops future scans, disables actions that depend on that account, and pauses queued Threads publications. Existing local tasks and drafts remain until you remove them. Operational connection and publication records may remain for safety, support, and audit until the final production retention schedule is published; they are not a long-term archive of platform content.
Waitlist records are retained for 12 months from submission unless consent is renewed or the record is deleted sooner at the person’s request. The waitlist database is backed up weekly, and backups are retained for no more than 30 days. A deleted record may remain in a restricted backup until that backup expires; verified deletion requests are reapplied if a backup is restored.
10. Rights, deletion, and choices
Depending on the circumstances, UK data protection law may give you rights to access, correct, erase, restrict, or receive your personal data, object to processing, and withdraw consent. Requests are handled without undue delay and ordinarily within 30 days. If a lawful extension or exemption applies, we will explain it.
You can disconnect Reddit or Threads from the desktop Connections screen. Disconnecting is not the same as deleting prior local tasks, drafts, or operational records. Full local workspace deletion currently requires stopping ThreadCue and removing its local data directory; see the data deletion instructions for exact steps and important limits. There is no Facebook connection or Facebook data to delete in the current product. Waitlist deletion requests can be sent from the subscribed email address using the contact method below.
You may complain to the UK Information Commissioner's Office at ico.org.uk, although we encourage you to contact us first so we can try to resolve the issue.
11. Hosting, providers, and recipients
The public website is hosted in Germany. The current website does not send waitlist data to a CRM, analytics provider, advertising network, or email-delivery service.
Reddit and Meta process account and platform data under their own terms when you connect the currently supported corresponding service. The current Meta connection is for Threads; the planned Facebook direction does not cause any Facebook data to be sent to ThreadCue. An optional AI provider receives eligible project context or drafts only when you choose that feature. Hosting and service providers may process information on GLOBALCARD NETWORKS LIMITED's behalf under appropriate agreements, or as independent controllers under their own terms.
12. Security
ThreadCue uses access controls, protected account connections, bounded source reads, rate limits, cancellation, status records, and short retention windows. No system is risk-free, and the desktop product remains a development build that has not completed an external security assessment. Protect the device where your local workspace is stored and disconnect an account if you no longer want ThreadCue to use it.
13. International transfers and age
The website is hosted in Germany. A connected platform, hosting provider, or optional AI provider may process information in other countries. Where GLOBALCARD NETWORKS LIMITED appoints a provider to process personal data outside the United Kingdom, it will use a lawful transfer mechanism and appropriate contractual and security safeguards where required.
ThreadCue is intended only for people aged 18 or over. It is not directed to children, and we do not knowingly collect waitlist information from anyone under 18.
14. Changes and contact
This policy will change as ThreadCue adds production infrastructure, sources, or publishing capabilities. Material changes should receive a new effective date and, where required, direct notice. Before a public multi-user launch, ThreadCue will publish the final operator details, provider relationships, retention schedule, and account-wide deletion process.
Contact: getthreadcue@gmail.com.