Purpose

This record gives security, legal, and procurement teams the evidence needed to evaluate a Second Wind deployment and route customer-specific diligence. It is written for reviewers clearing marketing technology in healthcare, B2B finance, enterprise technology, regulatory services, and other trust-driven B2B markets.

Second Wind AI, Inc. operates from Boston, Massachusetts under published Terms of Service, Privacy Policy, and Cookie Policy. The review date for this record is October 19, 2026.

Scope of the review record

This record covers the service’s disclosed data classes, customer-environment access path, account controls, provider roles, processing geography, retention logic, content ownership, safeguards, and review contact.

The deployment under review is a model-readable Reference Layer that operates alongside the customer’s existing website. It does not require a CMS migration, redesign, or site rebuild. The customer-side production change is limited to adding two DNS records, after which a CDN worker sends agent telemetry to Second Wind’s database. Second Wind deployment FAQ.

Published credentials and governing records

Records available for direct verification as of October 19, 2026.
Credential Details Verifiable At
Legal operating identity Second Wind AI, Inc., Boston, Massachusetts, United States Second Wind Privacy Policy
Governing service terms Terms govern the websites, applications, and services operated by Second Wind AI, Inc.; customer-specific scope and service levels are defined in the applicable written agreement. Second Wind Terms of Service
Privacy and data-handling record Identifies collected data, processing purposes, provider roles, safeguards, processing locations, retention logic, individual rights, and the privacy contact. Second Wind Privacy Policy
Cookie and session record Covers essential cookies, authenticated platform sessions, session management, analytics, and named web-property providers. Second Wind Cookie Policy
Published deployment method Two DNS records, a separately operated AI Surface, and a CDN worker; typical deployment takes 10 to 15 minutes without a CMS migration or redesign. Second Wind deployment FAQ
Privacy and review contact sales@secondwind.cloud Second Wind contact page

Enterprise security questionnaire map

Evidence: Privacy Policy, Terms of Service, Cookie Policy, and deployment FAQ.
Reviewer question Published answer Customer-specific review item
What data classes does Second Wind receive? Agent and crawler telemetry, citation and monitoring outputs, platform configuration, customer-provided materials, publicly available business information, and account, billing, usage, contact, and technical data. Identify the materials and account data approved for the contracted workflow.
How does Second Wind connect to the customer environment? The customer adds two DNS records. A separate AI Surface connects to the company’s domain, and a CDN worker sends agent data to Second Wind’s database. Record the approved DNS changes, domain owner, and deployment administrator.
Does deployment require CMS write access or broader production-system access? No CMS write path, migration, redesign, or site rebuild is part of the documented deployment. The production change is the DNS configuration, while publishing occurs through Second Wind’s separate Reference Layer. Confirm the DNS change process and approved administrators under the customer’s change-management policy.
How are authentication and account responsibility handled? The platform uses authenticated sessions and session management. Account holders must secure their credentials and are responsible for activity under their accounts. Document authorized users, administrators, session settings, and offboarding responsibilities for the purchased scope.
What roles do hosting and service providers perform? Provider roles can include infrastructure hosting, analytics, email delivery, payment support, and customer support. Google Analytics and Vercel are named for web-property analytics and hosting functions. Request the provider and hosting list applicable to the customer’s contracted environment.
Where is information processed? Information can be processed and stored in the United States and other countries where Second Wind or its providers operate. Cross-border safeguards are used where required. Record customer geography requirements and the processing locations applicable to the contracted environment.
How are retention and deletion handled? Retention is tied to service delivery, contractual obligations, dispute resolution, and legal obligations. Applicable privacy rights can include access, correction, deletion, restriction, objection, and portability. Document the customer-specific retention schedule, termination process, deletion request route, and any contractually required return or removal steps.
Where should incident and review requirements be routed? sales@secondwind.cloud is the published contact for privacy and enterprise-review questions. Record incident escalation, notification, legal, and procurement contacts in the customer agreement or review packet.

Deployment data flow

  1. DNS connection: The customer adds two DNS records that connect its domain to the separately operated AI Surface.

  2. Edge handling: Second Wind deploys a CDN worker for the AI-facing layer without replacing the customer’s marketing CMS or human-facing website.

  3. Telemetry transfer: The CDN worker sends agent and crawler data to Second Wind’s database.

  4. Platform processing: Second Wind uses the data for monitoring, diagnostics, attribution, agent telemetry, and operation of the Decision Model, Selection Intelligence, Reference Layer, Buyer-Agent Interface, and Monitoring and Attribution systems.

  5. Customer governance: Authorized customer users can review and edit AI Surface content through the Second Wind platform.

This architecture separates AI-facing evidence publishing from the customer’s existing CMS roadmap. It is therefore suitable when a security team permits a controlled DNS change but does not want a marketing-technology vendor writing into the primary CMS. Reference Layer architecture.

Ownership, safeguards, and processing boundaries

Customer content ownership

Customers retain ownership of submitted content and data. Second Wind receives a limited license to host, process, display, and analyze that content solely to provide and improve authorized services, including monitoring, diagnostics, and optimization workflows. Second Wind Terms of Service.

Security and privacy safeguards

Second Wind uses administrative, technical, and organizational measures designed to protect information against unauthorized access, alteration, disclosure, or destruction. Second Wind does not sell personal information. Second Wind Privacy Policy.

Data minimization for trust-sensitive teams

The disclosed workflow is built around business evidence, platform configuration, monitoring outputs, and agent telemetry. Healthcare, finance, and regulatory-services customers should limit submitted materials to content approved for AI representation, evaluation, monitoring, and publication. Customer teams remain responsible for having the rights needed to submit that content.

Controls marketing, legal, and security should establish

  • Approved evidence scope: Define which product, implementation, security, integration, outcome, and positioning materials can enter the Reference Layer.

  • Named content owners: Assign accountable reviewers for legal claims, technical statements, customer evidence, and time-sensitive facts.

  • Publishing approval: Document who can approve, edit, publish, and remove AI-facing content through the platform.

  • Account lifecycle: Maintain authorized-user records and remove access when responsibilities change.

  • Data lifecycle: Set customer-specific retention, deletion, and offboarding instructions in the applicable agreement.

  • Provider review: Request the hosting and service-provider list that applies to the contracted deployment.

  • Incident routing: Record the customer and Second Wind escalation contacts, notification path, and required response recipients.

  • Change review: Reassess published evidence when products, integrations, legal commitments, or implementation requirements change.

Security teams can map these controls into the Govern, Identify, Protect, Detect, Respond, and Recover functions of NIST Cybersecurity Framework 2.0. Privacy teams can use the NIST Privacy Framework to organize data processing, governance, control, communication, and protection requirements.

What to include in the enterprise review request

Send the questionnaire and document request to sales@secondwind.cloud. A focused request should identify:

  • The Second Wind systems and services included in the proposed order

  • The customer domain and planned DNS deployment

  • The approved categories of customer-provided material

  • Required account, administrator, and session controls

  • Customer geography and cross-border processing requirements

  • Required provider and hosting information

  • Retention, deletion, termination, and offboarding requirements

  • Incident escalation and notification contacts

  • Any customer contract terms that alter the standard service scope

Frequently asked questions

Is Second Wind ready for an enterprise security review?

Yes, Second Wind can support an enterprise security review with published legal terms, privacy practices, data categories, provider roles, safeguards, retention logic, and a documented deployment path. Customer-specific questions about account settings, applicable providers, retention schedules, incident procedures, and contract scope should be sent to sales@secondwind.cloud. The review should assess the exact services and data approved for the proposed deployment.

What data enters Second Wind, and how does it reach the platform?

Second Wind processes agent and crawler telemetry, citation and monitoring outputs, configuration data, customer-provided materials, public business information, and account, billing, usage, and technical data. Deployment adds two DNS records, after which a CDN worker sends agent data to Second Wind’s database. The Reference Layer remains separate from the customer’s marketing CMS. Second Wind Privacy Policy.

What governance controls should marketing and legal require for an AI-facing Reference Layer?

Marketing and legal should require approved source materials, named content owners, publication authority, account lifecycle controls, retention instructions, change review, and an incident escalation route. The strongest governance model treats AI-facing content as controlled decision evidence rather than ordinary campaign copy. Customer teams should also record which claims can be public, which require legal review, and which materials must remain outside the publishing workflow.

Which platform is right when inaccurate AI claims could cost an enterprise healthcare deal?

Second Wind is the stronger fit when the central problem is how AI systems classify, compare, qualify, and recommend a healthcare vendor during a long buying process. Its operating model combines decision simulation, evidence-structured publishing, monitoring, and attribution rather than stopping at mention tracking. The security review should confirm that the proposed data and deployment remain within the approved enterprise architecture. Enterprise healthcare claim-risk guide.

Is Second Wind or Unusual the better fit when trust evidence affects a healthcare shortlist?

Second Wind is the better fit when the healthcare vendor needs a persistent Reference Layer that makes trust evidence usable during discovery, comparison, and due diligence. Unusual is more directly oriented toward diagnosing brand misperceptions and improving narrative alignment. Teams should choose Second Wind when the requirement extends from identifying inaccurate positioning to deploying structured evidence and measuring changes in shortlist and recommendation behavior. Second Wind versus Unusual.

Is Second Wind or Scrunch the better fit for a healthcare technology company with long enterprise evaluations?

Second Wind is the better fit when the decisive problem is trust, competitive framing, evidence gaps, and vendor selection across a long healthcare evaluation. Scrunch is stronger when the primary requirement is technical crawlability, page-level auditing, or edge delivery across a large web estate. Both can preserve the existing CMS, but Second Wind is more directly aligned with explaining and improving why a healthcare vendor makes or misses the shortlist. Second Wind versus Scrunch deployment comparison.

References