ThreadKore privacy policy
Legal review pending.
This policy describes the website’s current information handling and privacy controls. It has not been reviewed or approved by legal counsel.
On a small screen, tables can scroll horizontally. Keyboard users can focus a table area and use the left and right arrow keys.
Effective date: October 11, 2026
Last updated: October 20, 2026
1. Overview
ThreadKore, LLC ("ThreadKore," "we," "us") makes a Builder's Operating System for homebuilders. This Privacy Policy explains how we collect, use, share and protect personal information when you visit www.threadkore.com (the "Site"), book a demo or contact us. It also explains the choices and rights you have.
The Site is built for businesses: homebuilders, their teams, and the trades and vendors who work with them. Most of the information we receive is business contact information, such as your name, company and work email.
This policy covers the Site only. It does not cover the ThreadKore platform that customers use under a separate agreement. Consult your customer agreement or contact us for information about the terms that apply to platform data.
In short:
- We collect what you type into our contact form, plus basic technical information needed to run and secure the Site.
- Analytics and advertising tracking are off unless you turn them on in our privacy-choices panel.
- With analytics permission, a random cookie recognizes returning browsers, and a submitted form email can be linked to earlier and later consented activity in the same session. This email is self-reported, not verified identity.
- If you turn on advertising, Google, Meta, LinkedIn and Apollo receive information through their tags. Apollo replaces RB2B and requires a fresh choice; earlier advertising grants do not authorize Apollo. It tracks page visits and may enrich visits with business information without a form submission. Some state laws call these disclosures a "sale" or "sharing." You can turn them off at any time, and we honor Global Privacy Control and Do Not Track signals.
- The Site stores form submissions for inquiry handling; its tracking code does not send form contents to advertising tags.
2. Information we collect
2.1 Information you give us
When you use the contact or demo form at /contact/, we collect:
| Field | Required? |
|---|---|
| Your name | Required |
| Company | Required |
| Work email | Required |
| Phone | Optional |
| What you're interested in (for example, a production or custom builder demo, an Orbit walkthrough, JobCloser for trades and vendors, the founding partner program, a builder reference conversation, or another conversation) | Optional |
| Builder type (for example, production, semi-custom, custom, 55+, build for rent, or build on your lot) | Optional |
| Annual closings (a range) | Optional |
| Your role (for example, owner or executive, finance and accounting, purchasing and estimating, construction and operations, or sales and design) | Optional |
| A free-text message about what you'd like to discuss | Optional |
| A checkbox confirming that ThreadKore may contact you about your inquiry | Required |
The form also includes a hidden field that people can't see. Automated spam tools tend to fill it in, so it helps us filter out spam. Please don't put confidential customer or financial information in the message box.
If you email us, call us or write to us, we collect what you choose to share, such as your name, contact details and the content of your message.
We group saved website submissions with the same trimmed, lower-case email address in protected contact records so our team can follow up on repeat inquiries. Each submission keeps its own submitted name, company and original reference. This operational grouping does not require optional analytics, does not verify who controls the email, and does not attach browsing activity. Activity is connected only through an explicitly recorded, consented submission/session relationship; recognizing the same browser alone does not identify the person using it.
2.2 Information we collect automatically
Always, to run and protect the Site. Like any website, our servers and our hosting and security provider, Cloudflare, receive technical information when your browser requests a page. This includes your IP address, browser and device type, the page you asked for, the referring page, and the date and time. We use it to deliver pages, keep the Site secure and stop abuse. We also keep anonymous, grouped counts of request errors, missing pages, form failures and rate limits to maintain the Site. These counts contain no visitor identifiers and none of what you submit.
Only if you opt in to "Analytics, returning browsers and submitted-email linking." With your permission, we record:
- Activity: page views, navigation and button clicks, form steps and outcomes, scroll depth, successful request counts, and page-load and responsiveness measurements. Event text never includes form contents, names, email addresses or raw IP addresses.
- Returning browsers: a random first-party cookie lets us recognize the same browser across consented visits. It does not establish who is using it. We do not use IP matching, fingerprinting or cross-device identity matching for this first-party recognition.
- Submitted-email connections: when you submit a form with analytics permission, we keep the submitted email separately in protected contact records. Internal references connect that submission and self-reported email to earlier and later consented activity in the same session. We do not verify that you own the email, and a shared browser or mistyped email can make a connection misleading. Email is not placed in event text or sent to tracking providers by this linking feature.
- Estimated location: your network-based country, state or region, and city, as estimated by our hosting provider. We never request GPS access. We never store coordinates, street addresses or postal codes. Estimates can be wrong, especially if you use a VPN, and if no location is available, it stays unknown.
- Google Analytics: Google Analytics (measurement ID G-MM58VPCHN8) collects information about your visit, such as pages viewed, approximate location, device and browser details, and identifiers stored in cookies.
Restricted public network IP records — currently unavailable; no addresses are saved by this feature. A separate feature is being prepared to record a public network IP only when the hosting provider can supply a verified original-visitor address. That source has not been verified, so capture is disabled. An unverified request header or address supplied by the visitor is not accepted. This does not change the technical information Cloudflare receives to deliver and protect the Site.
If enabled, analytics capture would require the updated analytics consent. A separate, narrowly limited security purpose would cover form handling and abuse prevention without analytics permission; security records would not authorize optional visitor analytics. Raw addresses would stay in restricted storage, outside event text and ordinary reports. Ordinary reports would show masked network information. An address can represent a shared office, household, VPN or other network, not a person; we do not infer identity or match devices from it.
The prepared retention limit for these raw records is 30 days, after which current reporting views exclude them immediately. Physical cleanup is request-driven only, not scheduled, and is not guaranteed while the Site is idle. No office or VPN network ranges are configured; network classification remains unknown. This description is not a claim that raw network IP capture is currently available.
Only if you opt in to "Advertising." With your permission, we load advertising tags from Google Ads (AW-18146724072), Meta (Meta Pixel) and LinkedIn (LinkedIn Insight Tag). These tags collect information such as the pages you view, actions you take on the Site, your IP address, browser and device details, and cookie or other online identifiers. Each company may link this to an account you have with it.
The same optional category, labeled "Advertising and business visitor identification" in the panel, enables Apollo, replacing RB2B. Apollo receives visited page URLs, a randomly generated browser identifier, and network/browser information inherent in its requests. Its privacy policy describes IP-based enrichment to infer company, industry or location. This is separate from our own activity measurements and submitted-email connections: an analytics-only choice does not enable Apollo. Earlier RB2B advertising grants do not authorize Apollo; prior opt-outs remain honored.
Static review of the Apollo script found requests to aplo-evnt.com for visitor tracking eligibility and page-visit collection. The script captures attribution parameters and referrers; before loading advertising tags, the Site strips the initial page's query string and fragment and exposes only the referring origin. Vendor code can still read later page URLs. The Site does not pass submitted form contents to Apollo.
The script also attempts to load d-code.liadm.com/did-0091.min.js to resolve MD5/SHA2 email identifiers through LiveIntent. This secondary script and unreviewed partner requests remain blocked by our security policy, so visitor matching may be limited. Hashing is not anonymization. We have not verified a complete downstream dependency inventory and do not allow unknown origins merely to make identification work. Apollo's script may change independently; this review does not guarantee all future behavior. The old RB2B loader and its exclusive network permissions have been removed.
See section 5 for the cookies and similar technologies involved.
2.3 Information from third parties
- Advertising and analytics providers. If you have opted in, Google, Meta and LinkedIn may give us reports about how our ads and Site perform. These reports are usually aggregated, meaning grouped and not tied to one person.
- Business visitor identification. With advertising permission, Apollo may associate visits with business information. Such results are not necessarily anonymous. Its LiveIntent hashed-email dependency is currently blocked. The Site does not save Apollo identification results in its first-party activity, performance or location records.
- Our hosting provider. Cloudflare provides the network-based location estimate described above.
We do not ask for sensitive personal information, such as Social Security numbers, financial account details or precise geolocation, through the Site. Please do not include it in a free-text message.
3. How we use information
We use personal information to:
- Respond to your inquiry. We schedule demos, answer questions and follow up on the request you made.
- Understand your business needs. We tailor a demo to your builder type, size and role.
- Run, maintain and secure the Site. This includes preventing spam, fraud, bots and abuse, and fixing errors.
- Measure and improve the Site (only with analytics consent). We learn which pages are useful, how the Site performs and which consented journeys lead to inquiries. Internal reports can recognize returning browsers and connect a submitted self-reported email with consented activity in the same session. These reports are not public.
- Measure and personalize advertising (only with advertising consent). We see whether our ads on Google, Meta and LinkedIn work, and show relevant ads.
- Identify business visitors (only with advertising consent). Apollo may enrich visits with business information. The Site itself does not send outreach to matched contacts.
- Send business communications as described in section 13.
- Meet legal obligations. We keep records, respond to lawful requests, and enforce or defend our rights.
We do not use the Site's information to make decisions that have legal or similarly significant effects on you, such as decisions about credit or employment.
4. How we share information
4.1 Service providers
We use the following companies to help operate the Site and handle business inquiries. The table describes their functions, not a legal classification of their contractual roles.
| Provider | What they do for us | Info involved |
|---|---|---|
| Cloudflare | Website hosting, content delivery, security, bot and spam protection, the network-based location estimate, and the site's initial inquiry storage | Technical and request data, IP address, form submissions passing through and stored by the Site |
| Cadence2Close | Managing CRM follow-up | Inquiry and business contact information |
| Microsoft 365 | Business email | Email correspondence |
| Microsoft Teams | Running demos | Name, email, meeting details |
The Site saves inquiries in its own database. Automated forwarding to Cadence2Close or sending email notifications has not been configured on this website.
The Site is configured to suppress automatic Cloudflare Web Analytics script injection, separately from the optional analytics described in this policy.
4.2 Analytics, advertising and business identification partners (only with your consent)
| Partner | Category | What it's used for | Partner's policy |
|---|---|---|---|
| Google Analytics | Analytics | Site measurement | Google Privacy Policy |
| Google Ads | Advertising | Ad measurement and personalization | Google Privacy Policy |
| Meta (Meta Pixel) | Advertising | Ad measurement and personalization | Meta Privacy Policy |
| LinkedIn (Insight Tag) | Advertising | Ad measurement and personalization | LinkedIn Privacy Policy |
| Apollo | Advertising and business visitor identification | Page-visit tracking, browser recognition and potential business enrichment; LiveIntent matching dependency currently blocked | Apollo Privacy Policy |
These partners receive information directly through their tags and use it under their own privacy policies. They may combine it with other information they hold about you.
Apollo's policy describes its own collection, enrichment, marketing and sharing practices. Do not assume it acts solely as our service provider. Please review its policy for its uses and privacy choices. Removing RB2B does not delete historical consent audit records or recall information RB2B previously received.
4.3 What "sale" and "sharing" mean here
Some state privacy laws define "sale" and "sharing" broadly. Under the California Consumer Privacy Act, as amended by the CPRA, "sharing" means giving personal information to a third party for cross-context behavioral advertising, which is ads based on your activity across different businesses' websites and apps, whether or not money changes hands. Several other states treat this kind of activity as a "sale" or as "targeted advertising."
When you turn on the Advertising category, the Google Ads, Meta and LinkedIn tags receive identifiers (such as cookie IDs, advertising IDs and IP addresses) and Site activity that those companies can use for this kind of advertising. The Site's privacy controls treat these disclosures as a potential "sale" or "sharing" and let you keep them off.
Advertising permission also enables Apollo business visitor identification. Apollo receives online identifiers and Site activity and may enrich visits with business information. We include this disclosure in the Advertising opt-out and treat it as a potential sale or sharing rather than assuming a service-provider exemption.
Google Analytics loads under the Analytics category. This describes the Site's loading control, not a guarantee about Google's account-level data uses. To prevent it from loading, leave Analytics off or choose Essential only.
The Site's tracking code does not send form contents (your name, company, email, phone or message) to these tags, and the Site has no automated inquiry-list upload to advertising platforms. RB2B may independently match your visit to contact information held elsewhere.
We do not knowingly sell or share the personal information of anyone under 16.
To opt out, see section 7.3.
4.4 Other sharing
We may also disclose personal information:
- For legal reasons: to comply with law, a court order or another legal process, or to protect the rights, property or safety of ThreadKore, our customers or others.
- In a business transfer: as part of a merger, acquisition, financing or sale of assets. The information would stay subject to this policy or to protections that are at least as strong.
- With your direction or consent: for example, if you ask us to introduce you to a ThreadKore builder reference.
5. Cookies and the privacy choices panel
5.1 How the panel works
The first time you visit without a remembered choice, a slim notice appears at the bottom of the page. Choose "Accept all", "Essential only", or "Customize". Closing this initial notice, including with Escape, saves an essential-only choice rather than granting tracking permission. Customize opens a detailed dialog with two optional categories. That dialog pauses interaction with the page while open, but acceptance is not required to use the Site. Closing settings reopened from the footer preserves your saved choice.
- Analytics, returning browsers and submitted-email linking: our own activity and estimated location records, random-cookie browser recognition, connections between submitted self-reported email and consented same-session activity, plus Google Analytics.
- Advertising and business visitor identification: Google Ads, Meta Pixel, LinkedIn Insight and Apollo tags. Apollo may enrich visits with business information without a form submission; its secondary LiveIntent dependency is currently blocked.
Both are off by default. Nothing optional loads until you explicitly accept all optional tracking or turn a category on and save your choices, and the Site confirms permission. If you choose "Essential only", or don't make a choice, no analytics or advertising tags load and no analytics or advertising cookies are set. The contact form and the rest of the Site work either way. Necessary security and contact-form functions remain available.
A "Your Privacy Choices" link appears at the bottom of every page, so you can change or withdraw your permission at any time. Changing a choice may reload the page to stop tags that are already running.
When you withdraw analytics permission, we stop new collection, clear the returning-browser cookie, remove the current session's submitted-email connections and remove recognition links for that browser. We also ask for removal of the current session's location estimate. This does not automatically delete your inquiry, historical activity records or information already received by providers. Location records keep their original expiration date (see section 6).
Your choice is recognized in your browser for 180 days from your explicit decision. Browsing alone does not extend that period. After that, or if you clear your browser storage or we change the tracking categories, the panel may appear again. Browser settings or private browsing may clear it earlier. These browser records contain privacy choices, not form details.
We ask visitors with an earlier opt-in to choose again because Apollo replaces RB2B for business visitor identification. Earlier acceptance does not authorize Apollo; earlier declines remain honored. Existing analytics and first-party recognition purposes are unchanged. Optional tracking stays off until the new choice is saved and confirmed.
5.2 Cookies and similar technologies we use
The entries below reflect website code and the Apollo script statically checked on October 20, 2026. Third-party entries are not an exhaustive inventory of every provider cookie. Actual storage and lifetimes depend on provider settings and browser behavior, and providers can change them.
Strictly necessary
| Name | Set by | Purpose | Typical lifetime |
|---|---|---|---|
__Host-tk-inquiry | ThreadKore (first party) | Verifies an inquiry-form session and helps protect submissions from abuse | 30 minutes |
tk-privacy-choice-v7-apollo (browser local storage) | ThreadKore (first party) | Remembers choices after the Apollo replacement notice, without form details | 180 days from your explicit decision; browser storage may clear earlier |
tk-privacy-choice-v6, tk-privacy-choice-v5, tk-privacy-choice-v4, tk-privacy-choice-v3, tk-privacy-choice-v2, tk-privacy-choice-v1 (legacy browser local storage) | ThreadKore (first party) | Compatibility opt-outs so older open pages cannot continue under an earlier grant | Recognized for 180 days from the recorded decision; browser storage may clear earlier |
__Host-tk-activity | ThreadKore (first party) | Records selected tracking permissions; links activity only when analytics is allowed. May also exist for an advertising-only choice, without allowing first-party analytics | 30 minutes |
Cloudflare security cookies (such as __cf_bm), if triggered | Cloudflare | Bot and abuse protection | Depends on the security service and its configuration |
Analytics (only with analytics consent)
| Name | Set by | Purpose | Typical lifetime |
|---|---|---|---|
__Host-tk-browser | ThreadKore (first party) | Random returning-browser recognition, not verified personal identity; contains no submitted email | 180 days |
_ga, _ga_MM58VPCHN8 | Google Analytics | Tells visits apart and measures Site use | Up to 400 days, depending on browser and provider settings |
Advertising (only with advertising consent)
| Name | Set by | Purpose | Typical lifetime |
|---|---|---|---|
_gcl_au, _gcl_ls (local storage) | Google Ads | Ad conversion measurement | Up to 90 days |
IDE | Google (doubleclick.net) | Ad delivery and measurement | Up to 400 days |
_fbp | Meta | Ad measurement and delivery | Up to 90 days |
bcookie, bscookie, lidc, li_sugr, UserMatchHistory, AnalyticsSyncHistory, li_adsId (local storage) | Ad measurement, matching and delivery | From one day to one year | |
apolloAnonId | Apollo (first-party local storage) | Random browser identifier | No built-in expiry in reviewed script; cleared on withdrawal |
6ace0a589065e200105e1839_eventQueue | Apollo (first-party local storage) | Queued page visits | No built-in expiry; processed during sending; cleared on withdrawal |
6ace0a589065e200105e1839_canTrack | Apollo (first-party local storage) | Tracking eligibility | 24-hour expiry checked on read; cleared on withdrawal |
liveIntentData | Apollo (first-party local storage) | Potential MD5/SHA2 email matching cache | 24-hour expiry checked on read; matching dependency currently blocked; key cleared on withdrawal |
Legacy _reb2b… identifiers | Previously RB2B | Historical matching storage; no new RB2B loading | Known accessible first-party keys/cookies cleared during privacy transitions; external provider data is not recalled |
You can also block or delete cookies in your browser settings. Storage controlled by Google, Meta, LinkedIn, Apollo or its partners may also need to be managed through your browser or with those companies. Withdrawal stops future loading of Apollo on this Site and reloads the page to halt running tags; it does not delete information already received by providers, including RB2B before its removal.
The Apollo entries above come from static review of the main script, not execution of the vendor or a complete list of partner storage. The Site removes these known Apollo local-storage entries on withdrawal, cancels pending initialization and reloads to stop running tags. It also clears known accessible legacy RB2B storage, but cannot delete third-party-domain or inaccessible cookies, or recall data already sent to providers.
6. How long we keep information
The following describes the Site's current retention settings. Browser cookie lifetimes are not the same as retention of information already received by us or a provider. Some records have no automated expiry, as noted below.
| Information | How long we keep it |
|---|---|
| Contact-form submissions | Retained in the Site's database without an automated deletion schedule. You may contact us about deletion as described below. |
| Related correspondence and CRM records | Kept outside the Site's inquiry database; no fixed retention period is specified in this policy. Contact us about records associated with your inquiry. |
| First-party estimated location records (with analytics consent) | Up to 720 days from collection, then they expire and are excluded from reports. Records collected under an earlier 90-day setting keep that shorter period. Expired records are cleared as the Site receives requests. |
| New detailed journey events and related event metadata (with the updated analytics consent) | Up to 90 days from collection. Expired events are excluded from current reporting views immediately; cleanup runs as requests arrive. |
| Returning-browser recognition, submitted-email contact records and internal session/submission connections | Up to 180 days. Expired or deleted connections are not used in current reporting views; expired records are cleared as requests arrive. These analytics contact records are separate from inquiry submissions. |
| Protected operational submission-to-contact grouping | Each grouping expires 180 days after the original submission, independently of analytics permission. Grouping an existing submission does not renew its original retention window. Original inquiry records follow their separate retention policy. |
| Earlier first-party activity and performance history | The earlier history is unchanged and has no automated expiry. Withdrawing consent stops new collection but does not automatically delete that history. |
| Restricted raw public network IP records (currently unavailable; no addresses saved) | Prepared limit: 30 days, with expired records hidden from current reporting views immediately. Capture requires verified hosting-provider metadata that is not yet available. Physical cleanup is request-driven only, not scheduled or guaranteed while idle. Analytics and necessary security are separate purposes. |
| Inquiry security sessions and rate-limit information | The inquiry cookie lasts about 30 minutes. Abuse checks use short windows, including approximately 10 minutes. Older inquiry-session records and related rate-limit digests are cleared after approximately one day as requests arrive; this does not delete the inquiry itself. |
| Anonymous, grouped operational counts | Daily aggregates have no automatic expiry. Issue aggregates are cleared after 90 days as requests arrive. |
| Your privacy choice (in your browser) | 180 days from the explicit decision, unless cleared earlier by the browser |
| Cloudflare request and security logs | Subject to Cloudflare's services and account settings; no fixed log retention period is specified here. |
| Google Analytics data | Subject to Google's policies and the Analytics account settings; this policy does not specify an account-level retention period. |
| Data collected by Google Ads, Meta, LinkedIn and RB2B | Subject to each company's policies and account settings. Withdrawing Site consent does not delete information already received by those companies. Contact us about any identification results held by ThreadKore. |
| Records of privacy requests and how we handled them | May be retained to document the request and its handling and meet applicable legal requirements; no fixed period is specified here. |
Expiry or removal of analytics connections does not delete the underlying inquiry, correspondence, CRM records or all historical activity. Contact us to request deletion of information associated with you; applicable rights and verification are described below.
7. Your US state privacy rights
7.1 Who these rights apply to
Depending on where you live and whether a law applies to ThreadKore and the information involved, you may have rights under California or other US state privacy laws. Coverage and exceptions vary; business-to-business information is covered by some laws but excluded by others. The description below does not mean that every state privacy law applies to ThreadKore or every visitor.
7.2 Your rights
Depending on applicable law and its exceptions, your rights may include:
- Know and access: ask what personal information we have collected about you, where it came from, why we collected it and who we disclosed it to, and get a copy.
- Correct: ask us to fix inaccurate personal information.
- Delete: ask us to delete personal information we collected from you.
- Portability: get your information in a usable format.
- Opt out of sale, sharing and targeted advertising: see 7.3.
- Limit certain uses of sensitive personal information: we do not ask for sensitive information in the contact form. Third-party identification can derive location information as described in section 2.2; keep Advertising off to prevent those tags from loading.
- Opt out of profiling for decisions with legal or similarly significant effects: we don't do this.
- Appeal: if you live in a state that provides this right and we decline your request, you can appeal (see 8.4).
Any visitor can contact us with a privacy question or request. The Site's optional tracking controls are available regardless of where you live.
7.3 Do Not Sell or Share My Personal Information
You can opt out of the "sale" or "sharing" of your personal information, and of targeted advertising, in any of these ways:
- Privacy choices panel: click "Your Privacy Choices" at the bottom of any page, turn off Advertising and business visitor identification and save, or click "Essential only." Advertising is off unless you turn it on.
- Global Privacy Control (GPC): if your browser or extension sends a GPC signal, we treat it as a valid request to opt out of the sale and sharing of your personal information, and of targeted advertising, for that browser. We keep the Advertising category off, so Google Ads, Meta, LinkedIn and RB2B tags do not load, and the panel shows that your GPC signal was honored. If GPC conflicts with an earlier choice to turn advertising on, GPC wins in that browser. To learn more, visit globalprivacycontrol.org.
- Email or phone: contact us using section 8. We will apply the opt-out to any information tied to you that we can identify.
Our site also keeps optional analytics off when a GPC or Do Not Track preference is active.
Opt-outs set in the panel or by GPC apply to the browser and device you use. If you use another browser or device, or clear your browser storage, set your choice again.
7.4 Categories in the current Site implementation
| Category (CCPA) | Examples | Source | Business purpose | Disclosed to | Sold or shared? |
|---|---|---|---|---|---|
| Identifiers | Name, work email, phone, IP address, cookie and online IDs; business contacts potentially matched by RB2B | You; your browser; Cloudflare; RB2B and its sources (advertising consent) | Responding to inquiries, Site operations and security, analytics, advertising and business visitor identification (with consent) | Operational providers; Google, Meta, LinkedIn and RB2B (with applicable consent) | Advertising disclosures are treated as potential sale/sharing. Form contents are not sent by the Site's tracking code. RB2B may independently match names, emails and profiles. |
| Professional or employment-related information | Company, role, builder type, annual closings; business/company details potentially matched by RB2B | You; RB2B and its sources (advertising consent) | Responding to inquiries, tailoring demos; business visitor identification (advertising consent) | Operational providers; RB2B supplies matched information | Form contents are not sent by the Site's tracking code. RB2B identification is included in the Advertising opt-out. |
| Internet or other electronic activity | Pages viewed, clicks, scroll depth, performance | Your browser (with consent) | Analytics, ad measurement, business visitor identification | Operational providers; Google; Meta, LinkedIn and RB2B (advertising consent) | Advertising disclosures are treated as potential sale/sharing. |
| Network-derived geolocation | First-party country, region and city estimates; third-party identification may include coordinates and postal codes as described in section 2.2 | Cloudflare (with analytics consent); ad, analytics and identification partners | Analytics, ad measurement, business visitor identification | Operational providers; Google, Meta, LinkedIn and RB2B (with applicable consent) | Advertising disclosures are treated as potential sale/sharing where tags derive location from your IP address. |
| Communications | Your message and email correspondence | You | Responding to inquiries | Operational providers | The Site does not send message contents to tracking tags. |
The contact form does not ask for sensitive personal information, and the Site does not offer a financial-incentive program for providing personal information.
This table describes the current Site, including RB2B. It is not a record of company-wide disclosures over the preceding 12 months. Contact us to request information about disclosures relating to you.
8. How to submit a request and how we verify it
8.1 How to submit a request
- Email: support@threadkore.com
- Phone (toll-free): 855-954-KORE (855-954-5673)
- Mail: ThreadKore, LLC, Attn: Privacy, 2520 Northwinds Parkway, Suite 300, Alpharetta, GA 30009
Please tell us what you are asking for, your name, and the email address or other details you used with us.
8.2 How we verify your identity
To protect your information, we need to confirm a request comes from you before we act on it. We will:
- Match the details you give us against the information we hold. Usually this means confirming your email address by sending you a message there.
- Ask for more information only if needed. For requests for specific pieces of information or for deletion, that may include more details that match our records.
- Use any information you give us for verification only for that purpose.
You don't need to verify your identity to opt out of sale or sharing.
With analytics permission, internal references can connect consented activity to a submitted self-reported email, but neither that connection nor a browser cookie verifies your identity. RB2B identification results may also contain named business contacts. If we can't verify that particular data belongs to you, we will tell you, and you can still use the privacy choices panel or GPC to control future tracking.
8.3 Response timing
Response deadlines depend on the law that applies to your request. We will respond within the applicable legal period and explain any permitted extension. You can stop future optional tracking in your browser immediately through the privacy choices panel, without waiting for an email response.
8.4 Appeals
If we decline your request, in whole or in part, we will explain why. If your state provides a right to appeal, you can appeal by replying to our decision or emailing support@threadkore.com with "Privacy Appeal" in the subject line. We will respond to appeals within the time required by your state's law. If you are not satisfied, you may contact your state attorney general.
9. Authorized agents
You can use an authorized agent to make a request for you. We will ask the agent for proof that you gave them permission, such as written permission you signed, or a valid power of attorney. Unless the agent has a power of attorney, we may also ask you to verify your identity directly with us or confirm that you authorized the agent. We may deny a request from an agent who can't provide proof.
10. Non-discrimination
We will not discriminate against you for exercising your privacy rights. We won't deny you our services, charge you a different price or give you a lower quality of service because you made a request. Choosing not to allow analytics or advertising has no effect on the contact form or any other part of the Site.
11. Security
The Site uses encrypted (HTTPS) connections, Cloudflare hosting and security services, and inquiry-form safeguards including spam filtering, session checks and rate limits. Inquiry records are not published on the Site.
No website or system is completely secure, and we can't guarantee the security of information sent to us online. If you think your information has been put at risk, contact us right away.
12. Children's privacy
The Site is a business-to-business website. It is not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child under 16 has given us personal information, contact us and we will review the request and take appropriate steps to delete it. We do not operate a parental-verification system.
13. Marketing communications and unsubscribing
When you submit the contact form, you agree that ThreadKore may contact you about your inquiry. We will use your details to respond, set up a demo and follow up on that conversation.
The form's required checkbox is permission to contact you about your inquiry, not a separate newsletter or marketing-text subscription. The Site does not automatically enroll inquiries in a marketing email list, send marketing email or text campaigns, or initiate calls.
To ask us to stop promotional contact or to ask about communications you have received, email support@threadkore.com. If a message provides an unsubscribe option, you can also use that option. Messages needed for an active inquiry or business relationship may be separate from promotional communications.
Your phone number is optional. The Site has no separate consent form for marketing texts or autodialed or prerecorded marketing calls.
Mobile Information and SMS Consent
When a mobile telephone number is provided to ThreadKore and consent is given to receive text messages, ThreadKore may use that mobile number to provide communications associated with inquiries, accounts, services, appointments, support requests, product or service information, and other communications for which consent has been provided.
ThreadKore does not sell, rent, share, or otherwise provide mobile phone numbers, SMS/MMS opt-in information, or messaging consent data to third parties or affiliates for their marketing or promotional purposes.
Mobile information may be provided to service providers, such as telecommunications and technology providers, solely as necessary to deliver and support ThreadKore's messaging services. These service providers may use the information only to provide services on behalf of ThreadKore and not for their own marketing or promotional purposes.
Mobile information may also be disclosed when required by law, regulation, legal process, or governmental request, or when reasonably necessary to prevent fraud, protect security, or protect the rights and safety of ThreadKore, its users, or others.
SMS/MMS consent is specific to the person providing the consent, the mobile number provided, ThreadKore as the sender, and the types of communications described when consent is obtained. Consent to receive messages from another company or organization does not constitute consent to receive text messages from ThreadKore.
SMS/MMS Messaging
Individuals who separately opt in to the ThreadKore Messaging Program may receive SMS and/or MMS messages from ThreadKore. Messages may include communications regarding inquiries, appointments, account activity, services, customer support, product information, and other communications associated with the individual's relationship or prospective relationship with ThreadKore. Marketing or promotional messages may be sent only when the appropriate consent for those communications has been obtained.
Message frequency varies depending on account activity, inquiries, services, and communication needs.
Message and data rates may apply.
Consent to receive text messages is optional and is not a condition of purchasing products or services from ThreadKore.
To stop receiving text messages from ThreadKore, reply STOP to a message. Additional opt-out keywords supported by the messaging provider may also be recognized. After an opt-out request is processed, no additional messages will be sent to that mobile number through the applicable messaging program unless the individual subsequently provides valid consent to receive messages again.
For assistance with text messaging, reply HELP or contact ThreadKore using the customer support information provided below.
SMS/MMS Data Security
ThreadKore takes reasonable administrative, technical, and organizational measures designed to protect personal information, including mobile telephone numbers, message content, and messaging consent information, from unauthorized access, disclosure, alteration, or destruction.
Communications transmitted through telecommunications networks and third-party service providers are also subject to the security and privacy practices of those providers.
Messaging Contact Information
If you have any questions, concerns, or comments about our terms and conditions and/or privacy policy you may contact us during normal business hours.
For questions or assistance related to the ThreadKore Messaging Program, contact:
ThreadKore
Email: support@threadkore.com
Phone: 855-954-KORE
Website: https://threadkore.com
14. International visitors
ThreadKore is based in the United States. If you visit from outside the US, your information may be processed in the United States and other countries where the providers described in this policy operate. Data protection laws may differ from those where you live. Contact us with questions about handling your information across borders or rights available where you live. Visiting the Site does not waive rights that apply to you.
15. Changes to this policy
We may update this policy from time to time. We will post the new version on this page and change the "Last updated" date at the top. If we make material changes, such as using personal information in a significantly new way, we will give more prominent notice, such as a notice on the Site or a new privacy choices prompt. We will ask for your consent where the law requires it.
16. Contact us
ThreadKore, LLC
Attn: Privacy
2520 Northwinds Parkway, Suite 300
Alpharetta, GA 30009
Phone: 855-954-KORE (855-954-5673)
Email: support@threadkore.com
Website: www.threadkore.com